Bill Cole wrote:
Here was the specific context to which I was responding:
they might even send out email using the user's own
email account and/or email client.
Swen does that. Really.
Yes, but not necessarily. Its installation procedure asks
the user to enter his smart host and credentials, and the
"effects" can be very interesting... ;-)
Generally it was possible to determine the relevant abuse@
for SWEN by looking at the Return-Path, but not _always_
SPF does nothing at all to stop it.
Yes, SWEN is quite unusual. SPF could help to enforce the
_always_ in this case, but it can't replace a working abuse@
or the "enforced submission rights" in RfC 2476 option 6.1.
Take care if you send SWEN complaints automatically, it's not
always correct to use the Return-Path with local part abuse(_at_)(_dot_)
Bye, Frank
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg