Problems with incoming email

Posted on 2005-04-11
Last Modified: 2009-12-16

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, 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.

Question by:joebilek
    LVL 104

    Expert Comment

    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.
    LVL 1

    Author Comment

    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.
    LVL 104

    Accepted Solution

    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.


    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    Promote certifications in your email signature

    Has your company recently won an award or achieved a certification? They'll no doubt want to show it off. Email signature images used to promote certifications & awards can instantly establish credibility with a recipient and provide you with numerous benefits.

    Email signatures have numerous marketing benefits. Here are 8 top reasons to turn your email signature into a marketing channel.
    Find out how to use Active Directory data for email signature management in Microsoft Exchange and Office 365.
    how to add IIS SMTP to handle application/Scanner relays into office 365.
    This video discusses moving either the default database or any database to a new volume.

    779 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    18 Experts available now in Live!

    Get 1:1 Help Now