#5.7.0 smtp;530 5.7.0 Must issue a STARTTLS command first
Hi Experts,
A user tries to send an email to user@amgen.com and receives an NDR. I sent a test mail using user's mailbox and the external user confirms that he received that email. I've checked at my server end and we are not using TLS settings.
Below is the NDR:
From: System Administrator
Sent: Monday, February 09, 2009 8:39 AM
To: dcharest@amgen.com
Subject: Undeliverable: heavy rain
Your message did not reach some or all of the intended recipients.
Subject: heavy rain
Sent: 2/9/2009 8:39 AM
The following recipient(s) could not be reached:
dcharest@amgen.com on 2/9/2009 8:39 AM
The recipient could not be processed because it would violate the security policy in force
<Mailbox_server_name.test.
Environment: Exchange 2003+SP2.
Any help is highly appreciable.
A user tries to send an email to user@amgen.com and receives an NDR. I sent a test mail using user's mailbox and the external user confirms that he received that email. I've checked at my server end and we are not using TLS settings.
Below is the NDR:
From: System Administrator
Sent: Monday, February 09, 2009 8:39 AM
To: dcharest@amgen.com
Subject: Undeliverable: heavy rain
Your message did not reach some or all of the intended recipients.
Subject: heavy rain
Sent: 2/9/2009 8:39 AM
The following recipient(s) could not be reached:
dcharest@amgen.com on 2/9/2009 8:39 AM
The recipient could not be processed because it would violate the security policy in force
<Mailbox_server_name.test.
Environment: Exchange 2003+SP2.
Any help is highly appreciable.
ASKER
Thanks Sandeep, I'll go thru it right now...
If I saw that error I would put the blame on the recipient's side.
Exchange 2003 doesn't do opportunist TLS, it is either on or off. As long as you don't have an SMTP connector for that domain that is using TLS, the remote server for some reason has tried to use TLS.
-M
Exchange 2003 doesn't do opportunist TLS, it is either on or off. As long as you don't have an SMTP connector for that domain that is using TLS, the remote server for some reason has tried to use TLS.
-M
ASKER
Hi Guys,
We've a separate secured SMTP connector for that domain who is using TLS. I now understood that the problem is there at recipint's domain. But as this is an intermittent problem, so could you suggest me is it possible to trace their server configuration from our end? If I get the proof of the misconfiguration at recipient's domain, then it'll be easier for me to have a solid proof. OR what step do you suggest me to take after this?
Thank you so very much for your input.
Regards,
Anupam
We've a separate secured SMTP connector for that domain who is using TLS. I now understood that the problem is there at recipint's domain. But as this is an intermittent problem, so could you suggest me is it possible to trace their server configuration from our end? If I get the proof of the misconfiguration at recipient's domain, then it'll be easier for me to have a solid proof. OR what step do you suggest me to take after this?
Thank you so very much for your input.
Regards,
Anupam
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Hi Mestha,
"If you have a connector for that domain that wants to use TLS, then every server that receives email for that domain must support TLS."
I may sound STUPID, but stll dying to know How I can come to know that a particular Exchange server is supporting TLS?
Thanks,
Anupam
"If you have a connector for that domain that wants to use TLS, then every server that receives email for that domain must support TLS."
I may sound STUPID, but stll dying to know How I can come to know that a particular Exchange server is supporting TLS?
Thanks,
Anupam
You mean for inbound email?
When the you telnet to port 25 and issue a ehlo, one of the commands returned in the list should be STARTTLS.
-M
When the you telnet to port 25 and issue a ehlo, one of the commands returned in the list should be STARTTLS.
-M
http://support.microsoft.com/default.aspx/kb/329061