Hi,
I’ve added backscatter and RBL rejections to my main.cf and all appears to work as expected.
However, I am getting complaints from clients saying that they haven’t received important emails.
These are usually down to the sender’s IP address being blacklist on SORBS, spamcop etc.
Is there a way to add a whitelist on a per virtual host basis?
My thoughts are that the onus is on the sender to get cleaned up but in reality, that is not always possible as the sender is usually non-technical and doesn’t even know what the bounced message is telling them.
I’m considering removing the RBL checks and let everyone fill their spam boxes.
Will the reject options I have stop backscatter on their own or do they also require the RBL checks. I was recently blacklisted on backscatter.org and do not want it to happen again.
My main.cf contains;
smtpd_sasl_authenticated_header = yes
helo_required = yes
disable_vrfy_command = yes
strict_rfc821_envelopes = yes
invalid_hostname_reject_code = 554
multi_recipient_bounce_reject_code = 554
non_fqdn_reject_code = 554
relay_domains_reject_code = 554
unknown_address_reject_code = 554
unknown_client_reject_code = 554
unknown_hostname_reject_code = 554
unknown_local_recipient_reject_code = 554
unknown_relay_recipient_reject_code = 554
unknown_sender_reject_code = 554
unknown_virtual_alias_reject_code = 554
unknown_virtual_mailbox_reject_code = 554
unverified_recipient_reject_code = 554
unverified_sender_reject_code = 554
smtpd_recipient_restrictions =
reject_invalid_hostname,
reject_unknown_recipient_domain,
reject_unauth_pipelining,
permit_mynetworks,
permit_sasl_authenticated,
reject_unauth_destination,
reject_rbl_client multi.uribl.com,
reject_rbl_client dsn.rfc-ignorant.org,
reject_rbl_client dul.dnsbl.sorbs.net,
reject_rbl_client sbl-xbl.spamhaus.org,
reject_rbl_client bl.spamcop.net,
reject_rbl_client dnsbl.sorbs.net,
reject_rbl_client cbl.abuseat.org,
reject_rbl_client ix.dnsbl.manitu.net,
reject_rbl_client combined.rbl.msrbl.net,
reject_rbl_client rabl.nuclearelephant.com,
permit