- dovecot - dovecot.org

[Dovecot] dovecot 2 in ubuntu 12.04 or Debian Squeeze
by pvsuja 20 Mar '13

20 Mar '13

Dear sir, I have to set up a mail gateway which will be explored to Internet and a secure mail server in the Intranet. I need a smart imap proxy in the mail gateway which will fetch the mail from server and present to user through either a stand alone mail client or a web mail client. All authentication is through ldap server. I have installed Dovecot 2.2 Unstable in my Ubuntu 12.04 with ssl enabled But when I am starting dovecot, I am getting the following error *doveconf: Fatal: Error in configuration file /usr/local/etc/dovecot/conf.d/10-ssl.conf line 12: Unknown setting: ssl_cert* I couldn't figure out what is wrong. Please help me to sort it out. Thanks & Regards, Suja PV LEOS -- View this message in context: http://dovecot.2317879.n4.nabble.com/dovecot-2-in-ubuntu-12-04-or-Debian-Sq… Sent from the Dovecot mailing list archive at Nabble.com.

5 14

Re: [Dovecot] Question regarding Postfix and Dovecot
by Daniel Reinhardt 19 Mar '13

19 Mar '13

Replying back to the list. On Thu, Mar 14, 2013 at 10:51 AM, mourik jan c heupink < heupink(a)merit.unu.edu> wrote: > please reply to the list > > > On 3/14/2013 11:38 AM, Daniel Reinhardt wrote: > >> Yes I have read everything on that, and yet postfix does not even see >> the dovecot virtual transport. >> >> >> On Thu, Mar 14, 2013 at 10:37 AM, mourik jan c heupink >> <heupink(a)merit.unu.edu <mailto:heupink@merit.unu.edu>**> wrote: >> >> Hi Daniel, >> >> I'm new to dovecot myself, but did you read this: >> http://wiki2.dovecot.org/LDA/_**_Postfix<http://wiki2.dovecot.org/LDA/__Postfix> >> >> <http://wiki2.dovecot.org/LDA/**Postfix<http://wiki2.dovecot.org/LDA/Postfix> >> > >> >> I'm guessing that perhaps you need to configure your virtual >> transport? So, in master.cf <http://master.cf>, include a line like: >> >> >> dovecot unix - n n - - pipe >> flags=DRhu user=vmail:vmail >> argv=/usr/local/libexec/__**dovecot/dovecot-lda -f ${sender} -d >> ${recipient} >> >> and configure virtual_transport = dovecot in main.cf <http://main.cf> >> >> >> But again... I'm very new to all this myself, but perhaps it helps? >> >> Regards, >> MJ >> >> >> >> >> -- >> Daniel Reinhardt >> cryptodan(a)cryptodan.net <mailto:cryptodan@cryptodan.**net<cryptodan(a)cryptodan.net> >> > >> http://www.cryptodan.net >> 301-875-7018(c) >> 410-455-0488(h) >> > -- Daniel Reinhardt cryptodan(a)cryptodan.net http://www.cryptodan.net 301-875-7018(c) 410-455-0488(h)

20 53

Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ?
by Clement PAULET 19 Mar '13

19 Mar '13

Hello Steffen, Thanks for your help, your message has reminds me that I forget the header specification. This new sieve script works for me : require ["fileinto"]; if allof (header :contains "To" "abuse(a)info.xx.com") { fileinto "INBOX.Test"; redirect "clement.xx(a)xx.net"; stop; } Thanks, Clement ----- Date: Mon, 18 Mar 2013 14:28:17 +0100 (CET) From: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ? Message-ID: <alpine.DEB.2.02.1303181419590.3303(a)pc-2m63.inf.fh-bonn-rhein-sieg.de> Content-Type: TEXT/PLAIN; format=flowed; charset=US-ASCII -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Mar 2013, Clement PAULET wrote: Dear Clement, This is my script (using for my test) : require "fileinto"; if address "To" "info(a)info.xx.com" { fileinto "Test"; } Works for me in v2.2. Did you verified that the header "To" really exists in the message and that "info(a)info.xx.com" is part of it? The log you've posted displays the envelope information, which is not necessary the same as the header information. Also, remove the precompiled Sieve script, in order to ensure that the pre-compiled one is really one from the script. You could also decompile it to make sure, it has been created from your test script. You'll find sieve-dump in src/sieve-tools/, if you compile from sources, or maybe in /usr/local/bin.

