Joseph Tam wrote: [dd]> > Whether you use any of them is up to you. As I said, direct mailbox > file access will work. However, if you deal with Gb size mailboxes, > re-indexing and general mail operations will be painful. > > > My mail goes through procmail, so Dovecot will not be the only one to > > touch the mboxes anyway. > > Not a deterrent: replace all mailbox recipies with a pipe to dovecot's LDA > > :0 ... pattern ... > | /path/to/dovecot-lda -d {user} -m {mailbox} > > ... > > # End of file: deliver to inbox > :0 w > | /path/to/dovecot-lda -d {user} >This will clutter up ~/.procmailrc, but may be I'll try someday. Now I have encountered a different problem. My Android IMAP client (the Gmail map) shows lots of mails in my Inbox. However, I already deleted those mails locally from /var/mai/vas. They are being cached somewhere. Is it not dovecot caching them? Nor can I find a way to forcefully rescan an IMAP folder in the Gmail app. -- Victor Sudakov, VAS4-RIPE, VAS47-RIPN 2:5005/49 at fidonet http://vas.tomsk.ru/
This time an Android IMAP client complains about the "unexpected end
of the network stream" while opening a mailbox named "dss", and
dovecot logs:
Sep 28 23:01:34 admin dovecot: imap-login: Login: user=<vas>,
method=PLAIN, rip=78.140.19.131, lip=95.179.154.55, mpid=85536, TLS,
session=<6ITSkfB2JfNOjBOD>
Sep 28 23:01:35 admin dovecot: Error:
imap(vas)<85536><6ITSkfB2JfNOjBOD>: Corrupted record in index cache
file /home/vas/Mail/.imap/dss/dovecot.index.cache: UID 56: Broken physical size
in mailbox dss: read(/home/vas/Mail/dss) failed: Cached message size smaller
than expected (8271 < 8282, box=dss, UID=56)
Sep 28 23:01:35 admin dovecot: Error:
imap(vas)<85536><6ITSkfB2JfNOjBOD>: Mailbox dss: UID=56:
read(/home/vas/Mail/dss) failed: Cached message size smaller than expected (8271
< 8282, box=dss, UID=56) (FETCH BODY[2])
Sep 28 23:01:35 admin dovecot: imap(vas)<85536><6ITSkfB2JfNOjBOD>:
FETCH read() failed in=896 out=54723 deleted=0 expunged=0 trashed=0 hdr_count=15
hdr_bytes=7777 body_count=14 body_bytes=37063
Sep 28 23:02:54 admin dovecot: imap-login: Login: user=<vas>,
method=PLAIN, rip=78.140.19.131, lip=95.179.154.55, mpid=85560, TLS,
session=<x6mSlvB2NN1OjBOD>
Sep 28 23:02:55 admin dovecot: Error:
imap(vas)<85560><x6mSlvB2NN1OjBOD>: Corrupted record in index cache
file /home/vas/Mail/.imap/dss/dovecot.index.cache: UID 27: Broken physical size
in mailbox dss: read(/home/vas/Mail/dss) failed: Cached message size smaller
than expected (4867 < 4878, box=dss, UID=27)
Sep 28 23:02:55 admin dovecot: imap(vas)<85560><x6mSlvB2NN1OjBOD>:
Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed:
(old_size <= _stream->pos - _stream->skip)
Sep 28 23:02:55 admin dovecot: imap(vas)<85560><x6mSlvB2NN1OjBOD>:
Fatal: master: service(imap): child 85560 killed with signal 6 (core not dumped
- https://dovecot.org/bugreport.html#coredumps - set service imap {
drop_priv_before_exec=yes })
Is this that corrupted index case? It even causes the panic in the
daemon. Can I fix the index or somehow reindex the mailbox?
--
Victor Sudakov, VAS4-RIPE, VAS47-RIPN
2:5005/49 at fidonet http://vas.tomsk.ru/
> On 28 September 2018 at 19:07 Victor Sudakov <vas at mpeks.tomsk.su> wrote: > > > This time an Android IMAP client complains about the "unexpected end > of the network stream" while opening a mailbox named "dss", and > dovecot logs: > > Sep 28 23:01:34 admin dovecot: imap-login: Login: user=<vas>, method=PLAIN, rip=78.140.19.131, lip=95.179.154.55, mpid=85536, TLS, session=<6ITSkfB2JfNOjBOD> > Sep 28 23:01:35 admin dovecot: Error: imap(vas)<85536><6ITSkfB2JfNOjBOD>: Corrupted record in index cache file /home/vas/Mail/.imap/dss/dovecot.index.cache: UID 56: Broken physical size in mailbox dss: read(/home/vas/Mail/dss) failed: Cached message size smaller than expected (8271 < 8282, box=dss, UID=56) > Sep 28 23:01:35 admin dovecot: Error: imap(vas)<85536><6ITSkfB2JfNOjBOD>: Mailbox dss: UID=56: read(/home/vas/Mail/dss) failed: Cached message size smaller than expected (8271 < 8282, box=dss, UID=56) (FETCH BODY[2]) > Sep 28 23:01:35 admin dovecot: imap(vas)<85536><6ITSkfB2JfNOjBOD>: FETCH read() failed in=896 out=54723 deleted=0 expunged=0 trashed=0 hdr_count=15 hdr_bytes=7777 body_count=14 body_bytes=37063 > Sep 28 23:02:54 admin dovecot: imap-login: Login: user=<vas>, method=PLAIN, rip=78.140.19.131, lip=95.179.154.55, mpid=85560, TLS, session=<x6mSlvB2NN1OjBOD> > Sep 28 23:02:55 admin dovecot: Error: imap(vas)<85560><x6mSlvB2NN1OjBOD>: Corrupted record in index cache file /home/vas/Mail/.imap/dss/dovecot.index.cache: UID 27: Broken physical size in mailbox dss: read(/home/vas/Mail/dss) failed: Cached message size smaller than expected (4867 < 4878, box=dss, UID=27) > Sep 28 23:02:55 admin dovecot: imap(vas)<85560><x6mSlvB2NN1OjBOD>: Panic: file istream.c: line 315 (i_stream_read_memarea): assertion failed: (old_size <= _stream->pos - _stream->skip) > Sep 28 23:02:55 admin dovecot: imap(vas)<85560><x6mSlvB2NN1OjBOD>: Fatal: master: service(imap): child 85560 killed with signal 6 (core not dumped - https://dovecot.org/bugreport.html#coredumps - set service imap { drop_priv_before_exec=yes }) > > > Is this that corrupted index case? It even causes the panic in the > daemon. Can I fix the index or somehow reindex the mailbox? > > -- > Victor Sudakov, VAS4-RIPE, VAS47-RIPN > 2:5005/49 at fidonet http://vas.tomsk.ru/You can use doveadm force-resync -u vas "*" Aki