On 2010-01-24 01:37:54 +, Robin Bowes wrote:
On 22/01/10 15:19, Matt Sergeant wrote:
Also consider using Enemies List on the HELO. It's very effective.
Didn't know about that. I'll try it.
How would I go about doing that?
See http://enemieslist.com/how/use.html
(The front
On 24. jan. 2010, at 12.28, Peter J. Holzer wrote:
See http://enemieslist.com/how/use.html
(The front page says this is not currently available for public use,
but it seems to be)
For example, if the client sends EHLO smtp28.orange.fr (taken from a
random spam message), you query
On 2010-01-24 15:49:35 +0100, Johan Almqvist wrote:
On 24. jan. 2010, at 12.28, Peter J. Holzer wrote:
See http://enemieslist.com/how/use.html
[...]
For example, if the client sends EHLO smtp28.orange.fr (taken from a
random spam message), you query smtp28.orange.fr.g.enemieslist.com.
On 22/01/10 15:19, Matt Sergeant wrote:
Also consider using Enemies List on the HELO. It's very effective.
Matt,
How would I go about doing that?
R.
Johan Almqvist wrote:
On 21. jan. 2010, at 16.57, Christian Herndler wrote:
I get a lot of spam where the sender uses a whole /24 Subnet as mail
relay, the helo uses the pattern
mx{last-octet-of-ip}.domainname.net
so it could be blocked using the check_spamhelo plugin, but to do
On 21. jan. 2010, at 16.57, Christian Herndler wrote:
I get a lot of spam where the sender uses a whole /24 Subnet as mail
relay, the helo uses the pattern
mx{last-octet-of-ip}.domainname.net
so it could be blocked using the check_spamhelo plugin, but to do that
this plugin would
