[exim-dev] [Bug 430] New: Advanced 550 error processing

Etusivu
Poista viesti
Vastaa
Lähettäjä: bug430
Päiväys:  
Vastaanottaja: exim-dev
Aihe: [exim-dev] [Bug 430] New: Advanced 550 error processing
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.

http://www.exim.org/bugzilla/show_bug.cgi?id=430

           Summary: Advanced 550 error processing
           Product: Exim
           Version: 4.63
          Platform: Other
        OS/Version: All
            Status: NEW
          Severity: wishlist
          Priority: medium
         Component: ACLs
        AssignedTo: ph10@???
        ReportedBy: marc@???
         QAContact: exim-dev@???



OK - I know Phil resists this idea but I will document WHY is it worth
considering.

The request. The ability to treat 550 errors in special circumstances as 421
errors and retry or branch to other processing.

The Reason:
-----------

There are special circumstances where you are sure that a 550 error is a
mistake. In this circumstance instead of bouncing the message you can do
something else like treat it like a 421 error until the problem on the
recipient server is fixed.

Examples:
---------


I am in the front end spam filtering business. People change their MX to point
to my servers, I clean the email, and forward it to their existing server which
is supposed to accept everything from my server.

However - I run into this problem. I set up routing in a table and the customer
changes the MX to point to my servers. Email comes in, processed, and then I
attempt to deliver it to the users original server. But - because of the MX
change the users server gives me a 550 error stating that I am not authorized
to relay email. And because of MX delays the user's server doesn't start
bouncing email till several hours after the change is made.

Or - my server ends up on some black list and the user's server is configured
to bounce mail from those who are listed. When you are in the front end spam
filtering business and a spam gets through then it looks like my server was the
source of the spam. In this case instead of bouncing all the email for that
domain I can store it, alert the user, get removed from the blacklist, and
reroute the message so it is sent from a different IP address.

I know this would be tricky and I can see why you wouldn't want to do it. But
there are reasons why this would be necessary.

Marc Perkel
http://www.junkemailfilter.com

--
Configure bugmail: http://www.exim.org/bugzilla/userprefs.cgi?tab=email