On Mon, Apr 27, 2015 at 03:12:04PM +0000, Peter Berghold wrote:
> Apr 27 10:58:50 chicweb0 postfix/smtpd[13505]: 7DC243FC1CC: client=
> oldmule.templefindwindow.com[23.89.2.18]
When was this address added to any of the RBLs you're using?
> > Output of postconf -n
>
> content_filter = scan:127.0.0.1:10025
> receive_override_options = no_address_mappings
Make sure that receive_override_options is set empty in the port
10025 post-filter SMTP service.
> smtp_tls_security_level = may
> smtp_use_tls = yes
The second of these is obsolete and redundant.
> smtpd_helo_restrictions = reject_unknown_helo_hostname
That's likely to reject more than a negligible amount of legitimate
mail.
> smtpd_recipient_restrictions =
> permit_sasl_authenticated,
> permit_mynetworks,
> reject_sender_login_mismatch,
> check_sender_access hash:/etc/postfix/access,
Move this (and the next 6 lines) *below* reject_unauth_destination.
> reject_invalid_hostname,
> reject_non_fqdn_sender,
> reject_non_fqdn_recipient,
> reject_unknown_sender_domain,
> reject_unknown_recipient_domain,
> reject_unauth_pipelining,
> reject_unauth_destination,
--- here ---
[ That is, move reject_unauth_destination, up above check_sender_access. ]
> check_recipient_access pcre:/etc/postfix/recipient_checks.pcre,
Which recipients match the regular expressions and what is the
action in that case?
> reject_rbl_client ubl.unsubscore.com,
> reject_rbl_client zen.spamhaus.org,
> reject_rbl_client dnsbl.dronebl.org,
> reject_rbl_client bl.spamcop.net,
> reject_rbl_client dnsbl.sorbs.net,
> reject_rbl_client noptr.spamrats.com,
> permit
> smtpd_use_tls = yes
Instead:
smtpd_tls_security_level = may
--
Viktor.
