Bug#776094: dovecot-imapd: corrupts mailbox after trying to retrieve it (fwd)

[Santiago Vila]

On Mon, May 04, 2015 at 11:43:23PM +0200, Robert Schetterer wrote:
> > BTW: Does getmail have an option doing the same as fetchmail --folder
> > option at all?
> 
> http://pyropus.ca/software/getmail/configuration.html#retriever-parameters
> 
>  All IMAP retriever types also take the following optional parameters:
> 
>     mailboxes (tuple of quoted strings) — a list of mailbox paths to
> retrieve mail from, expressed as a Python tuple. If not specified, the
> default is to retrieve mail from the mail folder named INBOX. You might
> want to retrieve messages from several different mail folders, using a
> configuration like this:
> 
>     mailboxes = ("INBOX", "INBOX.spam",
>         "mailing-lists.model-railroading")

Fine, if I wanted to use getmail I would have to use this:

mailboxes = ("inbox-b",)

> >> dig you tried fetchmail with
> >>
> >> bad-header accept ?
> > 
> > I appreciate that you are trying to help, but it seems to me that you
> > didn't read the report, or you didn't understand it.
> > 
> > Answer: No. I didn't. Why should I? The mbox was fine before I tried
> > to retrieve it. Please read the report!
> > 
> 
> sorry i wont invest any time in fetchmail, i quit with it years ago
> by tons of problems i managed to forget

But I'm not reporting a bug in fetchmail, I'm reporting a bug in dovecot.

Everything fetchmail does is to issue IMAP commands to dovecot, and it's those
IMAP commands what make the remote folder to be corrupted.

Please tell me: Is there any set of forbidden IMAP commands that one
"should not use" because of them being known to cause email corruption
in the server?

The corruption happens in the server running dovecot, not in the
client running fetchmail.

If I describe this problem with fetchmail and dovecot in the same
machine is only for simpliciry about reproducing it.