Handle misconfigured MX records
-
- Posts: 45
- Joined: Sat Sep 13, 2008 7:51 pm
-
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
-
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
-
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
Brett, I just tested by sending a message to the sna.com domain.
Even with the default setting (ie: without any of the reg changes i mentioned) it will detect the loop - or at least it does so on mine.
This is what would appear in the mta debug log when it exceeds the 20 threshold.
Message (xxx) from (xxx) could not be delivered as an infinite message loop was detected. (ERROR MTA-1010)
My test was to simply use an imap/smtp client from outlook. The server has relay granted for 127.0.0.1 to allow the loop to occur. I sent a message to the user test@sna.com.
The message then cycles and is detected and placed in the badmail folder.
Maybe you could try the same test and see what happens.
Even with the default setting (ie: without any of the reg changes i mentioned) it will detect the loop - or at least it does so on mine.
This is what would appear in the mta debug log when it exceeds the 20 threshold.
Message (xxx) from (xxx) could not be delivered as an infinite message loop was detected. (ERROR MTA-1010)
My test was to simply use an imap/smtp client from outlook. The server has relay granted for 127.0.0.1 to allow the loop to occur. I sent a message to the user test@sna.com.
The message then cycles and is detected and placed in the badmail folder.
Maybe you could try the same test and see what happens.
Regards, Andrew
-
- Posts: 45
- Joined: Sat Sep 13, 2008 7:51 pm
I don't see Postfix falling to it's knees when mail loops back to itself. Mind you, any MTA in the hands of an idiot has the potential to s**t the bed. Perhaps entering the correct details and recipient when sending an email, or finding a negro in one of the townships with some savvy, and the problem may not have appeared in the first place.
-
- Posts: 560
- Joined: Mon Nov 03, 2003 7:48 am
- Location: Cape Town
I ran a test after setting both items in the registry and by the time I stopped the MTA the message had 55 received lines.
Do the Received headers have to be consecutive from the start of the message ? We run SpamAssassin on incoming email so there is a gap in Received headers at the start of the file as follows:
Do the Received headers have to be consecutive from the start of the message ? We run SpamAssassin on incoming email so there is a gap in Received headers at the start of the file as follows:
Code: Select all
Received: from MYDOMAIN ([XXX.XXX.XXX.XXX]) by MYDOMAIN with MailEnable ESMTP; Tue, 1 Sep 2009 14:34:04 +0200
X-Spam-Checker-Version: SpamAssassin 3.2.5 (2008-06-10) on WEBSERVER
X-Spam-Level:
X-Spam-Status: No, score=-3.5 required=5.0 tests=ALL_TRUSTED,AWL,BAYES_00
autolearn=ham version=3.2.5
Received: from MYDOMAIN ([XXX.XXX.XXX.XXX]) by MYDOMAIN with MailEnable ESMTP; Tue, 1 Sep 2009 14:33:55 +0200
Received: from MYDOMAIN ([XXX.XXX.XXX.XXX]) by MYDOMAIN with MailEnable ESMTP; Tue, 1 Sep 2009 14:33:47 +0200
Received: from MYDOMAIN ([XXX.XXX.XXX.XXX]) by MYDOMAIN with MailEnable ESMTP; Tue, 1 Sep 2009 14:33:30 +0200
....
-
- Site Admin
- Posts: 4441
- Joined: Tue Jun 25, 2002 3:03 am
- Location: Melbourne, Victoria Australia
Yes, that is why - the loop detection assumes they are consecutive.
I have patched the smtp executable to accommodate the more desirable fix. http://www.mailenable.com/beta/upload/mesmtpc.exe. You could try replacing the executable as an interim workaround.
I have patched the smtp executable to accommodate the more desirable fix. http://www.mailenable.com/beta/upload/mesmtpc.exe. You could try replacing the executable as an interim workaround.
Regards, Andrew