- dovecot - dovecot.org

[Dovecot] system_groups_user syntax especially in LDAP
by ray klassen 02 Aug '13

02 Aug '13

so if possible, I'd like an example of how to include system_groups_user in the userdb setup. I'm using ldap, but I could revert to using pam on ldap. There is a ldap query (gleaned from smbldap-tools) that will return a list of groups for a user (&(objectclass=posixGroup)(memberuid=%u)) but I don't know if the ldap driver will handle it but above all I can't figure out how it fits into the dovecot configuration! I'm trying to get Dovecot 2.1.7 on debian wheezy to recognize shared folders that have group ownership.

1 1

[Dovecot] Lowering Log Levels Back to Defaults
by Asai 02 Aug '13

02 Aug '13

Greetings, I'm sorry for asking what may be a really obvious question, but I'm having a hard time turning off logging, or at least getting less verbose logging. My dsync logs are about 7 MB daily, and I'm trying to get that switched off. At one point I had it on a lower level of verbosity, and I turned it up for debugging purposes, but now I cannot seem to turn it back down, which is something I did many times before. For example the logs are getting tons of Info level messages. dsync(asai(a)globalchangemusic.org): Info: expunge: box=Trash, uid=61625, msgid=<JIRA.14456.1367259371732.1046.1367259384800@hexagon>, size=9586 In dovecot.conf I have commented out the following include, which used to lower the log levels back to the defaults, but I've upgraded Dovecot recently to 2.2.4 from 2.1 something: #!include conf.d/10-logging.conf I had the default levels raised in that config file. I'm not sure this helps but: [vmail@triata ~]# doveconf -n # 2.2.4: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-194.32.1.el5xen x86_64 CentOS release 5.5 (Final) ext3 auth_mechanisms = plain login mail_home = /vmail/%d/%n/home mail_location = maildir:/vmail/%d/%n mail_plugins = " mail_log notify" 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 namespace { inbox = yes location = prefix = separator = / type = private } passdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } plugin { sieve = /vmail/%d/%n/sievescript } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } unix_listener auth-master { group = vmail mode = 0660 user = vmail } unix_listener auth-userdb { mode = 0660 user = vmail } user = root } service imap-login { process_min_avail = 3 service_count = 0 vsz_limit = 0 } ssl_cert = </etc/postfix/ssl/triata.globalchangemultimedia.net.pem ssl_key = </etc/postfix/ssl/triata.key userdb { args = /etc/dovecot/dovecot-mysql.conf driver = sql } protocol lda { hostname = triata.globalchangemultimedia.net mail_plugin_dir = /usr/lib64/dovecot/ mail_plugins = sieve postmaster_address = postmaster(a)globalchangemultimedia.net } protocol imap { imap_idle_notify_interval = 24 mins mail_max_userip_connections = 60 } -- --Asai

2 2

[Dovecot] Custom quota setup
by Richard Platel 02 Aug '13

02 Aug '13

(Dovecot 2.2-ee) We have a weird quota requirement, we have file storage that we manage through our own APIs but want that usage to come out of the user's mail quota. The usage is in a maildirsize like file uncreatively called filestoresize in the user's maildir. In the past we've been doing this by modifying the quota plugin and re-compiling, but it seems like it should be possible to do this via configuration. Is there a way to add a quota setting pointing at this file for additional usage (not limits)? The feature is used infrequently so it would probably be acceptable use the dirsize backend, but I can't figure out how to configure that to point at a certain directory. We pass custom quota rules for each user in our userdb, and use a custom dict proxy program, so that program could read the file and pass a setting at log in time too (if, for example, there was a setting that said "offset the user's quota usage by X amount") Thanks.

2 5

[Dovecot] dsync backup mails compressed
by Robert Schetterer 02 Aug '13

02 Aug '13

Hi Timo , looks like if zlib plugin is enabled all backupmails ( Maildir ) getting compressed i tested this dsync -o plugin/acl= -o plugin/quota= -u user(a)beispiel.de backup maildir://nfs-backup-data/user@beispiel.de adding -o plugin/zlib= didnt help i am not sure , what is the expected behave , and why -o plugin/quota= does not work ? Best Regards MfG Robert Schetterer -- [*] sys4 AG http://sys4.de, +49 (89) 30 90 46 64 Franziskanerstraße 15, 81669 München Sitz der Gesellschaft: München, Amtsgericht München: HRB 199263 Vorstand: Patrick Ben Koetter, Axel von der Ohe, Marc Schiffbauer Aufsichtsratsvorsitzender: Florian Kirstein

