While trying to teach my spamassassin that the newsletters I don't remember subscribing to are in fact spam, I figured out that (being mailing lists) they probably come from same server(s), so instead, why not simply tell Exim to not accept any e-mails coming from these servers. It would be nice to have an example of a black list in our config files.
It seems that in Debian, this is already possible with the local_host_blacklist file, but we could probably copy that mechanism into our non-Debian files as well.
As for v3, the list could probably go into the database instead of being stored in a plain text file.
I think it would be great it we could ban e-mails not just coming from these blacklisted servers, but also having them among the Received headers (to cater for e-mails forwarded from other servers).
Also, it would be great to be able to specify a reason for blacklisting.
This blacklisting should happen after we accept all e-mail for postmaster though.
While trying to teach my spamassassin that the newsletters I don't remember subscribing to are in fact spam, I figured out that (being mailing lists) they probably come from same server(s), so instead, why not simply tell Exim to not accept any e-mails coming from these servers. It would be nice to have an example of a black list in our config files.
It seems that in Debian, this is already possible with the
local_host_blacklistfile, but we could probably copy that mechanism into our non-Debian files as well.As for v3, the list could probably go into the database instead of being stored in a plain text file.
I think it would be great it we could ban e-mails not just coming from these blacklisted servers, but also having them among the Received headers (to cater for e-mails forwarded from other servers).
Also, it would be great to be able to specify a reason for blacklisting.
This blacklisting should happen after we accept all e-mail for
postmasterthough.