On 8/28/2014 3:24 AM, Clement Thomas wrote: > Hi, > > Our outbound servers send out mails through different IPs and this > is doneas follows (postconf -n output: > https://gist.github.com/clement1289/2dfeea7b7625aee4a637 ). > > smtpd_end_of_data_restrictions = check_sender_access > pgsql:/etc/postfix/random-transports.cf # which will return FILTER > outbound1: > > and master.cf has each of the transports definedas below. > > outbound1 unix - - n - - smtp > -o smtp_bind_address=1.2.3.4 > -o syslog_name=postfix-outbound1 > > One of a remotedomaindomain.com has 4 MX records with priority > 5,10,15 and 20 MX server with priority 10 has some configuration > issues and wasn't accepting the mails. > Though MX with priority 5 is accepting mails normally, our mailq is > full of deferred mails trying to connect to MX server with priority 10
Only the LAST failure is noted in the mailq. To find errors connecting to lower numbered MX hosts, search the maillog for prior smtp connection warnings. Note the QUEUEID is not included on those warnings, you must search for the smtp process. -- Noel Jones > We planned of adding a transport_maps entry "domain.com > smtp:[mx_with_priority_5.mydomain.com]" , but since we use FILTER to > send out mails through different IPs, the transport_maps > wasn'tconsidered during delivery. Why was postfix trying MX with > priority 10? Is there anyway to specify transport_maps to clear the > mails in queue? > > Regards, > Clement
