- dovecot - dovecot.org

[Dovecot] bug? ldap auth CRAM-MD5
by André Höpner 25 Apr '07

25 Apr '07

Hello list, our users are authenticated against ldap-server. anything works fine... dovecot: imap-login: Login: user=<xxx>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured but now we want to use secure passwords and not only plain over ssl. so we configured dovecot to use cram-md5 and configured the ldap-server with CRAM-MD5 passwords. as client we used thunderbird 2.0 and a webfrontend called roundcube. that does not work, because the server gives... dovecot: auth(default): ldap(xxx,127.0.0.1): Password mismatch then we tried to use DIGEST-MD5. we changed the ldap password to the created one with dovecotpw. but this doesnt work too. thunderbird requests CRAM-MD5 and not DIGEST-MD5. so the log says: dovecot: auth(default): password(xxx,127.0.0.1): Requested CRAM-MD5 scheme, but we have only DIGEST-MD5 imap-login: Aborted login: user=<xxx>, method=CRAM-MD5 after that we changed the password back to CRAM-MD5, but we mad the failure not to delete the DIGEST-MD5 value. so the users had 2 passwords set... {CRAM-MD5}e02d374fde0dc75a17a557039a3a5338c7743304777dccd376f332bee68d2cf6 {DIGEST-MD5}358aefa044c08e6c19711c8117714fb0 password is "test" in both cases. on the next try we start thunderbird it works. i dont know why and the log of dovecot says... auth(default): ldap(xxx,127.0.0.1): Multiple password values not supported imap-login: Login: user=<xxx>, method=CRAM-MD5, rip=127.0.0.1, lip=127.0.0.1, secured user was logged in using CRAM-MD5. it's not nice but it works. anyone have an idea why? because of apache-module to auth against ldap and apache doesnt support nor CRAM-MD5 or DIGEST-MD5 we have set the password third time using MD5. So every user has three same passwords with different encryptions. Not nice - but it works. But what can we do to change this. I dont like to set passwords three times. our configuration: # /etc/dovecot/dovecot.conf ssl_cert_file: /etc/ssl/ssl.pem ssl_key_file: /etc/ssl/ssl.key login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login mail_extra_groups: mail mail_location: mbox:/var/mail/dovecot/%n:INDEX=/var/mail/dovecot/indexes/%n mail_plugins: quota imap_quota auth default: mechanisms: plain login cram-md5 digest-md5 verbose: yes passdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf userdb: driver: ldap args: /etc/dovecot/dovecot-ldap.conf plugin: quota: maildir:storage=1024 ------------- # /etc/dovecot/dovecot-ldap.conf hosts = 127.0.0.1:389 dn = cn=dovecot,dc=xxx,dc=com dnpass = dovecot sasl_bind = no sasl_mech = DIGEST-MD5 tls = no auth_bind = no ldap_version = 3 base = ou=People,dc=xxx,dc=com scope = subtree user_attrs = homeDirectory=home,uidNumber=uid,gidNumber=gid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid=user,userPassword=password pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = DIGEST-MD5 ------------- best regards Andre

1 0

[Dovecot] upgrading RHEL4 to RHEL5 - dovecot 0.99 to 1.0rc15
by Götz Reinicke 25 Apr '07

25 Apr '07

Hi, now that a lot off software is updated e.g. RedHat EL and dovecot got finaly final :-) we plan to upgrade our mailserver from RHEL4 dovecot 0.99 to RHEL5 with dovecot 1.0rc15 - the rpms provided by Red Hat. I've read the upgrading Dovecot manual from here http://wiki.dovecot.org/UpgradingDovecot, but yust to get things right I'd like to ask some questions: Simply spoken, we use the basic default dovecot-config, mbox format and imaps/pop3s. So will there be any big trouble to just use the most default settings of the 1.0 config file? Or which options are compleatly different? Dose there exist a migration how to beside the dovecot upgrade from the wiki? Thanks for hints and tips! Best regards Götz Reinicke -- Götz Reinicke IT Koordinator Tel. +49 7141 969 420 Fax +49 7141 969 55 420 E-Mail goetz.reinicke(a)filmakademie.de Filmakademie Baden-Württemberg GmbH Mathildenstr. 20 71638 Ludwigsburg www.filmakademie.de Eintragung Amtsgericht Stuttgart HRB 205016 Vorsitzender des Aufsichtsrats: Dr. Christoph Palmer, MdL, Minister a.D. Geschäftsführer: Prof. Thomas Schadt

