similar to: Accessing a strange mailbox

Hi, I noticed that wildcards work like the following, as described in the man page: # doveadm mailbox list -s -u bob dovecot* dovecot dovecot/pigeonhole dovecot/pigeonhole/2.0 however, wildcard subscriptions don't work: # doveadm mailbox subscribe -u bob dovecot* # doveadm mailbox list -s -u bob dovecot* dovecot dovecot* dovecot/pigeonhole

I'm looking at scripting a mechanism to delete a mailbox, which is easy with 'doveadm mailbox delete' -- however it gets complicated when there are children of arbitrary depth, for example, I may have this: restored.daily1.INBOX restored.daily1.Sent restored.daily1.Mystuff restored.daily1.Mystuff.foo I would like to delete the 'restored' mailbox and all its children (and

Hello, I'm trying to find out what the different 'doveadm mailbox create' error codes are. I've been looking through the source, but I can't seem to find them. I did determine that '65' happens when "Error: Can't create mailbox x: Mailbox already exists", but I've also received error 67, and the more mysterious error code 16640. Thanks for any

I have been working on converting people from courier maildir -> dovecot mdbox and during some of the dsync runs I'm seeing the quota_exceeded_message be printed as an Error: dsync(<user>): Error: Can't save message to mailbox INBOX: You are over quota. To avoid losing mail, immediately empty your Trash and Sent folders and \ delete emails with large attachments.

Restoring a user's mailbox yesterday resulted in 'doveadm import' panic'ing with an assertion failure and giving a backtrace: /usr/bin/doveadm import -u <user> mdbox:/maildir/riseup.net/a/<user>/.daily.1/mdbox restored_from_backups/daily1 all doveadm(<user>): Error: Transaction log

Looks like the recently added -s (for unsubscribing) option to doveadm mailbox delete went missing: root at vireo# /usr/bin/doveadm mailbox delete -u micahtest -s restored delete: invalid option -- 's' doveadm mailbox delete [-u <user>|-A] [-S <socket_path>] [-s] <mailbox> [...] although the option still is shown as valid :) micah --

I am having trouble scaling some regular dovecot cleanup operations on our servers. On a daily basis, I'm wanting to do this on each server, which contains its own isolated set of user storage: /usr/bin/doveadm expunge -A mailbox Trash* savedbefore 21d /usr/bin/doveadm expunge -A mailbox Spam savedbefore 7d /usr/bin/doveadm expunge -A mailbox Sent savedbefore 120d but these are a very

On Mon, 23 Jul 2018, Michael Wagner wrote: > here works a dovecot 2.2.27 on a raspberrypi and the behaviour is as > expected. > > doveadm -f tab fetch -u <user> "uid date.saved" mailbox Trash > uid date.saved > 314 2018-06-23 00:35:59 > 315 2018-06-23 12:39:10 > 316 2018-06-24 10:32:43 > ... > > And I have a cron script that

Hello. In our dovecvot we use mbox format with the default filesystem layout. Therefore it is not possible to have mailboxes which are subfolders of other mailboxes containing messages. The command "doveadm mailbox list" includes the file system directories, that contain only subfolders, as normal mailboxes in the output: archiv archiv/daemon archiv/dovecot Did I miss something

I've got my users in a replicated database setup and dovecot configured with two connect lines in dovecot-sql.conf: connect = host=127.0.0.1 port=3306 dbname=users user=user password=pass connect = host=127.0.0.2 port=3306 dbname=users user=user password=pass this works really well to help balance the load. However, when a new user is created, the replication information sometimes has not

It also got the bulletin out to new users without admin intervention. Sent from Mobile ________________________________ From: Doug Hardie<mailto:bc979 at lafn.org> Sent: ?2/?22/?2016 4:02 To: Dovecot Mailing List<mailto:dovecot at dovecot.org>; Timo Sirainen<mailto:tss at iki.fi> Cc: Kevin Kershner<mailto:cstkersh at outlook.com> Subject: Re: Dovecot Bulletin > On 20

We're running a huge imapc-Migration from an old Courier-IMAP to Dovecot. Courier always uses "INBOX."-prefix for his folders, so we set namespace inbox { [...] separator = . prefix = INBOX. [...] } on our new Dovecot 2.2.20 system. And also we added: imapc_list_prefix=INBOX to avoid the dublication of the INBOX prefix. At the end, doveadm/dsync/imapc see

I'm trying to determine what the best way to restore mail with mdbox is. Restoring using maildir was trivial, I just used rsync --ignore-existing which wrote any mails that were removed and didn't touch things that already existed[1]. With mdbox things have become more complicated, and I haven't found a way to restore mail that doesn't result in many message duplicates. My backup

Hi all, I mentioned this on the #dovecot irc channel, but I thought I would post here so I can provide more details. The basic problem is that when I upgraded from 2.1.4 to 2.1.7, some users no longer are able to see their folders in pine/alpine. The folders are actually there, and are subscribed (according to doveadm) and its possible to do operations on those folders, if you know the name (for

Hi, On saturday one of our dovecot machines had an OOPS, and we had to powercycle it. When it came up, it did a filesystem fsck (ext4) and fixed a couple things, but nothing in lost+found. Now, about 50 users have a problem where their indexes are corrupted. Dovecot tries to fix them, but for some reason it is failing. The users are seeing their mails duplicated and they cannot delete mails. I

> > On 29.9.2019 23.38, tovises via dovecot wrote: >> I have a quite old home server based on Debian 6.x packages using >> courier >> imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep >> my >> and my wife emails (about 25G). >> I want renew my server to Debian 10 (buster) and got a recommendation to >> use dovecot instead of

I have a quite old home server based on Debian 6.x packages using courier imap server (exim4, fetchmail, courier, apache2, squirrelmail) to keep my and my wife emails (about 25G). I want renew my server to Debian 10 (buster) and got a recommendation to use dovecot instead of courier. For this purpose I'm using a different PC as a sandbox. Debian 10 currently offer dovecot version 2.3.4.1

Hello, One of my users has a mailbox named 'INBOX.Kron & SPM' (maybe created a long time ago, when we use courier imap as pop/imap server, but I'm not sure). I can see the maildir with a doveadm list command: amateo_adm at myotis31:~$ sudo doveadm mailbox list -u <user> ... INBOX.Kron & SPM ... but I can't delete it, neithe rename it: amateo_adm at

Dear all i'm planning a transparent migration from a courier server that provides both IMAP and POP3 access to users to a remote dovecot server with both IMAP and POP3 access. I have to migrate about 2500 users for 250 GB of space. I'm using dovecot 2.2.5.4 on debian6 squeeze. To make a transparent migration i have to maintain old IMAP UIDs and POP3 UIDs, so i've read

Hello, I'm using 2.2.13 on Debian stable, and I perform regular dsync backups. Typically if there is an error, dsync can recover from it the next time it is run, but I've been encountering a new error that doesn't seem to self-heal: # /usr/bin/dsync -u gae backup ssh -i /root/.ssh/id_rsa backmaildir at internal.example /usr/bin/dsync -u micah dsync-remote(micah): Error: