On 4/17/2014 7:04 AM, Denny Fuchs wrote: > hi, > > Am 17.04.2014 um 13:16 schrieb Denny Fuchs <linuxm...@4lin.net>: > > >> smtp_fallback_relay = mailout.example.com > > just for testing: I added relayhost = mailout.example.com && postfix reload > && postsuper -r <id> && sendmailq -q .. and mails are delivered through the > relay server. So, it was working. After that, I removed the relayhost = ... > and reload .... > > So, why ever, smtp_fallback_relay doesn't work, relayhost works.
The clues are in the docs. http://www.postfix.org/postconf.5.html#smtp_fallback_relay So let's see if there's anything strange about that destination... # dig mx mailin.marc-werner.eu ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62202 ;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 13, ADDITIONAL: 2 ;; QUESTION SECTION: ;mailin.marc-werner.eu. IN MX ;; ANSWER SECTION: mailin.marc-werner.eu. 86242 IN MX 100 mx02.isphosts.net. mailin.marc-werner.eu. 86242 IN MX 10 mx01.isphosts.de. ;; ADDITIONAL SECTION: mx01.isphosts.de. 493 IN A 109.239.57.96 mx02.isphosts.net. 500 IN A 127.0.0.1 ;; Query time: 51 msec ;; SERVER: 127.0.0.1#53(127.0.0.1) ;; WHEN: Thu Apr 17 08:16:44 2014 ;; MSG SIZE rcvd: 344 Apparently they have an MX that points to the loopback address. The smtp_fallback_relay docs say: "To prevent mailer loops between MX hosts and fall-back hosts, Postfix version 2.2 and later will not use the fallback relays for destinations that it is MX host for " The relayhost parameter is unconditional, so it ignores the bogus MX entry. Typically in your situation one would use relayhost, with transport_maps overrides for internal destinations that are directly reachable. -- Noel Jones