1 0

[Dovecot] disabling pop/imap per mail address?
by Armijn Hemel 25 Apr '07

25 Apr '07

hello, first of all I want to say thanks to Timo for Dovecot 1.0. We've been running it in production at the company where I work and we're very pleased with it. Good job! One thing that we were wondering about today is if we can disable a certain protocol depending on the mailbox. So for example: user A can access via pop3s and imap, user B can only access via pop3, user C can use only imaps, and so on. thanks! armijn PS: am I assuming correctly that IMAP namespaces will make it possible to have shared IMAP folders with Dovecot? I'm still a bit of an IMAP dummy -- --------------------------------------------------------------------------- armijn(a)uulug.nl | http://www.uulug.nl/ | UULug: Utrecht Linux Users Group ---------------------------------------------------------------------------

2 1

[Dovecot] Experience with Dovecot + Sieve + Webmail?
by Steffen Kaiser 24 Apr '07

24 Apr '07

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, there were some posts into this lists regarding Webmail interfaces and Sieve. What are the experiences with them? I need a webmail frontend that is capable of IMAP, supporting dovecot's namespaces, verifying PGP and managing Sieve in conjunction with Dovecot. I found two mature products, I also saw posts about, so I'm going to ask. Some posts on this list suggest that some are using SquirrelMail/avelsieve and some Horde (IMP/Ingo). What are the experiences with them? Are they stable and are there configuration glitches (there is a thread about a bug in avelsieve, for instance). How do they interact with Dovecot in order to find the user's homedirectory to get/put the Sieve script? Maybe it's offtopic for the Wiki, but would you mind share your configuration on the Dovecot Wiki? Bye, - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBRi3/dS9SORjhbDpvAQLoCggAgGInRUJI944aAIOjOjDWsdlssCdnqTlk CWufMVfFpTjRqN9VobuUHiZzVY45zDN+9emVm4b68hL+L9bHQZyytiqsZjmDNlWM wcE49XckNAAOaq+qOJZR+2CxyKAECklGkhTrs5hfLSZx8i/5uGNCyAOHFQ98YU6Q 3VoDeNq5Cd0sVxiEEzeLeU6BrcY7Cnt+qeemZCSfKRI5cQow+edSM8Mb7BP7WuUU wlaMo5bTZLBWQCQPAPd7m9wiBueV6bDxhsfe9yuOYxUKHI/N/sKr3iRLcZCxRsXk wh3UT6OcFe4Mg873EMfdZClahLp5a3oUbP1lH7MP8Aa9iSOccEIcNg== =ADCc -----END PGP SIGNATURE-----

4 3

[Dovecot] message-of-the-day feature?
by Steven F Siirila 24 Apr '07

24 Apr '07

For lack of a better name, we are interested in a feature where one could get a notice out to all Dovecot users as quickly as possible, possibly without going through an MTA even. Given a message and a list of userids we could certainly do a mailing on the MDA server itself going through both Postfix and Dovecot LDA. However, we were wondering what other options we might have in Dovecot. For example, would it be possible to place the message into some file which Dovecot periodically checks for, and if the file exists, either present it to the user as a new message, or automatically deliver it at that time via Dovecot LDA? -- Steven F. Siirila Office: Lind Hall, Room 130B Internet Services E-mail: sfs(a)umn.edu Office of Information Technology Voice: (612) 626-0244 University of Minnesota Fax: (612) 626-7593

9 10

[Dovecot] Auth MD5 problem
by Azher Amin 24 Apr '07

24 Apr '07

