Available from the usual place:
http://phantom.dragonsdawn.net/~gordon/courier-pythonfilter/
This release features optional SQL support in its TtlDb module, so that
you can cluster courier machines running pythonfilter. This release's
support requires PostgreSQL, and the python-pgsql module fro
Jerry Amundson wrote:
> But a solution to either one solves both.
> Basically, aren't we saying(?):
> 1. As a company, mandate *no* signatures on the mail client for the
> company account.
> 2. Require SMTP AUTH.
> 3. Globally filter such that the script uses auth info to lookup
> fullname, title,
On Tue, Mar 18, 2008 at 7:55 PM, Gordon Messmer <[EMAIL PROTECTED]> wrote:
> Harry Duncan wrote:
> > On Tue, Mar 18, 2008 at 3:18 PM, Gordon Messmer <[EMAIL PROTECTED]> wrote:
> >
>
> > Are you saying that you could not modify mails with filters if the
> > mail is sent using SMTP AUTH?
> >
>
>
Sorry for the interruption, I have another few moments to continue now.
A good test regarding whether you have courier set properly to allow
SPF enabled senders to relay to you through lists is whether you are
able to receive my message, this message, through the list. This is
because I know my n
Mailing lists and SPF can conflict. It's all in the settings that the
mailing list admin
uses to forward messages. It may depend on whether the sender of the
message
being forwarded by the list has SPF enabled. If your SPF settings are 100%
correct, and you have SPF enabled, it can still be fo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi, I'm subscribed to many mailing lists, but I've been getting lots of SPF
517s, such as this:
/var/log/mail/log-2008-03-18-16:03:46:Mar 18 11:22:10 [courieresmtpd]
error,relay=209.132.176.174,from=<[EMAIL PROTECTED]>: 517 SPF
softfail [EMAIL PROT
