- dovecot - dovecot.org

[Dovecot] LMTP hostname ignoring ENV variables
by G H 21 May '14

21 May '14

I am having an issue with LMTP appending the local hostname to received mail from Postfix. I either want to append localhost, a custom string, or nothing at all. Looking through the source code, I believe I should be able to set "export DOVECOT_HOSTNAME" and "export DOVECOT_HOSTDOMAIN" in my initscript to override the hostname set in lmtp/commands.c, client_get_added_headers() I'm using Centos 5; my hostname is mailtest1.atest.qq -- it is not defined in /etc/hosts. The added header is below: Received: from mail.mailorxyz.de by mailtest1.atest.qq (Dovecot) with LMTP id sreUK1+sfFOseQAAPYI4hw for <admin(a)mailorxyz.de>; Wed, 21 May 2014 13:39:03 +0000 Received: by mail.mailorxyz.de (Postfix, from userid 97) id CC743116AB5; Wed, 21 May 2014 13:39:03 +0000 (UTC) I have the following defined in /etc/init.d/dovecot: export DOVECOT_HOSTDOMAIN=dovecot.mailorxyz.de export DOVECOT_HOSTNAME=dovecot.mailorxyz.de Am I missing something or did I misunderstand the source code? Thanks.

2 1

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi Again, we have one domain, i suppose we don't have any problem with %n parameter. our mail server has mapped LUN Storage disk , we have some empty space problems, so i think it's better keep user things in storage for backup etc. we have totally 40K users(most of students) but i think at most 50 of them use this filter, autorespond etc. :) thank you for your reply. Selçuk On Wed, May 21, 2014 at 3:15 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > Hi Selcuk, > > > i changed my 90-sieve.conf >> >> to >> >> sieve = /var/sieve-scripts/%u.sieve >> sieve_dir = /home/vmail/domains/sieve/%n/.sieve >> > > Yeah, looks good. However, do you host multiple domains? In your config > you differ domains: > > mail_location = mbox:/home/vmail/domains/%d/%u > > with sieve = /var/sieve-scripts/%u.sieve , too, but > with sieve_dir = /home/vmail/domains/sieve/%n/.sieve you do not. > > http://wiki2.dovecot.org/Variables > %u user full username (e.g. user@domain) > %n username user part in user@domain, same as %u if there's no domain > %d domain domain part in user@domain, empty if user with no domain > > I suppose, you should use: > > sieve_dir = /home/vmail/domains/sieve/%u/.sieve > > otherwise info(a)example.org and info@localhost share the same Sieve dir. > > BTW: Because you have an unique directory per user now anyway, why not use > is that as home directory? I'm not sure, what other things use the home > for. E.g. use > > mail_home = /home/vmail/domains/home/%d/%u > > and keep the home-relative paths for Sieve: ~/... > > > On Wed, May 21, 2014 at 12:10 PM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> Hash: SHA1 >>> >>> On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>> my dovecot conf is >>> >>>> >>>> doveconf -n >>>> # 2.0.9: /etc/dovecot/dovecot.conf >>>> >>>> [...] >>> >>> mail_location = mbox:/home/vmail/domains/%d/%u >>>> >>>> [...] >>> >>> userdb { >>>> args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext >>>> driver = ldap >>>> } >>>> >>>> you're right we have mail_location , >>>> >>>> should i add mail_home value >>>> >>>> >>> That depends on if your LDAP configuration contains a (for the mailserver >>> usable) home for the individual user. >>> >>> mail_home = /home/vmail/domains/%d/%u >>> >>>> >>>> >>> The value shows that you did not followed my advice from the last >>> response: "Read the link above about why not store Sieve files below an >>> user's mail location." maybe because you missed it because you toppost. >>> >>> to 10-mail.conf file ? >>> >>>> >>>> >>> never use the same dir for mail location and user's home. >>> >>> >>> On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < >>> >>>> skdovecot(a)smail.inf.fh-brs.de> wrote: >>>> >>>> -----BEGIN PGP SIGNED MESSAGE----- >>>> >>>>> >>>>> >>>> On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>>> >>>>> our users stored OpenLdap and users home folder like below: >>>>> >>>>> >>>>>> >>>>>> without seeing your current doveconf -n output and the ldap >>>>> configuration >>>>> file, I would guess that your users have no home directory: >>>>> http://wiki2.dovecot.org/VirtualUsers/Home >>>>> >>>>> >>>>> >>>>> /home/vmail/domains/domainname.edu.tr/username/... >>>>> >>>>>> >>>>>> now when i used default settings for dovecot sieve >>>>>> >>>>>> sieve = ~/.dovecot.sieve >>>>>> sieve_dir = ~/sieve >>>>>> >>>>>> sieve script write and work globaly and stored, >>>>>> /home/vmail/domains/sieve >>>>>> >>>>>> i looked up Dovecot docs for per user but i don't understand clearly >>>>>> >>>>>> can i replace sieve parameters like >>>>>> >>>>>> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot. >>>>>> sieve >>>>>> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/. >>>>>> sieve >>>>>> >>>>>> for per user scirpt. >>>>>> >>>>>> >>>>>> Read the link above about why not store Sieve files below an user's >>>>> mail >>>>> location. >>>>> >>>>> >>>> - -- Steffen Kaiser >>> -----BEGIN PGP SIGNATURE----- >>> Version: GnuPG v1.4.11 (GNU/Linux) >>> >>> iQEVAwUBU3xtn3z1H7kL/d9rAQIu1wf/XMXuEC1O1PQssoU1uHfTM5jOHpH1KHis >>> yUL1z2/WV8c7engx+CNtGPxnRewC1UFKBZcHaAyXHNxQM+jsYf+NkUo4PDlKkzfi >>> /JIn+SGOlwZKJUYarnAJbt0CdZG7f8auvMLsoovR8iNitSAdyH5AkRt9i25YFndW >>> Nm0lYO1CPJzKp3CVhDS0Lxs6sSD21xsMvuauzMmS4ZpYhXXEdOf4jqNkIYdJbSHz >>> nBHx8sjlJaKNKO3OWs1S5T7DxlRz+VYGw1IZ1BUgpBBD3LxDIOwTLG7NNjWRG2lB >>> nTB+WK02fvh0T+oJORVuKmgoXG5WKvZjFOa4oVqdbbzM6V4ZJSx9Sw== >>> =bLQp >>> -----END PGP SIGNATURE----- >>> >>> >> >> >> >> > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3yY9Hz1H7kL/d9rAQIIpwf/bfNNbI3zCEuJs3xYq5Nl+Td2QGX0uUzk > 8PA4taMNrq00W3jBtTi8J4/ZlqT+l15r5nDr6O/VSgffymi9l0JmRMRIfUyzfjBy > IThSQTrbjx9t+gCJa15Q2JISYEhXC0WYDpseEZle5vFyIKxWT01FYH5cJe45n9ci > LcY3QmCdrQ4JYuYPiECfOx5rFw7dvZBnS4YDLg/A/O3dUzx7BV6V+cSepAecpoom > 4U5udqoWRF1pDgKywn0elB0WorEbgnyOHLSrd5uPOuQuP9aW2bcWJGSpr1/j5tQk > tOYd/czhNhpPEKbzH/MJyn6mbhu4F3DGMAfuD9tweIAD25A41HgVpQ== > =6w4r > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

