Local domain does not exist (even though it is there)

[spslater]

Everything seems to be configured properly but I get the following message:

2011-02-08T13:45:26: SMTP Server rejected recipient ghogan@Domain.local: Server rejected recipient (ghogan@Domain.local): 550 5.1.1 5ZlQ1g00J2zJKlB01ZlSU5 <domain.local> does not exist E3110

The only thing I can see is the fact that "Domain" is capitalized.  Is this program case sensitive?  It will not let me enter it under the general tab with a capital D.

The domain definitely exists (with a capital "D").  Users are able to send but incoming E-Mail results in the above message.

SBS/Exchange 2003.  Webhost changed from pop.domain.com to exchange.ispdomain.net so pop3 connector in exchange no longer works.

Client has been WITHOUT E-Mail for 2 days so this is a critical issue.

Thanks.

Shawn Slater

[Eclarsys Support]

Hello,

the message is being rejected from the SMTP Server for some reason. PopGrabber does not modify the messages and Exchange should not care if the domain has a capital D or not. However, in this case the message is being rejected by Exchange.

Please check your server logs to get more information about the error, and verify not only that the domain exists, but also that it is configured to accept messages. Finally, check that your DNS server resolves the local domain correctly.

Regards,

Eclarsys Support

[spslater]

No errors in the logs.  DNS Resolves.

E-Mail was working previously (this could be the problem) using the SMTP connector built in to Exchange 2003.  Could they be in conflict with each other?  I followed the complete instructions for installing and setting up Popgrabber.  Perhaps there is something else that needs to be turned off.

I have since learned that the SMTP connector in Exchange 2003 cannot handle SSL.  Any idea what must be turned off in Exchange to allow PopGrabber to act as the sole SMTP server? 

Thanks

[Eclarsys Support]

If you are using an SMTP connector, make sure it is configured to handle messages from the specified domain.

If you are only using the Virtual SMTP Server, make sure that no smart host is configured there. If you need a smart host, you must use an SMTP connector and leave the smart host empty in the virtual SMTP Server.

You can find more information about the required settings here:

http://www.msexchange.org/tutorials/Using_SMTP_Connector_Internally.html
http://technet.microsoft.com/en-us/library/aa996068%28EXCHG.65%29.aspx

PopGrabber is not an SMTP server, it is a service that relays the messages from an external POP3 server to the internal SMTP Server (Exchange), so the SMTP service in Exchange is still used for the delivery and reception of messages.

Regards,

Eclarsys Support