- dovecot - dovecot.org

best practices for migrating to new dovecot version
by Shawn Heisey 18 Jul '18

18 Jul '18

I have a machine with my mail service on it running Debian Squeeze. The version of dovecot on that server is 1.2.15. I'm building a new server with Ubuntu 18.04 (started with 16.04, upgraded in place), where the dovecot version is 2.2.33. I plan to migrate all my services to this new machine. The virtual mailboxes are on disk in maildir format, with accounts in a mysql database managed by postfixadmin. When I copy them over to the new machine, would there be any value to excluding the files that dovecot creates, and letting the new version recreate them? In one mailbox here are some of the files I am considering excluding: dovecot.index dovecot.index.cache dovecot.index.log dovecot.index.thread dovecot-keywords dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.5876ca77 There are other files under consideration, like maildirsize and maildirfolder. One that I would be sure to *not* remove is subscriptions. If there are recommendations about dovecot files in a maildir that should not be removed during a migration, please let me know. I'm aware that rebuilding this information could be slow. My own personal mailbox on the system is over 8GB in size and has well over nine hundred thousand files in it. Thanks, Shawn

4 3

Dovecot Quota and subject utf-8
by Danilo G. Baio 17 Jul '18

17 Jul '18

Hi. When a user is over quota and a message is rejected, it sends a message back changing partially the subject (depending on the size). With utf-8 it breaks the information, we noticed this behavior when the subject line uses utf-8 and it is broken in more than one line: Subject: Quêm casé erat vim id, vix ín dicit putânt, minim çónsequuntur ea iús. Agam cetêro tê eôs, ád vim ipsum tantâs expetêndis. Ut prõ vidit diçit iudicabit, cum út çômmódo Subject of a delivered message: Subject: =?UTF-8?Q?Qu=C3=AAm_cas=C3=A9_erat_vim_id=2C_vix_=C3=ADn_dicit_p?= =?UTF-8?Q?ut=C3=A2nt=2C_minim_=C3=A7=C3=B3nsequuntur_ea_i=C3=BAs=2E_Agam_?= =?UTF-8?Q?cet=C3=AAro_t=C3=AA_e=C3=B4s=2C_=C3=A1d_vim_ipsum_tant=C3=A2s_e?= =?UTF-8?Q?xpet=C3=AAndis=2E_Ut_pr=C3=B5_vidit_di=C3=A7it_iudicabit=2C_cum?= =?UTF-8?Q?_=C3=BAt_=C3=A7=C3=B4mm=C3=B3do?= Subject of a message rejected with Dovecot Quota: Subject: Rejected: =?UTF-8?Q?Qu=C3=AAm_cas=C3=A9_erat_vim_id=2C_vix_=C3=ADn_dicit_p?=? =?... Auto-Submitted: auto-replied (rejected) Precedence: bulk https://pastebin.com/raw/SWJJARga Regards. -- Danilo G. Baio (dbaio)

1 0

Dovecot and Sieve setup
by Will Merkens 17 Jul '18

17 Jul '18

I thought I had sieve working I could create the rules in TB and it says it's communicating properly and saves the file but the sieve rules do not seem to be working. when I look at /var/spool/maildir/domain/user I see Maildir Maildir =uid=1000 inside Maildir =uid=1000/sieve I see my sieve script I created Test.sieve and a tmp directory Should not this be in the main Maildir/sieve directory. -- William Merkens IT Support Analyst Userful Corporation +1 403.538.7767 ext.289 +1 866.873.0091 Suite 300 736 8th Ave SW Calgary AB T2P 1H4 Canada https://www.userful.com

2 1

dsync panic
by Infoomatic 16 Jul '18

16 Jul '18

Hi, I just upgraded from dovecot 2.2.19 to 2.3.2. "doveadm backup" worked fine in v 2.2.19, but now panics (user with shared folder): /opt/dovecot/bin/doveadm backup -u testuser -1 sdbox:/tmp/testuser dsync(standl2): Panic: file mailbox-attribute.c: line 360 (mailbox_attribute_get_stream): assertion failed: (value_r->value != NULL || value_r->value_stream != NULL) dsync(standl2): Error: Raw backtrace: /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb6fa) [0x7f43679986fa] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(+0xcb769) [0x7f4367998769] -> /opt/dovecot/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f43679069c1] -> /opt/dovecot/lib/dovecot/libdovecot-storage.so.0(+0x568ff) [0x7f4367c9d8ff] -> /opt/dovecot/bin/doveadm(dsync_mailbox_import_attribute+0x4d) [0x56234f7b68dd] -> /opt/dovecot/bin/doveadm(dsync_brain_sync_mails+0x2fd) [0x56234f7b217d] -> /opt/dovecot/bin/doveadm(dsync_brain_run+0x538) [0x56234f7adb28] -> /opt/dovecot/bin/doveadm(+0x27fec) [0x56234f793fec] -> /opt/dovecot/bin/doveadm(+0x2a0e7) [0x56234f7960e7] -> /opt/dovecot/bin/doveadm(+0x2ad7b) [0x56234f796d7b] -> /opt/dovecot/bin/doveadm(doveadm_mail_try_run+0x1fa) [0x56234f79769a] -> /opt/dovecot/bin/doveadm(main+0x45b) [0x56234f786b2b] -> /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf0) [0x7f4367523830] -> /opt/dovecot/bin/doveadm(_start+0x29) [0x56234f786ca9] regards, infoomatic

5 8

ssl_dh required, even though DH is disabled.
by Eric Toombs 16 Jul '18

