On Wed, Jan 16, 2013 at 4:00 PM, Wietse Venema <wie...@porcupine.org> wrote:
> The way smtp_fallback_relay is implemented, it adds each relay as > a low-priority MX host with a safety check: if the relay does not > resolve, then mail is not bounced. > Hey, Wietse. I appreciate the reply. Ok - as far as I can tell, the relay IS resolving. And actually, I've got it configured as smtp_fallback_relay = [mailer2.example.com] in brackets to eliminate the MX lookup. > If you see deferred mail on mailer1, then it still needs to be > forwarded to the smtp_fallback_relay. The maillog file should > say why that hasn't happened yet. > qshape isn't showing deferred mail on mailer1, though. qshape deferred is all zeros. The active queue is massive, however (over 91K messages in it now) and more than half of them are in the 1280 column. When a destination replies to mailer1 like this: Jan 16 16:10:15 mailer1 postfix-aol/smtp[1744]: 41C4F4F6F7D: host mailin-04.mx.aol.com[64.12.90.34] refused to talk to me: 554 mtain-mh04.r1000.mx.aol.com ESMTP not accepting connections Should that not trigger handing the message over to the fallback relay for subsequent attempts? Thx, Steve
