On Tue, 2008-02-26 at 10:01 -0500, Scott Kitterman wrote:
On Tuesday 26 February 2008 07:57, ram wrote:
I think the oft repeated "SPF-breaks-forwarding" and
"Use-SRS-when-frowarding" is the still top problems for SPF acceptance.
The next big hurdle is when ISP's block smtp access to corporate
mailservers and force the corporates to include a plethora of IP into
their SPF
Use the submission port, port 587. That's virtually never blocked.
Regarding the first problem
I am using Postfix and cyrus on my mailserver and use sieve rules for
forwarding. Frustratingly even though SRS has been around for ages now
there is not a single implementation of SRS for my setup. I remember
trying some smtp milter but that never worked
Postfix still (unless it's in 2.5, I haven't looked) lacks a way for external
programs to rewrite mail from so you'd need to do it with a transparent
filter. There's been some disucssion about this being a good feature to have
(for more than just SRS) on postfix-users, but someone either needs to
provide a patch or convince the postfix developers it's important enough to
do themselves (SRS along won't be enough)
I am surely missing something. Why should SRS be handled by the MTA ?
On the postfix list you got a reply from He-Who-Shall-Not-Be-Named :-)
He was clearly not interested in implementing SRS.
Why not cyrus-sieve send the forwarded message with the from id changed
as required
Thanks
Ram
-------------------------------------------
Sender Policy Framework: http://www.openspf.org
Archives: http://www.listbox.com/member/archive/735/=now
RSS Feed: http://www.listbox.com/member/archive/rss/735/
Modify Your Subscription:
http://www.listbox.com/member/?member_id=2183229&id_secret=95887956-51703a
Powered by Listbox: http://www.listbox.com