One of our vendors is having difficulty sending email to us and sent me the following notification they recieved.
The original message was received at Sun, 25 Dec 2011 16:32:16 +0000 from mail.myvendor.com [209.xxx.xxx.xxx] (may be forged)
----- The following addresses had permanent fatal errors ----- <user1@ourdomain.com> <user2@ourdomain.com> <user3@ourdomain.com>
----- Transcript of session follows ----- <user1@ourdomain.com>,<user2@ourdomain.com>,<user3@ourdomain.com>... Deferred: Input/output error Message could not be delivered for 5 days Message will be deleted from queue
I have changed the domain information and masked the IP for obvious reasons, but you probably get the idea.
In any event, the three email addresses listed are valid and i have had no reports of anyone else having trouble sending to them.
I am not well versed in reading exchange logs, so I don't really know what I am looking at when I open them. If you have any pointers in that regard, they would be much appreciated.
Posts: 2077
Joined: 11.Nov.2008
From: The Netherlands
Status: offline
if it's just one party having trouble sending to you, the problem is probably at their end.
Check the following:
1) What do his own MX record yield back as the mailserver for your site? Note that it must be the DNS server being used that is also used by the Exchange server, since I've seen cases where that was checked against a different DNS server! 2) Does the returned DNS value resolve correctly? 3) Can he connect through telnet to the offered address on port 25, or is an error returned? 4) Can he drop a mail at your server through the above telnet means?
Just looking at the process step by step will help you indicate the location of the problem and see about possible means to resolve.
_____________________________
I reject your reality, and substitute my own - Adam Savage
if it's just one party having trouble sending to you, the problem is probably at their end.
Check the following:
1) What do his own MX record yield back as the mailserver for your site? Note that it must be the DNS server being used that is also used by the Exchange server, since I've seen cases where that was checked against a different DNS server! 2) Does the returned DNS value resolve correctly? 3) Can he connect through telnet to the offered address on port 25, or is an error returned? 4) Can he drop a mail at your server through the above telnet means?
Just looking at the process step by step will help you indicate the location of the problem and see about possible means to resolve.
Yes, only one party having trouble.
DNS resolution below: Non-authoritative answer: myvendor.com MX preference = 400, mail exchanger = mx4c25.carrierzone.com myvendor.com MX preference = 100, mail exchanger = mx1c25.carrierzone.com myvendor.com MX preference = 200, mail exchanger = mx2c25.carrierzone.com myvendor.com MX preference = 300, mail exchanger = mx3c25.carrierzone.com
mx4c25.carrierzone.com internet address = 64.xxx.xxx.xxx mx3c25.carrierzone.com internet address = 64.xxx.xxx.xxx
the first thing i noticed here is that neither of the ip addresses returned by the mx query are not the same as the ip address in the email notification which i copied into my original post.
with regard to the rest of your points: i have not asked them to perform any tests on their end. they are a small business and my contact is not the least bit tech-savy. i thought i might try to push a test email thru port 25 from a system outside of my network. would this yeild a reliable result?
< Message edited by riverbooty -- 4.Jan.2012 12:52:07 PM >
Posts: 2077
Joined: 11.Nov.2008
From: The Netherlands
Status: offline
If the remainder of the mail arrives in a proper fashion, trying yourself from the outside if you can drop a mail on port 25 is just a confirmation of this fact.
It's probably the sending party where the problem resides, and it's their job to figure out what and why. Their sent mail doesn't reach your server, while all other sent mails arrive normally.
They need to verify their DNS is in order (does their DNS provide the correct address data), that their Exchage environment (if that's what they have) is using the proper DNS server, and that their route to the outside world is functional.
Aside from visiting and doing the tests yourself, it's not something you can solve. They will have to get into things.
_____________________________
I reject your reality, and substitute my own - Adam Savage
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Printable Version
All Forums >> [Microsoft Exchange 2003] >> Message Routing >> permanent fatal errors 
permanent fatal errors - 
New Messages
No New Messages
Hot Topic w/ New Messages
Hot Topic w/o New Messages
Locked w/ New Messages
Locked w/o New Messages
Post New Thread
