On 2009-12-08 23:08:56 -0800, BOBOTEK, ALEX (ATTCINW) wrote:
One approach to identifying a destination for spam reports is to inspect
the RECEIVED headers of the suspect message and fire the report back to
the last MTA (or perhaps a DNS txt 'spamReport' record assigned to that
MTA). This assumes that it knows what to do with it, possibly leading
to a cascading effect. IMHO, this is a good way of getting the info
back to systems/parties that we expect to block it.
One potential hazard is the reports being cascaded back to the spammer,
or otherwise exposing the reporters to the extent that list washing
would be possible.
I think that would actually be a feature. I'd love it if spammers
removed my address(es) from their lists. Unfortunately I don't see that
happening.
hp
--
_ | Peter J. Holzer | Openmoko has already embedded
|_|_) | Sysadmin WSR | voting system.
| | | hjp(_at_)hjp(_dot_)at | Named "If you want it -- write it"
__/ | http://www.hjp.at/ | -- Ilja O. on
community(_at_)lists(_dot_)openmoko(_dot_)org
signature.asc
Description: Digital signature
_______________________________________________
Asrg mailing list
Asrg(_at_)irtf(_dot_)org
http://www.irtf.org/mailman/listinfo/asrg