- dovecot - dovecot.org

outlook idiocy - IMAP folders with /
by Wojciech Puchar 20 Dec '18

20 Dec '18

user attempts to create folders with / dovecot naturally cannot create it so it returns error but outlook of course "create" it and keep data in local store only. data is lost when you remove local store .pst file. The question is - can dovecot be configured so it will automatically replace slash in name with something else?

8 15

SIS feature request
by Daniel Miller 20 Dec '18

20 Dec '18

I tried SIS a couple years ago - I was very excited with the resulting decrease in storage requirements but the undiagnosed intermittent issues became too significant to ignore so I switched away. Recently I was thinking about it again. The primary issue with SIS seemed to be links would be deleted even though the source attachment files and related mails still existed. It was possible to either manually re-build the links or have a script scan the mail error log and perform such. I haven't looked at the code - but a thought for a possible "temporary" fix: 1. Whatever function in dbox code that performs the deletion of links - prior to actually deleting call a new function that will verify if any mails exist that reference it. A new function, without modifying existing code, may catch something the existing functions don't - and if it logs the fact that it was called and found something...perhaps we can find the flaw in the original algorithm. Just a thought. 2. In the mail retrieval function, if the attachment link doesn't exist - perform the relevant scan through the attachment database and if found re-create the link automatically. This should log an error but indicate the recovery. -- Daniel

1 0

Intentionally use weak server key
by Stavros Tsolakos 20 Dec '18

20 Dec '18

Hi list! For some reason I need to use a really weak server key (256 bit) with dovecot for imaps access. Is this possible? I tried but getting this error: dovecot: imap-login: Error: SSL: Stacked error: error:04075070:rsa routines:RSA_sign:digest too big for rsa key This is on an Ubuntu 14.04 on x64. Thank you! Stavros

4 7

High Load average on NFS Spool - v.2.1.15 & 2.2.13
by Albert E. Whale, CEH CHS CISA CISSP 19 Dec '18

19 Dec '18

I have two servers pointing to an NFS mounted mail spool with dovecot. Since I recently switched from using Dovecot v1.X, I have been experiencing high CPU use with the two Dovecot servers. I am not certain why they are not well behaved. Here is the configuration information. This configuration is currently running at a load average of 17. /usr/sbin/dovecot -n # 2.1.15: /etc/dovecot/dovecot.conf # OS: Linux 3.10.54-server-2.mga3 i686 Mageia 3 base_dir = /var/run/dovecot/ disable_plaintext_auth = no lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_debug = yes mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mbox_lock_timeout = 15 mins mmap_disable = yes passdb { driver = pam } protocols = imap pop3 service anvil { client_limit = 203 process_limit = 1 } service auth { user = root } service imap-login { chroot = login client_limit = 10 user = dovecot vsz_limit = 256 M } service pop3-login { chroot = login client_limit = 20 user = dovecot } ssl = no syslog_facility = local2 userdb { driver = passwd } verbose_proctitle = yes protocol pop3 { mail_max_userip_connections = 20 pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_uidl_format = %08Xv%08Xu } protocol lda { postmaster_address = postmaster(a)example.com } protocol imap { mail_max_userip_connections = 10 } And the other server which is currently running with a load average of 10. dovecot -n # 2.2.13: /etc/dovecot/dovecot.conf doveconf: Warning: service anvil { client_limit=100 } is lower than required under max. load (303) # OS: Linux 4.1.15-server-2.mga5 x86_64 Mageia 4 base_dir = /var/run/dovecot/ disable_plaintext_auth = no listen = * lock_method = dotlock login_greeting = SpamZapper Email ready. login_log_format_elements = user=<%u> method=%m rip=%r lip=%l %c mail_fsync = always mail_location = maildir:~/Maildir mail_nfs_index = yes mail_nfs_storage = yes mail_privileged_group = mail mmap_disable = yes passdb { driver = pam } protocols = imap pop3 service anvil { client_limit = 100 process_limit = 1 } service auth { user = root } service imap-login { chroot = login client_limit = 48 user = dovecot vsz_limit = 256 M } service pop3-login { chroot = login client_limit = 50 user = dovecot } ssl = no syslog_facility = local2 userdb { driver = passwd } verbose_proctitle = yes protocol pop3 { mail_max_userip_connections = 50 pop3_logout_format = top=%t/%p, retr=%r/%b, del=%d/%m, size=%s pop3_uidl_format = %08Xv%08Xu } protocol lda { postmaster_address = postmaster(a)example.com } protocol imap { mail_max_userip_connections = 40 } Can you please offer a suggestion on what is happening? The timeouts to the imap server are frequent due to the load average. Thank you. -- -- -- Albert E. Whale, CEH CHS CISA CISSP *President - Chief Info Security Officer* IT Security, Inc. <http://www.IT-Security-inc.com> - A Service Disabled Veteran Owned Company - (*SDVOSB*) *HUBZone Certified* LinkedIn <https://www.linkedin.com/in/albertwhale> Profile Phone: 412-515-3010 | Email: Albert.Whale(a)IT-Security-inc.com Cell: 412-889-6870

