search for: firstsaved

...e not in July is 107: [~]# doveadm fetch -u cepheid date.saved mailbox Junk 107 date.saved: 2019-05-29 05:57:55 This seems... not right. The results are similarly strange for my other users. > 2. That timestamp should also be the same in dovecot.list.index: > doveadm mailbox status -u user firstsaved Junk" For this I get: [~]# doveadm mailbox status -u cepheid firstsaved Junk Junk firstsaved=1563154976 I can't tell how that timestamp corresponds to a human-readable date, however. Cheers and thanks. --- Amir -------------- next part -------------- An HTML attachment was scrubbed....

On 8 Aug 2019, at 13:03, Amir Caspi <cepheid at 3phase.com> wrote: > IMHO the setting should apply regardless of protocol, but is that actually the case in practice? It seems to be broken. I have namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { autoexpunge = 14 days auto = subscribe special_use = \Junk } ? } and I have messages in my

On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot <dovecot at dovecot.org> wrote: > > * Amir Caspi via dovecot, 12.08.19 22:01 > >> [~]# doveadm mailbox status -u cepheid firstsaved Junk >> Junk firstsaved=1563154976 >> >> I can't tell how that timestamp corresponds to a human-readable date, however. > > [zlatko at disclosure:~]$ date -d @1563154976 > Mon Jul 15 03:42:56 CEST 2019 So this is the same timestamp as date.saved on message 1... as...

.... Is the idea to simply override the mail_location with -o ? That seems to work for doveadm mailbox but not for doveadm fetch or search # doveadm -f table mailbox status -u johan all dovecot mailbox messages recent uidnext uidvalidity unseen highestmodseq vsize guid firstsaved dovecot 0 0 1 1362145026 0 1 164208086 64bd9f0003af305190040000b9256959 1471825482 # doveadm -f table -o "mail_location=mdbox_deleted:~/mdbox" mailbox status -u johan all dovecot mailbox messages recent uidnext uidvalidity unseen highestmodseq vsize gu...

...gt; > The mailbox implicated in the backtrace ("Spam") does have a very large number of messages in it. > On sender: > Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 highestmodseq=744588 vsize=34468460093 > guid=090ed93a7a055559abf10200fdf6807a firstsaved=1498744186 > On receiver: > Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 unseen=16 highestmodseq=744589 vsize=34468496809 > guid=090ed93a7a055559abf10200fdf6807a firstsaved=1519396172 > > Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index...

* Amir Caspi via dovecot, 12.08.19 22:01 > [~]# doveadm mailbox status -u cepheid firstsaved Junk > Junk firstsaved=1563154976 > > I can't tell how that timestamp corresponds to a human-readable date, however. [zlatko at disclosure:~]$ date -d @1563154976 Mon Jul 15 03:42:56 CEST 2019 HTH, Thomas

...019, at 5.57, Amir Caspi via dovecot <dovecot at dovecot.org> wrote: > > On Aug 12, 2019, at 8:54 PM, Thomas Zajic via dovecot <dovecot at dovecot.org> wrote: >> >> * Amir Caspi via dovecot, 12.08.19 22:01 >> >>> [~]# doveadm mailbox status -u cepheid firstsaved Junk >>> Junk firstsaved=1563154976 >>> >>> I can't tell how that timestamp corresponds to a human-readable date, however. >> >> [zlatko at disclosure:~]$ date -d @1563154976 >> Mon Jul 15 03:42:56 CEST 2019 > > So this is the same timestamp...

...d trying a fresh sync. The mailbox implicated in the backtrace ("Spam") does have a very large number of messages in it. On sender: Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 highestmodseq=744588 vsize=34468460093 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1498744186 On receiver: Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 unseen=16 highestmodseq=744589 vsize=34468496809 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1519396172 Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index file /gnoc/mail/home/bge...

...d trying a fresh sync. The mailbox implicated in the backtrace ("Spam") does have a very large number of messages in it. On sender: Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 highestmodseq=744588 vsize=34468460093 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1498744186 On receiver: Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 unseen=16 highestmodseq=744589 vsize=34468496809 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1519396172 Feb 23 14:57:20 dovecot: dsync-local(bgeels): Warning: fscking index file /gnoc/mail/home/bge...

