550 5.7.1 Unable to relay

[kmcallister]

I just installed an accounting package that allows the accounting department to send out PO via emails. Using Outlook, my users are able to send and receive email fine. They are able to send PO to users within the domain but they are not able to send POs to anyone outside of the abcxyz.com domain. Is there anyway to enable this functionality and not open my system to relays.

Kamtek

 

[jimw32]

Can you be a little more specific. when you sya users are trying to send out P.O's out are they sending them out from this new program. If so does this new program run from it's own server ?

 

[kmcallister]

Sorry about that. The users are logging into the app server and from within the accounting application there is a setting to an your email server (which is local) I entered xxx.xxx.xxx.xxx port 25 within the accounting app. The user will then open a PO and their option is to print, fax or email. They select the email option and enter the email address, hit send and within 30 sec. it bounces back with the unable to relay error. If they were to type in a local user email address, the message gets sent successfully.

Kamtek

 

[Davetoo]

You have to add the IP of the app server in your "allow the list below to relay" on your Exchange server's SM.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[kmcallister]

What if the app server is the same as the email server. They are both running on the same machine.

Kamtek

 

[Davetoo]

Add it.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[kmcallister]

I added the IP to the allow ro relay list. Restarted all Exchange services and still not able to send email out using the app.

Kamtek

 

[Davetoo]

Do you have the latest service pack for Exchange installed? Also, have you tried it for recipients at different companys?

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[kmcallister]

Yes to both of your questions.

 

[Davetoo]

Hmmmm...can you post the exact return message (minus specific ip's of course)?

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[kmcallister]

550 5.7.1 unable to relay for janedoe@microsoft.com

 

[Davetoo]

That's the entire message?

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[jimw32]

Take a look at this

http://support.microsoft.com/default.aspx?scid=kb;en-us;q289553

 

[xmsre]

By default, authenticated users can relay; anything else can't. When the user sends the message via outlook, they are an authenticated user. The third party app is not an authenticated user, so this behavior is expected. On the relay restrictions tab, you'll have to allow the IP address of the app server to relay.

 

[Davetoo]

He already did that xmsre, 7th post.

I'm Certifiable, not certified.
It just means my answers are from experience, not a book.

 

[xmsre]

Looks liek they already allow it to relay. Let's see...

"They are able to send PO to users within the domain but they are not able to send POs to anyone outside of the abcxyz.com domain. Is there anyway to enable this functionality and not open my system to relays."


"If they were to type in a local user email address, the message gets sent successfully."

I think jimw32 was on the right track. In order to accept for a domain, you have to have a recipient policy for the domain even if it has no filter. It could also depend on how the application is written. Is it doing an LDAP lookup of the recipient? What happens if...:

1. Create a contact for the user in the failed domain.
2. When sending mail, send to the contact, faileduser@abcxyz.com.
3. Does it go?

 

[kmcallister]

I'm not sure I understand what you want me to do.

 

[buztwet]

kmcallister, I'm having this same type problem with our database application. We're running nat so I've tried allowing my workstation ip and I've tried allowing the app server ip and neither will allow the mail to go through. I've even tried sending the email from the client app on the app server and that doesn't work either. I turned on allow users who authenticate and that allowed for open relay so I shut that off quick. Right now I am just allowing relaying from my app server ip. What type of diagnostic logging should I turn on to see what's happening when the message gets to the exchange server?

 

[kmcallister]

Not sure about the diagnostic logging. I would receive an error message within seconds of submitting the request to email.

 

[buztwet]

My database software says that the e-mail message sent, but that the server returned the two messages sent out to the internet as invalid. It does send the internal message.