- dovecot - dovecot.org

Re: [Dovecot] LDA vs. LMTP
by Martin Burgraf 30 Jul '13

30 Jul '13

Joseph Tam wrote: > I don't know why you would consider a background process inferior to a > run-on-demand executable. Well, the background process is hogging CPU and RAM while it basically does nothing. And when it's running as root there is always the danger of privilege escalation. LDA only runs when it's needed and since it uses only user rights it shoudbe more harmless. bye Martin

2 1

[Dovecot] LDA vs. LMTP
by Martin Burgraf 30 Jul '13

30 Jul '13

Hi there, I'm using Dovecot together with Postfix; as I understand it, there are two ways to transfer the mail from Postfix to Dovecot. 1.) by using LDA with mailbox_command = /usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT" 2.) by using LMTP with mailbox_transport = lmtp:unix:private/dovecot-lmtp (currently using number 1) I'm interessted in the differences and the advantages/disadvantages of each of those solutions. According to http://wiki2.dovecot.org/LDA the recommended way is to use LMTP, since it's supposed to have a better performance. On the other hand, http://wiki2.dovecot.org/LMTP says, that LMTP is a backgound process, while LDA is only called when needed. I've also read, that LDA only uses the users privileges, which both means, that LDA should be better. I've also noticed, that LMTP adds an additional Recieved:-Header to the mail. Are there any other differences? Thank you M.

7 7

[Dovecot] Problem switching from Dovecot LDA to LMTP - on dovecot 2.2.4
by Michael Long 29 Jul '13

29 Jul '13

Dovecot LDA has been working fine for me but when I tried to follow the wiki and switch to LMTP I get: Recipient address rejected: User unknown in local recipient table; In postfix/main.cf I went from: mailbox_transport = dovecot-spam to mailbox_transport = lmtp:unix:private/dovecot-lmtp Added this: service lmtp { unix_listener /var/spool/postfix/private/dovecot-lmtp { group = postfix mode = 0600 user = postfix } } protocol lmtp { mail_fsync = optimized postmaster_address = postmaster@domainname mail_plugins = sieve zlib } And some other pertinent parts of the config: passdb { args = /etc/dovecot/passdb driver = passwd-file } passdb { driver = pam } protocol lda { mail_fsync = optimized auth_socket_path = /var/run/dovecot/auth-master deliver_log_format = msgid=%m: %$ mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = sieve zlib postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r lda_mailbox_autocreate = yes }

1 0

[Dovecot] Maildir permissions and Solr re-indexing
by Michael Welsh Duggan 29 Jul '13

29 Jul '13

I am running a very small dovecot installation with only one user (me). I use the Solr indexer for indexing. Due to complicated reasons, I was forced to remove all the indexes and need to re-index everything. All the files in my Maildir are owned by md5i:mail (I am md5i), and have 660 permissions. All directories have the same user:group permissions, and 770 with the setguid bit set. (That last may not be necessary, but I was trying several things to get my use case to work.) Unfortunately, I can't seem to get re-indexing to work. When I do "doveadm fts rescan -A" as root, I get the following error for each of my subgroups: doveadm(md5i): Error: fchown(/home/md5i/Maildir/.mail.test/dovecot.index.log.newlock, group=8(mail)) failed: Operation not permitted (egid=1000(md5i), group based on /home/md5i/Maildir/.mail.test - see http://wiki2.dovecot.org/Errors/ChgrpNoPerm) After this, each directory has a dovecot.index.log with md5i:md5i 600 permissions. I've read the mentioned page, and played around with the ideas on it, but haven't gotten things to work. Anyone have any clue to ship my way? -- Michael Welsh Duggan (md5i(a)md5i.com)

1 1

[Dovecot] zlib error when running doveadm
by Michael Long 29 Jul '13

29 Jul '13

