- dovecot - dovecot.org

Configuration is not working with Thunderbird
by Quark 22 May '17

22 May '17

Hi, I'm new to the list (and postfix / dovecot), so if I mistakenly omit something, then please forgive me. I cannot log into Thunderbird via IMAP with my configuration. However, I can check the mail of each user by logging into their user account & then using the "mail" command. Is there something that is wrong with my config to not allow me to log into Thunderbird (Version 52.1.1)? I'm using Postfix 3.1.0 if that helps. Any help would be greatly appreciated. Thanks! Here is the output of "|dovecot -n"|: # 2.2.22 (fe789d2): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.13 (7b14904) doveconf: Warning: NOTE: You can get a new clean config file with: doveconf -n > dovecot-new.conf doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:105: listen=..:port has been replaced by service { inet_listener { port } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:105: protocol { listen } has been replaced by service { inet_listener { address } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:106: ssl_listen=..:port has been replaced by service { inet_listener { port } } doveconf: Warning: Obsolete setting in /etc/dovecot/dovecot.conf:106: protocol { ssl_listen } has been replaced by service { inet_listener { address } } # OS: Linux 4.4.0-77-generic x86_64 Ubuntu 16.04.2 LTS mail_location = maildir:~/Maildir 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 = imap service imap-login { inet_listener imap { address = * port = 143 } inet_listener imaps { address = * port = 993 } } ssl_cert = </etc/letsencrypt/live/REDACTED/fullchain.pem ssl_key = </etc/letsencrypt/live/REDACTED/privkey.pem userdb { driver = passwd } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep }

2 5

Backing up and restoring maildir folders
by Timothy D Legg 22 May '17

22 May '17

Hello, I am migrating to a different distribution of Linux that involves changing to an earlier version of dovecot (2.2.22 to 2.2.13). As part of this process, I will be copying several maildirs to the new machine. One of these has a number of files and directories that resemble this one example: cur/ dovecot.index dovecot.index.cache dovecot.index.log dovecot.mailbox.log dovecot-uidlist dovecot-uidvalidity dovecot-uidvalidity.59206030 .Drafts/ new/ .Sent/ subscriptions tmp/ .Trash/ Is it good enough to simply stop dovecot and tar this folder, and others like it, and copy them back to a similar location on the new installation? I haven't yet seen anything that resembles an official or standardized backup/recovery method for dovecot. With thanks and appreciation, Tim Legg

2 1

core from 2.2.29.1
by Luciano Mannucci 22 May '17

22 May '17

