Package: procmail
Version: 3.22-11
Severity: minor
In the event of formail being killed unexpectedly, it can leave the
cache file in an unusable state. It appears that the fix for this is
simple, to ensure that the file is always null terminated. At
appropriate place in formail startup (I couldn't tell where), just do
the following:
fseek(idcache, -1, SEEK_END);
fwrite("\0", 1, 1, idcache);
fseek(idcache, 0, SEEK_SET);
I have been manually fixing my formail cache but a more intelligent
solution would be better.
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (990, 'testing'), (500, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.14
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Versions of packages procmail depends on:
ii libc6 2.3.5-8 GNU C Library: Shared libraries an
Versions of packages procmail recommends:
ii exim4 4.60-1 metapackage to ease exim MTA (v4)
ii exim4-daemon-light [mail-tran 4.60-1 lightweight exim MTA (v4) daemon
ii fetchmail 6.2.5.4-1 SSL enabled POP3, APOP, IMAP mail
-- no debconf information
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
