full-disclosure - Spam Solution

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: <200406180621.i5I6LjX09575@tag.witbe.net>
From: rol at witbe.net (Paul Rolland)
Subject: Spam Solution

Hello,

> It seems to me that if we make all MTA's register somehow 
> (both SMTP and 
> POST), this would eliminate the hijacked machine as spambot 
> phenomenon. We 
> already have MX records for SMTP, but a lot of providers use 
> different 
> machines to receive (via SMTP) and send mail (POST). So, 
> maybe a new DNS 
> record is introduced for POST. Your machine(s) could do both 
> or not. When 
> your server goes to accept a message, it looks to see if the 
> IP of the 
> sending machine is listed in this new DNS record. If not, 
> return a 5XX error.

Hell, this just means that before spamming, people will also have
to break DNS ... or am I missing something ?

> Didn't I read something somewhere about the possibility of this?

The whole thread titled "Akamai"... :-(

Regards,
Paul