Package: getmail4
Version: 4.6.5-1
Severity: normal
By default, getmail considers a delivery to have failed if the delivery
process outputs anything to stderr, regardless of what the exit code was:
if exitcode or err:
raise getmailDeliveryError('command %s %d error (%d, %s)'
% (self.conf['command'], childpid, exitcode, err))
I can see the reason for this, but there are times when it would be
nice to be able to not fail on stderr output; nonfatal errors and warnings
can end up there too, leading to endlessly duplicated mail (because the
delivery succeeds but getmail doesn't purge the message from the server).
In particular, the default configuration of the current version of
maildrop in etch/sid prints a nonfatal warning more or less every time
it's run. It would be nice if getmail had an option to either completely
ignore stderr output if the delivery process terminated successfully, or
(ideally) to pass it through as a warning and continue.
Dnaiel
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-2-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages getmail4 depends on:
ii python 2.4.4-1 An interactive high-level object-o
ii python-support 0.5.6 automated rebuilding support for p
getmail4 recommends no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
