lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Message-ID: <871080DEC5874D41B4E3AFC5C400611E03F60218@UTDEVS02.campus.ad.utdallas.edu> From: pauls at utdallas.edu (Schmehl, Paul L) Subject: About spamb strange characters I'll tell you how we "solved" one of the problems. We were getting almost daily form letter complaints from something called "myNetwatchman". Most of them were "RESEARCH PENDING" or complaints about KaZaA and other P2P apps which we can do nothing about. I emailed them three separate times to three different addresses (all cc'd on each message) asking them to please send us useful information *only* or we would route their mail to /dev/null. Guess where their mail goes now... The biggest scourge on the planet for security types right now is those damn home firewalls that send auto complaints with useless information. Paul Schmehl (pauls@...allas.edu) Adjunct Information Security Officer The University of Texas at Dallas AVIEN Founding Member http://www.utdallas.edu/~pauls/ -----Original Message----- From: vogt@...senet.com [mailto:vogt@...senet.com] Sent: Tuesday, May 13, 2003 9:35 AM To: nexus@...rol.i-way.co.uk; John.Airey@...b.org.uk; full-disclosure@...ts.netsys.com Subject: AW: [Full-Disclosure] About spamb strange characters > Edjumakating all these clueless MTA sysadmins that provide > spammers with > thousands of open relays would be the only way to do it IMHO. > Mind you, that's also as likely... may as well repeatedly > bang your head against the ISP's abuse@ auto-ignorer ;-) You should see what finds its way into the abuse@ account. If the quality of abuse reports were better, more could be done about it. I have seen:
Powered by blists - more mailing lists