Upgraded to dovecot 2.2.4 from 2.1.16 Error I see is: doveadm(root): Error: Module is for different ABI version 2.1.16 (we have 2.2.ABIv3(2.2.4)): /usr/local/lib/dovecot/doveadm/lib10_doveadm_zlib_plugin.so How do I resolve this? Configure options: ./configure --with-bzlib --with-ssl --with-mysql --with-zlib --with-pam Configuration: # 2.2.4: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 3.2.0-48-generic x86_64 Ubuntu 12.04.2 LTS doveconf: Warning: Dovecot was last started using /etc/dovecot/dovecot-postfix.conf, but this config is /usr/local/etc/dovecot/dovecot.conf auth_mechanisms = plain login cram-md5 disable_plaintext_auth = no listen = * log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = mail mail_debug = yes mail_gid = 8 mail_location = maildir:~/Maildir mail_plugins = " zlib" mail_privileged_group = mail 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 passdb { args = /etc/dovecot/passdb driver = passwd-file } passdb { driver = pam } plugin { fts = squat sieve = ~/.dovecot.sieve sieve_debug = yes sieve_dir = ~/ sieve_global_dir = /etc/dovecot sieve_global_path = /etc/dovecot/dovecot.sieve zlib_save = gz zlib_save_level = 6 } protocols = imap pop3 sieve service auth { unix_listener /var/run/dovecot/auth-master { group = postfix mode = 0666 user = postfix } unix_listener /var/spool/postfix/private/dovecot-auth { group = postfix mode = 0666 user = postfix } user = root } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl_cert = </etc/postfix/certs/postfix_public_cert.pem ssl_cipher_list = ALL:!LOW:!SSLv2:ALL:!aNULL:!ADH:!eNULL:!EXP:RC4+RSA:+HIGH:+MEDIUM ssl_key = </etc/postfix/certs/postfix_private_key.pem userdb { driver = passwd } verbose_proctitle = yes protocol imap { imap_client_workarounds = delay-newmail mail_max_userip_connections = 50 mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = " zlib fts fts_squat zlib imap_zlib" } protocol pop3 { mail_max_userip_connections = 20 mail_plugins = " zlib zlib" pop3_client_workarounds = outlook-no-nuls oe-ns-eoh pop3_uidl_format = %08Xu%08Xv } protocol lda { auth_socket_path = /var/run/dovecot/auth-master deliver_log_format = msgid=%m: %$ lda_mailbox_autocreate = yes mail_plugin_dir = /usr/local/lib/dovecot mail_plugins = sieve zlib postmaster_address = postmaster quota_full_tempfail = yes rejection_reason = Your message to <%t> was automatically rejected:%n%r }

4 3

[Dovecot] Upgrading to dovecot2 broke IDLE on one mailer, but not another
by John Stracke 29 Jul '13

29 Jul '13

Last weekend I upgraded my server (complete reinstall, actually), from Debian sarge to wheezy, which brought me from dovecot 1.x (I think) to 2.1.7. It's all working now, *except* that the MUA I use on Android, Kaiten (a fork of K-9), apparently no longer gets IDLE notifications. Before the upgrade, when mail arrived, Kaiten would pop up an Android notification immediately; now, it never does (or it might, hours later, with all the messages it notices at that time--presumably this happens when its background service gets killed off and restarted). The weird thing is that IDLE still works flawlessly with Thunderbird, which suggests this is a protocol interaction between Dovecot 2 and Kaiten. (I plan to check with the Kaiten folks next.) Has anybody here seen this? Is there something I can turn on in Dovecot to help debug it? I did check my old Dovecot settings, and they didn't specify anything non-default about IDLE. Thanks in advance! My configuration from dovecot -n: # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.9.3-x86-linode52 i686 Debian 7.0 log_timestamp = "%Y-%m-%d %H:%M:%S " mail_access_groups = mail mail_location = mbox:~/mail:INBOX=/var/mail/%u mail_privileged_group = mail passdb { driver = pam } protocols = imap pop3 service auth { user = root } service imap-login { inet_listener imap { port = 0 } } service pop3-login { inet_listener pop3 { port = 0 } } ssl_cert = </etc/ssl/certs/dovecot-2009.cert ssl_key = </etc/ssl/private/dovecot.pem userdb { driver = passwd } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } and the no-comments version of conf.d/20-imap.conf: protocol imap { imap_idle_notify_interval = 10 mins } -- /==============================================================\ | John Stracke | http://www.thibault.org | HTML OK | | François Thibault |---------------------------------------| | East Kingdom | "Okay, one more time, with *vowels*." | | francis(a)thibault.org | -- Ozy and Millie | \==============================================================/

2 2

[Dovecot] how to setup different quota for multiple namespaces
by Andreas Oster 29 Jul '13

29 Jul '13

Hello all, I am using dovecot for some time now but always had very basic configurations. I recently have configured a new, additional namespace in order to move archived mails (Thunderbird Archives) to another storage system. namespace { type = private separator = . prefix = Archives. location = maildir:/var/vmail/archive/%Ln/Maildir subscriptions = yes list = children inbox = no } This works well but unfortunately I cannot find a solution to either ignore this new namespace from quota computation or add a separate quota value for it. I have integrated user authentication with LDAP and fetch some user attributes from LDAP entries: user_attrs = =home=/var/vmail/%Ln/Maildir,=mail=maildir:/var/vmail/%Ln/Maildir/,otherPager=quota_rule=*:storage=%$ I configured the quota plugin in the following way: plugin { quota = maildir:User quota:ns= quota2 = maildir:Archive quota:ns=Archives. quota_rule = *:storage=1G quota_rule2 = ns=Archives.:ignore } unfortunately this does not give the desired result. Folders under the Archives namespace use the same quota as INBOX. Does anyone have an idea how to fix this ? Thank you for your kind help Andreas