I've got this in my logfile, should I worry? May 19 14:45:04 imap(liscia_mcs): Panic: file mail-index-transaction-update.c: line 19 (mail_index_transaction_lookup): assertion failed: (seq >= t->first_new_seq && seq <= t->last_new_seq) May 19 14:45:04 imap(liscia_mcs): Error: Raw backtrace: /usr/lib/dovecot/libdovecot.so.0(+0x9cd16) [0xb7568d16] -> /usr/lib/dovecot/libdovecot.so.0(+0x9cd9f) [0xb7568d9f] -> /usr/lib/dovecot/libdovecot.so.0(i_fatal+0) [0xb74f204e] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xe3ebf) [0xb76b7ebf] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xe730c) [0xb76bb30c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_index_lookup_uid+0x1d) [0xb76bf47d] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_decision_state_update+0xac) [0xb769ff8c] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_cache_lookup_headers+0x7f) [0xb76a23bf] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb2898) [0xb7686898] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_get_first_header+0xbf) [0xb768723f] -> /usr/lib/dovecot/libdovecot-storage.so.0(mail_get_first_header+0x45) [0xb7601e95] -> /usr/lib/dovecot/libdovecot-storage.so.0(+0xb4fc1) [0xb7688fc1] -> /usr/lib/dovecot/libdovecot-storage.so.0(+ 0xb518f) [0xb768918f] -> /usr/lib/dovecot/libdovecot-storage.so.0(index_mail_close+0x136) [0xb76896e6] -> /usr/lib/dovecot/libdovecot-storage.so.0(mailbox_save_cancel+0x6c) [0xb761085c] -> dovecot/imap() [0x8052e1d] -> dovecot/imap() [0x805303c] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x67) [0xb7580997] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run_internal+0xeb) [0xb75823ab] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0x45) [0xb7580a55] -> /usr/lib/dovecot/libdovecot.so.0(io_loop_run+0x48) [0xb7580c18] -> /usr/lib/dovecot/libdovecot.so.0(master_service_run+0x2d) [0xb74fd1ad] -> dovecot/imap(main+0x344) [0x806dbc4] -> /lib/libc.so.6(__libc_start_main+0xfe) [0xb7357c2e] May 19 14:45:04 imap(liscia_mcs): Fatal: master: service(imap): child 24082 killed with signal 6 (core dumped) Here is mi doveconf -n: # 2.2.29.1 (e0b76e3): /usr/local/etc/dovecot/dovecot.conf # Pigeonhole version 0.4.17 (e179378) # OS: Linux 3.0.101-105-pae i686 openSUSE 11.4 (i586) ext3 auth_cache_size = 3 k auth_debug = yes auth_debug_passwords = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 1249 default_vsz_limit = 712 M disable_plaintext_auth = no first_valid_gid = 0 first_valid_uid = 100 info_log_path = /var/log/dovecot/logfile.info listen = * log_path = /var/log/dovecot/logfile login_greeting = Dovecot at Baobab ready. login_trusted_networks = 127.0.0.0/8 212.45.144.0/24 192.168.134.0/24 mail_location = mbox:/var/spool/mailboxes/%u:INBOX=/var/spool/mail/%u:DIRNAME=mbox:INDEX=/var/dovecot_indexes/%u maildir_copy_with_hardlinks = no 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 mbox_lock_timeout = 443 secs namespace { inbox = yes location = prefix = separator = . type = private } passdb { driver = pam } plugin { mail_log_events = delete undelete expunge copy mailbox_delete mailbox_rename mail_log_fields = uid box msgid size } protocols = pop3 imap service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } user = root } service imap-login { inet_listener imaps { address = * } process_limit = 512 } service pop3-login { chroot = executable = pop3-login -D inet_listener pop3s { address = * } process_limit = 512 } ssl_ca = </etc/ssl/ca.crt ssl_cert = </etc/ssl/certs/dovecot.pem ssl_key = # hidden, use -P to show it userdb { driver = passwd } version_ignore = yes protocol imap { imap_client_workarounds = delay-newmail mail_plugins = mail_log notify } protocol pop3 { pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_enable_last = yes } protocol lda { info_log_path = /var/log/dovecot/lda.log log_path = /var/log/dovecot/lda-errors.log postmaster_address = postmaster(a)mcs.it } Cheers, Luciano. -- /"\ /Via A. Salaino, 7 - 20144 Milano (Italy) \ / ASCII RIBBON CAMPAIGN / PHONE : +39 2 485781 FAX: +39 2 48578250 X AGAINST HTML MAIL / E-MAIL: posthamster(a)sublink.sublink.ORG / \ AND POSTINGS / WWW: http://www.lesassaie.IT/

1 0

Re: Pacaging/build issues with AIX and vac (dovecot-2.2.25)
by seema pandhre 22 May '17

22 May '17

Hi Micheal, I am currently working on AIX + VAC + NTPv4 build. and I have also faced same issues as mentioned by you in link https://www.dovecot.org/list/dovecot/2016-October/105597.html Wondering if you have got any resolution for above issue. If yes, please help me with your guidance. thanks in advance, seema

1 0

Using Dovecot for a Geo-replicated World-wide Email Service
by Lennart Oldenburg 22 May '17

22 May '17

