On 05/06/2015 09:57 AM, Teemu Huovila wrote: > On 05/05/2015 05:26 PM, Santiago Vila wrote: >> I have just verified with IMAP commands. This is the procedure: >> >> telnet localhost 143 >> >> and then type this: >> >> A0001 CAPABILITY >> A0002 LOGIN "bluser" "bluser" >> A0003 SELECT "inbox-b" >> A0004 EXPUNGE >> A0005 FETCH 1:12 RFC822.SIZE >> A0006 FETCH 1 RFC822.HEADER >> A0007 FETCH 1 BODY.PEEK[TEXT] >> A0008 STORE 1 +FLAGS (\Seen \Deleted) >> A0009 EXPUNGE >> A0010 FETCH 1 RFC822.HEADER >> A0011 FETCH 1 BODY.PEEK[TEXT] >> A0012 STORE 1 +FLAGS (\Seen \Deleted) >> A0013 EXPUNGE >> A0014 FETCH 1 RFC822.HEADER >> A0015 FETCH 1 BODY.PEEK[TEXT] >> A0016 STORE 1 +FLAGS (\Seen \Deleted) >> A0017 EXPUNGE >> A0018 FETCH 1 RFC822.HEADER >> A0019 FETCH 1 BODY.PEEK[TEXT] >> A0020 STORE 1 +FLAGS (\Seen \Deleted) >> A0021 EXPUNGE >> A0022 FETCH 1 RFC822.HEADER >> A0023 FETCH 1 BODY.PEEK[TEXT] >> A0024 STORE 1 +FLAGS (\Seen \Deleted) >> A0025 EXPUNGE >> A0026 FETCH 1 RFC822.HEADER >> A0027 FETCH 1 BODY.PEEK[TEXT] >> A0028 STORE 1 +FLAGS (\Seen \Deleted) >> A0029 EXPUNGE >> A0030 FETCH 1 RFC822.HEADER >> A0031 FETCH 1 BODY.PEEK[TEXT] >> A0032 STORE 1 +FLAGS (\Seen \Deleted) >> A0033 EXPUNGE >> A0034 FETCH 1 RFC822.HEADER >> A0035 FETCH 1 BODY.PEEK[TEXT] >> A0036 STORE 1 +FLAGS (\Seen \Deleted) >> A0037 EXPUNGE >> A0038 FETCH 1 RFC822.HEADER >> A0039 FETCH 1 BODY.PEEK[TEXT] >> A0040 STORE 1 +FLAGS (\Seen \Deleted) >> A0041 EXPUNGE >> A0042 FETCH 1 RFC822.HEADER >> A0043 FETCH 1 BODY.PEEK[TEXT] >> A0044 STORE 1 +FLAGS (\Seen \Deleted) >> A0045 EXPUNGE >> A0046 FETCH 1 RFC822.HEADER >> A0047 FETCH 1 BODY.PEEK[TEXT] >> A0048 STORE 1 +FLAGS (\Seen \Deleted) >> A0049 EXPUNGE >> A0050 FETCH 1 RFC822.HEADER >> A0051 LOGOUT >> >> After this, mbox folder inbox-b is corrupted, as the line saying >> >> From: abcdefghijklmnopqrstuvwxyzabcdefghijklmnopqrstuvw...@example.com >> >> becomes >> >> rstuvwxyzabcdefghijklmnopqrstuvw...@example.com >> >> >> So: Could we please stop blaming fetchmail for this? >> It's just the messenger. > Could you also sprovide your "dovecot -n" output and any warnings and errors > in dovecot logs. Ah, found the dovecot -n earlier in the thread, but the logs would still be relevant.
Teemu