4 19

[Dovecot] convert to mdbox
by Birta Levente 29 Jul '13

29 Jul '13

Hi How can I convert all virtual mailboxes from maildir to mdbox? Manually, one by one, working, but I have a lot ... Virtual users and domains stored in sql database. Thats what I want: mail_location = maildir:/var/vmail/%d/%n/Maildir to mail_location = mdbox:/var/vmail/%d/%n/mdbox Thanks Levi

3 3

[Dovecot] Please help with : undefined symbol: mail_deliver_save_open
by Markus Kalb 28 Jul '13

28 Jul '13

Greetings dovecot-mailing list! after upgrading from debian squeeze -> debian wheezy and therefore making the big dovecot jump from 1.x to 2.x we are stuck with one final(?) error that we can't get fixed. During login attempts the following is written to the logfiles. Error: dovecot: imap: Error: dlopen(/usr/lib/dovecot/modules/lib90_sieve_plugin.so) failed: /usr/lib/dovecot/libdovecot-sieve.so.0: undefined symbol: mail_deliver_save_open Searching the mailinglist and google in general the only thing i could find was that this error could be connected to loading the sieve plugin outside of lda. But as you can see in the attached config dump, we only load it inside the lda protocol block. ciao markus Our setup: > dovecot --version 2.1.7 > dovecot -n # 2.1.7: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-686-pae i686 Debian 7.1 auth_debug = yes auth_mechanisms = plain login digest-md5 cram-md5 auth_verbose = yes mail_debug = yes mail_plugins = acl fts fts_solr mail_shared_explicit_inbox = 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 ihave imapflags notify namespace { hidden = no list = children location = maildir:/home/lists/.mail/:CONTROL=%h/.mail/private/.imap/shared/control:INDEX=%h/.mail/private/.imap/shared/index prefix = lists/ separator = / subscriptions = no type = shared } namespace { hidden = yes list = no location = maildir:/home/security/.mail/:CONTROL=%h/.mail/private/.imap/shared/control:INDEX=%h/.mail/private/.imap/shared/index prefix = security/ separator = / subscriptions = no type = shared } namespace { hidden = yes list = children location = maildir:/home/dsys/.mail/:CONTROL=%h/.mail/private/.imap/shared/control:INDEX=%h/.mail/private/.imap/shared/index prefix = duales_system/ separator = / subscriptions = no type = shared } namespace inbox { hidden = no inbox = yes list = yes location = mbox:%h/.mail/private:INBOX=/var/mail/%u 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 = separator = / type = private } passdb { args = scheme=DIGEST-MD5 username_format=%u /etc/dovecot/passwd driver = passwd-file } plugin { acl = vfile:/etc/dovecot/acls:cache_secs=300 sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve_extensions = +imapflags +notify } protocols = " imap sieve" service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0666 user = postfix } } service imap-login { inet_listener imap { port = 143 } } ssl_cert = </etc/ssl/certs/SERVER.pem ssl_key = </etc/ssl/private/SERVER.key userdb { args = username_format=%u /etc/dovecot/passwd default_fields = mail_plugins=sieve system_groups_user=%u driver = passwd-file } protocol lda { mail_plugins = acl fts fts_solr sieve } protocol imap { mail_max_userip_connections = 20 mail_plugins = acl fts fts_solr } # dpkg -l '*dovecot*' |grep ii | cut -c 0-60 ii dovecot-antispam 2.0+20120225-3 ii dovecot-core 1:2.1.7-7 ii dovecot-imapd 1:2.1.7-7 ii dovecot-ldap 1:2.1.7-7 ii dovecot-managesieved 1:2.1.7-7 ii dovecot-sieve 1:2.1.7-7 ii dovecot-solr 1:2.1.7-7

1 1

Re: [Dovecot] LDA vs. LMTP
by Joseph Tam 28 Jul '13

28 Jul '13

"Martin Burgraf" <martin.bg(a)web.de> writes: > According to http://wiki2.dovecot.org/LDA the recommended way is to use > LMTP, since it's supposed to have a better performance. The performance gains comes mostly from avoiding the overhead of invoking an executable and spawning a new process for each delivery. If your mail system isn't stressed, I don't think it matters much. > On the other hand, http://wiki2.dovecot.org/LMTP says, that LMTP is a > backgound process, while LDA is only called when needed. I've also > read, that LDA only uses the users privileges, which both means, that > LDA should be better. I don't know why you would consider a background process inferior to a run-on-demand executable. > I've also noticed, that LMTP adds an additional Recieved:-Header to the mail. > Are there any other differences? >From a past discussion on this topic, I think Timo stated that if you use SIS (single-instance storage or de-duping), it's more efficient using LMTP since it knows all message bodies to multiple recipients will be identical. Joseph Tam <jtam.home(a)gmail.com>

1 0