3 5

Re: How to configure Dovecot to disable NIST's curves and still rertain EECDH?
by Kurt Fitzner 19 Dec '18

19 Dec '18

My opinion is that security by RFC is not security, it's mommy medicine. Standards have had a terrible time keeping up with security realities. NITS's curves leak side channel information all over the place. I don't have details on what implementations are set to calculate the NIST curves in constant time, and that's not an easy feat to do anyway so I don't want to depend on implementations that say they are actually doing it the right way. Frankly I can't be bothered to keep up with that. There are better curves TODAY, so yes I intend to use them if I can find a way. Otherwise, I'll just keep EECDH disabled. I have EDH now, and I've not yet run into a client that doesn't support it. I want EECDH, but I won't use it without safe curves. I'm confident that EECDH with safe curves and a second choice of EDH will support any clients that are worth using. OpenSSL supports X25519, and that is half the battle. Is there a way to change the curve selection in Dovecot? On 2018-12-19 01:49, Tributh via dovecot wrote: > Do you really plan to do this? > RFC 8446 section 9.1: > A TLS-compliant application MUST support key exchange with secp256r1 > (NIST P-256) and SHOULD support key exchange with X25519 > > I think your idea could be not future proved. > > Beside that, how many mail-clients will remain usable with this cipher > selection? > > Torsten

2 1

How to configure Dovecot to disable NIST's curves and still rertain EECDH?
by Kurt Fitzner 19 Dec '18

19 Dec '18

I am interested in configuring Dovecot's TLS so as to retain forward secrecy, but eliminate all of NIST's elliptic curves. Besides being subject to side channel attacks [1], in some quarters there is a general distrust of NIST's curves and any of their other cryptographic primitives after the Dual EC DRBG debacle. >From what I can tell, the following will prevent the use of NIST's curves (along with other dangerous primitives) in Dovecot, but this is accomplished by simply disabling EECDH entirely. ssl_cipher_list = HIGH:!DSS:!EECDH:!ECDH:!SHA1:!aNULL:!eNULL:@STRENGTH This should still retain forward secrecy through the use of EDH, but this doesn't leave much in the way of allowable algorithms on my server: $ openssl ciphers -V 'HIGH:!DSS:!EECDH:!ECDH:!SHA1:!aNULL:!eNULL:@STRENGTH' 0x00,0x9F - DHE-RSA-AES256-GCM-SHA384 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(256) Mac=AEAD 0x00,0x6B - DHE-RSA-AES256-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(256) Mac=SHA256 0x00,0x9D - AES256-GCM-SHA384 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(256) Mac=AEAD 0x00,0x3D - AES256-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(256) Mac=SHA256 0x00,0x9E - DHE-RSA-AES128-GCM-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AESGCM(128) Mac=AEAD 0x00,0x67 - DHE-RSA-AES128-SHA256 TLSv1.2 Kx=DH Au=RSA Enc=AES(128) Mac=SHA256 0x00,0x9C - AES128-GCM-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AESGCM(128) Mac=AEAD 0x00,0x3C - AES128-SHA256 TLSv1.2 Kx=RSA Au=RSA Enc=AES(128) Mac=SHA256 Is there a better way to do this? Is there a way to disable only the suspect NIST curves and still retain EECDH but with side-channel safe curves like X25519? Thanks, Kurt Fitzner Links: ------ [1] https://blog.cr.yp.to/20140323-ecdsa.html

2 1

Errors with missing links to files when using Single Instance Storage and zlib (Dovecot 2.3.4)
by Daniel Schütze 18 Dec '18

18 Dec '18