2 3

Re: [Dovecot] HTTP passdb (was: feature request: IMAP passdb prefetch)
by Timo Sirainen 02 Aug '13

02 Aug '13

(Cc'd to dovecot list anyway since other people might be interested) On 2.8.2013, at 18.34, Richard Platel <rplatel(a)tucows.com> wrote: >> Uh. Why not simply something completely different like HTTP-based passdb? > > I can't find info for HTTP on the wiki, can we set that up as a success/fail passdb? We do our own password auth (so we can support custom hash types, etc). I've only a private version of a HTTP-based passdb implemented for a customer. I'm not sure if I should bother adding something to be distributed with Dovecot, since I guess most people would want to modify it in some way anyway. Here's a somewhat modified version of it that hopefully works (at least it compiles): http://dovecot.org/patches/2.2/passdb-openam.c

1 0

[Dovecot] feature request: IMAP passdb prefetch
by Richard Platel 02 Aug '13

02 Aug '13

> On 2.8.2013, at 18.20, Richard Platel <rplatel(a)tucows.com> wrote: > >> It'd be useful for us if the IMAP passdb could be used as a prefetch userdb. >> >> The remote IMAP server could respond with something like >> >> * OK key=value >> * OK key=value >> SEQ OK [CAPABILITY ...] Logged in. >> >> Or >> >> * OK <some JSON key value pairs> >> SEQ OK [CAPABILITY ...] Logged in. >> >> Would anyone else find this useful? > > Uh. Why not simply something completely different like HTTP-based passdb? > I can't find info for HTTP on the wiki, can we set that up as a success/fail passdb? We do our own password auth (so we can support custom hash types, etc).

1 0

[Dovecot] feature request: IMAP passdb prefetch
by Richard Platel 02 Aug '13

02 Aug '13

It'd be useful for us if the IMAP passdb could be used as a prefetch userdb. The remote IMAP server could respond with something like * OK key=value * OK key=value SEQ OK [CAPABILITY ...] Logged in. Or * OK <some JSON key value pairs> SEQ OK [CAPABILITY ...] Logged in. Would anyone else find this useful?

2 1

Re: [Dovecot] Mail being delivered but MUA showing empty inbox
by Nigel Smith 02 Aug '13

02 Aug '13

> You should take this discussion off list. Tell me Dem.... which part of my original question was not fit for the list ? It was a perfectly valid technical question relating to Dovecot, and according to the description of the mailing list "This is the main list for requesting help with Dovecot or talking about it in general" So I was "requesting help" with Dovecot, and everyone else is perfectly within their rights to "talk about it".

1 0

[Dovecot] 2.2.4 - Some questions about and needing help with quota-status
by Axel Luttgens 02 Aug '13

02 Aug '13

Help! I'm stuck. :-( The config of my experimental setup appears at the end of this message; I'm providing hereafter some more info that may not be immediately obvious. This is dovecot 2.2.4 with changesets 9091d0f2d971 and 2be295a0b64f. All involved databases are sqlite ones. passdb and userdb are devised so as to change usernames. For example, I could have a user with addresses "doe(a)oldexample.com", "johnd(a)oldexample.com" and "john.doe(a)example.com" needing to be able to log in as "jdoe" or "u123456"; all db lookups for that user then end with name "john.doe". This is a single mail user setup (user/group "dovemailer", uid/gid 999). Service lmtp has been configured to run as that user; that required a slight adjustment at the auth-userdb socket level. As a general rule, the quota dict appears to be correctly updated upon message arrivals and removals (thru lmtp, pop, imap), and to be correctly queried/interpreted by the various parts of the server. For example, thru the userdb query, user john.doe has been given an even lower quota limit than the already low default defined for testings: $ sudo doveadm quota get -u john.doe Quota name Type Value Limit % Quota utilisateur STORAGE 20 5 400 Quota utilisateur MESSAGE 14 - 0 and is clearly recognized as being over-quota by lmtp: $ telnet /_ROOT/var/run/dovecot/lmtp Trying /_ROOT/var/run/dovecot/lmtp... Connected to (null). Escape character is '^]'. 220 almba.local Dovecot ready. mail from:<mary.jane(a)example.com> 250 2.1.0 OK rcpt to:<john.doe(a)example.com> 250 2.1.5 OK data 354 OK Subject: test . 552 5.2.2 <john.doe(a)example.com> Quota exceeded (mailbox for user is full) Note that both services config and dict are launched if they aren't running. Since it has been previously seen that running quota-status as root comes with its own problems, and since it is a single user setup anyway, I'm trying to run it as dovemailer as well. So, let's try to see what quota-status thinks about john.doe: $ 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 '^]'. Connection closed by foreign host. Clearly, not much... Looking in the log: dovecot[10554]: quota-status: Fatal: Error reading configuration: net_connect_unix(/_ROOT/var/run/dovecot/config) failed: Permission denied This thus raises a first question: Q1. What makes lmtp and quota-status different? How does lmtp manage to fetch all needed info, while quota-status seems to require an access to the config socket? Let's then slightly adjust dovecot.conf, in the hope to make quota-status happy: service config { unix_listener config { group = dovemailer mode = 0660 } } Q2. Should the above really be needed, wouldn't there be a better way? I ask, because it seems to me that I'm starting to seriously lose the benefits of privilege separation... Anyway, let's ask quota-status again: $ sudo -u _postfix telnet /_ROOT/var/spool/postfix/private/quota-policyd Password: Trying /_ROOT/var/spool/postfix/private/quota-policyd... Connected to (null). Escape character is '^]'. recipient=john.doe(a)example.com size=10000 action=OK ^] telnet> quit Connection closed. In the log: dovecot[11050]: auth: Debug: userdb out: USER 1 john.doe(a)example.com quota_rule=*:storage=5k dovecot[11050]: quota-status: Debug: auth input: john.doe(a)example.com quota_rule=*:storage=5k dovecot[11050]: quota-status: Debug: Added userdb setting: plugin/quota_rule=*:storage=5k dovecot[11050]: quota-status(john.doe(a)example.com): Debug: Effective uid=999, gid=999, home=/_Mailstores/john.doe dovecot[11050]: quota-status(john.doe(a)example.com): Debug: Quota root: name=Quota utilisateur backend=dict args=john.doe:proxy::sql_quota dovecot[11050]: quota-status(john.doe(a)example.com): Debug: Quota rule: root=Quota utilisateur mailbox=* bytes=5120 messages=0 dovecot[11050]: quota-status(john.doe(a)example.com): Debug: Quota grace: root=Quota utilisateur bytes=512 (10%) dovecot[11050]: quota-status(john.doe(a)example.com): Debug: dict quota: user=john.doe, uri=proxy::sql_quota, noenforcing=0 dovecot[11050]: quota-status(john.doe(a)example.com): Debug: fs: root=/_Mailstores/john.doe/mboxes, index=, indexpvt=, control=, inbox=/_Mailstores/john.doe/mboxes/inbox, alt= It is to be noted that the config server is now launched as expected, but that the dict server still isn't. Trying a dirsize backend instead of the dict backend doesn't help. The problem seems to be circumscribed to the interaction with the quota backend since, for example, querying quota-status for an unknown recipient yields an expected "action=REJECT Unknown user". Hence my last question, after having tried a lot of things for several days now, with no more success: Q3. What am I doing wrong? Many thanks in advance, Axel # 2.2.4: /_ROOT/etc/dovecot/dovecot.conf # OS: Darwin 12.4.0 x86_64 auth_debug = yes dict { sql_quota = sqlite:/_ROOT/etc/dovecot/dict-quota.conf } disable_plaintext_auth = no listen = * mail_debug = yes mail_gid = dovemailer mail_home = /_Mailstores/%n mail_location = mbox:~/mboxes:INBOX=~/mboxes/inbox mail_plugins = quota mail_uid = dovemailer managesieve_sieve_capability = vacation mbox_write_locks = fcntl passdb { args = /_ROOT/etc/dovecot/db.conf driver = sql } plugin { quota = dict:Quota utilisateur:%n:proxy::sql_quota quota_rule = *:storage=50M sieve = ~/sieve/active_script.sieve sieve_dir = ~/sieve/scripts sieve_extensions = vacation sieve_max_actions = 3 sieve_max_redirects = 2 sieve_max_script_size = 10K sieve_user_log = ~/sieve/log } service auth { unix_listener auth-userdb { group = dovemailer mode = 0660 user = $default_internal_user } } service dict { unix_listener dict { group = dovemailer mode = 0660 } } service lmtp { group = dovemailer user = dovemailer } service quota-status { client_limit = 1 executable = quota-status -p postfix group = dovemailer unix_listener /_ROOT/var/spool/postfix/private/quota-policyd { user = _postfix } user = dovemailer } ssl = no userdb { driver = prefetch } userdb { args = /_ROOT/etc/dovecot/db.conf driver = sql } protocol lmtp { mail_plugins = quota sieve postmaster_address = postmaster(a)example.com sendmail_path = /_ROOT/postfix/sbin/sendmail } protocol pop3 { pop3_uidl_format = %08Xv%08Xu }

