- dovecot - dovecot.org

[Dovecot] Auth-woker log lines
by Grzegorz Staniak 02 Aug '13

02 Aug '13

Hi, Are log lines like the following: Jul 28 15:30:50 mx1.somewhere dovecot: auth-worker(18980): sql(user(a)domain,217.67.x.x): unknown user Jul 28 15:32:56 mx1.somewhere dovecot: auth-worker(18980): sql(user(a)domain,212.182.x.x): Password mismatch written every time any authetntication phase fails, in SASL as well as in POP3/IMAP mailbox access? I have a legacy app that would gain a lot if I could distinguish between failed SASL authentication and failed POP3/IMAP authentication. I know I can use the "auth failed" lines for the latter case, and postfix log lines in the former, but they don't contain user info. Is there a way for log monitoring software to get failed login lines with both user info, and the reason (SASL, POP3, IMAP)? Regards, -- Grzegorz Staniak <gstaniak [at] gmail _dot_ com>

2 1

[Dovecot] 2.2.4 - quota-status changing the user it is running as
by Axel Luttgens 02 Aug '13

02 Aug '13

Hello, I'm currently experimenting with this quota-status service configuration: service quota-status { client_limit = 1 executable = quota-status -p postfix # Let's make the default explicit. user = root unix_listener /var/spool/postfix/private/quota-policyd { user = postfix } } The idea is to run the service as root during the preliminary tests (at worst, since the service is going to be used as a policy daemon by Postfix only, it shouldn't be very problematic to have it running as root anyway). A user, with address john.doe(a)example.com and identified as john.doe, is known to be over-quota. A "doveadm quota get" returns: $ sudo doveadm quota get -u john.doe Password: Quota name Type Value Limit % Quota utilisateur STORAGE 5 5 100 Quota utilisateur MESSAGE 9 - 0 and messages for that user are correctly rejected by lmtp: dovecot[4989]: lmtp(5069, john.doe(a)example.com) QWSWLgrP4lF7FAAA5Q0ykw: msgid=<20130714161643.9085DF176F2(a)ALMba.local>: save failed to INBOX: Quota exceeded (mailbox for user is full) Let's now simulate a connection from Postfix: $ sudo -u postfix telnet /_ROOT/var/spool/postfix/private/quota-policyd Trying /_ROOT/var/spool/postfix/private/quota-policyd... Connected to (null). Escape character is '^]'. A look at the output of top (excerpt) confirms that quota-status is running as root: PID COMMAND UID 5100 quota-status 0 Going on with our telnet session: recipient=john.doe(a)example.com size=10000 action=OK Hmmm... OK, this may be a config problem of mine which may require further investigation. Anyway, looking at top's output: PID COMMAND UID 5100 quota-status 999 it appears that quota-status is now running as the mail_uid/mail_gid user; the switch happens immediately after having entered the empty line in the telnet session. Let's then try to go further within the telnet session: recipient=john.doe(a)example.com size=10000 action=DEFER_IF_PERMIT Internal error occurred. Refer to server log for more information. ^] telnet> quit Connection closed. and a look at the log indeed reveals that quota-status doesn't have sufficient privileges anymore: dovecot[4989]: quota-status(john.doe(a)example.com): Error: user john.doe(a)example.com: Error reading configuration: net_connect_unix(/_ROOT/var/run/dovecot/config) failed: Permission denied Is this the expected behavior, to have quota-status switch to another user? TIA, Axel

3 8

[Dovecot] [PATCH] quota-status: allow different action for messages that are too large (over maximum quota)
by Ulrich Zehl 02 Aug '13

02 Aug '13

