Issues with RBL

[wenfrazier]

I am having an issue with my servers RBL configuration and need some guidance to get this sorted out. Basically I have clients that are being blocked by sorbs and spamcop, but are very important to my company's business. So far I have tried the below steps but still am having clients get blocked:


[zimbra@mail ~]$ zmprov gacf | grep zimbraMtaRestriction
zimbraMtaRestriction: reject_non_fqdn_sender
zimbraMtaRestriction: reject_unknown_sender_domain
zimbraMtaRestriction: reject_rbl_client dnsbl.njabl.org
zimbraMtaRestriction: reject_rbl_client cbl.abuseat.org
zimbraMtaRestriction: reject_rbl_client bl.spamcop.net
zimbraMtaRestriction: reject_rbl_client dnsbl.sorbs.net
zimbraMtaRestriction: reject_rbl_client sbl.spamhaus.org
zimbraMtaRestriction: reject_rbl_client relays.mail-abuse.org

Here is the command I ran to remove sorbs and spamcop:

[zimbra@mail ~]$ zmprov mcf \
> zimbraMtaRestriction reject_non_fqdn_sender \
> zimbraMtaRestriction reject_unknown_sender_domain \
> zimbraMtaRestriction "reject_rbl_client dnsbl.njabl.org" \
> zimbraMtaRestriction "reject_rbl_client cbl.abuseat.org" \
> zimbraMtaRestriction "reject_rbl_client sbl.spamhaus.org" \
> zimbraMtaRestriction "reject_rbl_client relays.mail-abuse.org"


Finally here is the output that shows we are no longer using them:

[zimbra@mail ~]$ zmprov gacf | grep zimbraMtaRestriction zimbraMtaRestriction: reject_non_fqdn_sender
zimbraMtaRestriction: reject_unknown_sender_domain
zimbraMtaRestriction: reject_rbl_client dnsbl.njabl.org
zimbraMtaRestriction: reject_rbl_client cbl.abuseat.org
zimbraMtaRestriction: reject_rbl_client sbl.spamhaus.org
zimbraMtaRestriction: reject_rbl_client relays.mail-abuse.org

Also Zimbra has been restarted since the change to no avail. Is there something more that I can do to get this situation remedied so clients' emails are no longer getting blocked?

[devicegrip]

Just add the sender's domain to your global whitelist. This should bypass any spam filters. If the domain is not specific enough, spicify the user@domain and list all of the affected users.

This is a normal part of using the RBLs. It's a good idea to compile a list of addresses or domains that you want to always get through anyway.

[soba@ukw.edu.pl]

Originally Posted by devicegrip

Just add the sender's domain to your global whitelist. This should bypass any spam filters. If the domain is not specific enough, spicify the user@domain and list all of the affected users.

This is a normal part of using the RBLs. It's a good idea to compile a list of addresses or domains that you want to always get through anyway.

You can try to add in your main.cf (postfix) this line:

check_rbl = reject_rbl_client sbl.spamhaus.org, reject_rbl_client sbl.spamhaus.org=127.0.0.2, reject_rbl_client xbl.spamhaus.org,
reject_rbl_client xbl.spamhaus.org=127.0.0.4, reject_rbl_client xbl.spamhaus.org=127.0.0.5, reject_rbl_client xbl.spamhaus.org=127.0.0.6, reject_rbl_client pbl.spamhaus.org, reject_rbl_client
pbl.spamhaus.org=127.0.0.10, reject_rbl_client pbl.spamhaus.org=127.0.0.11, reject_rbl_client zen.spamhaus.org, reject_rbl_client zen.spamhaus.org=127.0.0.2, reject_rbl_client zen.spamhaus.org=127.0.0.4,
reject_rbl_client zen.spamhaus.org=127.0.0.5, reject_rbl_client zen.spamhaus.org=127.0.0.6, reject_rbl_client zen.spamhaus.org=127.0.0.7, reject_rbl_client zen.spamhaus.org=127.0.0.8,
reject_rbl_client zen.spamhaus.org=127.0.0.10, reject_rbl_client zen.spamhaus.org=127.0.0.11, reject_rbl_client dnsbl.sorbs.net, reject_rbl_client dnsbl.sorbs.net=127.0.0.2