Alessandro Vesely wrote:
> Julian Mehnle wrote:
> > pureperlfilter is the bootstrapping executable for Courier::Filter.
> > C:F cleans up its socket when shutting down (e.g. when told to by
> > courierfilter), but refuses to start if the socket it wants to create
> > already exists.
>
> I see. It is different from Courier's libfilter: libfilter provides for
> triggering 432 messages when filters are active but temporarily down.
> Don't you want that functionality?
Define "temporarily down".
Courier::Filter itself, as a filter module framework, is never temporarily
down. Individual modules however can return whatever
status code they want, and automatically cause a temporary error ("432 Mail
filters temporarily unavailable.") if they crash for a
given message.
> > I have been thinking about an intelligent way for C:F to detect during
> > startup if an existing socket is stale (then it may just be
> > overwritten during restart) or belongs to an already running instance
> > of C:F. But I haven't invested enough time into this yet.
>
> Shouldn't that be courierfilter's job?
What do you mean? As far as I can see, socket creation and clean-up is the
responsibility of individual courierfilters, and
Courier's `courierfilter` executable does nothing to that extent.
-------------------------------------------------------
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
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