2 9

[Dovecot] mails delivered to the wrong user when using lmtp_proxy and reject_unverified_recipient
by Peer Heinlein 02 Aug '13

02 Aug '13

Hi, looks like we detected a serious bug in dovecot's lmtp proxying where e-mails are delivered to the wrong user. The setup is: *) Dovecot is configured with "lmtp_proxy=yes" # Support proxying to other LMTP/SMTP servers by performing passdb lookups. lmtp_proxy = yes *) Postfix uses "dynamic recipient verification", so Postfix starts sending a (verify) mail by LMTP to dovecot, but quits the lmtp-session right after the RCPT TO:. No DATA-stage is reached in the protocol and no real e-mail is sent. But Postfix had a LMTP-connection for "user1". *) Just some seconds later a "real" e-mail to "user2" has to be delivered to dovecot by LMTP. But Dovecot will deliver this mail to the wrong "user1" instead of "user2". Looks like dovecot re-uses the (still opened?) lmtp-proxy-connection from "user1" to deliver an e-mail to "user2". Have a log at the protocol: 1) There's a verify call to user1 from Postfix: Jul 19 13:49:49 mailms postfix/lmtp[9842]: DE653280C51: to=<user1(a)example.com>, relay=localhost[127.0.0.1]:24, conn_use=2, delay=120, delays=117/0.45/0/2.5, dsn=2.1.5, status=deliverable (250 2.1.5 OK) 2) Just five seconds later the e-mail to user2 (see Postfix' point of view in the last line) is delivered to user2 (see result from Dovecot in the last line): Jul 19 13:50:04 mailms dovecot: lmtp(10965, kraemer): save: box=INBOX, uid=49880, msgid=<59798276-E5D1-4053-A570-9901B731DF5D(a)example.come>, size=11020 Jul 19 13:50:04 mailms dovecot: lmtp(10965, kraemer): 1zTeKrMn6VHVKgAAhyqEuA: msgid=<59798276-E5D1-4053-A570-9901B731DF5D(a)example.com>: saved mail to INBOX Jul 19 13:50:04 mailms postfix/lmtp[10953]: C25FC280BE5: to=<user2(a)example.com>, relay=localhost[127.0.0.1]:24, conn_use=19, delay=116, delays=115/0.53/0/0.33, dsn=2.0.0, status=sent (250 2.0.0 <user2> 1zTeKrMn6VHVKgAAhyqEuA Saved) Same with user3 and user4: Jul 19 14:47:53 mailms postfix/lmtp[10845]: C389A2809D7: to=<user3(a)example.com>, relay=localhost[127.0.0.1]:24, delay=4.7, delays=3.7/0.87/0/0.19, dsn=2.1.5, status=deliverable (250 2.1.5 OK) Jul 19 14:47:55 mailms dovecot: lmtp(26546, fs211113): save: box=INBOX, uid=8504, msgid=<928729810.113.1374238063381(a)example.com>, size=233151 Jul 19 14:47:55 mailms dovecot: lmtp(26546, fs211113): MbMvI2816VGyZwAAhyqEuA: msgid=<928729810.113.1374238063381(a)example.com>: saved mail to INBOX Jul 19 14:47:55 mailms postfix/lmtp[22524]: 6F0D2280A6E: to=<user4(a)example.com>, relay=localhost[127.0.0.1]:24, conn_use=2, delay=10, delays=8.4/1/0/0.8, dsn=2.0.0, status=sent (250 2.0.0 <user3> MbMvI2816VGyZwAAhyqEuA Saved) The user itself is quite normal in the user database (but has a mailhost=127.0.0.1 set): root@mailms:/etc/dovecot/conf.d# doveadm user user2(a)example.com userdb: user2(a)example.com uid : 5000 gid : 5000 home : /srv/mail/user2 root@mailms:/etc/dovecot/conf.d# doveadm auth user2(a)example.com Password: passdb: user2(a)example.com auth failed extra fields: user=user2 Peer -- Heinlein Support GmbH Schwedter Str. 8/9b, 10119 Berlin http://www.heinlein-support.de Tel: 030 / 405051-42 Fax: 030 / 405051-19 Zwangsangaben lt. §35a GmbHG: HRB 93818 B / Amtsgericht Berlin-Charlottenburg, Geschäftsführer: Peer Heinlein -- Sitz: Berlin

4 3