- dovecot - dovecot.org

[Dovecot] wrong config file?
by Phil Howard 10 May '10

10 May '10

The sample provided config file (the one I started with by editing it) included the following text: # ------------------------------ WARNING ------------------------------- > > # If there's a file /etc/dovecot/dovecot-postfix.conf, which is part of > # dovecot-postfix package, it will be used instead of dovecot.conf. > > # Keep in mind that, if that file exist, none of the changes in > # /etc/dovecot/dovecot.conf will have effect on dovecot's configuration. > # In that case you should customize /etc/dovecot/dovecot-postfix.conf. > > # ------------------------------ WARNING ------------------------------- > So I expected it would use that by default. It seems to not be doing so. Does this mean I have to modify the startup scripts to add the -c option to force the use of this config file? Or should I just put all my configs in the default "/etc/dovecot/dovecot.conf" file? When doing "dovecot -n" it became apparent that my configs were not being used. But "dovecot -c /etc/dovecot/dovecot-postfix.conf -n" was doing it. Any idea why it's not behaving as those comments described?

2 7

[Dovecot] configuration user= or auth_user=
by Phil Howard 10 May '10

10 May '10

The sample config file has: # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. Note that this user is NOT used to access mails. # That user is specified by userdb above. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. # Note that valid_chroot_dirs isn't needed to use this setting. #chroot = So is the variable for the authentication process user supposed to be "user" or "auth_user"? It would make more sense to be "auth_user". Is it just "user" for legacy reasons, and the reference to "auth_user" is in error? Or can either name be used? Also, those of you who change this, do you change it to something existing like "dovecot" or "vmail" or "nobody" or do you make a whole new user for it?

1 0

[Dovecot] lmtp_generic_maps with postfix
by derwyn 10 May '10

10 May '10

Hi All, I am new to dovecot so this may be a very easy thing to do. I need to setup a postfix+dovecot server for a multilocation setup The rules are very simple mails to *(a)local.example.com send to dovecot mails to *(a)otherlocation.example.com send to smtp:[otherlocation] But the users are created on dovecot as user(a)example.com. How can I configure dovecot to accept mails for *(a)local.example.com and deliver to *(a)example.com I use lmtp_generic_maps for a similar thing in postfix+cyrus Thanks Derwyn.

1 0

[Dovecot] problems implementing dovecot LDA with Postfix
by Stan Hoeppner 09 May '10

09 May '10

Per the instructions here http://wiki.dovecot.org/LDA and here http://wiki.dovecot.org/LDA/Postfix I set postmaster_address = postmaster(a)hardwarefreak.com in /etc/dovecot/dovecot.conf and mailbox_command = /usr/lib/dovecot/deliver in /etc/postfix/main.cf When I restart dovecot I get this: [07:17:00][root@greer]/etc/dovecot$ /etc/init.d/dovecot restart Restarting IMAP/POP3 mail server: dovecotError: Error in configuration file /etc/dovecot/dovecot.conf line 754: Unknown setting: postmaster_address Fatal: Invalid configuration in /etc/dovecot/dovecot.conf failed! And after restarting Postfix and sending a test message from a gmail account I get this in the mail log: May 9 07:26:09 greer postfix/qmgr[13384]: AEE976C32C: from=<snugmonster(a)gmail.com>, size=1628, nrcpt=1 (queue active) May 9 07:26:09 greer dovecot: deliver(stan): Fatal: postmaster_address setting not given May 9 07:26:09 greer postfix/local[13392]: AEE976C32C: to=<stan(a)hardwarefreak.com>, relay=local, delay=1.4, delays=1.3/0.03/0/0.04, dsn=4.3.0, status=deferred (temporary failure) The server is Debian Lenny 5.0.4 with Postfix 2.5.5 and Dovecot 1.2.11 from Lenny backports. Any ideas? Everything I've found via Google relating to this Dovecot startup error has to do with people converting old dovecot.conf files to a new dovecot version. -- Stan

3 4

[Dovecot] CRYPT scheme and 8 character limit
by Phil Howard 09 May '10

