18 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Status of SRS (SP...
FromSent OnAttachments
Pierre OssmanNov 17, 2004 10:12 am 
Sam VarshavchikNov 17, 2004 3:19 pm 
Julian MehnleNov 17, 2004 8:34 pm 
Julian MehnleNov 17, 2004 8:57 pm 
cour...@gmx.netNov 18, 2004 3:10 am 
Sam VarshavchikNov 18, 2004 4:07 am 
Pierre OssmanNov 18, 2004 4:24 am 
Julian MehnleNov 18, 2004 6:27 am 
Julian MehnleNov 18, 2004 6:45 am 
Sam VarshavchikNov 18, 2004 3:50 pm 
Pierre OssmanNov 18, 2004 10:06 pm 
Alessandro VeselyNov 19, 2004 12:26 am 
Julian MehnleNov 19, 2004 4:48 am 
Sam VarshavchikNov 19, 2004 3:37 pm 
Bill TaroliNov 19, 2004 4:52 pm 
Alessandro VeselyNov 20, 2004 3:25 am 
cour...@gmx.netNov 20, 2004 8:51 am 
Julian MehnleNov 22, 2004 5:43 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Status of SRS (SPF forwarding "fix")Actions...
From:Alessandro Vesely (ves@tana.it)
Date:Nov 20, 2004 3:25:49 am
List:net.sourceforge.lists.courier-users

Julian Mehnle wrote:

[...] Now someone at pobox.com (which is SPF protected) sends me a message to my cpan.org address. The cpan.org MTA forwards the message to the mehnle.net MTA, which sees the "pobox.com" envelope sender being used on a message coming from a cpan.org MTA. But the pobox.com SPF record doesn't authorize cpan.org MTAs to send mail on their behalf, so mehnle.net rejects the message.

To solve the problem, cpan.org would have to rewrite the envelope sender to something at cpan.org before forwarding the message.

That not only requires cpan.org to implement SPF, but also SRS. The SPF checking on the final message is not much useful: it only tells that you can accept mail from cpan.org, which you should know already, since you have an account there.

If that message should be SPF-rejected, only cpan.org could do it. I would be content if they just implemented SPF.