Package: spampd
Severity: normal
Hello,
Thanks for the fast responses to my previous reports - excellent
maintainer work. But here is another one..
I have the problem that, from time to time, the spampd child process is
killed due to a timeout. This makes postfix send me an error message and
refuse the mail with 4xx ("queue file write error"). Bad..
My primary wish is to stop these errors (if they are actually
errors) or error messages (if there is no error at all). If you know
what to do - please stop reading here and tell me. What follows is what
I have tried on my own and it may be misleading ;-).
I can't reproduce the behaviour in any way, but I deduced that it must
occur during reading after the DATA command, because the satimeout
(which is shorter) is not hit.
I guess that the above behaviour might occur when the client sends his
mail very slowly, but at a constant rate. The spampd timeout just counts
the seconds and doesn't care if there is data coming or not. The postfix
timeout algorithm in contrast only runs when there is no data received
at all.
I see 2 possible solutions for this problem:
- Implement postfix style timeouts for spampd.
- Implement additional spampd style timeouts for postfix. This should
make postfix do the timeout and thus not send any error mails.
But is this reasonable? I think there must be a reason why postfix
does it its way.
With this report sent to spampd you probably know what solution I
currently favour.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.7
Locale: LANG=C, [EMAIL PROTECTED]
bye
Nikolaus
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
