search for: mdbox_deleted

Accessing or listing "mdbox_deleted" contents seems to destroy MDBOX indexes. Examples of commands which triggers this problem ($home being the home directory of $user, and mail_location being mdbox:~/mdbox): doveadm -o mail="mdbox_deleted:$home/mdbox" -f table mailbox status -u "$user" 'messages vsi...

...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 guid firstsaved dovecot 0 0 1 0 0 1 0 ddb9421479f0595bf21b0100b9256959 18446744073709551615 # dovea...

...> 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 guid firstsaved > dovecot 0 0 1 0 0 1 0 ddb9421479f0595bf21b0100b9256959 18446744073709551615...

...here too > https://dovecot.org/pipermail/dovecot/2018-July/112441.html > The location in my dovecot.conf is > > mdbox:%%h/mdbox:INDEX=/indexdisk/indexes/%%n:INDEXPVT=~/mdbox/shared/%%n This syntax is for accessing shared folders. You probably should try doveadm -Dv -o mail_location=mdbox_deleted:/path/to/mdbox fetch -u victim text ALL > I'm trying to fetch a message (for testing purposes now) based on it's guid as that is available from doveadm dump. > So my syntax is (based on the previous person who didn't get it to work). > > doveadm -o "mail_location=mdbo...

...could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords (see 10-logging.conf comment) + mdbox: Added "mdbox_deleted" storage, which can be used to access messages with refcount=0. For example: doveadm import mdbox_deleted:~/mdbox "" mailbox inbox subject oops + ssl-params: Added ssl_dh_parameters_length setting. - master process was doing a hostname.domain lookup for each created proces...

...could have been exploitable by local users. You may need to modify your setup to keep it working. See http://wiki2.dovecot.org/AuthDatabase/CheckPassword#Security + auth: Added ability to truncate values logged by auth_verbose_passwords (see 10-logging.conf comment) + mdbox: Added "mdbox_deleted" storage, which can be used to access messages with refcount=0. For example: doveadm import mdbox_deleted:~/mdbox "" mailbox inbox subject oops + ssl-params: Added ssl_dh_parameters_length setting. - master process was doing a hostname.domain lookup for each created proces...

...not get > moved .. I assume that a delete in Trash is not actually an expunge on > TB and hence does get caught by the plugin. > > 3) Since mdbox doesnt delte anything anyway until purged would it be > better not to use lazy-expunge but just have a job that moves any > messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. > does doveadm move work with mdbox_deleted ??? > > any help appreciated > > rgds > > Matt -------------- next part -------------- An HTML attachment was scrubbed... URL: <https://dovecot.org/pipermail/dovecot/attachments/201805...

...e a message ... then it does not get moved .. I assume that a delete in Trash is not actually an expunge on TB and hence does get caught by the plugin. 3) Since mdbox doesnt delte anything anyway until purged would it be better not to use lazy-expunge but just have a job that moves any messages in mdbox_deleted: storage to the hidden .EXPUNGED namespace .. does doveadm move work with mdbox_deleted ??? any help appreciated rgds Matt

Yesterday I had to recover an e-mail which a user had deleted. If I understand this correctly the message was expunged but not purged (doveadm purge had not been run). This e-mail was clearly still in the mdbox stored with zlib compression as I could tell using the doveadm dump command (doveadm dump -t dbox filename). I could however not reveal the e-mail with the normal doveadm fetch -u

You can use mdbox_deleted driver to access mails with refcount 0. See https://wiki2.dovecot.org/MailboxFormat/dbox Aki On 10.11.2020 12.42, Daniel Sch?tze wrote: > > Yesterday I had to recover an e-mail which a user had deleted.? If I > understand this correctly the message was expunged but not purged > (dovea...