...licated in the backtrace ("Spam") does have a very large number of messages in it. On sender: Spam messages=1217764 recent=0 uidnext=1218103 uidvalidity=1379509105 unseen=16 highestmodseq=744588 vsize=34468460093 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1498744186 On receiver: Spam messages=1217766 recent=352 uidnext=1218105 uidvalidity=1379509105 unseen=16 highestmodseq=744589 vsize=34468496809 guid=090ed93a7a055559abf10200fdf6807a firstsaved=1519396172 Feb 23 14:57:20 dovecot: dsync-local(bgeels):...

...override the > mail_location with -o ? That seems to work for doveadm mailbox but not for > doveadm fetch or search > > # doveadm -f table mailbox status -u johan all dovecot > mailbox messages recent uidnext uidvalidity unseen highestmodseq vsize guid firstsaved > dovecot 0 0 1 1362145026 0 1 164208086 64bd9f0003af305190040000b9256959 1471825482 > > # doveadm -f table -o "mail_location=mdbox_deleted:~/mdbox" mailbox status -u johan all dovecot > mailbox messages recent uidnext uidvalidity unseen hig...

...th the namespace prefix (set to "INBOX/" on new server). Any hint? Thanks. show there is no messages in INBOX # doveadm mailbox status -u (myuser) all INBOX INBOX messages=0 recent=0 uidnext=1 uidvalidity=1553630060 unseen=0 highestmodseq=1 vsize=0 guid=d54cd42849739b5cb5790000ed87e144 firstsaved=18446744073709551615 show there is messages in subdirectory # doveadm mailbox status -u (myuser) all INBOX/Sent INBOX/Sent messages=253 recent=0 uidnext=8721 uidvalidity=1263328366 unseen=0 highestmodseq=256 vsize=16335358 guid=bfb2e03fdce327671e82bf173b1ccb8b firstsaved=1553634631 The command I&...

...pc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some er...

...pc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some er...

...1: removed I then use this command to query the state of the mailbox: sudo doveadm mailbox status -u local-it-support all INBOX and get this response: INBOX messages=142 recent=0 uidnext=5596 uidvalidity=1455577845 unseen=0 highestmodseq=1163 vsize=11315688 guid=2a997739f55ac2560d180000e171d23e firstsaved=1577094051 What can be happening that means that Dovecot doesn't treat a newly delivered message as unseen? Installation details: # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.21 (92477967) # OS: Linux 4.15.0-1041-aws x86_64 Ubuntu 18.04.3 LTS auth_verbose = yes a...

...pc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some er...

...pc: Add quota=imapc backend to use GETQUOTA/GETQUOTAROOT on the remote server. + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. + If dovecot.index.cache corruption is detected, reset only the one corrupted mail instead of the whole file. + doveadm mailbox status: Add "firstsaved" field. + director_flush_socket: Add old host's up/down and vhost count as parameters - More fixes to automatically fix corruption in dovecot.list.index - dsync-server: Fix support for dsync_features=empty-header-workaround - imapc: Various bugfixes, including infinite loops on some er...

...> > and I have messages in my Junk Mail from 16 July 2019 Quoting questions from Timo: "1. What's the first mail's saved-timestamp? doveadm fetch -u user date.saved mailbox Junk 1 2. That timestamp should also be the same in dovecot.list.index: doveadm mailbox status -u user firstsaved Junk" can you check that information? Sami

...mmand to query the state of the mailbox: > > sudo doveadm mailbox status -u local-it-support all INBOX > > and get this response: > > INBOX messages=142 recent=0 uidnext=5596 uidvalidity=1455577845 unseen=0 highestmodseq=1163 vsize=11315688 guid=2a997739f55ac2560d180000e171d23e firstsaved=1577094051 > > What can be happening that means that Dovecot doesn't treat a newly delivered message as unseen? > > Installation details: > # 2.2.33.2 (d6601f4ec): /etc/dovecot/dovecot.conf > # Pigeonhole version 0.4.21 (92477967) > # OS: Linux 4.15.0-1041-aws x86_64 Ubun...

...nd to use GETQUOTA/GETQUOTAROOT on the > remote server. > + passdb imap: Add allow_invalid_cert and ssl_ca_file parameters. > + If dovecot.index.cache corruption is detected, reset only the one > corrupted mail instead of the whole file. > + doveadm mailbox status: Add "firstsaved" field. > + director_flush_socket: Add old host's up/down and vhost count as > parameters > - More fixes to automatically fix corruption in dovecot.list.index > - dsync-server: Fix support for dsync_features=empty-header-workaround > - imapc: Various bugfixes, including...