nanog mailing list archives

Re: Time to check the rate limits on your mail servers


From: "Edward B. Dreger" <eddy+public+spam () noc everquick net>
Date: Sat, 5 Feb 2005 20:01:08 +0000 (GMT)


AL> Date: Sat, 5 Feb 2005 13:11:11 -0600
AL> From: Adi Linden

AL> Now that we have established a "trust chain" an verify the sending user we
AL> have an easy way (shuffling through mail logs is by no means easy in my
AL> books) for support people to address SPAM complaints.

Note that I'm ignoring SMTP proxies that may munge headers.


AL> Even better, due to the verified sender we can now send bounce messages
AL> and notifications to originator. Sure, it'll result in "I never send
AL> this..." type support calls but support can now say "Sure, your computer
AL> did behind your back...".

I hadn't thought of setting "Return-Path:" based on authenticated user...


Eddy
--
Everquick Internet - http://www.everquick.net/
A division of Brotsman & Dreger, Inc. - http://www.brotsman.com/
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 785 865 5885 Lawrence and [inter]national
Phone: +1 316 794 8922 Wichita
________________________________________________________________________
DO NOT send mail to the following addresses:
davidc () brics com -*- jfconmaapaq () intc net -*- sam () everquick net
Sending mail to spambait addresses is a great way to get blocked.
Ditto for broken OOO autoresponders and foolish AV software backscatter.


Current thread: