spf-discuss
[Top] [All Lists]

Re: RFC 2821 and responsibility for forwarding

2004-12-04 16:02:09
Andy Bakun wrote:

The problem with forwarding is not forwarding within an
organization, it's re-injecting the mail back into the
Internet.

That's true, but from the sender's POV that's none of his
business, he can't do anything about it in a sender policy.

is it reasonable to expect big email providers will have
what amounts to B2B help desks for getting mutual trust
relationships setup?

Not sure, but the original sender isn't in the position to
do anything about it, so that's something the receiver and
his providers (forwarder and final destination) must solve.

The sender is busy with figuring out MSAs and RfC 2476 ;-)

 [postmaster of user(_at_)smallisp talking to big $company]
This is the postmaster of smallisp.example.com.  I have a
user who wants to forward all their mail from their account
here to their new account with you guys.  I need you to
whitelist me."

"Yeah, right."

LOL.  In that case let the poor user find a smaller provider
for his second hop, or try SRS.  As postmaster(_at_)smallisp you
are flexible.  If Meng (pobox) can do it, and GMX can do it
(largest German freemailer), it can't be impossible.

Hannah's case is special, they are AFAIK the biggest hoster
of the world.

I, for one, wouldn't want to blindly whitelist big free email
providers for my entire site

Now postmaster(_at_)ebay wants something from you.  But that's at
the moment unnecessary, if ebay is on trusted-forwaders.org (?)

How do you get users to understand that by whitelisting
big-free-email-provider-spammer-haven.com puts them at risk

That puts your entire site at risk, and its about the final
destination,  Of course _that_ part, adding something to the
WL, can't be done by the user with a Web form, you (as admin)
have to approve it.

Okay, I can see it, big ISPs just won't do it for medium size
or small forwarders, it needs too much support and could open
obscure loopholes, it would be easier to do no SPF at all. :-(

Back to plan B:  Small or medium forwarder hates SRS (that's
the assumption, otherwise there's no problem), next hop won't
white list, 551 is suicide.  Let him store SPF protected mail
in an ordinary POP3 mailbox, and the user can get it on demand.

Or offer to send stored mail say daily in the form of an mbox
resp. multipart/digest.  Mailing lists often have a "digest
mode", why not do it also for single "forwarded" users ?

IMHO there's almost always another way for the forwarder, he
could limit the 551 to over quota in the POP3 solution.  Bye.