Hello everyone, my colleagues and I from Technische Universität Berlin are currently looking into the best way to setup a Dovecot-powered email service that is simultaneously accessible world-wide and still provides short response times by redirecting users to the geographically-closest cluster. We imagine the setup to make use of multiple data center regions in public clouds around the world, e.g. in Amazon Web Services (AWS) or Google Compute Platform (GCP). At the same time, state is considered to be shared, i.e. changes made on file system in any local cluster will have to be synchronized with all other clusters around the globe (mailbox replication) and mailboxes might be manipulated from any data center in the world, potentially at the same time. Naturally, problems arise. We have multiple questions and would be very interested in the best way to approach them based on your experiences and recommendations: 1) Which path should we take replication-wise? Please keep in mind that we are targeting replication between more than 2 clusters. Traditionally, in a rather small local setup with mostly reliable network, a distributed file system such as NFS or GlusterFS might be the best option. Unfortunately, though, when scaling to more than 2 data centers geographically-distributed around the globe, latency becomes severe and distributed file systems might not be the way to go anymore. What is your recommendation for replicating state? 2) We are mostly interested in providing short response times to client requests while maintaining global state consistency (that is, avoiding conflicts in state and not losing any user data). What are your recommendations in that direction? Any particular performance optimizations we could apply to Dovecot? 3) Is there a recommended way to measure and monitor Dovecot's service quality? For example, is there a way to export "live" metrics of a running Dovecot deployment to something such as Prometheus (https://prometheus.io)? 4) Maildir as the way to represent mailboxes and deliver emails on file system is kind of a given. I wonder, though, how well is dbox replicatable? What happens when dbox files are synchronized (e.g. via dsync) and a conflict arises? Does dbox offer a performance improvement over Maildir? 5) We perceive Dovecot to come with many optimizations to speed up "read" IMAP commands, i.e. non-state-changing ones. Is this perception correct? Or is Dovecot able to use its various index and log files for fast "write" IMAP commands (e.g. CREATE, DELETE, RENAME, APPEND, STORE, ...) as well? 6) Would DovecotPRO by Dovecot Oy offer any advantage to state replication? For example, could the Object Storage Plugin be used to replicate mailboxes through some object store service offered world-wide? 7) Is the setup we have in mind based on Dovecot a feasible solution for world-wide email comparable to services like Gmail? If not, what would you change or not do at all? Please excuse if some questions might be of rather basic nature, we are not at all Dovecot experts. I tried to gather as much information on that topic as possible from the wiki and sources found online but I might have missed an important page. In that case, please point me towards existing resources on the questions raised above. Thanks in advance and kind regards, Lennart Oldenburg

1 0

Sieve GLOBAL + Sieve LOCAL
by Luescher Claude 19 May '17

19 May '17

