Package: maildrop Version: 2.0.3-1 Severity: normal maildrop has a global timeout that seems to be intended to stop non-terminating or excessively long-running filters. However, it also stops arbitrarily long messages being fetched on my system, because the mail fetcher pipes the message directly into maildrop. Hence, if the message takes too long to fetch, maildrop times out. It seems to me that maildrop needs some idea of how much CPU time it has used (or some other way of telling it has been running a filter), not merely how long it has waited.
-- System Information: Debian Release: lenny/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.18-4-686 (SMP w/1 CPU core) Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages maildrop depends on: ii courier-authlib 0.59.3-1 Courier authentication library ii esmtp-run [mail-transpo 0.5.1-4.1 User configurable relay-only MTA ii libc6 2.5-9+b1 GNU C Library: Shared libraries ii libgcc1 1:4.2-20070627-1 GCC support library ii libgdbm3 1.8.3-3 GNU dbm database routines (runtime ii libpcre3 6.7-1 Perl 5 Compatible Regular Expressi ii libstdc++6 4.2-20070627-1 The GNU Standard C++ Library v3 maildrop recommends no packages. -- no debconf information -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
