full-disclosure - Strange Emails -- What are they?

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <44871D00.8030902@cbnco.com>
Date: Wed Jun  7 19:38:06 2006
From: ppatters at cbnco.com (Pam Patterson)
Subject: Strange Emails -- What are they?

Ademar Gonzalez wrote:
> On 6/7/06, Simon Smith <simon@...soft.com> wrote:
>> ok, that makes sense... will greylisting counter this?
> 
> don't think graylisting will have much effect, each bot sending a few 
> mails.

Greylisting works by temporarily rejecting the first email from a sender 
at an ip address to a recipient, and then waiting the see if the sending 
mail server tries again as it should. If the server retries, the 
ip:sender:recipient tuple is added to a database and not delayed ever again.

Most spam-sending programs never retry, even with a temporary error.  So 
  greylisting would probably help in this case.

What would really help is SPF, if you can manage it. That way you can 
reject mail that claims to come from your domain but does not come from 
your mail servers.  But this is all a bit OT, not really full disclosure.

-- 
Pam