Looping condition

Posted on 2006-06-01
Last Modified: 2010-03-06
Hi I have a 2003 exchnage enviroment and in our config we have a few public facing SMTP servers that our MX records are pointed to and what is happening is when a bogus email address mx record hits our SMTP server the SMTP server hands it off to exchnage and exchange can not deliver the message and it seems like it is sending it back to SMTP and SMTP is sending it right back. Is there a way I can correct this in exchnage so when a bogus email address comes in that Exchnage drops it instead of bouncing it back to the SMTP server? I thought about lowering the hop count but I do not  want to cause legimit email to be droped because of that any ideas?
Question by:fbicocchi
    LVL 104

    Accepted Solution

    This is not an Exchange problem.
    Your public facing servers are not conforming to the SMTP standards and relaying the NDR back.

    If the Exchange servers were public facing, then I would recommend enabling recipient filtering. This stops the messages at the SMTP stage, so they aren't even delivered.
    If you are using something else for email delivery, then I would look to see if you can use LDAP lookup to filter recipients at the gateway.

    Some people would suggest disabling NDR generation.
    I don't tend to recommend this, because it means that legitimate NDRs are also not generated. However as your public facing servers aren't allowed the NDRs out, it becomes a debatable point.

    You should really sort out the NDR handling on the public facing servers. Do you want to tell the sale manager that a six figure order was missed because the sender got a spelling incorrect and didn't get an NDR saying so, and therefore presumed that the order was ignored?

    LVL 9

    Expert Comment

    I must say this could be a Reverse NDR SPAM issue.

    Try and setup Sender / recipient filtering. This would really help cut a lot of SPAM.

    I would also suggest considering Connection filtering and add free DNS blocking providers like "SORBS" or "SPAMCORP".

    Check KB pasted below;
    How to configure connection filtering to use Realtime Block Lists (RBLs) and how to configure recipient filtering in Exchange 2003

    Connection filtering would help you curb a lot of dynamic IP's listed with popular DNS blocking organizations and also known SPAM originating IP's.


    Featured Post

    Highfive Gives IT Their Time Back

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Join & Write a Comment

    ADCs have gained traction within the last decade, largely due to increased demand for legacy load balancing appliances to handle more advanced application delivery requirements and improve application performance.
    Not sure what the best email signature size is? Are you worried about email signature image size? Follow this best practice guide.
    The video tutorial explains the basics of the Exchange server Database Availability groups. The components of this video include: 1. Automatic Failover 2. Failover Clustering 3. Active Manager
    how to add IIS SMTP to handle application/Scanner relays into office 365.

    745 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

    15 Experts available now in Live!

    Get 1:1 Help Now