- dovecot - dovecot.org

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

31 Jul '13

Martin Burgraf writes: > > 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. "Hogging" CPU and memory is putting it strongly, as it is basically suspended while blocked on waiting for a connection, and if left for a long time in an idle state, might be swapped out to disk and not consuming (real) memory, or consuming real memory that isn't in use otherwise. As I stated before, the resource usage is small compared with all the other stuff going on, so if you don't have a busy mail server, I don't think you should sweat the difference. The benefits of LMTP should increase with load, as having LMTP resident will save you the overhead of repeatedly loading/unloading LDA, and I'm sure the CPU and memory usage of servicing that overhead will be non-trivial. If you have oodles of memory, then it's no problem keeping a LMTP resident. If you don't have enough memory and are VM disk thrashing, you'll have other problems and LDA/LMTP is the least of your worries. > 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. I didn't contest the privilege separation aspect, as it a necessary design trade-off that one daemon doing things for all user will need overriding access. However, if this is a concern, you can virtualize all your users. LMTP can theoretically be subverted, but at least won't be as root. (I'm assuming LMTP stays as root, and not spawning off user processes to do the real work.) Joseph Tam <jtam.home(a)gmail.com>

3 2

Re: [Dovecot] dovecot-lda not logging if dovecot runs under daemontools
by Jost Krieger 30 Jul '13

30 Jul '13

On Fri Jul 26 14:51:30 2013, Roberto Puzzanghera wrote: > > Hi Jost, thanks for your reply. > > Il 26.07.2013 13:11 Jost Krieger ha scritto: > >Dovecot-lda runs under qmail, so you'll find the output in qmail's > >logs. If you run, say, doveadm manually, the output will be on your > >terminal. > > I didn't explain myself very well. The qmail's log > /var/log/dovecot/current doesn't show the lda output as expected. I That's dovecot's log, not qmail's. > see onlythe output of imap and pop3. Anyway, running dovecot > manually or as daemon in the normal way (without daemontools) show > the lda output in the log. You are logging to stderr, in the delivery case that means qmail-local's output. This is somewhere in a place like /var/qmal/logs/qmail/current and looks similar to @4000000051f793e218f78c54 delivery 847552: success: lda(xxxxxxxx):_Info:_msgid=<20130730102215.ECB48809E9(a)carlos.noc.ruhr-uni-bochum.de>:_saved_mail_to_NOC-Order/did_0+0+1/ Yours Jost Krieger -- | Jost.Krieger+sig(a)ruhr-uni-bochum.de Please help stamp out spam! | | Postmaster, JAPH, resident answer machine at RUB Comp. Center | | Sincere words are not sweet, sweet words are not sincere. | | Lao Tse, Tao Te King 81 |

2 1

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