1 0

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi, Steffen i changed my 90-sieve.conf to sieve = /var/sieve-scripts/%u.sieve sieve_dir = /home/vmail/domains/sieve/%n/.sieve and it works. thank you. On Wed, May 21, 2014 at 12:10 PM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > my dovecot conf is >> >> doveconf -n >> # 2.0.9: /etc/dovecot/dovecot.conf >> > [...] > >> mail_location = mbox:/home/vmail/domains/%d/%u >> > [...] > >> userdb { >> args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext >> driver = ldap >> } >> >> you're right we have mail_location , >> >> should i add mail_home value >> > > That depends on if your LDAP configuration contains a (for the mailserver > usable) home for the individual user. > > mail_home = /home/vmail/domains/%d/%u >> > > The value shows that you did not followed my advice from the last > response: "Read the link above about why not store Sieve files below an > user's mail location." maybe because you missed it because you toppost. > > to 10-mail.conf file ? >> > > never use the same dir for mail location and user's home. > > > On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < >> skdovecot(a)smail.inf.fh-brs.de> wrote: >> >> -----BEGIN PGP SIGNED MESSAGE----- >>> >> > On Wed, 21 May 2014, Selcuk Yazar wrote: >>> >>> our users stored OpenLdap and users home folder like below: >>> >>>> >>>> >>> without seeing your current doveconf -n output and the ldap configuration >>> file, I would guess that your users have no home directory: >>> http://wiki2.dovecot.org/VirtualUsers/Home >>> >>> >>> >>> /home/vmail/domains/domainname.edu.tr/username/... >>>> >>>> now when i used default settings for dovecot sieve >>>> >>>> sieve = ~/.dovecot.sieve >>>> sieve_dir = ~/sieve >>>> >>>> sieve script write and work globaly and stored, >>>> /home/vmail/domains/sieve >>>> >>>> i looked up Dovecot docs for per user but i don't understand clearly >>>> >>>> can i replace sieve parameters like >>>> >>>> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve >>>> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/. >>>> sieve >>>> >>>> for per user scirpt. >>>> >>>> >>> Read the link above about why not store Sieve files below an user's mail >>> location. >>> >> > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3xtn3z1H7kL/d9rAQIu1wf/XMXuEC1O1PQssoU1uHfTM5jOHpH1KHis > yUL1z2/WV8c7engx+CNtGPxnRewC1UFKBZcHaAyXHNxQM+jsYf+NkUo4PDlKkzfi > /JIn+SGOlwZKJUYarnAJbt0CdZG7f8auvMLsoovR8iNitSAdyH5AkRt9i25YFndW > Nm0lYO1CPJzKp3CVhDS0Lxs6sSD21xsMvuauzMmS4ZpYhXXEdOf4jqNkIYdJbSHz > nBHx8sjlJaKNKO3OWs1S5T7DxlRz+VYGw1IZ1BUgpBBD3LxDIOwTLG7NNjWRG2lB > nTB+WK02fvh0T+oJORVuKmgoXG5WKvZjFOa4oVqdbbzM6V4ZJSx9Sw== > =bLQp > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] dovecot auth ldap attributes - unused?
by Maciej Uhlig 21 May '14