09 May '10

I've decided that having users supply cleartext passwords for me to encrypt and encode is a bad idea, anyway. So maybe I won't need dovecotpw. The idea is that users supply an already-encrypted password. Most of the users can fetch their login password from /etc/shadow on their own computer. Wiki page http://wiki.dovecot.org/Authentication/PasswordSchemes indicates that scheme name CRYPT is the one that uses the libc crypt() function. But it also says it uses no more than 8 characters. Then there is MD5-CRYPT. But that doesn't call crypt(), I presume. No limit on password size is indicated. But this at least looks like SOME of the encrypted passwords I have. Other passwords I have have ids indicating SHA-256 and SHA-512. Here is an example from /etc/shadow that encrypted the clear password "dovecotandpostfix" (in case it is necessary to test it): $6$IwZzpjjj$p1VrkxQmgmTED8iQnQrV3sVEZpBmw2N8oD1ykOguXB5tf8aahICesX0TF6.VMThIW2QFs1buHjT3eDtnaAFhF1 The big question is, what scheme name should I use for these passwords? I can, of course, consider the id (6 in the above example, suggesting SHA-512) if there is one (so far all are like this). But the other consideration is most of the passwords are longer than 8, some longer than 12, characters. So apparently CRYPT can't be used in those cases (so I can't have the automatic identification of crypt() to detect the scheme). What scheme would I use for the various passwords? What scheme would be used for the above example for starters? What if the id is 5 or 1 (the ones documented for the crypt() call)?

3 4

[Dovecot] looking for feedbacks on courier to dovecot
by Mihamina Rakotomandimby 08 May '10

08 May '10

Manao ahoana, Hello, Bonjour, We currently run courier POP . We would like to switch to Dovecot. I encounter problems when migrating the UIDL because we have big Maildirs and POP re-downlading the data is not possible for most of the users. I tried the http://www.dovecot.org/tools/courier-dovecot-migrate.pl script but I still have the re-downloading event. What are your stories and advices about courier-to-dovecot move? Misaotra, Thanks, Merci. -- Architecte Informatique chez Blueline/Gulfsat: Administration Systeme, Recherche & Developpement +261 34 29 155 34 / +261 33 11 207 36

1 1

[Dovecot] v2.0.beta4: Couldn't drop privileges: Unknown mail_privileged_group
by Thomas Leuxner 08 May '10

08 May '10

Hi, latest HG throws this error: May 8 06:42:33 spectre dovecot: master: Dovecot v2.0.beta4 (0a35407e6ff4) starting up May 8 06:48:01 spectre dovecot: imap(alias(a)domain.tld): Error: user alias(a)domain.tld: Couldn't drop privileges: Unknown mail_privileged_group: 5000 May 8 06:48:01 spectre dovecot: imap(alias(a)domain.tld): Error: Internal error occurred. Refer to server log for more information. Regards Thomas

1 0

[Dovecot] Questions, Issues with 2.0
by Kelsey Cummings 08 May '10

08 May '10

I'm trying to use an external program to set the location of user's maildirs to match an existing hashing schema but the docs for how to do this in 1.x do not seem to apply to 2.0 or I'm misinterpreting them. protocol imap { mail_executable = /opt/dovecot-test/sonic-imap ... This correctly executes the and attempts to sets the MAIL variable but it appears that mail_executable is run before the user is logged in so the $USER variable isn't set and the process' uid is still 0. We also need to have dovecot include an additional maildir for each user that is currently stored outside of the user's main maildir directory into the same namespace as a specific folder name. Is there a way to do this in dovecot directly or will it need to be hacked (as it is currently with courier) or could it be done with a plugin? I've also noticed that while doveconf complains about mail_executable: May 3 13:44:10 a dovecot: config: Obsolete setting in /opt/dovecot-test/etc/dovecot/conf.d/imap.conf:7: mail_executable has been replaced by service { executable } However, when replaced as suggested by doveconf: protocol_imap { executable = /opt/dovecot-test/sonic-imap ... It fails altogether: doveconf: Fatal: Error in configuration file /opt/dovecot-test/etc/dovecot/conf.d/imap.conf line 7: Unknown setting: executable Similarly, it also suggests 'drop_priv_before_exec = no' which doesn't appear to be valid either. -- Kelsey Cummings - kgc(a)corp.sonic.net sonic.net, inc. System Architect 2260 Apollo Way 707.522.1000 Santa Rosa, CA 95407

