Quoting Robert Vangel [EMAIL PROTECTED]:
I have been seeing a few (quite a few.. due to the amount of lists I am
subscribed to) messages in my postfix log's about
murphy.debian.org[146.82.138.6] being blocked due to being present in
spamhaus.org's SBL list.
Now it is in Spamcop's list:
On Thu, Nov 25, 2004 at 10:34:48AM +0100, Martin Schulze wrote:
For the stable distribution (woody) these problems have been fixed in
version 1.5.19-9.2
For the unstable distribution (sid) these problems have been fixed in
version 2.1.17-1.
Uhm, cyrus-imapd in unstable is 1.5.19-20.
The latest 2.4 kernel for Woody (kernel-image-2.4.18-1-686 version
2.4.18-13.1) is still vulnerable to the FPU crash CAN-2004-0554
discovered back in June 2004 and fixed in the 2.4.27 kernel. The code
available at http://www.securiteam.com/exploits/5ZP0N0AD5A.html will
crash an up to date
On Thursday 25 November 2004 10.50, Lupe Christoph wrote:
Now it is in Spamcop's list:
http://www.spamcop.net/w3m?action=checkblockip=146.82.138.6
spamcop does explicitly not recommend using their RBL for blocking - they
know why. That's the downside of a fully automated system.
Every
On Thu, Nov 25, 2004 at 10:50:19AM +0100, Lupe Christoph wrote:
I have removed bl.spamcop.net from our RBLs. Alas Spamcop does not
publish a contact mail address to tell them they have done something
Stoopid(tm).
[snip]
Since Spamcop does not talk to lowly insignificant users, can the
listmaster
* Adrian 'Dagurashibanipal' von Bidder ([EMAIL PROTECTED]) wrote:
plug
And, of course, postgrey as the very first line of defense.
/plug
Coupled with the usual checking on HELO (blocking 'localhost' HELOs and my
own IP does wonders!), SMTP protocol conformance (pipelining), sender
6 matches
Mail list logo
