Re: DNSBL and IPv6
"Peter J. Holzer" <[email protected]>
| Newsgroups | gmane.ietf.asrg |
|---|---|
| Message-ID | <[email protected]> |
On 2012-10-20 21:42:57 -0000, John Levine wrote: > >} Is there a reason why a legitimate MTA (talking to MXs, not submission > >} servers) would want to hop around in its net? > > Probably not, although I'm waiting for ESPs to figure out that if they > send every message from a different IP, I thought of that but I wouldn't be surprised to overflow the router's ARP table even with our moderately sized mailing-lists (a few thousand subscribers at most). That's why I only mentioned "one address per customer", not "one address per message" as a likely tactic. > it'll be much easier to process bounces and complaints since all > they'll need is the IP to figure out what the list and address was. Is it? For mailing-lists, I think VERP is simpler and more robust. The IP address is buried somewhere in the Received headers of the bounced message, so you have to parse those. For complaints to an ISP about a customer that might indeed be useful. Depends on what information is included in the complaint. If it contains the complete header of the message there is probably other identifying information. It it doesn't, chances are that the IP address isn't included, either. > Bad guys could use it to listwash, of course, but it's not totally > ridiculous. There are other ways to listwash. I'm more worried that the bad guys are using rapidly changing IP addresses to escape or overflow BLs. hp -- _ | Peter J. Holzer | Der eigene Verstand bleibt gefühlt messer- |_|_) | Sysadmin WSR | scharf. Aber die restliche Welt blickt's | | | [email protected] | immer weniger. __/ | http://www.hjp.at/ | -- Matthias Kohrs in desd _______________________________________________ Asrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/asrg
signature.asc
(application/pgp-signature, 828 B)
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iQIVAwUBUIRnJ/IOSFES/ihdAQIVOg/+Iy+JBx8FQaBAPsPJLQD4yWhwKTg5paov GwjWcZIGo/+lmRbny471H1NcBgkSRNaBEmv6yIUMUtgpE6MGhtgrj/4sZ1D+3BK9 h1Qmm8xAmoiX+s6+TCown0M6qbYf0parVJo4BmugNQiGcdeaBD8+C7mBYyZhFAwd 5km6Pq7waU2wk54OngQq+8xuB9gREyZ06JeLFWJ8KzTcCHLP5ea6sfLiizOuRLFj 7CpWAxIvAz+IHhEbdHjc654Y4vU79TiBWHHlGN7pJfCiJQV64L9kA2EYl5YJi8Z8 VEpTQY/NTygfEiZH91XezfXs99DZices1sDg6R5pnLxBeBJ2wrlnJCMcPcVB7yrk xeNcDMS4icBg+pKBVhDYb1GU8zw/NBnUW7aLrmRO6BF1Fa/qgDOFCDi2TagnhFQk 3/DXSb+/zE/w9X8Hs5MF0mntj9UejiyLW21sUjDR0LBVG1R15463Epb8RZZ0CK1G UkmG7hiFvcfrc+c6gBgCK7e57C/YPs4QYeL9Iw/ou5ADpG5RK+s34UDlmRlyhitE 2R4CgQWt0uY1JuGGuBjkkrnexapnYqre/EX9fC2Sys07sYL6a+KXS+gUE9HZftiY n7wn3nBL7ocoWbEe7hgOZSnEDvTdrTq4ZeQotvrDE/kHoCuRdIfeEWrq98d/Wh8g VZ39DUd36uA= =EwOt -----END PGP SIGNATURE-----