I checked the install dir and didn't see any release notes or anything hinting that some changes between .41 and .42 may have affected the
There aren't, at least I can't think of anything.
filtering. Its almost like the filters are never getting accessed by esmtpd. I checked the conf file in /etc (enablefiltering) and it has esmtpd as a line in it.
I'm trying to think of some other way to track it down. Can any of you courier gurus perhaps point me in the right direction? I sure would appreciate it. I modeled the safilter off the sophos avfilter(after stripping out a lot of the av stuff).
Make sure you have a courierfilter process running, as well as your own filter process(es).
You didn't mention your platform, but at least on Linux its fairly easy to check what's listening where. Using the stock dupfilter as example:
# ps auxw | grep dupfilter
daemon 30725 0.0 0.2 34400 512 ? S Aug10 0:00 dupfilter
root 7224 0.0 0.2 3548 560 pts/0 S 02:00 0:00 grep dupfilter
[EMAIL PROTECTED] courier]# ls -al /proc/30725/fd
total 0
dr-x------ 2 daemon daemon 0 Aug 11 02:00 .
dr-xr-xr-x 3 daemon daemon 0 Aug 11 02:00 ..
lr-x------ 1 daemon daemon 64 Aug 11 02:00 0 -> pipe:[1945710]
l-wx------ 1 daemon daemon 64 Aug 11 02:00 1 -> pipe:[1945708]
l-wx------ 1 daemon daemon 64 Aug 11 02:00 2 -> pipe:[1945708]
lrwx------ 1 daemon daemon 64 Aug 11 02:00 4 -> socket:[1945711]
[EMAIL PROTECTED] courier]# netstat -a | grep 1945711
unix 2 [ ACC ] STREAM LISTENING 1945711 /var/spool/courier/filters/.dupfilter
Keep in mind that in this example the actual socket is /var/spool/courier/filters/dupfilter. The socket is originally created as .dupfilter, then it is renamed to dupfilter, but netstat still shows the original socket name.
Check to see if the listening socket is present in /var/spool/courier/filters (or /usr/lib/courier/libexec/filters).
pgp00000.pgp
Description: PGP signature
