gdbm fatal: read error
Hello, I have installed mutt 1.5.18-6 on a 2.6.18-xenU kernel (Debian stableà with my ~/.mutt* configuration files that works on others boxes. But if I open ~/mail/inbox (maildir) which was created by procmail, I have a gdbm fatal: read error. Any idea(s) to solve this issue ? May be should I upgrade mutt ? Thank you for help. -- Alexandre Delanoë
Encoding problem when verifying GPG sigs
Hi, I have a weird encoding problem when I verify GPG sigs. The following messages shows this problem (I trimmed all unimportant parts): From si...@ruderich.org Sat Nov 14 23:02:56 2009 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable ... Danke + Gru=DF! -Urspr=FCngliche Nachricht- ... -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My text here ... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIc... -END PGP SIGNATURE- When I view this message with mutt -F /dev/null -n message everything is displayed correctly: ... Danke + Gruß! -Ursprüngliche Nachricht- ... -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 My text here ... -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) iQIc... -END PGP SIGNATURE- But if display it with mutt -n -f message and this .muttrc I get problems: set pgp_auto_decode=yes The umlauts in Gruß and Ursprüngliche are no longer displayed correctly and instead I get this: ... Danke + Gru\337! -Urspr\374ngliche Nachricht- ... [-- Error: unable to create PGP subprocess! --] [-- BEGIN PGP SIGNED MESSAGE --] My text here ... [-- END PGP SIGNED MESSAGE --] (The [-- Error: unable to create PGP subprocess! --] isn't a problem, I get the same when the message is checked with gpg. The signature is invalid though - bad formatting - maybe this could be a problem.) Do you have an idea what the source for this problem may be or could this be a bug in mutt? Thanks, Simon -- + privacy is necessary + using gnupg http://gnupg.org + public key id: 0x92FEFDB7E44C32F9 pgpTRjdAjswEP.pgp Description: PGP signature
Re: gdbm fatal: read error
* On Wed, Feb 10, 2010 12:24PM +0100 Alexandre (neonoe123...@gmail.com) muttered: I have installed mutt 1.5.18-6 on a 2.6.18-xenU kernel (Debian stableà with my ~/.mutt* configuration files that works on others boxes. But if I open ~/mail/inbox (maildir) which was created by procmail, I have a gdbm fatal: read error. Any idea(s) to solve this issue ? Maybe deleting the header cache helps? HTH, Michael -- Besides, I think [Slackware] sounds better than 'Microsoft,' don't you? (By Patrick Volkerding) PGP-Key-ID: 0xDC1A44DD Jabber: init...@amessage.de
Re: gdbm fatal: read error
Le jeudi 11 février de l'année 2010, vers 06 heures et 40 minutes, Michael Tatge écrivait: * On Wed, Feb 10, 2010 12:24PM +0100 Alexandre (neonoe123...@gmail.com) muttered: I have installed mutt 1.5.18-6 on a 2.6.18-xenU kernel (Debian stableà with my ~/.mutt* configuration files that works on others boxes. But if I open ~/mail/inbox (maildir) which was created by procmail, I have a gdbm fatal: read error. Any idea(s) to solve this issue ? Maybe deleting the header cache helps? HTH, Exactly! Thank you Michael, I did not think about it. YIH (Yes It Helped) -- Alexandre Delanoë