1 0

[Dovecot] SMTP Client authentication to remote Postfix/Dovecot
by Christian Benke 19 Mar '13

19 Mar '13

Hello! This is probably another basic question and i'm not even sure if it's something where Dovecot is involved, but i'll give it a shot. So i've setup Postfix with Dovecot and system-auth on my remote server. So far it looks like everything is working fine and dandy via SASL(PLAIN) and TLS. I'm just not happy about my local SMTP client settings. I'm going to try to work with mutt in the future, so i need a local MTA - i've decided to try it with Postfix. This works so far and i can send mails with mutt. However - my setup relies on smtp_sasl_password_maps for authentication. I'm not too happy to have plaintext-passwords of remote systems lying around on my local filesystem. It doesn't really ease my mind that the file is readable by root only, this doesn't help if my laptop's harddisk gets mounted elsewhere. Are there alternatives or better ways to do SMTP authentication? http://www.postfix.org/SASL_README.html#server_cyrus_comm says: > saslauthd can verify the SMTP client credentials by using them to log into an IMAP server So i have my mutt-client which is logged in to the remote Dovecot IMAP. Mutt uses the local MTA to send the mail. Is there some way to tell the local postfix or a local dovecot to authenticate the SMTP-Session via the existing IMAP-login? Or some other way where i at least don't rely on plaintext passwords but secure, encrypted hashes? Sorry if this is a redundant thread, "smtp client" authentication site:dovecot.org/list' and the likes are not exactly the most rewarding or unique search terms unfortunately. Thanks, Christian -- Central Asia by bike, starting May 2013 - http://poab.org

1 1

[Dovecot] Integrating with Drupal SQL db
by info＠stos.se 19 Mar '13

19 Mar '13

Hi I'm trying to get Dovecot to use Drupal users password for authenticating IMAP users. But I just cant figure out how to make Dovecot understand the password hash type that Drupal 7 is using. My example user with password Teacher1 looks like this in Drupal database: $S$DZwJa.U8HXT2PvTmwCK13rGEYEvnx5DB6/hlqnfCBum4s4U7MVWU Dovecot retrieves this hash but complains that its not a recognized hash type, or that the hash is wrong, depending on if I change the default hash type in Dovecot config. Any help appreciated. root@SSiS:/etc/postfix# dovecot --version 1.2.15 root@SSiS:/etc/postfix# dovecot -n # 1.2.15: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-12-pve i686 Debian 6.0.7 simfs log_timestamp: %Y-%m-%d %H:%M:%S login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mail_privileged_group: mail mail_location: maildir:/home/vmail/ mbox_write_locks: fcntl dotlock auth default: verbose: yes debug: yes debug_passwords: yes passdb: driver: pam passdb: driver: sql args: /etc/dovecot/dovecot-sql.conf userdb: driver: passwd root@SSiS:/etc/postfix# root@SSiS:/etc/postfix# grep -v '^ *$#.*$\?$' /etc/dovecot/dovecot-sql.conf driver = mysql connect = host=127.0.0.1 dbname=Drupal user=Dru_Adm password=localu default_pass_scheme = CRYPT password_query = SELECT name AS user, pass AS password FROM users WHERE name='%n' user_query = SELECT CONCAT(SUBSTRING_INDEX(mail,'@',-1),'/',SUBSTRING_INDEX(mail,'@',1),'/') AS mail FROM users WHERE name='%n' root@SSiS:/etc/postfix# tail /var/log/mail.log Mar 11 16:17:42 SSiS dovecot: auth(default): new auth connection: pid=8593 Mar 11 16:17:51 SSiS dovecot: auth(default): client in: AUTH#0111#011PLAIN#011service=imap#011secured#011lip=127.0.0.1#011rip=127.0.0.1#011lport=143#011rport=52316#011resp=AFRlYWNoZXIxAFRlYWNoZXIx Mar 11 16:17:51 SSiS dovecot: auth-worker(default): pam(Teacher1,127.0.0.1): lookup service=dovecot Mar 11 16:17:51 SSiS dovecot: auth-worker(default): pam(Teacher1,127.0.0.1): #1/1 style=1 msg=Password: Mar 11 16:17:54 SSiS dovecot: auth-worker(default): pam(Teacher1,127.0.0.1): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: Teacher1) Mar 11 16:17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): query: SELECT name AS user, pass AS password FROM users WHERE name='Teacher1' Mar 11 16:17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): Password mismatch Mar 11 16:17:54 SSiS dovecot: auth-worker(default): md5_verify(Teacher1): Not a valid MD5-CRYPT or PLAIN-MD5 password Mar 11 16:17:54 SSiS dovecot: auth-worker(default): Invalid OTP data in passdb Mar 11 16:17:54 SSiS dovecot: auth-worker(default): Invalid OTP data in passdb Mar 11 16:17:54 SSiS dovecot: auth-worker(default): sql(Teacher1,127.0.0.1): CRYPT(Teacher1) != '$S$DZwJa.U8HXT2PvTmwCK13rGEYEvnx5DB6/hlqnfCBum4s4U7MVWU' Mar 11 16:17:56 SSiS dovecot: auth(default): client out: FAIL#0111#011user=Teacher1 Mar 11 16:18:01 SSiS dovecot: imap-login: Disconnected: Too many invalid commands (auth failed, 1 attempts): user=<Teacher1>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured Mar 11 16:32:36 SSiS dovecot: auth(default): new auth connection: pid=9075 Mar 11 16:32:41 SSiS dovecot: imap-login: Disconnected: Too many invalid commands (no auth attempts): rip=127.0.0.1, lip=127.0.0.1, secured root@SSiS:/etc/postfix#

