Re: Home Directory Creation

On 2.10.2019 4.00, Asai via dovecot wrote: > Hello, > > I hate to have to ask this, but... why isn't the home directory being > created automatically? > > Due to legacy compatibility we've had to use this type of home dir > config: > > mail_location = maildir:/vmail/%d/%n > mail_home = /vmail/%d/

Re: Home Directory Creation

Asai via dovecot skrev den 2019-10-02 03:00: https://doc.dovecot.org/configuration_manual/home_directories_for_virtual_users/#home-directories-for-virtual-users mail_home = /var/vmail/%d/%n mail_location = maildir:~/mail little diff Hello, Thanks for replying.  I understand that that's i

Re: Home Directory Creation

Asai via dovecot skrev den 2019-10-02 03:00: mail_location = maildir:/vmail/%d/%n mail_home = /vmail/%d/%n/home Can anyone point me in the right direction? https://doc.dovecot.org/configuration_manual/home_directories_for_virtual_users/#home-directories-for-virtual-users mail_home = /var/v

Home Directory Creation

Hello, I hate to have to ask this, but... why isn't the home directory being created automatically? Due to legacy compatibility we've had to use this type of home dir config: mail_location = maildir:/vmail/%d/%n mail_home = /vmail/%d/%n/home We're in the middle of upgrading to new hardware,

Re: Unable to connect/authenticate after Debian SSL update

And as usually happens, right after posting this I found the problem by looking in the right place!: Oct 01 17:06:58 Error: pop3-login: Failed to initialize SSL server context: Can't load DH parameters: error:1408518A:SSL routines:ssl3_ctx_ctrl:dh key too small: user=<>, rip=199.73.114.98, li

Unable to connect/authenticate after Debian SSL update

Just applied Debian SSL updates, due to vulnerabilities reported: "Package: openssl CVE ID : CVE-2019-1547 CVE-2019-1549 CVE-2019-1563 Three security issues were discovered in OpenSSL: A timing attack against ECDSA, a padding oracle in PKCS7_dataDecode() and CMS_decrypt_set1_pk

UNSEEN flag issues with multiple clients

Hi all, I've been bugged by this issue for a while, and while I see that the \UNSEEN flag is specified in the RFC to be reset once *any* client connects and looks at a mailbox, I was wondering if there's a way to change the behavior so that it's tracked on a per-client basis? Or if there's even

Re: [ext] Re: dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

> > This command quickly pointed to > > ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp > > That file was written excessively. > > Was it one user's dovecot.index.tmp or for a lot of users? There's just one user. All mail goes to one mailbox. > This > means that dovecot.index is being re

Lost mails with sieve "duplicate" extension in case of failure

Hi! we just experienced the following issue: We have a global sieve_before script using the duplicate extension. require ["duplicate", "imap4flags"]; if duplicate { discard; } Now the storage of our mailbox store got full and lmtp deliveries started to fail. This resulted in logs like this

Re: dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

On 1 Oct 2019, at 16.31, Ralf Hildebrandt via dovecot wrote: > > I set up system copying all mails to a backup system. > > This used to work without a hitch - now in the last few days mails > would pile up in the Postfix Queue, waiting to be delivered using the > lmtp transport into dovecot. >

Fwd: lmtp and virtual users

Good morning. I was just reading https://wiki.dovecot.org/AuthDatabase/LDAP/PasswordLookups and found the following statement > When using LDA and static userdb, > deliver can check if destination user exists. With auth binds this > check isn't possible. Is this sti

Re: [ext] dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

* Ralf Hildebrandt via dovecot : > But why is that? Why would the index file be updated so often? BTW: This post is a followup to my "2.3.7 slower than 2.3.6?" post from back in July.

dovecot 2.3.7.2-1~bionic: Performance issues caused by excessive IO to ~/mdbox/mailboxes/INBOX/dbox-Mails/dovecot.index.tmp

I set up system copying all mails to a backup system. This used to work without a hitch - now in the last few days mails would pile up in the Postfix Queue, waiting to be delivered using the lmtp transport into dovecot. So dovecot was being slow, but why? After all, nothing changed. After readin

Re: Mailbox INBOX sync: mailbox_delete failed

Am 01.10.19 um 11:31 schrieb Sami Ketola: > > >> On 1 Oct 2019, at 12.20, Alex La via dovecot wrote: >> >> Hi. >> >> When I run the backup I always get this error. >> >> ``` >> [r...@mail.domain.com:~]# doveadm -o mail_fsync=never backup -D -R -u >> off...@domain.com imapc: >> >> dsync(off...@do

Re: Mailbox INBOX sync: mailbox_delete failed

> On 1 Oct 2019, at 12.20, Alex La via dovecot wrote: > > Hi. > > When I run the backup I always get this error. > > ``` > [r...@mail.domain.com:~]# doveadm -o mail_fsync=never backup -D -R -u > off...@domain.com imapc: > > dsync(off...@domain.com): Info: imapc(imap.mailbox.org:993): Connec

Mailbox INBOX sync: mailbox_delete failed

Hi. When I run the backup I always get this error. ``` [r...@mail.domain.com:~]# doveadm -o mail_fsync=never backup -D -R -u off...@domain.com imapc: dsync(off...@domain.com): Info: imapc(imap.mailbox.org:993): Connected to 2001:67c:2050:106::143:199:993 (local 2a01:4f8:c2c:6d05::1:59928) dsync

Re: Migration

Am 01.10.19 um 10:32 schrieb Sami Ketola via dovecot: > > >> On 1 Oct 2019, at 11.29, Alex La via dovecot > > wrote: >> >> Am 30.12.18 um 10:53 schrieb Sami Ketola: >>> On 29 Dec 2018, at 23.49, Hans Brage >>> > wrote: Hi! >>>

Re: Migration

> On 1 Oct 2019, at 11.29, Alex La via dovecot wrote: > > Am 30.12.18 um 10:53 schrieb Sami Ketola: >> >>> On 29 Dec 2018, at 23.49, Hans Brage wrote: >>> >>> Hi! >>> >>> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire >>> that server. I've set up an new server

Re: Migration

Am 30.12.18 um 10:53 schrieb Sami Ketola: > >> On 29 Dec 2018, at 23.49, Hans Brage wrote: >> >> Hi! >> >> I'm currently running an small imap-server on Dovecot 2.2.4 but will retire >> that server. I've set up an new server with Dovecot 2.3.4 and will migrate >> the mailboxes (maildir-format)

Re: Best way to move mail from one server to another

Hi Robert. Am 06.09.18 um 08:50 schrieb Robert Schetterer: > Am 05.09.2018 um 07:37 schrieb Aki Tuomi: >> >>> On 04 September 2018 at 23:20 Robert Schetterer wrote: >>> >>> >>> Am 04.09.2018 um 18:27 schrieb Sami Ketola: > On 4 Sep 2018, at 18.38, Robert Schetterer wrote: > >>>

Re: courier to dovecot migration

> On 30 Sep 2019, at 14.07, tovises via dovecot wrote: > Tath's help! But something still missing :( > > $ sudo doveadm -D -o imapc_user=tovis -o imapc_password= -o > imapc_host=nusi -R -u tovis imapc: > > Exited with messages (excerption - too many private information exposed): > > dsync(tov

Re: courier to dovecot migration

Hi. Am 30.09.19 um 13:07 schrieb tovises via dovecot: >> >> On 30.9.2019 13.40, tovises wrote: > On 30 Sep 2019, at 13.13, tovises via dovecot > wrote: > WOW! - amazing quickly, I'm really grateful. > > I was using: -u tovis imapc: nusi but still something wrong. > Pa