Hi, I am using dovecot 1.0 with squirrelmail. But when i use $imap_auth_mech = 'digest-md5' instead of plain, dovecot throws this line: dovecot: Apr 23 09:16:07 Info: imap-login: Aborted login: user=<azher>, method=DIGEST-MD5, rip=127.0.0.1, lip=127.0.0.1, secured and user can't login. Plz suggest. Regards -Azher Settings: ====== disable_plaintext_auth = yes auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain login cram-md5 digest-md5 Mysql Tables: Passwords are stored with the help of MD5 function dovecot-sql.conf : ============ user_query = SELECT home, uid, gid FROM users WHERE userid = '%u' password_query = SELECT userid as user, password, home as userdb_home, uid as userdb_uid, gid as userdb_gid FROM users WHERE userid = '%u' -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.

4 8

[Dovecot] SASL Problems
by Phillip T. George 23 Apr '07

23 Apr '07

Hello all, I seem to be having a problem with SASL. It doesn't seem to work with Outlook. Upon searching a bit, I found that I need to enable "login" for auth mechanisms. However, when I do that, (after I stop and start dovecot and postfix), and then try to use SMTP auth using Outlook, it causes postfix to crash. It works fine with Thunderbird still though. Any ideas as to what the cause might be? I'm using Dovecot 1.0.0 and Postfix 2.3.5. Thanks, Phillip

1 2

Re: [Dovecot] Mixing MBOX and Maildir?
by Paul 23 Apr '07

23 Apr '07

> Is it possible to have some folders be mbox and some be maildir format? Claudio Succa posted his successful configuration back in 2005, at my request. I never actually put it into practice, and I don't know how much has changed since 1.0test68, but good luck!: http://www.dovecot.org/list/dovecot/2005-June/007574.html

1 0

[Dovecot] Trying to explain mutt+dovecot(ssl) to myself :(
by Wilkinson, Alex 23 Apr '07

23 Apr '07

Hi all, I have recently migrated my mail from courier-imap to dovecot. In doing so, I finally configured mutt to connect to imaps (SSL). In the end I got it all working. I then sat back and thought: "I kinda don't understand the SSL/TLS part even though it works". And I hate setting stuff up and not truely understanding the mechanics of it. So I started to write about it and am stuck. Can those that _understand_ mutt+ssl have a read of what I wrote to myself and give me your $00.02 worth (corrections etc). Trying to explain mutt+ssl and getting it all wrong --------------------------------------------------- * mutt(with openssl support built in) initiates with a "SSL-Client-Hello" to SSL on port 993 i.e. mutt's capabilities (algorithms, SSL version etc). * dovecot:993 compares mutt's CipherSuites with its own. Of the CipherSuites mutt and dovecot have in common, dovecot:993 chooses the _most_ secure algorithm. * Dovecot:993 will then tell mutt what it has decided to use and assigns a Unique session ID. From now on all communication is via this ID. * Now that the CipherSuite is set between mutt and dovecot, dovecot sends its SSL certificate to mutt [/usr/local/share/dovecot/certs/dovecot.pem]. mutt then uses dovecot's corresponding public key [/usr/local/share/dovecot/private/dovecot.pem] to verify that the ceritificate is authentic. * once mutt has verified that the certificate is authentic ... and here I got unstuck. Cheers -aW IMPORTANT: This email remains the property of the Australian Defence Organisation and is subject to the jurisdiction of section 70 of the CRIMES ACT 1914. If you have received this email in error, you are requested to contact the sender and delete the email.

2 1

[Dovecot] deliver failing to execute sendmail (sieve)
by Justin McAleer 21 Apr '07

21 Apr '07

I have apparently done something to mess up my test installation, as deliver's attempts to send messages now fail with the following error: deliver(user(a)example.com): execv() failed: No such file or directory In these cases, I have sieve rules trying to send messages. It had been working though, and I've tried going through all the changes I made yesterday (related to dictionary quota debugging) to find what could be wrong, but no luck so far. So, I was hoping for suggestions. Basically, deliver seems to not know where sendmail is. I have sendmail_path set in dovecot.conf (never changed that), yet when deliver tries to pull the location via deliver_set->sendmail_path, it's just returning an empty string. If I hard-code the location in smtp-client.c, it works again. Any ideas?

3 5