Ben Kennedy wrote: > > Hey all, > > I've been having a slightly annoying issue with mail filters. > Specifically, doing 'courierfilter stop' or otherwise having courier stop > or restart leaves sockets kicking around, leading to "socket already > exists" log messages and/or "432 Mail filters temporarily unavailable" > rejections.
The socket should remain there to trigger the "432 ..." message. Using courierfilter stop one can maintain a global filter without would-be-bounced messages taking advantage of that pause. The remote server should retry sending after a reasnably short time. When the filter restarts it opens the socket with a temporary name and then moves it to its final place, replacing the old one. To delete the socket for good one uses filterctl. "socket already exists" is an error I never got. (But then I don't use perlfilter.) Perhaps strace might reveal some more? > srw-rw---- 1 mail mail 0 Apr 14 15:09 perlfilter I have the same permissions, and drwxr-x--- on the directory. > In this example, pureperlfilter is cleaning up its socket (though > sometimes for whatever reason the socket stays around causing it to > refuse to launch subsequently); perlfilter is not removing its. IMHO, the latter is correct. But again, I have no experience with pureperlfilter. Shouldn't it work the same way? ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ courier-users mailing list courier-users@lists.sourceforge.net Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
