On 08/19/2010 10:42 PM, Tim Lyth wrote:
Curiously, I still have v2.4 and v2.5 of Python installed on the
system, alongside v2.6...
Having the older versions installed won't help if you run pythonfilter
with the new python. The new version will only search its own
directories for modules
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi guys,
After I upgraded the python packages on my server, I'm no getting
neither of my greylisting or SA filtering methods applied through the
PythonFilter module.
In /var/log/mail.log I have the following when I start up courier-mta:
Aug 20
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thank you Jeff,
That solved the problem.
I also took the opportunity to upgrade from v1.5 to v1.7 of
PythonFilter as I couldn't locate the tar ball I'd previously downloaded.
Curiously, I still have v2.4 and v2.5 of Python installed on the
system,
Art Sackett wrote:
Color me puzzled. Can anyone provide me a pointer in the right direction
toward the solution of this problem?
Apparently not. :(
Try stopping the courierfilter process (make sure it's actually not
running) and start it up again while you tail the log file. See if it
Greetings!
None of my installed filters (clamcour, courier-filter-perl, dupfilter,
perlfilter) will run. This is on a Debian lenny (testing) system running
Courier 0.53.3 installed from the Debian package.
I've got the expected symlinks from /etc/courier/filters/active to
I wanted to give a huge thanks to everyone who replied and said nothing
about my ignorance of how to do things.
Thanks to this list (including reading archived posts of this list) mail
filters are working beautifully now.
Once again... Thanks. Still would like to know about logging though,
Hi all. I modified my courierperlfilters recently, and after a
while, they seem to clog up, and refuse to deliver e-mail. The only
solution I've found is a hard reset (no, shutdown -r doesn't work).
Obviously when the machine is in this state, I don't have too much time to
do problem
Hi,
Searching this list I found a few messages related to outbound mail
filtering but didn't seem to find any straight answers...
Is there a simple way to identify a filter which is run only on outbound
mail? I want to check some header information on all outbound mail, but
not on inbound mail.
Sam,
I'd like to ask whether there are any obstacles from implementing allowing
the globalfilters modify the message (Dobos Sandor sent a patch some time
ago allowing this) to the main Courier distribution. I think it'd be very
useful for lots of people for implementing virus scanning on