Hello List, I am using dovecot: ii dovecot-antispam 2.0+20130822-2 amd64 Dovecot plugins for training spam filters ii dovecot-core 1:2.2.10-1 amd64 secure POP3/IMAP server - core files ii dovecot-imapd 1:2.2.10-1 amd64 secure POP3/IMAP server - IMAP daemon ii dovecot-ldap 1:2.2.10-1 amd64 secure POP3/IMAP server - LDAP support ii dovecot-lmtpd 1:2.2.10-1 amd64 secure POP3/IMAP server - LMTP server ii dovecot-managesieved 1:2.2.10-1 amd64 secure POP3/IMAP server - ManageSieve server ii dovecot-mysql 1:2.2.10-1 amd64 secure POP3/IMAP server - MySQL support ii dovecot-pop3d 1:2.2.10-1 amd64 secure POP3/IMAP server - POP3 daemon ii dovecot-sieve 1:2.2.10-1 amd64 secure POP3/IMAP server - Sieve filters support doveconf -n | grep -i sieve 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 ihave editheader vnd.dovecot.duplicate sieve = ~/.dovecot.sieve sieve_after = ~/sieve_after sieve_dir = ~/sieve sieve_extensions = +editheader +vnd.dovecot.duplicate sieve_max_redirects = 20 protocols = " imap lmtp sieve pop3" service managesieve-login { inet_listener sieve { mail_plugins = " quota sieve" mail_plugins = " quota sieve" I would like to have a Global and per user based Local sieve_before file. Since doveconf does not indicate I believe my version does not support: sieve_global_path A path to a global sieve script file, which gets executed ONLY if user's private Sieve script doesn't exist, e.g. /var/lib/dovecot/default.sieve. Be sure to pre-compile this script manually using the sievec command line tool, as explained below. But what I would need is execute a global sieve_before for all users to apply some spam selection rules. Did anybody easily achieved it? An obvious workaround would be to create a script which goes through all current users mail directories and creates a sieve_before script with the settings I need and then modify the user creation to do the same when new mailboxes get created. Thank you!

3 3

lmtp segfault after upgrade
by Tom Sommer 19 May '17

19 May '17

I just upgraded our Director to 2.2.29.1 from 2.2.26, and now my dmesg and /var/log/messages are getting flooded by these errors: lmtp[45758]: segfault at 21 ip 00007fb412d3ad11 sp 00007ffe83ad2df0 error 4 in libdovecot.so.0.0.0[7fb412c95000+11c000] lmtp[46304]: segfault at 91 ip 00007f771ba64d11 sp 00007ffe830635a0 error 4 in libdovecot.so.0.0.0[7f771b9bf000+11c000] lmtp[45775]: segfault at 21 ip 00007f206ed81d11 sp 00007ffd0f0daad0 error 4 in libdovecot.so.0.0.0[7f206ecdc000+11c000] lmtp[46649]: segfault at 21 ip 00007ff4aa027d11 sp 00007ffc05841430 error 4 in libdovecot.so.0.0.0[7ff4a9f82000+11c000] lmtp[45774]: segfault at 21 ip 00007ff1f3e0bd11 sp 00007ffe0ba00340 error 4 in libdovecot.so.0.0.0[7ff1f3d66000+11c000] lmtp[45776]: segfault at 411 ip 00007f96ded95d11 sp 00007ffce6401870 error 4 in libdovecot.so.0.0.0[7f96decf0000+11c000] lmtp[46896]: segfault at 21 ip 00007fbf1aa70d11 sp 00007ffc79e22bf0 error 4 in libdovecot.so.0.0.0[7fbf1a9cb000+11c000] lmtp[46695]: segfault at 21 ip 00007fd5ccad6d11 sp 00007ffe19e759d0 error 4 in libdovecot.so.0.0.0[7fd5cca31000+11c000] lmtp[45773]: segfault at 21 ip 00007f0eb7b65d11 sp 00007fff9d02e570 error 4 in libdovecot.so.0.0.0[7f0eb7ac0000+11c000] lmtp[47101]: segfault at 21 ip 00007fa95b052d11 sp 00007fff2d5485a0 error 4 in libdovecot.so.0.0.0[7fa95afad000+11c000] lmtp[45772]: segfault at 21 ip 00007f2f52b49d11 sp 00007fff99a4a6e0 error 4 in libdovecot.so.0.0.0[7f2f52aa4000+11c000] lmtp[46595]: segfault at 21 ip 00007f0ccbdbad11 sp 00007ffd17bfe9e0 error 4 in libdovecot.so.0.0.0[7f0ccbd15000+11c000] lmtp[45770]: segfault at 21 ip 00007f94a576ed11 sp 00007ffc29c2ff00 error 4 in libdovecot.so.0.0.0[7f94a56c9000+11c000] lmtp[45769]: segfault at 21 ip 00007f34999b5d11 sp 00007ffe28818350 error 4 in libdovecot.so.0.0.0[7f3499910000+11c000] lmtp[47371]: segfault at 21 ip 00007f13c611fd11 sp 00007ffcdb000b10 error 4 in libdovecot.so.0.0.0[7f13c607a000+11c000] lmtp[47419]: segfault at 21 ip 00007f4010ff2d11 sp 00007ffd97519420 error 4 in libdovecot.so.0.0.0[7f4010f4d000+11c000] lmtp[47511]: segfault at 581 ip 00007fd5e3d21d11 sp 00007ffce61f29c0 error 4 in libdovecot.so.0.0.0[7fd5e3c7c000+11c000] lmtp[47277]: segfault at 21 ip 00007f04c3d6cd11 sp 00007ffc421da1b0 error 4 in libdovecot.so.0.0.0[7f04c3cc7000+11c000] lmtp[45771]: segfault at 21 ip 00007f55c690ed11 sp 00007fff35521fc0 error 4 in libdovecot.so.0.0.0[7f55c6869000+11c000] lmtp[47543]: segfault at 21 ip 00007f11ea946d11 sp 00007ffdd9a97690 error 4 in libdovecot.so.0.0.0[7f11ea8a1000+11c000] lmtp[47669]: segfault at 21 ip 00007f8f58abbd11 sp 00007ffdd5573220 error 4 in libdovecot.so.0.0.0[7f8f58a16000+11c000] lmtp[46959]: segfault at 41 ip 00007ff9d6f3ed11 sp 00007ffe28dc8ea0 error 4 in libdovecot.so.0.0.0[7ff9d6e99000+11c000] Any ideas? -- Tom

4 17

per user procmail filtering and dovecot-lda
by James Nord 18 May '17

18 May '17

Hi all, I recently migrated my system (postfix/Dovecot)from mbox to Maildir. Almost everything is working (phone and thunderbird show all my mail and folders with mail) However I am stuck on my .procmailrc rules # cat /etc/procmailrc SENDMAIL=/usr/sbin/sendmail SENDMAILFLAGS=-oi LOGFILE=/var/log/procmail.log ORGMAIL=${HOME}/Maildir/ DEFAULT=${ORGMAIL} MAILDIR=${HOME}/Maildir/ DELIVER="/usr/lib/dovecot/deliver -d $LOGNAME" # next line is to support user .procmailrc files INCLUDERC=$HOME/.procmailrc :0 w | $DELIVER # cat ~/.procmailrc :0 w * ^List-ID:.*jenkinsci-dev.googlegroups.com | $DELIVER -m mailing-lists/jenkinsci-dev :0 w * ^List-ID:.*jenkinsci-users.googlegroups.com | $DELIVER -m mailing-lists/jenkinsci-users However dovecot-lda complains that the mailboxes "mailing-lists/jenkinsci-users", "mailing-lists/jenkinsci-dev" etc do not exist so delivers to the INBOX. Everything I have read says that the mailbox specified by -m is the name as seen by the mail client, and this is what the client sees (see image). I have tried changing the mailbox to INBOX/mailing-lists/... inbox/mailing-lists/... but the same still happens. So I am missing something somewhere and my google foo is unfortunately letting me down this time. Is there someone that can help me? (I'm not subscribed to the list so a CC to me would be appreciated) Regards /James

5 7

Re: Sieve GLOBAL + Sieve LOCAL
by Joseph Tam 17 May '17

17 May '17

Luescher Claude <stargate(a)tango.lu> writes: > I am using dovecot: > ... > ii dovecot-sieve 1:2.2.10-1 amd64 > secure POP3/IMAP server - Sieve filters support > ... > doveconf -n | grep -i sieve > Since doveconf does not indicate I believe my version does not support: > > sieve_global_path I see mentions of this configuration variable in 7 year old dovecot posts, so it's been around a long time. You should do doveconf -a | grep sieve_global_path since "-n" won't list unchanged (defaulted) configuration values. Joseph Tam <jtam.home(a)gmail.com>

1 0

Conditionally Filter Mails During IMAP Fetch
by Ory Drilon 17 May '17

17 May '17

Hi, is there a way to arbitrarily filter out mails at the moment the IMAP request is made, based on properties of the IMAP session and the mail itself? All the filtering methods I find occur during delivery time.

2 1