Bug 40569 – listfilter.py is closed with exit status 1 and error message flooded mail.log

Bug 40569 - listfilter.py is closed with exit status 1 and error message flooded mail.log


Summary:	listfilter.py is closed with exit status 1 and error message flooded mail.log

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	Mail
Version:	UCS 4.1
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.1-0-errata
Assigned To:	Daniel Tröder
QA Contact:	Sönke Schwardt-Krummrich

URL:
Keywords:

Depends on:	40376
Blocks:
	Show dependency tree / graph

Reported:	2016-02-03 15:01 CET by Sönke Schwardt-Krummrich
Modified:	2016-09-27 12:34 CEST (History)
CC List:	3 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	1: Nuisance – not a big deal but noticeable
User Pain:	0.006
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Sönke Schwardt-Krummrich

2016-02-03 15:01:19 CET

Bug 40376 does not fix this issue. The original message of postfix/spawn is still shown. Exactly 100 seconds after last use of listfilter.py.





+++ This bug was initially created as a clone of Bug #40376 +++

I find the following message in mail.log too often (~450 times per day):

postfix/spawn[16878]: warning: command /usr/share/univention-mail-postfix/listfilter.py exit status 1

I think listfilter.py hit an error and exit with sys.exit(1). It would be nice to log the error messages of listfilter.py, to find why it suddenly exit with status 1.

There is also an try-except code block, where the exception is not logged anyway, and the return result is DUNNO (which means, you never get informed about this issue if it occurred).

Comment 1 Daniel Tröder

2016-02-03 15:06:32 CET

http://www.postfix.org/postconf.5.html#smtpd_policy_service_timeout

smtpd_policy_service_timeout (default: 100s)

    The time limit for connecting to, writing to, or receiving from a delegated SMTPD policy server.

Comment 2 Daniel Tröder

2016-02-03 16:49:52 CET

Changed listfilter.py to:
* exist gracefully when told to (receives "")

Commit: 67154
Advisory: 67155

Comment 3 Daniel Tröder

2016-02-03 16:51:54 CET

PS: the 100s was max_idle (http://www.postfix.org/postconf.5.html#max_idle).

Comment 4 Sönke Schwardt-Krummrich

2016-02-03 21:42:54 CET

OK: code change
OK: functional test → no log message if timeout has been reached and process is asked to quit
OK: YAML

Comment 5 Janek Walkenhorst

2016-02-04 14:00:27 CET

<http://errata.software-univention.de/ucs/4.1/87.html>