Lindsay Haisley [fmou...@fmp.com] wrote:
What's the current status of SPF and Courier? I note that SPF can be
implemented as a 3rd party filter via a perl object library, but does
this handle issues such as sender address rewriting (I have _lots_ of
customer mail redirections on my mail server)?
No, Courier::Filter::Module::SPF does not do sender address rewriting (it
technically cannot do this in an elegant way). Although the SPF concept
as a whole cannot work without sender address rewriting (using SRS or some
custom method), SPF checking and sender address rewriting are distinct
concepts. Theoretically, for your server to do SPF checking when
receiving messages, you don't need to rewrite sender addresses when
forwarding, i.e. sending, messages. Only when a server you forward
messages to performs SPF checking is sender address rewriting required.
For an elegant solution, sender address rewriting would need to be
integrated directly into Courier. A hackish solution would be to
"deliver" to-be-forwarded messages locally to a script (e.g. by using a
dot-courier file) that programmatically reinjects the message with
rewritten sender and recipient addresses. Maybe there's yet another way,
but I currently don't see it.
Are there any plans to incorporate this as a standard feature in
Courier, and if so, when?
As far as I know Sam doesn't like the SPF concept and thus, SPF or sender
address rewriting isn't one of his priorities. *I* do like SPF, so maybe
I will at some point create a proper patch, but it is highly unlikely that
this will happen within the next 6 months.
4 messages in net.sourceforge.lists.courier-users[courier-users] RE: SPF and Courier?
