On Wed, 6 Feb 2008, David MacQuigg wrote:
Problem P - Recipients have difficulty keeping track of and updating
their forwarding arrangements.
These aren't like the three forwarding problems I've laid out.
Problem P is a root cause of my three problems, but is not a forwarding
problem in and of itself.
It's not even THE root cause -- it shares credit with recipient
indifference to the other forwarding problems.
If:
* legitimate mail from <sarah(_at_)example(_dot_)com> to
<fred(_at_)example(_dot_)org> is
forwarded to <ralph(_at_)example(_dot_)net>, run through SpamAssassin by
example.net
and then delivered to Ralph's mailbox.
* false-postive mail from <sarah(_at_)example(_dot_)com> to
<fred(_at_)example(_dot_)org> will
be bounced to <sarah(_at_)example(_dot_)com> when Example.net 5xxs example.orgs
the attempt to forward to Ralph.
* actual spam, forged in <sarah(_at_)example(_dot_)com>'s name and sent to
<fred(_at_)example(_dot_)org>, will also be bounced to
<sarah(_at_)example(_dot_)com> when
Example.net 5xxed it.
...then Forwarding Problem B is active. But Ralph doesn't mind. If his
spam-filter triggers, he doesn't worry because he knows the original
sender will know from the bounce that the mail wasn't delivered, and if it
was indeed spam, he never had to acknowledge seeing it.
Sarah will be angry about the backscatter, and will sic the Lumber Cartel
(TINLC) on Example.org, but Ralph *doesn't care about that*.
The only way Ralph will care is if Example.org *deliberately* breaks his
forwarding to punish him.
Problem R - The reliability of the global email system is so bad that
users cannot be confident of delivery unless there is prior arrangement
between Agents at the Border of the sending and receiving networks.
This isn't specific to forwarding, and doesn't even apply very strongly
to forwarding.
Forwarding Problem B doesn't affect reliability (from the recipient
perspective) at all, unless the forwarder starts playing Tit for Tat to
force the recipient to eat his spam instead of causing deadletters.
Forwarding Problem S can be avoided easily by the recipient, by not
deploying receiverside SPF.
Forwarding Problem K could cause "reliability problems", but it's only an
issue at Karma-counting final mailstores.
---- Michael Deutschmann <michael(_at_)talamasca(_dot_)ocis(_dot_)net>
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Archives: http://v2.listbox.com/member/archive/735/=now
RSS Feed: http://v2.listbox.com/member/archive/rss/735/
Modify Your Subscription:
http://v2.listbox.com/member/?member_id=2183229&id_secret=93125367-007d07
Powered by Listbox: http://www.listbox.com