I think all of those are considered now except that it will still error out on
the malformed packet. I'm not sure an automatic fallback on error is the
right answer.
The patch that's coming looks to see if the truncate flag is set and retries
if it is. The inconsistent behavior you saw was
On Monday 24 March 2008 16:48, John Neffenger wrote:
> You mean "master.cf", right? Putting the configuration file as an
> argument in "main.cf" caused Postfix to reject all mail with "451 4.3.5
> Server configuration error."
Yes. Additionally I'm preparing an upload now so that python-spf will
Apologies. In upstream terms 0.4 is a long time ago (I'm also the upstream
developer for python-policyd-spf). 0.4 had a bug in it and that config
option doesn't actually work in that release. I'm trying to reconstruct how
I fixed it so I can give you a patch.
--
python-policyd-spf failing o
That's enough information. I'll have a look at it. I suspect this is
either a pthyon-dns limitation or a router firewall issue. DNS via TCP is
generally risky and not recommended.
--
python-policyd-spf failing on AOL SPF records.
https://bugs.launchpad.net/bugs/205254
You received this bug n
