> Please wake me from my nightmare. I thought I had this > figured out - may > have bit off too much, lacking Perl experience and all. > > In maillog: > May 9 12:40:11 arsenic courierfilter: Starting pureperlfilter > May 9 12:40:11 arsenic courierfilter: Can't call method > "close" on an > undefined value at > /usr/local/lib/perl5/site_perl/5.8.4/Courier/Filter.pm > line 299. >
Hi there, This seems to be a problem with the Courier/Config file, where all the system paths are defined. I use the RPM build process for my RH box, and the paths there are different from the default values for Courier::Filter. The close call is for file descriptor #3, the one to signal that the filter has initialized properly, but something seems to be wrong. I never tried running the filter without setting the paths first though... What are your system paths, and how does the Courier/Config.pm file look? I'm still having some issues with logging from my filter modules, but otherwise it's working like a charm. The Dialback and Comeagain filters I wrote mimicks the pythonfilter equivialents, and in Perl there are no thread issues on my box.. Together with ClamAV as a courierfilter it works for me.. If anybody would be interested in the Perl Dialback/Comeagain filters I'll post them somewhere on my web? /Werner ------------------------------------------------------- This SF.Net email is sponsored by Sleepycat Software Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver higher performing products faster, at low TCO. http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
