We recently switched from GoDaddy POP mail to an internal Exchange 2007 server. Everything has been running smoothly, except for one problem that crops up every once in a while. Let's say that I (me@domain.com) send an email to my friend (him@remote.com). Every once in a while, I get a failure on our Exchange server and I receive the following email, from our Exchange server: Generating server: exchange.domain.com him@remote.com server.remote.com #550-Verification failed for 550-The mail server could not deliver mail to me@domain.com. The account or domain may not exist, they may be blacklisted, or missing the proper dns entries. 550 Sender verify failed # # What's confusing me is the 'could not deliver mail to me@domain.com' part, since this is an email I sent out. Any ideas on this one?
You should verify you have a Reverse DNS record setup that points to your external IP address that your exchange server uses. You may also want to consider setting up a SPF DNS record. -- Richard Rodgers M3 PostMasters M3PostMasters@nospam.m3tg.com M3 Technology Group www.m3postmasters.com wrote in message news:602d5aa0-3df1-4ddf-9f59-aafdae44f5e5@p73g2000hsd.googlegroups.com... > We recently switched from GoDaddy POP mail to an internal Exchange > 2007 server. Everything has been running smoothly, except for one > problem that crops up every once in a while. > > Let's say that I (me@domain.com) send an email to my friend > (him@remote.com). Every once in a while, I get a failure on our > Exchange server and I receive the following email, from our Exchange > server: > > > Generating server: exchange.domain.com > > him@remote.com > server.remote.com #550-Verification failed for 550-The > mail server could not deliver mail to me@domain.com. The account or > domain may not exist, they may be blacklisted, or missing the proper > dns entries. 550 Sender verify failed # # > > > What's confusing me is the 'could not deliver mail to me@domain.com' > part, since this is an email I sent out. > > Any ideas on this one? >