21 May '14

Please explain the following dovecot (2.2.13) behaviour: I run dovecot in ldap auth debug mode and log file excerpt follows: 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): bind search: base=o=tree,dc=do,dc=ma,dc=in filter=(&(objectClass=MailAccount)(accountActive=TRUE)(mail=user@domain)) 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mail=user@domain; mail unused 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mail=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: client passdb out: OK 24 user=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): user search: base=o=tree,dc=do,dc=ma,dc=in scope=subtree filter=(&(objectClass=MailAccount)(accountActive=TRUE)(mail=user@domain)) fields=mail,quota,mailbox 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mailbox=maildir:/mail/domain/user/mail/ quota=1G mail=user@domain; mail,mailbox,quota unused 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: ldap(user@domain,pcip,<bdKvA+P5HQCbnmFI>): result: mailbox=maildir:/mail/domain/user/mail/ quota=1G mail=user@domain 2014-05-21T08:22:01+02:00 dovecot/ip dovecot: auth: Debug: master userdb out: USER 3606315009 user@domain quota_rule=*:bytes=1G mail=maildir:/mail/domain/user/mail/ home=/mail/domain/user Question: why are there two ldap result log lines while the first line shows unused attributes and the second doesn't. Does the first occurence show some code being excessive somehow? Thanks. MU

