Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden using our free interactive tool and use it to determine the right price for your IT services. Start calculating Now!
#< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'EOF' (delivery attempts: 0)> #SMTP#
I had this question after viewing Exchange Message Reject 5.4.7.
People,
I've been told by my customer that they are getting this NDR: #< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'EOF' (delivery attempts: 0)> #SMTP# when sending email to one of the accepted email domain in my Exchange server.
What does it means and where does the email being hold up before it is expired and discarded?
There is another SmartHost (Virtual Appliance) VM that is running email hygiene check, but so far I did not find any error in the spam filter.
People,
I've been told by my customer that they are getting this NDR: #< #5.0.0 smtp; 5.4.7 - Delivery expired (message too old) 'EOF' (delivery attempts: 0)> #SMTP# when sending email to one of the accepted email domain in my Exchange server.
What does it means and where does the email being hold up before it is expired and discarded?
There is another SmartHost (Virtual Appliance) VM that is running email hygiene check, but so far I did not find any error in the spam filter.
Do more with
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
If I am reading your situation correctly this suggests that the SMTP server they use to send email to your Exchange server is unable to contact your server. The error is self explanatory in that their server has tried to contact your mail server repeatedly and after a preconfigured period hasn't been able to and expired the msg.
- Are the senders sending say via their ISP's SMTP server
- Have you changed IP addresses for your external gateway, looking to see if a DNS server has an old IP for your MX record
- Use something like DNS Checker.org to make sure your correct IP is replicated.
- Use MXToolbox to see what results are reported
- Do an NSLOOKUP from the customers site to see what IP the MX record has returned
Hi,
I do have MXToolbox premium access, but which test do I need to run ?
because my customer IT department insist that the problem is not on their own.
But upon digging through the Spam filter and also Exchange server, I cannot find the email logged in both systems.
I do have MXToolbox premium access, but which test do I need to run ?
because my customer IT department insist that the problem is not on their own.
But upon digging through the Spam filter and also Exchange server, I cannot find the email logged in both systems.
Check that your MX record is correct across the WWW.
What version of exchange are you running?
- Using MXToolbox just run a check of your domain choosing MX as the return type, see what it delivers
- Using DNSChecker, enter your domain name (not your MX ) and choose MX record and see that the IP/Domain details for your mx are the same across all DNS servers globally.
- Is your Internet connection congested? Some ISP's set the retries on delayed mail to 1 or 2 attempts rather than having their servers loaded with retieis for thousands of customers
What version of exchange are you running?
How did the Check DNS go?
Are you in a position to ask the clients IT team to do some DNS checks from their end, pointing out its mutually beneficial, and ask the to send you the results. If they will
Are you in a position to ask the clients IT team to do some DNS checks from their end, pointing out its mutually beneficial, and ask the to send you the results. If they will
- Ping the DNS name of your mailserver
- Do an NSLookup to see what it gets at their end
- Do a traceroute or pathping piped to a text file to see what hops they go thru - eg
- Pathping mail.mymailserver.com.yz > list.txt
Premium Content
You need an Expert Office subscription to comment.Start Free Trial