restricted relay from / to $mynetwork only
hi, we want to create a restricted relay for our campus, which allows only internal relaying, based on $mynetwork or pcre. Looking for the domain part isn’t a way, because we have some subdomains which has (for example) Google as primary MX. Should it working with smtpd_recipient_restrictions / smtpd_sender_restrictions and $mynetwork? We have Postfix 2.9.6 cu denny signature.asc Description: Message signed with OpenPGP using GPGMail
Strange behavior: smtp_fallback_relay not used for one MX destination
hi, in our university we have to use a relay server, for delivering mails to external destinations. It works since two years with: smtp_fallback_relay = mailout.example.com Postfix tries to deliver the mail directly, but it fails, with a connection refused /network unreachable(ipv6) (blocked port 25), so the daemon use the smtp_fallback_relay, which is our mailout.exmaple.com. It's working, usually. For the Domain mailin.marc-werner.eu Postfix never tries to use fallback_relay: == 265041031C 1165 Thu Apr 17 13:01:05 m...@sub.example.com (connect to mx01.isphosts.de[109.239.57.96]:25: Connection refused) f...@mailin.marc-werner.eu == The domain mailin.marc-werner.eu is nothing from us, so external. So I don't understand, why Postfix doesn't use the smtp_fallback, but for all others. Debian Wheezy: ii postfix 2.9.6-2 amd64 High-performance mail transport agent Any suggestions? cu denny signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Strange behavior: smtp_fallback_relay not used for one MX destination
hi, Am 17.04.2014 um 13:16 schrieb Denny Fuchs : > smtp_fallback_relay = mailout.example.com just for testing: I added relayhost = mailout.example.com && postfix reload && postsuper -r && 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. === Apr 17 13:37:45 MX01 postfix/cleanup[16726]: E86F7FEBC: message-id= Apr 17 13:37:45 MX01 postfix/qmgr[16131]: E86F7FEBC: from=, size=1076, nrcpt=1 (queue active) Apr 17 13:37:45 MX01 postfix/smtp[16140]: E86F7FEBC: to=, relay=none, delay=0.17, delays=0.15/0.01/0/0, dsn=4.4.1, status=deferred (connect to mx01.isphosts.de[109.239.57.96]:25: Connection refused) === ... very strange. everything else works, as expected: Apr 17 14:01:46 MX01 postfix/qmgr[16131]: F12C2FF2D: from=, size=1067, nrcpt=1 (queue active) Apr 17 14:01:46 MX01 postfix/smtp[20988]: connect to mail.4lin.net[2a01:7e0:0:200:3::1]:25: Network is unreachable Apr 17 14:01:46 MX01 postfix/smtp[20988]: connect to mail.4lin.net[212.224.84.186]:25: Connection refused Apr 17 14:01:47 MX01 postfix/smtp[20988]: F12C2FF2D: to=, relay=mailout.example.com[1.2.3.4]:25, delay=1.6, delays=0.15/0.01/0.1/1.4, dsn=2.0.0, status=sent (250 2.0.0 s3HC1kqO004038 Message accepted for delivery) Apr 17 14:01:47 MX01 postfix/qmgr[16131]: F12C2FF2D: removed cu denny signature.asc Description: Message signed with OpenPGP using GPGMail
Re: Strange behavior: smtp_fallback_relay not used for one MX destination
hi, Am 17.04.2014 um 15:21 schrieb Noel Jones : > Typically in your situation one would use relayhost, with > transport_maps overrides for internal destinations that are directly > reachable. thanks @all for debugging ... I think, is is simply broken, what the maintainer of the zone does. Is there a way to check for so such broken DNS configurations? cu denny signature.asc Description: Message signed with OpenPGP using GPGMail