This proposed patch to quota-status allows the administrator to return different actions for messages that (a) cannot currently fit in the quota (because there's not enough free space) and (b) are over the maximum quota limit (and could not even be delivered if the mailbox was empty). Configuration works like this: plugin { quota_status_overquota = DEFER_IF_PERMIT 4.2.2 Mailbox full quota_status_toolarge = REJECT 5.2.3 Message length exceeds administrative limit } The patch is backwards compatible: If quota_status_toolarge is not set, quota_status_overquota is returned. No changes are necessary in setups where the new feature is not desired. The reason I developed this patch is: In my environment, I have mostly POP3 mailboxes, where condition (a) changes frequently (usually after each login), but condition (b) will almost never change (users do not get additional mailbox space often). Thus, I'd like to avoid bouncing mails that could be delivered half an hour later. This patch works for 2.2 and 2.1. (This assumes you have already applied the trivial patch I sent earlier; otherwise patch(1) will report some fuzz.) What do you think of this? Ulrich --- a/src/plugins/quota/quota-status.c 2013-08-01 18:05:24.000000000 +0200 +++ b/src/plugins/quota/quota-status.c 2013-08-01 18:03:30.000000000 +0200 @@ -46,13 +46,12 @@ } static int -quota_check(struct mail_user *user, uoff_t mail_size, const char **error_r) +quota_check(struct mail_user *user, uoff_t mail_size, const char **error_r, bool *too_large) { struct quota_user *quser = QUOTA_USER_CONTEXT(user); struct mail_namespace *ns; struct mailbox *box; struct quota_transaction_context *ctx; - bool too_large; int ret; if (quser == NULL) { @@ -64,7 +63,7 @@ box = mailbox_alloc(ns->list, "INBOX", 0); ctx = quota_transaction_begin(box); - ret = quota_test_alloc(ctx, I_MAX(1, mail_size), &too_large); + ret = quota_test_alloc(ctx, I_MAX(1, mail_size), too_large); quota_transaction_rollback(&ctx); mailbox_free(&box); @@ -82,6 +81,7 @@ struct mail_storage_service_user *service_user; struct mail_user *user; const char *value = NULL, *error; + bool too_large; int ret; if (client->recipient == NULL) { @@ -98,14 +98,21 @@ if (ret == 0) { value = nouser_reply; } else if (ret > 0) { - if ((ret = quota_check(user, client->size, &error)) > 0) { + if ((ret = quota_check(user, client->size, &error, &too_large)) > 0) { /* under quota */ value = mail_user_plugin_getenv(user, "quota_status_success"); if (value == NULL) value = "OK"; } else if (ret == 0) { - /* over quota */ - value = mail_user_plugin_getenv(user, "quota_status_overquota"); + if (too_large == TRUE) { + /* even over maximum quota */ + value = mail_user_plugin_getenv(user, "quota_status_toolarge"); + if (value == NULL) /* backwards compatibility */ + value = mail_user_plugin_getenv(user, "quota_status_overquota"); + } else { + /* over quota */ + value = mail_user_plugin_getenv(user, "quota_status_overquota"); + } if (value == NULL) value = t_strdup_printf("554 5.2.2 %s", error); }

2 1

Re: [Dovecot] LDA vs. LMTP
by Joseph Tam 02 Aug '13

02 Aug '13

(Weird: this message digest got dumped into Google's spam folder. Maybe it didn't like the string in a later post (obfuscated here) master(dot)cf, which in the context of this mailing list is a postfix configuration file, but which Gmail interpret as a website. However, that domain is a SURBL/DBL blacklisted URI). Ben Morrow writes: > > > 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'm assuming LMTP stays as root, and not spawning off user > > processes to do the real work.) > > It doesn't stay as root; Dovecot's LMTP switches down to the user's uid > to perform delivery, including sieve scripts. I stand corrected. This removes the other objection that the original poster for running a peristent LMTP process. Joseph Tam <jtam.home(a)gmail.com>

1 0

[Dovecot] misconception in uid and gid
by Felix Rubio Dalmau 02 Aug '13

02 Aug '13

Hi, I'm using a SQL database to store the usernames and passwords of my users. However, I have found that I must explicitly return the uid and gid with every query, even though all virtual users use the same uid and gid. The query, that works, is: user_query = SELECT mail, 'vmail' AS uid, 'vmail' AS gid, home, CONCAT('*:storage=', quota_MB*1024) AS quota_rule \ FROM virtual_users AS V LEFT JOIN virtual_domains AS D ON V.domain_id=D.id WHERE V.user='%n' AND D.name='%d' Nevertheless, if I remove the segments "'vmail' AS uid, 'vmail' AS gid" and modify the file conf.d/10-mail.conf to show mail_uid = vmail mail_gid = vmail I get this error: dovecot: auth: Error: userdb(<mail>): client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (change userdb socket permissions) Does anybody know what is wrong in my set-up? Regards, Felix

3 4

Re: [Dovecot] dovecot Digest, Vol 124, Issue 4
by Felix Rubio Dalmau 02 Aug '13

02 Aug '13

Hello Axel, but then I don't get it: I thought that "uid" and "gid" in the user_query where used to access the local FS, whereas the "unix_listener auth-userdb" are used to indicate under which owner/group must be auth-userdb run... although maybe I'm wrong :-S :-) What I'm looking forward to is to eliminate the need for returning these two fixed items, as long as all the virtual_users will be using the same uid and gid. Does anybody know how can I do it?? Regards, and thank you! Felix > Date: Thu, 1 Aug 2013 17:50:33 +0200 > From: Axel Luttgens <AxelLuttgens(a)swing.be> > To: Dovecot Mailing List <dovecot(a)dovecot.org> > Subject: Re: [Dovecot] misconception in uid and gid > Message-ID: <89AC3212-EFE6-41E5-A22D-97DC8E771218(a)swing.be> > Content-Type: text/plain; charset=iso-8859-1 > > Le 1 ao?t 2013 ? 15:43, Felix Rubio Dalmau a ?crit : > > > [...] > > > > Nevertheless, if I remove the segments "'vmail' AS uid, 'vmail' AS gid" and modify the file conf.d/10-mail.conf to show > > > > mail_uid = vmail > > mail_gid = vmail > > > > I get this error: > > > > dovecot: auth: Error: userdb(<mail>): client doesn't have lookup permissions for this user: userdb reply doesn't contain uid (change userdb socket permissions) > > > > Does anybody know what is wrong in my set-up? > > Hello Felix, > > Yes and no... > This still remains a bit unclear to me, but you could try something like this: > > service auth { > > unix_listener auth-userdb { > > # default: user = $default_internal_user > group = vmail # default: group = > mode = 0660 # default: mode = 0666 > } > } > > The code has some provisions to avoid the auth-userdb to be too widely open, in spite of that default mode 0666. Changing that mode short-circuits those provisions, and the above is the most secure setting I could think of in the case of a single uid/gid setup. > > HTH, > Axel

2 1

[Dovecot] Wrong remote IP (rip) in mail.log using IMAP login
by tyli 02 Aug '13

02 Aug '13

Dear list users While trying to secure our dovecot server with fail2ban I came across the following problem: We use dovecot (1.2.9, ubuntu package) behind a NAT, and failed login attempts are logged with our firewall as the remote ip. Example: Apr 15 08:36:26 mail dovecot: imap-login: Disconnected (auth failed, 6 attempts): user=<xy>, method=PLAIN, rip=192.168.0.1, lip=192.168.0.3 Therefore I would ban 192.168.0.1 which means that I ban EVERY user. Funny thing is that POP3 login attempts are logged correctly: Apr 13 11:05:50 mail dovecot: pop3-login: Disconnected (auth failed, 1 attempts): user=<sgvyniwx>, method=PLAIN, rip=217.81.27.55, lip=192.168.0.3 Any ideas how to change this? Thanks in advance tyli

5 5

[Dovecot] Dovecot v2.2.4 (ebbe00999da8) doveadm crash
by e-frog 01 Aug '13

01 Aug '13

Hello, Current Dovecot v2.2 HG crashes using the following command: $ doveadm mailbox status -A -t unseen 'virtual/unread' Please see backtrace below and dovecot -n output attached. Thanks, e-frog gdb /usr/bin/doveadm 24023 GNU gdb (GDB) 7.5.91.20130417-cvs-ubuntu Copyright (C) 2013 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "i686-linux-gnu". For bug reporting instructions, please see: <http://www.gnu.org/software/gdb/bugs/>... Reading symbols from /usr/bin/doveadm...Reading symbols from /usr/lib/debug/usr/bin/doveadm...done. done. Attaching to program: /usr/bin/doveadm, process 24023 warning: unable to open /proc file '/proc/24023/status' warning: unable to open /proc file '/proc/24023/status' ptrace: No such process. [New LWP 24023] warning: Can't read pathname for load map: Input/output error. [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/i386-linux-gnu/libthread_db.so.1". Core was generated by `doveadm mailbox status -A -t unseen virtual/unread'. Program terminated with signal 11, Segmentation fault. #0 i_stream_next_line (stream=0x0) at istream.c:382 382 istream.c: No such file or directory. (gdb) bt full #0 i_stream_next_line (stream=0x0) at istream.c:382 _stream = <optimized out> pos = <optimized out> #1 0xb754656b in auth_master_user_list_next (ctx=0xb91bfbd8) at auth-master.c:689 line = <optimized out> #2 0xb7634a0b in mail_storage_service_all_next (ctx=0xb91c4ba8, username_r=username_r@entry=0xbf8e6630) at mail-storage-service.c:1260 __FUNCTION__ = "mail_storage_service_all_next" #3 0xb7752d46 in doveadm_mail_cmd_get_next_user (ctx=0xb91be478, username_r=0xbf8e6630) at doveadm-mail.c:416 No locals. #4 0xb7753e95 in doveadm_mail_all_users (wildcard_user=0x0, argv=0xb91ba1ec, ctx=0xb91be478) at doveadm-mail.c:368 ret = <optimized out> input = {module = 0x0, service = 0xb77918f3 "doveadm", username = 0xb91bf8a0 "test1(a)local.lan", session_id = 0x0, local_ip = {family = 0, u = { ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = { s_addr = 0}}}, remote_ip = {family = 0, u = {ip6 = {__in6_u = {__u6_addr8 = '\000' <repeats 15 times>, __u6_addr16 = {0, 0, 0, 0, 0, 0, 0, 0}, __u6_addr32 = {0, 0, 0, 0}}}, ip4 = {s_addr = 0}}}, local_port = 0, remote_port = 0, userdb_fields = 0x0, flags_override_add = (unknown: 0), flags_override_remove = (unknown: 0), no_userdb_lookup = 0} user_idx = 0 user = 0xb91bf8a0 "test1(a)local.lan" error = 0x10 <Address 0x10 out of bounds> #5 doveadm_mail_cmd (argv=0xb91ba1ec, argc=-1189371412, cmd=0xbf8e668c) at doveadm-mail.c:523 ctx = 0xb91be478 getopt_args = <optimized out> ret = <optimized out> c = <optimized out> wildcard_user = 0x0 error = <optimized out> #6 doveadm_mail_try_run (cmd_name=cmd_name@entry=0xb91ba200 "mailbox", argc=5, argc@entry=6, argv=argv@entry=0xb91ba1dc) at doveadm-mail.c:608 cmd = 0xbf8e668c #7 0xb7752903 in main (argc=6, argv=0xb91ba1dc) at doveadm.c:398 cmd_name = 0xb91ba200 "mailbox" i = <optimized out> quick_init = false c = <optimized out> (gdb)

2 4

[Dovecot] [PATCH] quota-status: remove unnecessary newlines
by Ulrich Zehl 01 Aug '13

01 Aug '13

Here's a trivial patch for quota-status.c that removes unecessary newlines present in the default overquota message. It applies to 2.2 and 2.1. Ulrich --- a/src/plugins/quota/quota-status.c 2013-08-01 14:35:35.000000000 +0200 +++ b/src/plugins/quota/quota-status.c 2013-08-01 17:58:26.000000000 +0200 @@ -107,7 +107,7 @@ /* over quota */ value = mail_user_plugin_getenv(user, "quota_status_overquota"); if (value == NULL) - value = t_strdup_printf("554 5.2.2 %s\n\n", error); + value = t_strdup_printf("554 5.2.2 %s", error); } value = t_strdup(value); /* user's pool is being freed */ mail_user_unref(&user);

1 0

[Dovecot] trouble with setting individual quota values for multiple namespaces
by Andreas Oster 01 Aug '13

01 Aug '13

Hello all please apologize that I repost this problem again. I tried to get some help several times on the list but did not find/get a solution. I am still struggling to setup different quotas for namespaces. In addition to the default "INBOX" namespace I have created a namespace called "MailArchive" which should have its own quota value of 5G per user. At first I configured quota2 like this: quota2 = maildir:MailArchive quota:ns=MailArchive/ quota2_rule = *:storage=5G and this seemd to work quite well. Users, accessing the MailArchive namespace can see the 5G limit in their mail client, unfortunately in the mail.err log file, errors like these repeatedly appear: Jul 29 11:40:24 mailserver dovecot: imap(testuser): Error: quota: Unknown namespace: MailArchive/ Jul 29 11:41:43 dovecot: last message repeated 47 times In the WIKI I have read, that in order to have quota for different namespaces, one would have to use different quota backends so I changed the quota config for the MailArchive namespace to SQL. namespace inbox { disabled = no hidden = no ignore_on_failure = no inbox = yes list = yes location = mailbox Drafts { auto = subscribe driver = special_use = \Drafts } mailbox Junk { auto = subscribe driver = special_use = \Junk } mailbox Sent { auto = subscribe driver = special_use = \Sent } mailbox "Sent Messages" { auto = no driver = special_use = \Sent } mailbox Trash { auto = subscribe driver = special_use = \Trash } prefix = separator = / subscriptions = yes type = private } namespace { disabled = no hidden = no ignore_on_failure = no inbox = no list = yes location = maildir:/var/vmail/archive/%Ln/Maildir mailbox "Archived Mails" { auto = subscribe driver = } prefix = MailArchive/ separator = / subscriptions = yes type = private } plugin { quota = maildir:User quota:ns= quota2 = dict:Archive Quota:%u.mailarchive:ns=MailArchive/:proxy::sqlquota quota2_rule = *:storage=5G quota_rule = *:storage=1G quota_rule2 = Trash:storage=+200M } dict { sqlquota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext } Unfortunately this did not change anything. Quota is working like expected but I still get the same errors in mail.err. I am currently using dovecot version 2.2.4. Thank you for your kind help best regards Andreas

2 4

[Dovecot] SSL warning messages
by Anand Kumria 01 Aug '13

01 Aug '13

Hi, I've had the following appear in my logfile, and am just wondering what the warning means? dovecot: managesieve-login: Warning: SSL alert: where=0x4008, ret=256: warning close notify [a.b.c.d] dovecot: imap-login: Warning: SSL alert: where=0x4004, ret=256: warning close notify [w.x.y.z] Should I be worrying about these kinds of messages? Dovecot 2.2.4 on Ubuntu 12.04 LTS if it is important. Thanks, Anand

2 1

Re: [Dovecot] Maildir permissions and Solr re-indexing
by Joseph Tam 01 Aug '13

01 Aug '13

Michael Welsh Duggan writes: > 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 > ... > > 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 think the cause is clear enough: you (user=md5i/uid=1000) are not part of group mail (gid=8), so the dovecot user process doing things on your behalf cannot create index files that are anlogous to the mailbox it's indexing. You can either 1) add "md5i" to group mail 2) remove g+w permission on your mail files (making group membership irrelevant) 3) fiddle with "mail_privileged_group = mail", but I'm a little hazy on all the ramifications of this. I don't know your particular circumstances, so I don't know which is best. If (big if) nothing on your system (particularly the MTA) requires access to your mail spool files by running as group=mail, probably 2) is your best option. Joseph Tam <jtam.home(a)gmail.com>

2 1

[Dovecot] LMTP: userdb lookup - user-filter with variables
by Burckhard Schmidt 31 Jul '13

31 Jul '13

I tried to use dovcots lmtp instead of dovecot-lda. postfix has in master.cf ... dovecot-lda -f ... -d ${user} to separate the user part from user(a)hostname.domain. So lookup of "user" succeeds in userdb (LDAP) done by dovecot-lda. I have always local addresses like to=<user(a)hostname.domain> postfix/lmtp[6579]: [ID 197553 mail.info] B3CDA66A16: to=<h0094slk(a)mailstore4.hu-berlin.de> With lmtp the userpart must be separated also. I tried user_filter (LDAP) with %n, %Ln, %8n without success: userdb lookup: user(a)hostname.domain doesn't exist) dovecot-2.1.17 I used "doveadm user h0094slk" and "doveadm user h0094slk(a)mailstore4.hu-berlin.de" for my tests. userdb { driver = ldap args = /usr/dovecot/etc/ldapuser.conf } and ldapuser.conf with ... user_filter = (&(uid=%n) (objectClass=cmsAccount)) user_attrs = homeDirectory=home I modified user_filter like uid=%Ln or uid=%8u success for doveadm user h0094slk (because nothing to split) userdb: h0094slk home : /home/p0094/h0094slk but no success for doveadm user h0094slk(a)mailstore4.hu-berlin.de userdb lookup: user h0094slk(a)mailstore4.hu-berlin.de doesn't exist It looks for me like user_filter do not use variables at this point? What I'm missing? -- Mit freundlichen Grüßen --- Burckhard Schmidt Abteilung Systemsoftware und Kommunikation ZE Computer- und Medienservice der Humboldt-Universität zu Berlin Postanschrift: Unter den Linden 6, 10099 Berlin Standort: Rudower Chaussee 26; 12489 Berlin Tel.: +49-30-2093-70058 Fax: +49-30-2093-2959 Mail: bschmidt(a)cms.hu-berlin.de

1 1

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

[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