x13
asked on
MS Exchange 550 5.7.1 message does not comply?
We have one Windows SBS server that has MS Exchange 2003 on it. I set it up myself last year but sort of muddled through it. (I hadn't done it before and haven't since).
Recently the users have started getting the following error message:
"The following recipient could not be reached:
<email address>@<certain domain>.com on <date> <time>
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<our domainname>.com #5.7.1 smtp;550 5.7.1 m8AHVlq4008019 This message does not comply with required standards."
The message headers seem to indicate that the message never left our Exchange server (all the domains listed in the headers are ours).
The error ONLY occurs when replying or forwarding to any email to one specific domain (a local company). Removing the text "RE:" in the subject does not help. We have contacted them and they say the problem is not on their end (which the message headers seem to agree with). Problem has been occuirring for approximately one month. I cannot see anything stuck in the message queue in the Exchange System Manager.
Any assistance appreciated.
Recently the users have started getting the following error message:
"The following recipient could not be reached:
<email address>@<certain domain>.com on <date> <time>
You do not have permission to send to this recipient. For assistance, contact your system administrator.
<our domainname>.com #5.7.1 smtp;550 5.7.1 m8AHVlq4008019 This message does not comply with required standards."
The message headers seem to indicate that the message never left our Exchange server (all the domains listed in the headers are ours).
The error ONLY occurs when replying or forwarding to any email to one specific domain (a local company). Removing the text "RE:" in the subject does not help. We have contacted them and they say the problem is not on their end (which the message headers seem to agree with). Problem has been occuirring for approximately one month. I cannot see anything stuck in the message queue in the Exchange System Manager.
Any assistance appreciated.
This has to be getting rejected by the Recipients mail server, Please increase the NCSA logging on the SMTP virtual server of your exchange & you should see that the recipients server is rejecting the emails
ASKER
Okay I can get into the Exchange system manager and find the SMTP virtual server listed under Protocols. How do I increase the NCSA logging and where would I find the logs? Thanks.
Although I am pretty sure it is our server doing the rejecting. I have attached the e-mail headers of one of the bounce messages. You will note that the only domain listed is ours, and the X-MimeOLE header clearly states "Produced by Microsoft Exchange v6.5" (which our exchange is on the SBS server 2003, so do the versions match?"
I just have no idea how to go about finding and fixing the problem on Exchange. ????
Although I am pretty sure it is our server doing the rejecting. I have attached the e-mail headers of one of the bounce messages. You will note that the only domain listed is ours, and the X-MimeOLE header clearly states "Produced by Microsoft Exchange v6.5" (which our exchange is on the SBS server 2003, so do the versions match?"
I just have no idea how to go about finding and fixing the problem on Exchange. ????
ASKER
Well, I spent a long time typing everything into the code snippet box and now I can't see it. :-(
I will re-type it into this box now. Hopefully someone can help me. :(
[[[CODE]]]
Microsoft Mail Internet Headers Version 2.0
From: postmaster@ourdomain.com
To: localuser@ourdomain.com
Date: Mon, 15 Sep 2008 16:18:11 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu s;
boundary="9B095B5ADSN=_01C 8F3EF168C6 B760000044 4"
X-DSNContext: 7ce717b1 - 1194 - 00000002 - 00000000
Message-ID:
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01C8F3EF168 C6B7600000 444
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C8F3EF168 C6B7600000 444
Content-Type: message/delivery-status
--9B095B5ADSN=_01C8F3EF168 C6B7600000 444
Content-Type: message/rfc822
Subject: RE: Production start
Date: Mon, 15 Sep 2008 16:16:08 -0400
MIME-Version: 1.0
Content-Type: text/plain
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Message-ID: <6F69F6F56E925D4185450D7BB B867EE2025 9DD@SERVER NAME.ourdo main.local >
Content-Class: urn:content-classes:messag e
In-Reply-To: <6FA45EE2965545B08C855F514 D181A19@ou rdomain.lo cal>
X-MimeOLE: Produced by Microsoft Exchange v6.5
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Production start
thread-index: Acjz6Ww9hM16r6yEQr66i/jY4t NzaQAAHMEQ
References: <6FA45EE2965545B08C855F514 D181A19@ou rdomain.lo cal>
From: "Local User"
To:
--9B095B5ADSN=_01C8F3EF168 C6B7600000 444--
I will re-type it into this box now. Hopefully someone can help me. :(
[[[CODE]]]
Microsoft Mail Internet Headers Version 2.0
From: postmaster@ourdomain.com
To: localuser@ourdomain.com
Date: Mon, 15 Sep 2008 16:18:11 -0400
MIME-Version: 1.0
Content-Type: multipart/report; report-type=delivery-statu
boundary="9B095B5ADSN=_01C
X-DSNContext: 7ce717b1 - 1194 - 00000002 - 00000000
Message-ID:
Subject: Delivery Status Notification (Failure)
--9B095B5ADSN=_01C8F3EF168
Content-Type: text/plain; charset=unicode-1-1-utf-7
--9B095B5ADSN=_01C8F3EF168
Content-Type: message/delivery-status
--9B095B5ADSN=_01C8F3EF168
Content-Type: message/rfc822
Subject: RE: Production start
Date: Mon, 15 Sep 2008 16:16:08 -0400
MIME-Version: 1.0
Content-Type: text/plain
charset="iso-8859-1"
Content-Transfer-Encoding:
Message-ID: <6F69F6F56E925D4185450D7BB
Content-Class: urn:content-classes:messag
In-Reply-To: <6FA45EE2965545B08C855F514
X-MimeOLE: Produced by Microsoft Exchange v6.5
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: Production start
thread-index: Acjz6Ww9hM16r6yEQr66i/jY4t
References: <6FA45EE2965545B08C855F514
From: "Local User"
To:
--9B095B5ADSN=_01C8F3EF168
ASKER
Bump!
ASKER
This might help someone help me?
I found some logs on the Exchange Server (under Exchange System Manager, Message Tracking Center).
I was able to find the message that I posted above, here's what the server had to say about it
09/15/2008 16:16 SMTP Store Driver: Message submitted from store
09/15/2008 16:16 SMTP: Message submitted to advanced queuing
09/15/2008 16:16 SMTP: Started message submission to advanced queue
09/15/2008 16:16 SMTP: Message submitted to categorizer
09/15/2008 16:16 SMTP: Message categorized and queued for routing
09/15/2008 16:16 SMTP: Message routed and queued for remote delivery
09/15/2008 16:16 SMTP: Started outbound transfer of message
09/15/2008 16:16 SMTP: Non-delivered report (NDR) generated
Would the NDR have been generated by Exchange or by the remote SMTP server - at our ISP?
ANY help appreciated!!
I found some logs on the Exchange Server (under Exchange System Manager, Message Tracking Center).
I was able to find the message that I posted above, here's what the server had to say about it
09/15/2008 16:16 SMTP Store Driver: Message submitted from store
09/15/2008 16:16 SMTP: Message submitted to advanced queuing
09/15/2008 16:16 SMTP: Started message submission to advanced queue
09/15/2008 16:16 SMTP: Message submitted to categorizer
09/15/2008 16:16 SMTP: Message categorized and queued for routing
09/15/2008 16:16 SMTP: Message routed and queued for remote delivery
09/15/2008 16:16 SMTP: Started outbound transfer of message
09/15/2008 16:16 SMTP: Non-delivered report (NDR) generated
Would the NDR have been generated by Exchange or by the remote SMTP server - at our ISP?
ANY help appreciated!!
This looks like its being generated by your Exchange Server.
Can you try to reply it using OWA.. Are you still getting the same message..
Can you try to reply it using OWA.. Are you still getting the same message..
ASKER
I can try, what is OWA?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Just as an update... I am still trying to get an answer from our ISP and have messaged them again today. my emails and calls have thus far gone unanswered. However, I think that a solution would benefit more people as I found posts on Google with this problem but no solutions.