Bernd Plagge wrote:
> today some customers complained that they couldn't send mails.
> Apparently pythonfilter crashed and after that no mails were send
> anymore.
> This is what the log says:
> ---
> Jan 11 10:35:48 linde courierfilter: Stopping pythonfilter
> Jan 11 10:35:51 linde courierfilter: Uncaught exception in
> "auto_whitelist" doFilter function:

That's not a pythonfilter crash. Pythonfilter catches all exceptions in
doFilter functions, and prints a trace for debugging purposes, in case
something goes wrong. What you see in the log here is pythonfilter
protecting itself from an error in one of the modules.

Since courierfilter was stopping pythonfilter, I expect that you were
restarting courier at the time. I'm not sure how messages in-process are
handled when courier shuts down, but I'm not alarmed that pythonfilter
was told to filter a message which was removed before it finished during
a shutdown.

The problem that your customers were reporting is probably earlier in
the logs. Or else they were complaining because someone shut down
courier. ;)

> man courierfilter says that "crashed filters won't be restarted".
>   

That is largely why pythonfilter has the traceback written in, rather
than letting python do it when a module fails.

> If that's the case how do I get a filter restarted - I tried "filterctl
> stop pythonfilter" and then start again. "courierfilter stop" and start.
>   

filterctl would normally do it, unless the process is stuck in a
syscall, or can't exit for some other reason. Then you might need to
restart courierfilter, too.

> Is there a single condition which ensures that courierfilter is at least 
> trying to run a particular filter? 
>   

I'm not sure what you mean.

> Besides that I'm worried that esmtp sending stopped (mail was till received).

If mail is being received, then your filters are working. If filters
stop working, you'll see something like "432 Mail filters temporarily
unavailable" in your logs.

> Is that a known "feature"?

You haven't described any design flaws or bugs in Courier, so I'd say...
yes?


> And if so is there a way to check automatically that the server is still 
> working?

Send an email to a mailbox where you can check for it. If you get it,
then the system is working.

If you want to know whether filters are broken, though, it's best to
watch the logs for an error indicating specifically that filters are not
available.


-------------------------------------------------------------------------
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services for
just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
courier-users mailing list
[email protected]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to