[milters] Archive

Lists Index Date Thread Search

Article: 1211
From: Rose, Bobby
Date: 2006-10-23 18:18:41 -0400
Subject: Re: Not Selecting the Best MX for Call-Back?

Removal...........: milters-request@milter.info?subject=remove
More information..: http://www.milter.info/#Support
--------------------------------------------------------

Errol, it is checking all the MXs based off preference but when a
rejection occurs, it's only going to report back to sendmail that the
last one checked was not responding which is why that is what you see in
the logs.

I think that milter-sender needs to temp fail due to unresponding MXs
instead of permanent fail.  I have a support request open on this issue.
 

-----Original Message-----
From: milters-bounce@milter.info [mailto:milters-bounce@milter.info] On
Behalf Of Errol Neal
Sent: Monday, October 23, 2006 4:35 PM
To: milters@milter.info
Subject: [milters] Re: Not Selecting the Best MX for Call-Back?

Removal...........: milters-request@milter.info?subject=remove
More information..: http://www.milter.info/#Support
--------------------------------------------------------

Errol Neal wrote:
>> Oct 23 13:16:21 mailscanner sendmail[4164]: k9NHCC04004164: Milter:
>> from=<gshen@optionsgroup.com>, reject=550 5.7.1 MX 100 'mail.uu.net.'
>> [199.171.54.202] for <gshen@optionsgroup.com> not answering Oct 23
>> 13:16:21 mailscanner sendmail[4164]: k9NHCC04004164:
>> from=<gshen@optionsgroup.com>, size=1107, class=0, nrcpts=0, 
>> proto=ESMTP, daemon=MTA, relay=smtp2.theoptionsgroup.com 
>> [65.195.119.253] Oct 23 13:23:19 mailscanner sendmail[5168]:
>> k9NHJJLk005168: Milter:
>> from=<gshen@optionsgroup.com>, reject=550 5.7.1 MX 100 'mail.uu.net.'
>> [199.171.54.202] for <gshen@optionsgroup.com> not answering Oct 23
>> 13:23:19 mailscanner sendmail[5168]: k9NHJJLk005168:
>> from=<gshen@optionsgroup.com>, size=1455, class=0, nrcpts=0, 
>> roto=ESMTP, daemon=MTA, relay=smtp2.theoptionsgroup.com 
>> 65.195.119.253]

Anthony Wrote:

> I have 21 milters, two do call-ahead and/or call-back. More context
would be helpful. More logging too:

Sorry, I meant for milter sender. I can increase logging, but I wont be
able to provide anything this round Because we got to keep the customers
happy. 

 
>> [root@mailscanner log]# host -t MX optionsgroup.com optionsgroup.com 
>> mail is handled by 10 smtp.theoptionsgroup.com.
>> tionsgroup.com mail is handled by 100 mail.uu.net.
>> optionsgroup.com mail is handled by 5 smtp2.theoptionsgroup.com.

> In both milter-sender and milter-ahead, the MXes are sorted by
priority 
> from lowest (best) to highest (less desireable) and used in that
order. 
Yeah, I figured that as well


> You should validate the lower MXes by hand first.
They seem not to be responding.... Mind checking on your end? Smtp2
quickly terminates the connection...





Lists Index Date Thread Search