[Dovecot] The Status: header is forced

Charlie Brady charlieb-dovecot at e-smith.com
Fri Apr 2 01:31:34 EEST 2004


On Tue, 30 Mar 2004, Olivier Tharan wrote:

> * Charlie Brady <charlieb-dovecot at e-smith.com> (20040330 13:03):
> > > > Is the Status: header really needed in every case? This breaks
> > > > mutt which displays mails with a 'O' flag instead of 'N'.
> > 
> > Is mutt accessing the mail store directly, or via IMAP?
> 
> In this case, the mail is fetched with fetchmail and then mutt
> accesses local mailboxes.

If you want a consistent view, I'd suggest you use IMAP to access the 
mailboxes.

> > > Well, I fixed it with a procmail rule, as these headers are
> > > undoubtedly needed with other MUAs.
> > 
> > Are you sure? If so, they are broken. RFC 2076 identifies the "Status:" 
> > header as non-standard. It's used for per-message storage of flags (which 
> > is done another way by dovecot with Maildir storage).
> 
> So mutt could be broken then?
>
> But, when I fetch mail from my Dovecot server on a local machine,
> and open the mailbox with mutt, I am most likely to not have seen
> the mail before, so I do not understand why the Status: should be
> 'O'.

I don't think this has much to do with dovecot.

--
Charlie

A: Because we read from top to bottom, left to right.
Q: Why should i start my reply below the quoted text?




More information about the dovecot mailing list