OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: Fixating on secondary...

From: Hamie (hamishtravellingkiwi.com)
Date: Tue Aug 03 2004 - 07:08:36 CDT


Victor Duchovni wrote:

>On Mon, Aug 02, 2004 at 03:11:28PM +0100, Hamie wrote:
>
>
>
>>I have a query form a user about a few emails that have 'gone
>>missing'... I've traced them down to residing in the queue of one of my
>>gateways, and they're continually getting 'connection refused' when
>>trying to connect to the MX.
>>
>>Now that's perfectly valid, as their gateway is indeed up, but no-one
>>listening... However the MX itself is actually a secondary, and their
>>primary is up & running fine... The DNS reports as
>>
>>br01ai01:# nslookup -type=MX elegant.com
>>
>>Non-authoritative answer:
>>elegant.com preference = 60, mail exchanger = ziggy.elegant.com
>>elegant.com preference = 20, mail exchanger = corp_isvr01.elegant.com
>>
>>

Sorry, I altered the names with a global search/replace (And didn't
state it till the end of the email)... Didn't check for elegant.com...
It's ACTUALLY eleganthotel.com...

>$ dig -t mx +noall +answer +additional elegant.com
>elegant.com. 86310 IN MX 10 truffle.elegant.com.
>truffle.elegant.com. 86310 IN A 67.69.24.106
>
>Postfix 2.1 connects to a backup MX after a temporary failure (not just
>connection problem) with the primary MX, only the final status is logged
>for each recipient. Temporary mail transaction problems with a non-final
>MX are not logged.
>
>

Right. So no logging of the non-fatal connect to the primary... But at
time of writing, the primary WAS up... The secondary wasn't... This is
the whole (Munged to prevent scraping) log for the relevant QID's...

br01ai01:/afs/.uk.baplc.com/mail_relay/arch/br01ai01# ar -p
mail.corp.postf03.200407.30.a mail.corp.postf03.20040730.235900.gz |
gzip -dc | egrep -i "91E7959|7A95B62"
Jul 30 13:26:28 mail-mgw02.baplc.com Message forwarded from cr02ae01:
postfix/smtpd[5660886]: 91E7959: client=intl-mgw02.baplc.com[161.2.239.202]
Jul 30 13:26:28 mail-mgw02.baplc.com Message forwarded from cr02ae01:
postfix/cleanup[2457688]: 91E7959:
message-id=<OF4CE2D6CB.57DEC286-ON80256EE1.00439757-80256EE1.00447D70holidays.britishairways.com>
Jul 30 13:26:28 mail-mgw02.baplc.com Message forwarded from cr02ae01:
postfix/qmgr[4235448]: 91E7959: from=<tamasina.kellyholidays.ba.com>,
size=4768, nrcpt=1 (queue active)
Jul 30 13:26:29 mail-mgw02.baplc.com Message forwarded from cr02ae01:
postfix/lmtp[7184384]: 91E7959: to=<AJacksoneleganthotls.com>,
relay=163.166.43.72[163.166.43.72], delay=1, status=sent (250 2.6.0 Ok,
id=6168592-02-79, from MTA: 250 Ok: queued as 751E6F2)
Jul 30 17:12:19 mail-mgw04.baplc.com Message forwarded from cr02ai01:
postfix/smtpd[3309694]: 7A95B62: client=intl-mgw02.baplc.com[161.2.239.202]
Jul 30 17:12:19 mail-mgw04.baplc.com Message forwarded from cr02ai01:
postfix/cleanup[6324446]: 7A95B62:
message-id=<OFD07B3613.B63279BE-ON80256EE1.0058C1EC-80256EE1.00592ACAholidays.britishairways.com>
Jul 30 17:12:19 mail-mgw04.baplc.com Message forwarded from cr02ai01:
postfix/qmgr[4653274]: 7A95B62: from=<tamasina.kellyholidays.ba.com>,
size=6147, nrcpt=1 (queue active)
Jul 30 17:12:20 mail-mgw04.baplc.com Message forwarded from cr02ai01:
postfix/lmtp[7741664]: 7A95B62: to=<ajacksoneleganthotls.com>,
relay=163.166.43.74[163.166.43.74], delay=1, status=sent (250 2.6.0 Ok,
id=4587676-01-82, from MTA: 250 Ok: queued as 58CB512D)
br01ai01:/afs/.uk.baplc.com/mail_relay/arch/br01ai01#