16 Jul '18

Here's my config: # 2.3.2 (582970113): /etc/dovecot/dovecot.conf # OS: Linux 4.17.5-1-ARCH x86_64 Arch Linux # Hostname: vault passdb { driver = pam } protocols = imap service imap-login { inet_listener imap { port = 0 } } ssl = required ssl_cert = </etc/letsencrypt/live/myhostname.com/fullchain.pem ssl_cipher_list = ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES128-SHA:ECDHE-ECDSA-AES256-SHA:ECDHE-ECDSA-AES128-SHA256:ECDHE-ECDSA-AES256-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-RSA-AES128-SHA:ECDHE-RSA-AES256-SHA:ECDHE-RSA-AES128-SHA256:ECDHE-RSA-AES256-SHA384 ssl_key = # hidden, use -P to show it ssl_min_protocol = TLSv1.2 My filesystem is ext4. Even though I use ssl_cipher_list to forbid DH, dovecot still doesn't work unless I provide an ssl_dh, delivering the following error: Jul 14 21:48:08 vault dovecot[8349]: imap-login: Error: Failed to initialize SSL server context: Couldn't parse DH parameters: error:0906D06C:PEM routines:PEM_read_bio:no start line: Expecting: DH PARAMETERS: user=<>, rip=10.0.0.1, lip=10.0.0.2, session=<4sGi5/9w3pwKAAAB> While providing an ssl_dh is only a minor annoyance, it would be nice if I didn't have to.

2 1

Re: Letsencrypt certificate for repo.dovecot.org expired May 14th..
by DurgaPrasad - DatasoftComnet 15 Jul '18

15 Jul '18

:) Rgds/DP 9849111010 Sent from my iPhone. Pls excuse brevity and typos if any. > On 15-Jul-2018, at 5:00 PM, Aki Tuomi <aki.tuomi(a)dovecot.fi> wrote: > > certbot clearly hates me > > --- > Aki Tuomi > Dovecot oy > > -------- Original message -------- > From: "B. Reino" <reinob(a)bbmk.org> > Date: 15/07/2018 11:49 (GMT+02:00) > To: Aki Tuomi <aki.tuomi(a)dovecot.fi> > Cc: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: Letsencrypt certificate for repo.dovecot.org expired May 14th.. > > Dear Aki, > > I think the renewal failed again. The SSL certificate expired Saturday, > 14 July 2018. > > This affects (at least) the repo.dovecot.org website and debian > repository. > > Thanks, > Bernardo. > > On 2018-05-15 08:15, Aki Tuomi wrote: > > On 15.05.2018 09:14, B. Reino wrote: > >> Dear all, > >> > >> Just in case you've missed it, the certificate for repo.dovecot.org > >> just expired yesterday. > >> > >> This causes errors in e.g. apt-get update. > >> > >> Thanks in advance for fixing it, > >> > >> -- > >> B. Reino > > > > Seems something went wrong during deployment, thanks. It's fixed now. > > > > Aki

1 0

Connection closed (IDLE running for 0.001 + waiting input for
by Sophie Loewenthal 15 Jul '18

15 Jul '18

Hi, Just noticed an Android email client called K9 Mail is producing these entries in a server's dovecot log: Jul 11 21:03:28 mx1 dovecot: imap(me(a)example.org): Connection closed (IDLE running for 0.001 + waiting input for 1728.597 secs, 2 B in + 10+0 B out, state=wait-input) in=353 out=2154 Jul 11 21:03:31 mx1 dovecot: imap(me(a)example.org): Connection closed (IDLE running for 0.001 + waiting input for 1731.069 secs, 2 B in + 10+0 B out, state=wait-input) in=389 out=1910 I cannot find out what this means after googling. Any ideas? Best wishes, Sophie

2 1

Sendmail Dovecot Trouble
by John Rowan 14 Jul '18

14 Jul '18

I've been struggling trying to get Thunderbird to read e-mail off a CentOS 7 server. Sendmail writes mail in /var/spool/mail I've configured dovecot to try to read from there using Thunderbird (POP3/SMTP). The firewall allows ports 25/110. I verified I have mail in /var/spool/mail but Thunderbird is unable to retrieve that mail. I've googled sendmail / dovecot config, I've looked a the wiki but I just can't figure this out. Please don't suggest using postfix, I just want to get sendmail / dovecot working. [@mail conf.d]# dovecot --version 2.2.10 [root@mail conf.d]# dovecot -n # 2.2.10: /etc/dovecot/dovecot.conf # OS: Linux 3.10.0-327.36.3.el7.i686 i686 CentOS Linux release 7.2.1511 (AltArch) auth_mechanisms = plain login disable_plaintext_auth = no mail_location = mbox:~/mail:INBOX=/var/mail/%u mbox_write_locks = fcntl namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } protocols = ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

3 2

Re: Sendmail Dovecot Trouble
by Alexander Dalloz 14 Jul '18

14 Jul '18

Am 13.07.2018 um 17:44 schrieb Aki Tuomi: > Should your INBOX path be/var/spool/mail/%u then? /var/spool/mail is the same as /var/mail on CentOS 7 as /var/mail is a symlink. Alexander

1 0

mdbox+ ALT storage + lazyexpunge
by Matt Bryant 14 Jul '18

14 Jul '18

All, Anyone know that if you setup lazyexpounge with mdbox that as ALT storage defined, whether the mail location for namespace used by lazyexpunge also need the ALT= specified ?? rgds Matt

1 1