Ok, It's confusing because the perlfilter works a little differently. According to the courierperlfilter manpage, there is a perlfilter wrapper binary in /usr/lib/courier/libexec/filters, and that wrapper will run whatever perl script is referenced in /etc/courier/filters/perlfilter.
> > # cat /etc/courier/filters/perlfilter > > /usr/lib/courier/libexec/filters/perlfilter.pl > > That's still confusing me. When I start a filter, it doesn't put > anything in /etc/courier/filters/. Did you create the "perlfilter" > file? Why isn't the file in /etc/courier/filters/active a symlink to > the perl script? What does the contents of > /usr/lib/courier/libexec/filters look like? So, /etc/courier/filters/perlfilter is considered a "configuration file" which points to the actual script that the perlfilter wrapper will run. And in this case, the active file is a symlink to the perlfilter wrapper binary. I've tried writing to STDERR in my perl script, but I still see nothing in the logs... Has anyone else worked with perlfilter that might know what's wrong? Ricardo ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
