On 10/16/2013 07:21 PM, Kevin Miller wrote:
So if I'm reading this right, milters such as smf-sav or milter-ahead will no
longer be of any use?
yep... One will have to be creative, start mantaining local rcpt list
copies, LDAP exports, etc - lottsa fun for all parties.
This also applies to Postfix's recipient address verification.
...Kevin
--
Kevin Miller
Network/email Administrator, CBJ MIS Dept.
155 South Seward Street
Juneau, Alaska 99801
Phone: (907) 586-0242, Fax: (907) 586-4500
Registered Linux User No: 307357
-----Original Message-----
From: Axb [mailto:axb.li...@gmail.com]
Sent: Wednesday, October 16, 2013 9:18 AM
To: users@spamassassin.apache.org
Subject: Re: one word spam (continued)
On 10/16/2013 06:42 PM, David F. Skoll wrote:
On 16 Oct 2013 09:15:07 -0700
"Neil Schwartzman" <n...@cauce.org> wrote:
List verification. Many receiving sites will block after X bounces,
clean up your list from 550s, and spam the real thing from another
botted IP.
<rant>
And you know who we can thank [sic] for this mechanism of list verification?
Microsoft, that's who.
For versions of Microsoft Exchange prior to 2013, you need to jump
through ridiculous hoops to configure it so that invalid RCPT commands are
rejected.
By default, Exchange accepts any old RCPT command and then either
rejects after DATA or (if a RCPT was valid) is forced to generate a
delivery failure notification.
For Exchange 2013, the ridiculous hoops no longer work and I don't
believe it is even possible to configure Exchange 2013 to reject
invalid RCPTs without truly grotesque hacks.
Thank you, Microsoft, for making the Internet a better place.
</rant>
Exchange 2013 can still reject mail to unknown users, except that it does it
_AFTER_ DATA, which means that everybody that tried to be a good player has
become a backscatterer, including their own services which have they have
elegantly turned into spam spewin bazookas.
May I join you?
<rant>
Thank you, Microsoft, for making the Internet a better place.
</rant>