2 4

[Dovecot] Dovecot version mismatch - after restart
by edeis 07 May '10

07 May '10

Getting the followng error when managesieve is enabled. Any other post I've read says this problem is because the service hasn't restarted after upgrade. I've restarted dovecot & postfix many times, reboot machine too. Still get the error. Racking my brains on this!! May 7 13:21:19 drizzle dovecot: dovecot: Created login processes successfully, unstalling May 7 13:21:20 drizzle dovecot: managesieve-login: Fatal: Dovecot version mismatch: Master is v1.2.11, login is v1.2.10 (if you don't care, set version_ignore=yes) May 7 13:21:20 drizzle dovecot: dovecot: Temporary failure in creating login processes, slowing down for now May 7 13:21:20 drizzle dovecot: managesieve-login: Fatal: Dovecot version mismatch: Master is v1.2.11, login is v1.2.10 (if you don't care, set version_ignore=yes) Running CentOS5.4. Installed Packages from atrpms dovecot.x86_64 1:1.2.11-3_108.el5 installed dovecot-managesieve.x86_64 0.11.11-0_4.el5 installed dovecot-sieve.x86_64 1:0.1.15-4.el5 installed Here's my dovecot settings: [root@drizzle /]# dovecot -n # 1.2.11: /etc/dovecot.conf # OS: Linux 2.6.18-164.15.1.el5.028stab068.9 x86_64 CentOS release 5.4 (Final) protocols: imap imaps pop3 pop3s managesieve ssl_cert_file: /etc/ssl/certs/mydomain.com.crt ssl_key_file: /etc/ssl/certs/mydomain.com.key login_dir: /var/run/dovecot/login login_executable(default): /usr/libexec/dovecot/imap-login login_executable(imap): /usr/libexec/dovecot/imap-login login_executable(pop3): /usr/libexec/dovecot/pop3-login login_executable(managesieve): /usr/libexec/dovecot/managesieve-login mail_privileged_group: mail mail_location: maildir:%h mail_debug: yes mail_executable(default): /usr/libexec/dovecot/imap mail_executable(imap): /usr/libexec/dovecot/imap mail_executable(pop3): /usr/libexec/dovecot/pop3 mail_executable(managesieve): /usr/libexec/dovecot/managesieve mail_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 mail_plugin_dir(managesieve): /usr/lib64/dovecot/managesieve namespace: type: private prefix: INBOX. inbox: yes list: yes subscriptions: yes lda: postmaster_address: me(a)mydomain.com auth default: mechanisms: plain login passdb: driver: checkpassword args: /var/www/ispcp/engine/ispcp-dovecot-mngr userdb: driver: sql args: /etc/dovecot/dovecot-sql-domain.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql-aliasdomain.conf userdb: driver: sql args: /etc/dovecot/dovecot-sql-subdomain.conf socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix master: path: /var/run/dovecot/auth-master mode: 432 user: vmail group: mail plugin: sieve: /etc/dovecot/sieve/dovecot.sieve [root@drizzle /]# -- View this message in context: http://old.nabble.com/Dovecot-version-mismatch---after-restart-tp28491245p2… Sent from the Dovecot mailing list archive at Nabble.com.

1 0

[Dovecot] Requiring STARTTLS only on some networks
by Thomas Hummel 07 May '10

07 May '10

Hello Timo, is there a way, either in 1.2.x or in 2.x to activate disable_plaintext_auth=yes only for some address or network ? The idea would be to enable clients from the internal networks to keep making clear text connections while forbidding it to the rest of the world. Thanks. -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

3 6