I'm running Dovecot 2.3.4 with Single Instance Storage (SIS) and zlib and I am frequently seeing errors where files are missing in the attachments directory even though the zipped file in the hash directory is actually there. This appears not to have been an issue in Dovecot 2.3.1 Requested output of the server below. The error looks like this in the log Dec 18 08:58:58 dovecot01 dovecot: imap(username)<3692><RKnPGEh9fC3AqAAB>: Error: Mailbox INBOX/FOLDER: UID=41: read(attachments-connector(zlib(/usr/home/vmail/mail/username//mdbox/storage/m.411))) failed: read(/usr/home/vmail/attachments/91/08/91085773a0774909207852b8f9c98dbe22fe5a31-e88ba0276aae135cd2050000d09efc50[base64:19 b/l]) failed: open(/usr/home/vmail/attachments/91/08/91085773a0774909207852b8f9c98dbe22fe5a31-e88ba0276aae135cd2050000d09efc50) failed: No such file or directory (FETCH BODY[]) I'm also seeing errors when replication fails dovecot: dsync-local(username)<bzg3MqjhGFxmFwAAzRvpBw>: Error: dsync(servername): read(attachments-connector(zlib(/usr/home/vmail/mail/username//mdbox/storage/m.413))) failed: read(/usr/home/vmail/attachments/45/42/4542dcf385f6b4a4dc8752b96db1d7ad8a8023d5-ac735007f6bd135c93440100cd1be907[base64:19 b/l]) failed: open(/usr/home/vmail/attachments/45/42/4542dcf385f6b4a4dc8752b96db1d7ad8a8023d5-ac735007f6bd135c93440100cd1be907) failed: No such file or directory (last sent=mail, last recv=mail (EOL)) It is not the case that every replication fail has a corresponding imap access fail. I am running Dovecot 2.3.4 on FreeBSD11.2 and I did not see this error on Dovecot 2.3.1 FreeBSD 10.4. Both installs had the same configuration for Dovecot. Both installs were made from source code and not packages (as the need for the non standard fts and mysql options). During my testing I had the 2.3.1 install receive mail and replicate to the 2.3.4 and that was working fine (except for tcp connection issues which I saw was fixed in the changelog). Unfortunately having gone into testing with real account and mail being sent to the 2.3.4 install I'm seeing the above errors. My clients are using Thunderbird on desktops and Roundcube for webmail. My users report they can see the e-mails fine in their webmail (Roundcube) and only Thunderbird is giving issues. I admit I don't know how this can be the case as both systems use the same account details. In everycase so far there is a file in the hashes directory I have hand crafted the missing file (i.e. link) using ln and this restores access in Thunderbird. Clearly this is an big issue for my install and I'd appreciate any help! At the moment it looks like my course will be to try and script creation (recreation?) of the links from the error logs (I've seen people talking about this online) but that isn't really what I'm after. DOVECOT CONFIG # 2.3.4 (0ecbaf23d): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.5.4 (60b0f48d) # OS: FreeBSD 11.2-RELEASE-p5 amd64 # Hostname: dovecot01.cwa.uk.com dict { acl = mysql:/usr/local/etc/dovecot/dovecot-dict-sql.conf.ext } disable_plaintext_auth = no doveadm_password = # hidden, use -P to show it first_valid_uid = 145 last_valid_uid = 145 mail_access_groups = mail mail_attachment_dir = /usr/home/vmail/attachments mail_attachment_min_size = 64 k mail_gid = vmail mail_location = mdbox:~/mdbox:INDEX=/indexdisk/indexes/%n mail_plugins = " fts fts_solr acl zlib notify replication" mail_privileged_group = mail mail_uid = vmail managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext namespace { list = yes location = mdbox:%%h/mdbox:INDEXPVT=~/mdbox/shared/%%n prefix = shared/%%n/ separator = / subscriptions = yes type = shared } namespace inbox { inbox = yes location = mailbox Drafts { auto = subscribe special_use = \Drafts } mailbox Junk { auto = subscribe special_use = \Junk } mailbox Sent { auto = subscribe special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { auto = subscribe special_use = \Trash } prefix = type = private } passdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } plugin { acl = vfile acl_shared_dict = proxy::acl fts = solr fts_autoindex = yes fts_solr = url=http://localhost:8983/solr/dovecot/ mail_replica = tcp:192.168.0.138:12345 replication_dsync_parameters = -d -l 30 -U sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_duplicate_default_period = 1h sieve_duplicate_max_period = 1d sieve_global_dir = /usr/home/vmail/sieve/global/ sieve_global_path = /usr/home/vmail/default.sieve sieve_vacation_default_period = 1d zlib_save = gz zlib_save_level = 6 } protocols = imap sieve service aggregator { fifo_listener replication-notify-fifo { user = vmail } unix_listener replication-notify { user = vmail } } service auth { unix_listener auth-userdb { mode = 0777 } } service dict { unix_listener dict { mode = 0600 user = vmail } } service doveadm { inet_listener { port = 12345 } } service replicator { process_min_avail = 1 unix_listener replicator-doveadm { mode = 0600 user = vmail } } ssl = no userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-sql.conf.ext driver = sql } protocol lda { mail_plugins = " fts fts_solr acl zlib notify replication sieve" submission_host = 192.168.0.1:25 } protocol imap { mail_plugins = " fts fts_solr acl zlib notify replication imap_acl imap_zlib" }

1 0

Change default mode for attachment files
by Олег Кривоносов 18 Dec '18

18 Dec '18

Hi I migrated my dovecot server from Maildir to mdbox with saving attachments to external files and enabled SIS a few days ago. Everything works fine except one issue. I have both virtual and system users. Dovecot saves attachments with mode 0600. So I catch such errors for system users: dovecot: lda(wasya): Error: fs-sis: Couldn't read hash file /var/mail/attachments/2e/dc/hashes/2edc6009bc9b6ba38febb581df03986dcaf134d9: Permission denied I want to fix this issue by changing default file mode to 0660 via group policy. I found such feature in the changelog (v2.1.rc2 2012-01-06): lib-fs: Added "mode" parameter to "posix" backend to specify mode for created files/dirs. Unfortunately I can't find any information about this feature in the dovecot documentation. Can I use it to setup mode 0660 for attachments in the dovecot configuration? uname -a Linux diplo.trueconf.ru 4.9.0-6-amd64 #1 SMP Debian 4.9.88-1+deb9u1 (2018-05-07) x86_64 GNU/Linux dovecot --version 2.2.27 (c0f36b0) 10-mail.conf dovecot configuration: mail_access_groups = vmail mail_location = mdbox:~/mdbox mdbox_preallocate_space = yes mdbox_rotate_interval = 1 weeks mdbox_rotate_size = 5 M mail_attachment_dir = /var/mail/attachments mail_attachment_min_size = 32k mail_attachment_fs = sis posix mail_attachment_hash = %{sha1} Thank you

1 0

Possible attack?
by Daniel Miller 18 Dec '18

18 Dec '18

I found an error in my log today... Dec 17 12:03:30 bubba dovecot: imap(user1(a)amfes.com)<23017><VzQFnjx9WNAKO2EC>: Error: fts_solr: received invalid uid '0' Dec 17 12:04:44 bubba dovecot: imap(user2(a)amfes.com)<25004><FeHDSj19i2ysOCn7>: Fatal: master: service(imap): child 25004 killed with signal 11 (core dumps disabled - https://dovecot.org/bugreport.html#coredumps) I've now enabled core dumps (I think) and restarted - if it comes back hopefully I can get a backtrace. But reading that fts_solr message, and some other comments, leads me to wonder - could this be caused by someone/thing trying to authenticate as root? On that theory - I tried doing so via telnet - and received: Dec 17 15:06:02 bubba dovecot: auth: Error: plain(ultradeitytypeperson(a)amfes.com,127.0.0.1,<4kQr0z99UMZ/AAAB>): user not found from any userdbs Dec 17 15:06:02 bubba dovecot: imap: Error: Authenticated user not found from userdb, auth lookup id=3522297857 (auth connected 1 msecs ago, handshake 0 msecs ago, request took 1 msecs, client-pid=29572 client-id=1) I have root's email aliased to a valid user's email. I'm not sure how I'm able to authenticate as root - there isn't a root user defined in my LDAP database and that should be the only auth backend enabled for Dovecot. Or do I need to explicitly block local users from /etc/passwd on the server? The only auth databases shown in doveconf -n: userdb { driver = prefetch } userdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } passdb { args = /usr/local/etc/dovecot/master-users driver = passwd-file master = yes } passdb { args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext driver = ldap } and "master-users" doesn't list root either. -- Daniel

1 0

Re: ECDSA client question
by Michael A. Peters 18 Dec '18

18 Dec '18

On 12/16/18 7:52 AM, Tributh via dovecot wrote: > > > Am 16.12.18 um 12:13 schrieb Michael A. Peters: >> Hi, for those who have adopted ECDSA, >> >> Are there still any commonly used IMAPS/POP3S clients that still can not >> handle ECDSA certificates? >> >> I know you can set up Dovecot dor dual cert, I am just trying to >> determine if there still is a real world need to. > > Nearly every client can handle ECDSA, but it depends on the size of the > certificate. > I used years ago ECDSA-384bit certificates, which covered most of the > clients. It came to the point to disable RSA in that time, but than came > Android7.0. This Version can only handle ECDSA-256bit certificates or RSA. > > The coverage of Android7.0 is still over 20%. Google reacted fast and > repaired this bug in 7.1, which is still not coming to most of the phones. > > Cheers > Torsten > Wow - My phone is running Android 6, I just checked with Dad - his phone (Motorola) is running Android 7.0 - the version with the bug. We don't replace phones just because new versions are available, we replace them when they stop working, and when we do we usually get refurbished because we hate how much electronic waste is in the world. I have to admit, the tin foil hat of mine just got an alert. We know there are unexplained constants in the NIST curves including P-256 - what if NSA was partially responsible for this bug (back room deal to avoid anti-trust prosecution, similar deal with IBM was made in the 70s I believe also involving cryptography) so that Android apps that use ECDSA (beyond just the mail client, e.g. chat apps) would use P-256 for compatibility and are maybe vulnerable to MITM for the key exchange. I want Ed25519 now.

2 1