SMTP Forgot Login

This E-mail and any attachments thereto is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. Dissemination, distribution or copying of this E-mail or the information herein by anyone other than the intended recipient, or an employee or agent responsible for delivering the message to the intended recipient, is prohibited. If you receive this E-mail in error please immediately notify me at 212-903-9600 and permanently destroy the original E-mail message, all copies, and any printout thereof.

[V.2007.0809.CARNEGIE.HALL.CORPORATION]

FYI... Tak's directions will only work if the api server is a member of the domain.  If it isn't you need to set up a new receive connector specifically for the servers that you want to allow to relay.  I can email you directions for that if that is your scenario.

-Rich

Our exhange serve is in our domain. So that shouldn't be an issue.

Hi David,

Good day.

Unable to relay when using Exchange 2007 as SMTP server

http://social.technet.microsoft.com/Forums/en-US/exchangesvrtransport/thread/a719cf6f-0481-414f-bee2-f563c3c685ed

 Unable to relay when using Exchange 2007 as SMTP server : Microsoft Exchange

http://objectmix.com/microsoft-exchange/751733-unable-relay-when-using-exchange-2007-smtp-server.html

have fun.

Ben

What do you see in the logs on the exchange server?

I thought about this some more last night and I think I know what your problem is.  The web api runs as the web account user which is a local user.  This user most likely cannot authenticate to the exchange server.  When you ran the telnet tests you were running them as a domain user and that is why you were able to test it OK.  I am including my directions below.  Give them a try and let me know if they work.  I am attaching them without images.  if you feel that the screen caps would help let me know and I can email them to you off list.

-Rich

Before you start this… Heed this warning.  If you make a mistake on the allow range you will open your server up to external relaying.  Even completely open internal relaying is not a good idea to allow.  Use these directions with caution.

To allow relaying off your e2k7 box:

From the Management Console:

1.       Go to Microsoft  Exchange > Server Configuration > Hub Transport

2.       If you have more than one Hub transport server make sure you pick the one you want to enable relaying on from the top.

3.       Right click on the Receive Connectors box at the bottom and choose “New Receive Connector”

4.       Call the connector whatever you would like (I will call it relaying).  Leave the intended use as Custom.

5.       Click Next.  If you need to modify the IP addresses you want to listen for the relay on do it here. 

6.       On the next screen you need to add all of the sources that you want to add relaying to.  This is my sandbox server so I am going to add my entire internal domain.  You probably only want to add the IP’s of your sending servers.  Make sure you remove the default range 0.0.0.0-255.255.255.255.

7.       Click through the rest to finish creating the connector.  Once it is created right click on it and pick properties.

8.       In the properties dialogue box go to the Permission groups tab and choose Exchange Servers and then go to theAuthentication Tab and turn on Externally Secured and Transport layer Security.

You should now be able to relay from any of the source server that you specified.

I thought about this some more last night and I think I know what your problem is.  The web api runs as the web account user which is a local user.  This user most likely cannot authenticate to the exchange server.  When you ran the telnet tests you were running them as a domain user and that is why you were able to test it OK.  I am including my directions below.  Give them a try and let me know if they work.  I am attaching them without images.  if you feel that the screen caps would help let me know and I can email them to you off list.

-Rich

Before you start this… Heed this warning.  If you make a mistake on the allow range you will open your server up to external relaying.  Even completely open internal relaying is not a good idea to allow.  Use these directions with caution.

To allow relaying off your e2k7 box:

From the Management Console:

1.       Go to Microsoft  Exchange > Server Configuration > Hub Transport

2.       If you have more than one Hub transport server make sure you pick the one you want to enable relaying on from the top.

3.       Right click on the Receive Connectors box at the bottom and choose “New Receive Connector”

4.       Call the connector whatever you would like (I will call it relaying).  Leave the intended use as Custom.

5.       Click Next.  If you need to modify the IP addresses you want to listen for the relay on do it here. 

6.       On the next screen you need to add all of the sources that you want to add relaying to.  This is my sandbox server so I am going to add my entire internal domain.  You probably only want to add the IP’s of your sending servers.  Make sure you remove the default range 0.0.0.0-255.255.255.255.

7.       Click through the rest to finish creating the connector.  Once it is created right click on it and pick properties.

8.       In the properties dialogue box go to the Permission groups tab and choose Exchange Servers and then go to theAuthentication Tab and turn on Externally Secured and Transport layer Security.

You should now be able to relay from any of the source server that you specified.

Hi Rich,

We have gone through the set up of the receive connector. We even get the recipient ok when we do the telnet test of the connector from the API server. However we still get the relay failed notice if I am on a packert sniffer watching the API try to send the forgot login. It works everytime with internal email as the recipient.  It seems like some kind of authentication issue. Weird.

We have only one Hub Transport server.

Thanks for your suggestion. Much Appreciated.