nanog mailing list archives
Re: ingress SMTP
From: hobbit () avian org (*Hobbit*)
Date: Sun, 14 Sep 2008 01:28:59 +0000 (GMT)
> How do you alert mail server operators who are smarthosting their > e-mail through you that their outbound messages contain spam? You don't let them falsify their envelope or headers to contain fields utterly unrelated to your own infrastructure, for starters. They try it, their mail bounces. It's a very rare piece of spam that actually comes from who it says it comes from anymore. Do that before thinking about rate-limiting or any other fanciness, and you've likely licked 90% of the problem right there. A smarthost with a strong "sense of self" backed up by port-25 rules is exactly what I'm talking about, and if certain large providers ever *read* their abuse boxes they'd find the same advice from me in more than one instance followed by a clear example of why. _H*
Current thread:
- Re: ingress SMTP, (continued)
- Re: ingress SMTP Robert E. Seastrom (Sep 10)
- Re: ingress SMTP Jeff Kinz (Sep 05)
- RE: ingress SMTP Frank Bulk (Sep 03)
- Re: ingress SMTP Tony Finch (Sep 04)
- ingress SMTP Ang Kah Yik (Sep 03)
- Re: ingress SMTP Suresh Ramasubramanian (Sep 03)
- Re: ingress SMTP Ang Kah Yik (Sep 03)
- Re: ingress SMTP Suresh Ramasubramanian (Sep 03)
- Re: ingress SMTP matthew (Sep 07)
- Re: ingress SMTP Michael Thomas (Sep 07)
- Re: ingress SMTP *Hobbit* (Sep 10)
- Re: ingress SMTP *Hobbit* (Sep 13)
- Re: ingress SMTP Matthew Moyle-Croft (Sep 13)