June 2011 - dovecot - dovecot.org

[Dovecot] 2.0: deliver run from multiple uids and configuration files
by Arkadiusz Miskiewicz 03 Jun '11

03 Jun '11

I'm trying to run deliver from exim transport in a way that it doesn't need to query userdb AND doesn't need to read configuration files. The problem is that config files are readable for root only and if I run deliver with multiple UIDs then I would have to allow reading config files for everyone. Of course that's not a option because configs contain database passwords and such stuff. I wonder if it is possible to avoid reading config files by deliver? The only solution I see it to run deliver via sudo which doesn't look nice. -- Arkadiusz Miśkiewicz PLD/Linux Team arekm / maven.pl http://ftp.pld-linux.org/

2 1

[Dovecot] LMTP/Sieve/sendmail path
by Andreas Schulze 03 Jun '11

03 Jun '11

Hello, I have a system using postfix multi instance feature. The first, main postfix-instance is a nullclient as suggested by http://www.postfix.org/MULTI_INSTANCE_README.html#split The second instance is for real use. Postfix receive mail and handover them to the dovecot lmtp server. Thats working. The lmtp server supports sieve. One account has activated a vacation rule. So while delivering a mail to this account, dovecot creates a new mail based on the vacation rules. *This one* fail. It is injected in the main postfix instance, which is wrong in this case. I tried to start dovecot with an additional environment MAIL_CONFIG=/etc/postfix-instance2 and enabled alternate_config_directories in main.cf of the first insance. ( http://www.postfix.org/postconf.5.html#alternate_config_directories ) I also configured the userdb to return an extrafield userdb_mail_config=/etc/postfix-instance2. But all produce strance postfix errors I never saw in my last 6 years as postfix-admin. Would it be possible to configure dovecot lmtp server to use an external smtp-server to submit new mails ? Any other Ideas ? Thanks Andreas -- Andreas Schulze Internetdienste | P252 DATEV eG 90329 Nürnberg | Telefon +49 911 319-0 | Telefax +49 911 319-3196 E-Mail info @datev.de | Internet www.datev.de Sitz: 90429 Nürnberg, Paumgartnerstr. 6-14 | Registergericht Nürnberg, GenReg Nr.70 Vorstand Prof. Dieter Kempf (Vorsitzender) Dipl.-Kfm. Wolfgang Stegmann (stellvertretender Vorsitzender) Dipl.-Kfm. Michael Leistenschneider Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

4 3

[Dovecot] Baffled after upgrade
by Bert Todger 02 Jun '11

02 Jun '11

