Hi friends,
here is another bug report from a Debian user. He saw some fetchmail
messages inserted in his mails. Expecting some serious brain damage
from fetchmail and tracking down this bug, we realized that user
invoked fetchmail in a small wrapper script that first closed STDIN,
STDERR and STDOUT. So, when fetchmail does a dup(), it uses one of
these, which is free. As some report functions use STDOUT as an
argument, they write data to the socket.
I understand this is a special case and that bug reporter did bad(tm)
things, but as a daemon I believe fetchmail should handle this case
robustly. A possible solution would be to use dup2() instead of
dup().
OK, I would understand if anybody thinks problem exists between
keyboard and chair. ;-)
Cheers,
Benjamin
--- Begin Message ---
Package: fetchmail
Version: 6.2.0-3
Severity: important
Tags: sid
Seemingly random messages are prepended with "fetchmail: (xxx body
octets)". Six culprit messages (out of maybe 300 received okay with this
fetchmail) can be viewed at http://dagobah.ucc.asn.au/fetchmail-dodgy.
Has started happening since I switched to using imap over ssl as the
transport.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux amidala 2.4.20 #11 Fri Feb 7 00:29:17 WST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages fetchmail depends on:
ii adduser 3.49 Add and remove users and groups
ii base-files 3.0.7 Debian base system miscellaneous f
ii debconf 1.2.23 Debian configuration management sy
ii debianutils 2.2.3 Miscellaneous utilities specific t
ii libc6 2.3.1-11 GNU C Library: Shared libraries an
ii libssl0.9.6 0.9.6h-3 SSL shared libraries (old version)
-- debconf information:
* fetchmail/confwarn:
* fetchmail/systemwide: true
* fetchmail/initdefaultswarn:
* fetchmail/runasroot: false
fetchmail/fetchidswarn:
--- End Message ---
--
.''`.
; ;' ; Debian GNU/Linux | Benjamin Drieu
`. `' http://www.debian.org/ | <benj(_at_)debian(_dot_)org>
`-