Hi, I started testing dovecot for our next POP/IMAP server (nearing production state), and noticed that the Status: header is always added, with a value of 'O' or 'RO'. This happens in `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in the Maildir case. Is the Status: header really needed in every case? This breaks mutt which displays mails with a 'O' flag instead of 'N'. My dovecot is 0.99.10.4 (FreeBSD port), but the behavior is still the same in the CVS version. -- olive
* Olivier Tharan <olive at pasteur.fr> (20040326 17:34):> I started testing dovecot for our next POP/IMAP server (nearing > production state), and noticed that the Status: header is always > added, with a value of 'O' or 'RO'. This happens in > `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in > the Maildir case. > > Is the Status: header really needed in every case? This breaks > mutt which displays mails with a 'O' flag instead of 'N'.Well, I fixed it with a procmail rule, as these headers are undoubtedly needed with other MUAs. I did not find any reference on which (IMAP software or mutt) have used this header first. FYI the procmail rule: ,---- | :0 fw: formail.lock | * ^Status: R?O | | ${FORMAIL} -I "Status" `---- -- olive
[ This belongs to an old thread so I keep extra info upfront ] * Olivier Tharan <olive at pasteur.fr> (20040330 18:31):> * Olivier Tharan <olive at pasteur.fr> (20040326 17:34): > > I started testing dovecot for our next POP/IMAP server (nearing > > production state), and noticed that the Status: header is always > > added, with a value of 'O' or 'RO'. This happens in > > `lib-index/mbox/mbox-rewrite.c'. This does not seem to happen in > > the Maildir case. > > > > Is the Status: header really needed in every case? This breaks > > mutt which displays mails with a 'O' flag instead of 'N'. > > Well, I fixed it with a procmail rule, as these headers are > undoubtedly needed with other MUAs. I did not find any reference > on which (IMAP software or mutt) have used this header first.Sometimes it is good to read back some good old manual. My problem is easily solved with a single keyword in the fetchmail configuration file: 'dropstatus'. -- olive