On 10/26/2011 10:44 AM, Simon Brereton wrote:
On 26 October 2011 10:27, Scott Kitterman<post...@kitterman.com> wrote:
On 10/26/2011 10:17 AM, Simon Brereton wrote:
...
So my obvious question to the list is - Can I get amavis to explicity
add a header with the SPF validity, and if not, can I do this with
policyd? And if not, and I must install postfix-policyd-spf-python
or postfix-policyd-spf-perl which do you recommend and why?
...
postfix-policyd-spf-perl is very simple and is, IMO, not suitable for
anything other than hobby installs. postfix-policyd-spf-python is well
documented, supports a wide variety of configurations for different uses and
is much more complete.
I'm the last one to do any work on the Perl implementation and the developer
of the Python implementation. Unless you are severely allergic to Python
and prepared to read/modify Perl source, I'd use the Python one. It is
available as a distribution package in many distros.
Thanks for the advice. Curiously for a "hobby installs" package it
has more howtos and documentation on Google. I'm not adverse to
python, but I'd still like reassurance that two policy filters is the
way to go.. For my edification, where would you put it in my
restrictions?
I'm not sure I understand the rationale behind your current setup well
enough to make a specific recommendation. I think the documentation
shipped with both policy servers should give sufficient guidance.
The Perl implementation was done several years before the Python one and
was, for many years, shipped with Postfix, so it's not surprising that
it would show up that way. If it works for you as is, it's fine, but it
is missing a lot of options supported in the new Python implementation
(grab the source and read the documentation for details).
Scott K