Hello all, I have just upgraded my Fedora 13 system to F15. With it came a shiny new dovecot 2.0.13 (Details of dovecot -n below). The configuration is different from the dovecot 1.something that I had been used to with F13, but I managed to get it working and all was well... Without changing anything related to dovecot (as far as I know), after a reboot, dovecot stopped working. I did a bit of digging, upped the verbosity of logging and found this in the logs: =======8<================================================================= Jun 02 09:58:21 auth: Debug: passwd-file /etc/passwd.dovecot: Read 3 users Jun 02 09:58:21 auth: Debug: auth client connected (pid=16699) Jun 02 09:58:21 auth: Debug: client in: AUTH 1 PLAIN service=imap secured lip=192.168.2.2 rip=192.168.2.2 lport=993 rport=33960 Jun 02 09:58:21 auth: Debug: client out: CONT 1 Jun 02 09:58:21 auth: Debug: client in: CONT 1 AG1hcmsAaWxIYWFkSFA= Jun 02 09:58:21 auth: Debug: Loading modules from directory: /usr/lib/dovecot/auth Jun 02 09:58:21 auth: Debug: Module loaded: /usr/lib/dovecot/auth/libauthdb_ldap.so Jun 02 09:58:21 auth: Debug: Module loaded: /usr/lib/dovecot/auth/libdriver_sqlite.so Jun 02 09:58:21 auth: Debug: Module loaded: /usr/lib/dovecot/auth/libmech_gssapi.so Jun 02 09:58:21 auth: Debug: passwd-file /etc/passwd.dovecot: Read 3 users Jun 02 09:58:21 auth: Debug: pam(mark,192.168.2.2): lookup service=dovecot Jun 02 09:58:21 auth: Debug: pam(mark,192.168.2.2): #1/1 style=1 msg=Password: Jun 02 09:58:23 auth: Info: pam(mark,192.168.2.2): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: mypass) Jun 02 09:58:23 auth: Debug: passwd-file(mark,192.168.2.2): lookup: user=mark file=/etc/passwd.dovecot Jun 02 09:58:23 auth: Debug: client out: OK 1 user=mark Jun 02 09:58:23 auth: Debug: master in: REQUEST 1125646337 16699 1 69152b70b5461508ad2a3eb02942b883 Jun 02 09:58:23 auth: Debug: passwd(mark,192.168.2.2): lookup Jun 02 09:58:23 auth: Debug: master out: USER 1125646337 mark system_groups_user=mark uid=500 gid=500 home=/home/mark Jun 02 09:58:23 imap-login: Info: Login: user=<mark>, method=PLAIN, rip=192.168.2.2, lip=192.168.2.2, mpid=16705, TLS =========8<=============================================================== Now it's entirely possible that I simply don't properly understand the password authentication process. I have PLAIN passwords set in /etc/passwd.dovecot which it seems to be reading OK, my /etc/dovecot/conf.d/auth-passwdfile.conf.ext file contains just =========8<============================================= passdb { driver = passwd-file args = scheme=PLAIN username_format=%u /etc/passwd.dovecot } =========8<============================================= and nothing else. ...and as I said - it *was* working fine. I am puzzled by the reference to PAM authentication in the logs and in the dovecot -n output. Should I comment out all references to PAM? (in auth-system.conf.ext?) I and my family access mail through a variety of means, using Evolution on the home network, mobile devices (eg iPhone), webmail (using squirrelmail configured to access dovecot) and over ssh (using mutt). I don't necessarily want my (or their) email passwords to be the same as our PAM logon passwords (and at the moment they're not). So for me PLAIN has been the best solution up until now. What is my best (and simplest) solution? Thanks in advance Mark # dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.38.6-27.fc15.i686.PAE i686 Fedora release 15 (Lovelock) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes auth_verbose_passwords = plain log_path = /var/log/dovecot mbox_write_locks = fcntl passdb { driver = pam } passdb { args = scheme=PLAIN username_format=%u /etc/passwd.dovecot driver = passwd-file } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd }

2 1

[Dovecot] DOVECOT v2.0.11 using SIEVE not working
by Matt Mc Namara 02 Jun '11

02 Jun '11

Hi, I'm trying to get sieve working with dovecot. I seem to have everything enabled but my scripts done seem to work. both sieve-filter (2000) and sieve (4190) are running along with pop3 and imap. I have a simple script which checks the email address and moves it to a folder. I'm at a loss as to what to check next. Thanks in advance, Matt

5 10

[Dovecot] Unknown setting: dbox_attachment_dir
by imap＠tnde.org 01 Jun '11

01 Jun '11

Hi, I am trying to set up Dovecot with sdbox and sis (single instance storage of attachments), however I get the following error when attempting to start dovecot: Starting Dovecot Imap: doveconf: Fatal: Error in configuration file /etc/dovecot/dovecot.conf line 89: Unknown setting: dbox_attachment_dir I'd appreciate help on getting this up and running. This is a virtual (for the time being) server, running Centos, and Dovecot 2. [root@localhost ~]# dovecot --build-options Build options: ioloop=epoll notify=inotify ipv6 openssl io_block_size=8192 Mail storages: cydir maildir mbox mdbox raw sdbox shared SQL driver plugins: mysql postgresql sqlite Passdb: checkpassword ldap pam passwd passwd-file shadow sql Userdb: checkpassword ldap(plugin) nss passwd prefetch passwd-file sql [root@localhost ~]# dovecot -n # 2.0.13: /etc/dovecot/dovecot.conf # OS: Linux 2.6.18-238.9.1.el5 x86_64 CentOS release 5.6 (Final) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes disable_plaintext_auth = no mail_location = sdbox:~/dbox mbox_write_locks = fcntl passdb { driver = pam } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd }

2 2

[Dovecot] Client IP log variable for proxy/director setups?
by Kelsey Cummings 01 Jun '11

01 Jun '11

Timo - it would be very convenient if we could get a variable that held the real client ip for use in logging with director/proxy setups. It's clearly already passed around in client->user->remote_ip but at this point, I don't see anyway to get it into the logs and it would take me ages to figure out the Right place to add it since client->user doesn't seem to be available in client-common.c: get_var_expand_table(..). Perhaps I'm missing something obvious? -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

1 1