5 8

[Dovecot] Random LDA failure to access auth socket
by Chris Richards 19 Mar '13

19 Mar '13

Greetings all. Please forgive me if I'm posting something that has already been addressed, but my google-foo is not strong enough to find the solution. I've got a dovecot server running version 2.0.19 on Gentoo Hardened. I have Postfix as my MTA, and it is calling the Dovecot LDA to deliver the mail. Everything is working great, mail is being delivered, and the users are happy. However, I am noticing that I have random entries like this: Mar 1 20:19:23 hermes dovecot: lda: Error: userdb lookup: connect(/var/run/dovecot/auth-userdb) failed: Permission denied (euid=97(dovecot) egid=97(dovecot) missing +r perm: /var/run/dovecot/auth-userdb, dir owned by 0:0 mode=0755) Mar 1 20:19:23 hermes dovecot: lda: Fatal: Internal error occurred. Refer to server log for more information. Since these messages came from the server log, looking in the server log for more information is rather pointless. I have 10-master.conf configured as follows: service auth { unix_listener auth-userdb { mode = 0600 user = vmail group = vmail } In 15-lda.conf I have: protocol lda { mail_plugins = $mail_plugins sieve quota } In Postfix master.cf, I have the following: dovecot unix - n n - - pipe flags=DRhu user=vmail:users argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${user}@${nexthop} Permissions on the socket are: srw------- 1 vmail vmail 0 Feb 24 23:43 auth-userdb Judging from the log, my problem is that the LDA appears to be trying to access the socket as the dovecot user (rather than the vmail user), but my question is why? What logging can I use to tell me if postfix is calling with the wrong permissions or if the lda is somehow getting confused? Any help or suggestions greatly appreciated. Thanks, Gizmo

2 6

[Dovecot] SASL + Postfix woes
by Jerry 18 Mar '13

18 Mar '13

Okay, I wasn't going to try and fix up the messed up mail server I was given; however, I decided that I might as well try. Situation: The system has a Postfix MTA and uses Dovecot for LDA and Cyrus-SASL for SASL. That works fine. I decided that I wanted to switch over to Dovecot for SASL. dovecot is presently using MySQL for its database. I make the (I thought) necessary changes in Postfix and restarted it. Big problem. SASL is now broken. I turned on logging in Dovecot to see what was happening, but apparently nothing is happening. There are no entries regarding Postfix attempting to negotiate an SASL request with Dovecot. This is the "dovecot -n" outout (yes, I know it is an old version) # 1.2.17: /usr/local/etc/dovecot.conf # OS: FreeBSD 8.3-STABLE amd64 ufs log_path: /var/log/dovecot.log login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login verbose_proctitle: yes first_valid_uid: 1000 first_valid_gid: 1000 mail_privileged_group: mail mail_location: maildir:/var/mail/vhost/seibercom.net/gerard mail_plugins: expire imap_client_workarounds: delay-newmail netscape-eoh tb-extra-mailbox-sep lda: postmaster_address: postmaster(a)seibercom.net mail_plugins: sieve sieve_global_path: /usr/local/etc/dovecot/sieve/gerard.sieve sendmail_path: /usr/sbin/sendmail auth default: mechanisms: plain login digest-md5 cram-md5 username_format: %Lu verbose: yes debug: yes debug_passwords: yes passdb: driver: sql args: /usr/local/etc/dovecot-sql.conf userdb: driver: sql args: /usr/local/etc/dovecot-sql.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: 384 user: vmail group: vmail plugin: expire: Trash 2 Spam/* 2 expire_dict: proxy::expire dict: expire: mysql:/usr/local/etc/dovecot-dict-expire.conf This is the "dovecot-sql.conf" file: driver = mysql connect = host=localhost dbname=Dovecot user=root password=xxxxxxxx password_query = SELECT concat(userid, '@', domain) AS user, password \ FROM users WHERE userid = '%n' AND domain = '%d' user_query = SELECT uid, gid, home FROM users WHERE userid = '%n' AND domain = '%d' This is the pertinent part of the postconf -fn output: broken_sasl_auth_clients = yes smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/usr/local/etc/postfix/sasl_password_maps smtp_sasl_security_options = noanonymous smtp_sasl_type = dovecot smtpd_client_restrictions = reject_unauth_pipelining permit_sasl_authenticated smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_path = private/auth smtpd_sasl_security_options = noanonymous, noplaintext smtpd_sasl_tls_security_options = noanonymous I have tried using "dovecot" in place of "private/auth", but it doesn't make any difference. This is the only output from the postfix maillog: Mar 18 08:13:02 scorpio postfix/smtpd[65217]: connect from localhost[127.0.0.1] Mar 18 08:13:02 scorpio postfix/smtpd[65217]: warning: localhost[127.0.0.1]: SASL CRAM-MD5 authentication failed: authentication failure Mar 18 08:13:02 scorpio postfix/smtpd[65217]: lost connection after AUTH from localhost[127.0.0.1] Again, it doesn't appear that Postfix ever actually makes contact with Dovecot. I am probably doing something extremely stupid, but I just cannot figure out what it is. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __________________________________________________________________

2 2

[Dovecot] Dovecot with sasl/imaps/postfix and thunderbird
by Alex 18 Mar '13

18 Mar '13

Hi, I have an fc18 system with postfix and dovecot-2.1.13 and have configured them to use sasl for SMTP Auth and Maildir with imaps. The system is running now, so I'm trying to set up thunderbird to autodetect all settings during the initial account setup. However, it seems to want to use port 143 and STARTTLS, and not port 993, which is what I would expect. When I force it to use 993, I receive a certificate failure message: Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: initializing the server-side TLS engine Mar 12 23:20:45 propnew postfix/tlsmgr[14425]: open smtpd TLS cache btree:/var/lib/postfix/smtpd_tls_session_cache Mar 12 23:20:45 propnew postfix/tlsmgr[14425]: tlsmgr_cache_run_event: start TLS smtpd session cache cleanup Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: connect from unknown[192.168.1.43] Mar 12 23:20:45 propnew dovecot: imap-login: Disconnected (no auth attempts in 0 secs): user=<>, rip=192.168.1.43, lip=66.111.222.101, TLS: SSL_read() failed: error:14094412:SSL routines:SSL3_READ_BYTES:sslv3 alert bad certificate: SSL alert number 42, session=<BGBS5MXXhQDAqAEr> Mar 12 23:20:45 propnew postfix/submission/smtpd[14423]: lost connection after CONNECT from unknown[192.168.1.43] These are self-signed certs created using dovecot's mkcert.sh script. Is this a problem with the cert or with the dovecot configuration? Is it conventional to use port 143 for encrypted IMAP connections these days, and not just 993? I'm finding that port 25 works with TLS and postfix now too, not just port 587, so I'm really confused. I've included my doveconf output below. I'd appreciate it if someone could review it for me to be sure. # 2.1.13: /etc/dovecot/dovecot.conf # OS: Linux 3.8.1-201.fc18.x86_64 x86_64 Fedora release 18 (Spherical Cow) ext4 auth_debug = yes auth_mechanisms = plain login auth_verbose = yes default_client_limit = 2000 disable_plaintext_auth = no lda_mailbox_autocreate = yes lda_mailbox_autosubscribe = yes mail_debug = yes mail_location = maildir:/home/%u/Maildir mail_privileged_group = mail 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 ihave namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } passdb { driver = pam } passdb { driver = pam } plugin { sieve = ~/.dovecot.sieve sieve_dir = ~/sieve } service auth { unix_listener /var/spool/postfix/private/auth { group = postfix mode = 0660 user = postfix } } service imap-login { inet_listener imaps { port = 993 ssl = yes } process_min_avail = 20 service_count = 0 } ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } userdb { driver = passwd } protocol lda { info_log_path = /var/log/dovecot-lda.log log_path = /var/log/dovecot-lda-errors.log } protocol imap { mail_max_userip_connections = 100 } protocol pop3 { pop3_uidl_format = %08Xu%08Xv } Thanks, Alex

9 18

Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ?
by Clement PAULET 18 Mar '13

18 Mar '13

Hello Steffen, Thanks for your reply, This is my script (using for my test) : require "fileinto"; if address "To" "info(a)info.xx.com" { fileinto "Test"; } Clement ------------------------------ Message: 7 Date: Mon, 18 Mar 2013 13:23:33 +0100 (CET) From: Steffen Kaiser <skdovecot(a)smail.inf.fh-brs.de> To: Dovecot Mailing List <dovecot(a)dovecot.org> Subject: Re: [Dovecot] Dovecot - Sieve script loaded but filtering doesn't works ? Message-ID: <alpine.DEB.2.02.1303181322430.3303(a)pc-2m63.inf.fh-bonn-rhein-sieg.de> Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 18 Mar 2013, Clement PAULET wrote: When I use a Sieve script, it 's loaded but actions are not respect with this logs : The sieve script just trying to redirect to INBOX.Test folder but doesn't works.. First of all, how does your script looks like? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEVAwUBUUcHRl3r2wJMiz2NAQKoswf/WczI0q9k0WqWzRPr7lwuBEeiQQlYBDaq Lap8YNnbxDsczxgYZ/i0gDrq7f612A0nKWHBC806DxH4dHNyUwBPYVqFAT7edvk4 ns99f4bNh6GsufC1CY5tY/1DjT5ykEzkTmaV443YH50jQ4iPnDohOMsBBRlhoWN4 8KCLCNafCYXf48QjnAfoLt4TjaxyYb//7otYJN2CqLOGbvWoJwrpNgmuhvST+PNm RQXLG1lpxzt7QMP++fTMXa6A/SwVsglhAUS6xFdAuoOBsx1jPtvA+mot9gqpi02I j2WquMsycviWprYD2FsET903TWU/5+boxg2UBOettsTqhfwABkIcvQ== =ygun -----END PGP SIGNATURE-----

2 1

[Dovecot] Dovecot not obeying disable_plaintext_auth = yes and how to force/disable encryption
by Darren Pilgrim 18 Mar '13

18 Mar '13

I'm using Dovecot 2.1.15. I need to require encryption and only secure auth on public addresses, but allow plaintext auth over an unencrypted connection on localhost. I have so far (excerpts from `doveconf -a`): auth_mechanisms = cram-md5 plain disable_plaintext_auth = yes listen = service imap-login { inet_listener imap-local { address = ::1 port = 143 ssl = no } inet_listener imap-pub { address = 2001:db8::1 port = 993 ssl = yes } } service managesieve-login { inet_listener sieve-local { address = ::1 port = 4190 ssl = no } inet_listener sieve-pub { address = 2001:db8::1 port = 4190 ssl = no } } The ssl option only seems to switch the inet_listener between using a secure socket and using STARTTLS. How do I tell a given inet_listener to do neither? How do I tell a given inet_listener to require STARTTLS before allowing AUTH/SASL? I would prefer to offer only CRAM-MD5 on the UGA/public ports, and only PLAIN or at least also PLAIN on localhost. I tried adding auth_mechanisms lines to each inet_listener block, but got parse errors. How do I do this? Dovecot seems to ignore disable_plaintext_auth = yes: # telnet 2001:db8::1 4190 Trying 2001:db8::1... Connected to host.example.com. Escape character is '^]'. "IMPLEMENTATION" "Dovecot Pigeonhole" "SIEVE" "fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date ihave" "NOTIFY" "mailto" "SASL" "CRAM-MD5 PLAIN" "STARTTLS" "VERSION" "1.0" OK "Dovecot ready." -- Please reply on list.

1 1