full-disclosure - Re: 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: <20040618022515.GC4389@jfet.org>
From: rsw at jfet.org (Riad S. Wahby)
Subject: Re: Spam Solution

Alavan <alavan@...geatech.com> wrote:
> 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.

Uhhh... isn't this just SPF?

-- 
Riad S. Wahby
rsw@...t.org