• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 306
  • Last Modified:

Problems with incoming email


Need help on this tricky problem.

Current setup:

- Email to domain XYZ.COM is first sent to an ISP that receives all email to this domain. Then their so called MailFeeder service sends all email (no filtering) to our mailserver which stands on local LAN with a firewall between.
- The mailserver is a Microsoft Exchange 2003 Server with Window Server 2003 Enterprise Server beneth. The server has Symantec Mail Security for Exchange as the primary virus and spam filtering software.


- Occasionally email sent to different recipients on our mailserver does not get thru. Senders get the following response:
(This response message is sent to the original sender from MAILER-DAEMON@nexus.tripnet.se, which is the ISPs mailfeed server).

"This message was created automatically by mail delivery software.
A message that you sent could not be delivered to all of its recipients.
The following adress (es) failed:


I said;
and then I sent the mail content

Server answerd:
550 5.7.1 Requested action not taken: message refused"

The ISP says that this error is happening at our mailserver, and that our server is the problem. But I´ve checked the message tracking log and cannot find any outgoing error messages such as the one above, which indicates that the problem could be at the ISP.

Does anyone have any ideas?

Our mailserver is configured as recommended with dns servers, smtp settings etc in Exchange.

  • 2
1 Solution
Unfortunately message tracking will not show this message going out as it is an SMTP NDR. That means that your server didn't actually generate a message - it told the sending server that it was refusing the message and the sending server generated the failure message.

The key thing with an NDR is to see what server rejected the message. This will either be an IP address or DNS name. Have you seen that to see which server did the reject?

Exchange MVP.
joebilekAuthor Commented:
No, where can I see an NDR for this type of problem?

As I wrote, the above error message was sent back to the original sender from the ISP.
Without a full NDR to prove that it was your server that generated the message you are stuck as the ISP will blame you (which is most ISPs first line of defence).

If it is an intermittent error then I would suspect the ISP. I am not a great lover of email relays etc that ISPs offer. I have had too much email get stuck inside them and then be delivered six weeks after being sent to think otherwise.

We went through a similar question last year. You might want to take a look at that question to see if it applies to yours.



Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now