2 1

[Dovecot] allow_nets + default + ldap
by Andreas Schulze 21 May '14

21 May '14

Hello, I'm playing with allow_nets function. It is really cool! In a filebased passwd backend you simply add "allow_nets=192.0.2.143/32" as mentioned in http://wiki2.dovecot.org/PasswordDatabase/ExtraFields/AllowNets But if I use an LDAP backend it looks different. Following http://wiki2.dovecot.org/AuthDatabase/LDAP/AuthBinds and http://wiki2.dovecot.org/AuthDatabase/LDAP/Userdb#Attribute_templates_.28v2… my pass_attrs looks this: pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets} Using this syntax I could add an attribute "allownets" in the ldapserver to limit access for a user. A problem occour if the attribute is not present. For example if a user should not be limited or only some but not any user should be limited. So I extend my pass_attrs with a default. pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets:10.0.0.0/8} Again, that's fine. Any user was allowed to connect from my private network. But then some users connect via ipv6. I tried to extend my default to pass_attrs = =user=%{ldap:uid}, \ =allow_nets=%{ldap:allownets:10.0.0.0/8,fec0::/16} That syntax, a comma separated list, produces errors no matter if quoting using " or ' or no quoting at all. So I looked at the source (thanks, it's open!) and wrote a little patch to allow simple defaults: - ALL -> allow any address - NONE -> deny any address Now I could write pass_attrs = =user=%{ldap:uid}, =allow_nets=%{ldap:allownets:ALL} or pass_attrs = =user=%{ldap:uid}, =allow_nets=%{ldap:allownets:NONE} to allow or deny any ldap account not having an attribute allownets. Maybe there are other solutions, but that's my way... Andreas

2 3

