- dovecot - dovecot.org

[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

[Dovecot] dovecot.spec
by J.Palacios 20 Apr '07

20 Apr '07

Hi List, Plis, where can i find an updated version (for recently dovecot v1.0.0) of dovecot.spec, needed to build an rpm for RH 4? Thanks in advance, Juan Carlos

3 5

[Dovecot] Dovecot 1.0.0 and Seive 1.0.1 on FreeBSD
by Ed Lucero 20 Apr '07

20 Apr '07

I have installed dovecot and sieve using the FreeBSD ports. Authentication is against a MySql Database. Dovecot is running using deliver as the LDA. But when I try to Sieve I get the following error in /var/log/dovecot.log deliver(mike(a)systemrt.com): Apr 19 14:07:19 Info: Loading modules from directory: /usr/local/libexec/dovecot deliver(mike(a)systemrt.com): Apr 19 14:07:19 Fatal: Plugin sieved not found from directory /usr/local/libexec/dovecot Yet in /usr/local/libexec/dovecot the binaries are there root@db3 /usr/local/libexec/dovecot> ll total 2432 -r-xr-xr-x 1 root wheel 29980 Apr 17 15:51 checkpassword-reply* -r-xr-xr-x 1 root wheel 476884 Apr 17 15:51 deliver* -r-xr-xr-x 1 root wheel 88700 Apr 17 15:51 dict* -r-xr-xr-x 1 root wheel 254984 Apr 17 15:51 dovecot-auth* -r-xr-xr-x 1 root wheel 30588 Apr 17 15:51 gdbhelper* -r-xr-xr-x 1 root wheel 34816 Apr 17 15:51 idxview* -r-xr-xr-x 1 root wheel 523128 Apr 17 15:51 imap* -r-xr-xr-x 1 root wheel 103968 Apr 17 15:51 imap-login* -r-xr-xr-x 1 root wheel 31996 Apr 17 15:51 logview* -r-xr-xr-x 1 root wheel 474288 Apr 17 15:51 pop3* -r-xr-xr-x 1 root wheel 98932 Apr 17 15:51 pop3-login* -r-xr-xr-x 1 root wheel 52764 Apr 17 15:51 rawlog* -r-xr-xr-x 1 root wheel 108980 Apr 11 09:17 sievec* -r-xr-xr-x 1 root wheel 50228 Apr 11 09:17 sieved* -r-xr-xr-x 1 root wheel 30784 Apr 17 15:51 ssl-build-param* What am I doing wrong? Ed Here is the dovecot.conf file ## Dovecot configuration file mail_debug = yes log_path = /var/log/dovecot.log info_log_path = /var/log/dovecot.log # IC - EL 2006.09.29 protocols = imap imaps pop3 pop3s # IC - EL 2006.09.29 disable_plaintext_auth = no # IC - EL 2006.09.29 ssl_disable = no # IC - EL 2006.09.29 ssl_cert_file = /usr/share/ssl/s/Cert.pem ssl_key_file = /usr/share/ssl/s/PrivateKey.pem login_process_size = 64 # IC - EL 2006.09.29 login_processes_count = 6 # IC - EL 2006.09.29 login_greeting = InternetCrusade ready. # IC - EL 2006.09.29 default_mail_env = maildir:/var/mail/%Ld/%Ln mail_save_crlf = yes maildir_copy_with_hardlinks = yes mail_extra_groups = mail verbose_proctitle = yes first_valid_gid = 0 protocol imap { imap_client_workarounds = delay-newmail outlook-idle netscape-eoh tb-extra-mailbox-sep } protocol pop3 { # IC - EL 2006.09.29 pop3_uidl_format = %v.%u pop3_client_workarounds = outlook-no-nuls oe-ns-eoh } protocol lda { postmaster_address = postmaster(a)internetcrusade.com sendmail_path = /usr/sbin/sendmail # Support for dynamically loadable plugins. mail_plugins is a space separated # list of plugins to load. mail_plugin_dir = /usr/local/libexec/dovecot mail_plugins = sieved # If there is no user-specific Sieve-script, global Sieve script is # executed if set. global_script_path = /usr/local/etc/sieve.default } auth default { # IC - EL 2006.09.29 mechanisms = plain login cram-md5 digest-md5 ntlm # IC - EL 2006.09.29 passdb sql { args = /usr/local/etc/dovecot-sql.conf } # IC - EL 2006.09.29 userdb static { args = uid=5000 gid=5000 home=/var/mail/%Ld/%Ln } # IC - EL 2006.09.29 socket listen { master { # Master socket provides access to userdb information. It's typically # used to give Dovecot's local delivery agent access to userdb so it # can find mailbox locations. path = /var/run/dovecot/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = icmail group = icmail } client { user = postfix group = postfix path = /var/spool/postfix/private/auth mode = 0660 } } } #dict { #quota = mysql:/etc/dovecot-dict-quota.conf #} auth_debug = yes auth_debug_passwords = yes verbose_ssl = yes mmap_disable=yes #fsync_disable=yes

5 8

[Dovecot] Automatic subscribtion to the Spam folder?
by Henk Wevers 20 Apr '07

20 Apr '07

Is this possible? Or need I make some shell scripts to add Spam into subscriptions? Henk

1 0

Re: [Dovecot] dovecot-auth %c variable is not working
by Bill Boebel 20 Apr '07

20 Apr '07

On Thu, April 19, 2007 3:23 pm, Andrey Panin <pazke(a)donpac.ru> said: > On 109, 04 19, 2007 at 12:17:41PM -0400, Bill Boebel wrote: >> In "doc/variables.txt" >> >> > For dovecot-auth there are also these variables: >> > >> > %c - "secured" string with SSL, TLS and localhost connections. >> > Otherwise empty. >> >> %c does not appear to be working. I am trying to use it in a MySQL query userdb >> and passdb query and it is always empty string. > > Seems like secured flag isn't passed to blocking passdb handler. > Can you try attached patch ? > This patch indeed fixed it. Tested with all 4 protocols... pop3 -> %c = '' pop3s -> %c = 'secured' imap -> %c = '' imaps -> %c = 'secured' Thanks Andrey! Bill

1 0

[Dovecot] Client with SSL client cert support?
by Peter Abrahamsen 20 Apr '07

20 Apr '07

Good day, all, I've gleaned that dovecot has support for verifying SSL client certs on connect. What IMAP clients have people found that support sending a specific SSL cert? I can't find this feature in Thunderbird, at least. Thanks, Peter

3 2