Whitelisting RBL domains
omta37.uswest2.a.cloudfilter.net 35.89.44.36
omta037.useast.a.cloudfilter.net 44.202.169.36
..etcetera. and some times that cloud service falls in some RBL spam lists:
# exim_checkaccess 44.202.169.36 customer@address.com
Rejected:
550-"JunkMail rejected - omta037.useast.a.cloudfilter.net [44.202.169.36] is in
550-an RBL: IP 44.202.169.36 ......I was not able to find a way to bypass the RBL checking for any "cloudfilter.net" subdomain. Documentation in CPanel about the option /etc/skiprbldomains is not very complete: "wildlsearch or nwildlsearch: These search a file linearly, like lsearch, but instead of being interpreted as a literal string, each key in the file may be wildcarded.[...] The following forms of wildcard are recognized: *.a.b.c data for anything.a.b.c *fish data for anythingfish"
Why the Exim wildsearch key doesn't work?
-
finally I have included a partial-lsearch in this line of the Exim advanced editor "hostlist greylist_common_mail_providers = partial-lsearch;/etc/greylist_common_mail_providers" because the line "!hosts = +greylist_common_mail_providers" exists in every RBL list Then I have included *.subdomains inside empty file /etc/greylist_common_mail_providers, and chattr +i the file to avoid changes. Hope it can works. Anyway, some option to whitelist domain hostnames is very needed. There are services of that style who are renting many Amazon AWS and similar solutions to use many host subdomains with different ips to send legitimate e-mail. A perfect option to avoid breaking the anti-spam filters in all the server would be whitelisting *.domains for concrete email addresses. 0 -
Thanks for sharing that solution!!! 0 -
just to add, it works with the sender's hosts. No with the domains names.
So it is necessary looking to the sender host, and then add it into the list.I write again here because still I cannot a find an easy way to whitelist the sender's domains.
Whitelisting hosts instead domains is not comfortable because many senders are using third hosts from microsoft and etcetera, and using composed subdomains which also are changing.
And it is not a good idea whitelisting *.microsoft.com or all the *.*.outlook.com because these are also used by spammers.
Why there is no a way to whitelist the sender domain?. I have a found in internet a patch for CPanel v11 and Exim but that's not a good way. It would be necessary a simple option to whitelist the sender's domain.
The same problem is extended to whitelist the DKIM validation for the senders domain names.
Why it doesn't exist a whitelist for the sender domain after so long time?. It will be implemented some day?Or is this already implemented and can be activated in some place?
thank you
0 -
I'm not seeing a good option that would do specific email addresses at this time. Have you submitted a feature request for this functionality at features.cpanel.net yet? If you aren't able to, I'm happy to submit one and I can bring it up with the email team.
0 -
It would be good to have such solution.. whitelist an specific email address against RBL checks.. sometimes customers need to receive an email from someone that works with mailing companys with strange reputation.. and whitelist a whole /21 is not a solution that fits antispam.
cPRex would love if you can submit the feature request.Thank you!
0 -
Rackmarkt - I'll get this one submitted, although the next features meeting isn't scheduled until December 5th, due to various team members with PTO and the US Thanksgiving holiday. I'll be sure to post again once I have more details!
0 -
Update - it *looks* like you can do this directly through SpamAssassin. Can you confirm that this is the behavior you're looking for?
0
Please sign in to leave a comment.
Comments
7 comments