Re: [Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi my dovecot conf is doveconf -n # 2.0.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-131.6.1.el6.x86_64 x86_64 Red Hat Enterprise Linux Server release 6.0 (Santiago) ext4 auth_debug = yes auth_debug_passwords = yes auth_default_realm = hostname.domainname.edu.tr auth_mechanisms = plain login auth_verbose = yes debug_log_path = /var/log/dovecot.debug disable_plaintext_auth = no first_valid_uid = 97 info_log_path = /var/log/dovecot.info last_valid_uid = 5000 mail_debug = yes mail_gid = 1001 mail_location = mbox:/home/vmail/domains/%d/%u mail_uid = 1001 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 mbox_write_locks = fcntl passdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } protocols = imap pop3 lmtp sieve service auth { unix_listener auth-userdb { mode = 0600 user = vmail } } service managesieve-login { inet_listener sieve { port = 4190 } inet_listener sieve_deprecated { port = 2000 } } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { args = /etc/dovecot/conf.d/dovecot-ldap.conf.ext driver = ldap } protocol lda { debug_log_path = /var/log/dovecot-lda-errors.log info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log mail_plugins = " sieve" } you're right we have mail_location , should i add mail_home value mail_home = /home/vmail/domains/%d/%u to 10-mail.conf file ? thanks. On Wed, May 21, 2014 at 11:43 AM, Steffen Kaiser < skdovecot(a)smail.inf.fh-brs.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > > On Wed, 21 May 2014, Selcuk Yazar wrote: > > our users stored OpenLdap and users home folder like below: >> > > without seeing your current doveconf -n output and the ldap configuration > file, I would guess that your users have no home directory: > http://wiki2.dovecot.org/VirtualUsers/Home > > > >> /home/vmail/domains/domainname.edu.tr/username/... >> >> now when i used default settings for dovecot sieve >> >> sieve = ~/.dovecot.sieve >> sieve_dir = ~/sieve >> >> sieve script write and work globaly and stored, /home/vmail/domains/sieve >> >> i looked up Dovecot docs for per user but i don't understand clearly >> >> can i replace sieve parameters like >> >> sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve >> sieve_dir = /home/vmail/domains/.........................edu.tr/%n/.sieve >> >> for per user scirpt. >> > > Read the link above about why not store Sieve files below an user's mail > location. > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.11 (GNU/Linux) > > iQEVAwUBU3xnMHz1H7kL/d9rAQIiRAgAmZYxZo1fn/5Iw0WHB2v3FpF1snq1VH4t > tvyhS/ISj3snMB7dbViUkjvYhzaIsWQKP9eXM3YtOmwpSdlwozqwq/5PvckQgAkU > cI8UIyXCErsdsvp7/aod/n+Qd+tnjf91b3PY9R7xYd6Qjf/8H7lSmX/xBMBltu7N > AVqwgHTivR9dwsDyTkIqQIfULWvwcWf5eXbKzP1YxamYzF+lMk6ippK7RebMrspe > CTg1BLCCLiHMTdSQrOrnfmNjgS/rAZctOEyc3/M98U8HxmEhT6ZFpTjQ4i0T0/17 > +9DQovMUi2/bZ1IhgBpS9u+YkPeuu+y4vAhMqCAT+fcEW1+MgfK2Lg== > =Sc/m > -----END PGP SIGNATURE----- > -- Selçuk YAZAR http://www.selcukyazar.blogspot.com

2 1

[Dovecot] Per-user Sieve script location question
by Selcuk Yazar 21 May '14

21 May '14

Hi, after some problems, i successfuly ran my dovecot delivery and pigeonhole service in redhat EL 6. our users stored OpenLdap and users home folder like below: /home/vmail/domains/domainname.edu.tr/username/... now when i used default settings for dovecot sieve sieve = ~/.dovecot.sieve sieve_dir = ~/sieve sieve script write and work globaly and stored, /home/vmail/domains/sieve i looked up Dovecot docs for per user but i don't understand clearly can i replace sieve parameters like sieve = /home/vmail/domains/..................edu.tr/%n/.dovecot.sieve sieve_dir = /home/vmail/domains/.........................edu.tr/%n/.sieve for per user scirpt. thanks in advance. -- Selçuk YAZAR

2 1

[Dovecot] Setting mail location in SQL?
by Marc Perkel 21 May '14

21 May '14

Trying to figure out the syntax to set a mail_location for SQL. This doesn't work: userdb { driver = sql args = /etc/dovecot/master-combined-sql.conf override_fields = mail_location=maildir:/fakedir/%d/%n:INBOX=/fakedir:LAYOUT=fs } Does anyone know the proper syntax? Thanks in advance

2 3

[Dovecot] Dict SQL lookups without username_field
by Andrew Beverley 20 May '14

20 May '14

Dear all, Is it possible to perform dict lookups with a SQL backend, without specifying the username_field in the SQL query? I am using the dict to retrieve a Sieve script. My dict configuration looks like this: map { pattern = priv/sieve/data/$id table = sieve_scripts username_field = email value_field = data fields { id = $id } } I don't want to specify the username though, as the sieve scripts are valid for all users. However, when I remove "username_field" I get the error "data with id `1' for script `main script' not found at path priv/sieve/data/1" Thanks, Andy

1 0

[Dovecot] Performing an action on mail receipt
by Andrew Beverley 20 May '14

20 May '14

Dear all, I would like to perform an action for certain users each time a mail arrives via LMTP. I would like to send an email notification to an external email address when new mail has arrived for certain users (note: not a forward). I am assuming that creating my own plugin using the existing "notify" plugin is the way to go. However, before I go down that route, I'd like to check that is the best approach? Or would it be better to perform this sort of thing before the mail reaches Dovecot? Assuming writing a plugin is answer, do they have to be written in C? Dovecot version: 2.1.7 Thanks, Andy

4 6