Comments on: Fixing Error 550 when sending to/from Google Apps email http://blog.boogly.net/2008/10/fixing-error-550-when-sending-tofrom-google-apps-email/ ...plus some Thu, 11 Mar 2010 08:39:09 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Andrew http://blog.boogly.net/2008/10/fixing-error-550-when-sending-tofrom-google-apps-email/comment-page-1/#comment-220 Andrew Tue, 02 Jun 2009 07:46:28 +0000 http://blog.boogly.net/?p=25#comment-220 Took me a while to understand what was going on when I had this problem, so I'll explain my situation and how it was resolved. It's pretty similar to above. 1. I migrated our site, "primary.com", to NewWebHost. 2. I migrated our email, "@primary.com", to NewWebHost. 3. I parked two other domains on the same account at NewWebHost, "other1.com" and "other2.com". I did not move the mail hosting for these domains to NewWebHost, however. When I set up domain parking for other1.com and other2.com, cPanel or some other mechanism at NewWebHost automatically added those domains to the "localdomains" context on the mail server. So, when emails to primary.com were being verified, the system was treating them as local mailboxes, rather than as boxes on external servers. The solution was for NewWebHost to manually move other1.com and other2.com to the "remotedomains" context. Took me a while to understand what was going on when I had this problem, so I’ll explain my situation and how it was resolved. It’s pretty similar to above.

1. I migrated our site, “primary.com”, to NewWebHost.
2. I migrated our email, “@primary.com”, to NewWebHost.
3. I parked two other domains on the same account at NewWebHost, “other1.com” and “other2.com”. I did not move the mail hosting for these domains to NewWebHost, however.

When I set up domain parking for other1.com and other2.com, cPanel or some other mechanism at NewWebHost automatically added those domains to the “localdomains” context on the mail server.

So, when emails to primary.com were being verified, the system was treating them as local mailboxes, rather than as boxes on external servers.

The solution was for NewWebHost to manually move other1.com and other2.com to the “remotedomains” context.

]]>