- dovecot - dovecot.org

[Dovecot] "Perfect Forward Secrecy" on Redhat/Fedora
by Reindl Harald 16 Oct '13

16 Oct '13

RHEL/CentOS 6.5 will support ECDHE Fedora currently makes the turnaround no wonder that i burned down many hours: https://bugzilla.redhat.com/show_bug.cgi?id=1019390 https://bugzilla.redhat.com/show_bug.cgi?id=319901#c108 ______________________________ recent dovecot with also support older clients but perfer best possible encryption for modern ones ssl_prefer_server_ciphers = yes ssl_cipher_list = EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS:!SSLv2:@STRENGTH ______________________________ the same for Apache: SSLHonorCipherOrder On SSLCipherSuite EECDH+ECDSA+AESGCM:EECDH+aRSA+AESGCM:EECDH+ECDSA+SHA384:EECDH+ECDSA+SHA256:EECDH+aRSA+SHA384:EECDH+aRSA+SHA256:EECDH+aRSA+RC4:EECDH:EDH+aRSA:RC4:!aNULL:!eNULL:!LOW:!3DES:!MD5:!EXP:!PSK:!SRP:!DSS

1 0

[Dovecot] Using dovecot as LDA for postfix
by Farzad Mahdikhani 15 Oct '13

15 Oct '13

Hi Here is my environment: Red Hat Enterprise Linux Server release 5.7 (Tikanga) postfix-2.9.1-1.rhel5 dovecot 1.0.7 I want to config a complete postfix-dovecot mail server. First I configured postfix to use procmail, its default LDA and dovecot for pop3 and imap. I didn't changed main.cf a lot, just myhostname and a few other properties. I didn't set home_mailbox. About dovecot.conf here is the output of dovecot -n : # 1.0.7: /etc/dovecot.conf log_path: /var/log/dovecot.log protocols: imap pop3 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 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_plugin_dir(default): /usr/lib64/dovecot/imap mail_plugin_dir(imap): /usr/lib64/dovecot/imap mail_plugin_dir(pop3): /usr/lib64/dovecot/pop3 auth default: mechanisms: plain login passdb: driver: pam userdb: driver: passwd As you can see mail_location is not set. At this time everything was OK and working. I was able to send email using SquirrelMail and thunderbird. I got two users, user1 and user2, in my linux machine and when I sent an email from user1(a)software.com to user2(a)software.com the sent mail was saved in /home/user1/mail/Sent and the received email was in /var/mail/user2. The log file for dovecot had entries like this for user1 and user2: dovecot: Oct 14 14:44:52 Info: IMAP(user1): maildir: couldn't find root dir dovecot: Oct 14 14:44:52 Info: IMAP(user1): mbox: root exists (/home/user1/mail) dovecot: Oct 14 14:44:52 Info: IMAP(user1): mbox: INBOX exists (/var/mail/user1) dovecot: Oct 14 14:44:52 Info: IMAP(user1): mbox: root=/home/user1/mail, index=/home/user1/mail, inbox=/var/mail/user1 At this point I tried to change the LDA from procmail to dovecot by the following settings: I added/changed the following in the main.cf: mailbox_command = /usr/libexec/dovecot/deliver dovecot_destination_recipient_limit = 1 virtual_mailbox_domains = software.com virtual_transport = dovecot I added the following in the master.cf: dovecot unix - n n - - pipe flags=DRhu user=vmail:vmail argv=/usr/libexec/dovecot/deliver -f ${sender} -d ${recipient} But it didn't work. When I send email from from user2 to user1 the sent email is correctly saved in /home/user2/mail/Sent but it seems that user1 doesn't receive the incoming email. dovecot.log had entries like the following: dovecot: Oct 14 14:54:04 Info: imap-login: Login: user=<user1>, method=PLAIN, rip=::ffff:172.27.7.8, lip=::ffff:172.16.100.183, TLS dovecot: Oct 14 14:54:04 Info: IMAP(user1): Effective uid=504, gid=504, home=/home/user1 dovecot: Oct 14 14:54:04 Info: IMAP(user1): maildir: access(/home/user1/Maildir, rwx): failed: No such file or directory dovecot: Oct 14 14:54:04 Info: IMAP(user1): maildir: couldn't find root dir dovecot: Oct 14 14:54:04 Info: IMAP(user1): mbox: root exists (/home/user1/mail) dovecot: Oct 14 14:54:04 Info: IMAP(user1): mbox: INBOX exists (/var/mail/user1) dovecot: Oct 14 14:54:04 Info: IMAP(user1): mbox: root=/home/user1/mail, index=/home/user1/mail, inbox=/var/mail/user1 Setting home_mailbox = Maildir/ in main.cf and mail_location = maildir:~/Maildir in dovecot.cf didn't help. I have been googling and reading and testing for 4 or 5 days for this but there was no chance. Now, I am stuck and any help would be really really appreciated. Regards, Ferez

4 3

[Dovecot] how to handle logging
by Andreas Schulze 15 Oct '13

15 Oct '13

Hello, I plan a migration to dovecot and have concerns about the amount of logged data. On a testsystem dovecot produced 1TB syslog per day with a comparable amount of pop3 sessions. The current server log to STDOUT which is connected to multilog (circular buffer, http://cr.yp.to/daemontools/multilog.html) That way I can have a look at the last activities to any time. I like to have that in dovecot too. But since dovecot uses syslog it's not possible to adopt 1:1 Any ideas? Thanks -- 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 Dipl.-Kfm. Dr. Robert Mayr Jörg Rabe v. Pappenheim Dipl.-Vw. Eckhard Schwarzer Vorsitzender des Aufsichtsrates: Reinhard Verholen

4 5

[Dovecot] POP3 Setup help - more info
by Thomas I Higgins 15 Oct '13

15 Oct '13

Well my last email went unaswered - I assume because I didn't provide enough detailed information. Not a surprise if that is the case. Anyway, I also noted that there is no dovecot/pop3 process like there is for IMAP. Not certain that is wrong, but I am guessing it is. I am enclosing the output from a doveconf -an query - hopefully you can see a screenshot, otherwise I have to figure out how to get it in text form (work disables cp & scp traffic). Hopefully this will provide information that will help define what I am missing? Thanks again, Thomas Higgins

5 4

[Dovecot] Analyzing and correlating Dovecot with Postfix logs
by Igor David 14 Oct '13

14 Oct '13

Hi All, I was wondering if anyone knows what are best practices for correlating logs between Postfix and Dovecot ? I am having setup with postfix + amavisd + spamassassin + dovecot and everything looks like a charm for few years now. However, when e-mail arrives to my system, postfix is sending it to amavisd on port 10024, which is returning back to postfix on 10025, and postfix is then delivering e-mail to Dovecot (which is acting as LDA), so I can find e-mail header via message-ID easily in Postfix logs. But after that I cannot find e-mail in my Dovecot Maildir list as a filename, as Dovecot is having it's own way of storing e-mails in Maildir format, and I can't see that messageID in directory. I can grep all e-mails which can take some time, so I was wondering if there is more appropriate work around or setup Postfix/Dovecot, e.g. to modify somehow dovecot Maildir naming convention or similar? I was trying to find answer around but could not so any help is appreciated! Versions: Dovecot: 2.1.13 Amavisd: amavisd-new-2.6.6 postfix: 2.3.3 Thanks in advance! -- Kind regards, Igor

1 0

[Dovecot] Email address with special characters in userdb
by Arnon Weinberg 14 Oct '13

14 Oct '13

Hi, I have a userdb file set up in passwd-file format containing the following entries: >doveadm user test1*test2(a)test.com test1-test2(a)test.com test1étest2(a)test.com test1@test2@test.com test1%test2(a)test.com I can access the 1st entry (no special characters) no problem: >doveadm user test1-test2(a)test.com -f home /var/vmail The 2nd entry (using UTF-8 encoding) doesn't come up: >doveadm user test1étest2(a)test.com -f home userdb lookup: user test1étest2(a)test.com doesn't exist The 3rd entry does come up: >doveadm user test1@test2@test.com -f home /var/vmail but Postfix escapes this case using quotes, and they don't work: >doveadm user '"'test1@test2'"'@test.com userdb lookup: user "test1@test2"@test.com doesn't exist The 4th entry does not come up at all: >doveadm user test1%test2(a)test.com -f home userdb lookup: user test1%test2(a)test.com doesn't exist I believe these are all valid characters for email addresses (per the RFC) except '@' (which ironically works without escaping). How can I get them working? >dovecot --version 2.1.16 -- Arnon Weinberg www.back2front.ca

2 1

[Dovecot] LMTP Proxy auth
by claus.r＠bayern-mail.de 14 Oct '13

14 Oct '13

Hi, i tried to use lmtp proxy to a cyrus-server where i need authentication. My passdb lookup gives me: user=mailbox(a)cyrus.serv.er host=192.168.1.1 proxy=Y pass=secret destuser=cyrus_lmtp_master As i see in packettrace to the lmtp-cyrus-server the dovecot-proxy didn't try any authentication. Could someone please confirm to me that LMTP proxy with auth isn't supported or is there any configuration issue i have missed?

1 0

[Dovecot] Questions about special_use mailboxes
by Florian Lindner 14 Oct '13

14 Oct '13

Hello, I am using using dovecot 2.1.7 from debian stable: namespace inbox { inbox = yes location = mailbox Drafts { special_use = \Drafts } mailbox Junk { special_use = \Junk } mailbox Spam { special_use = \Junk } mailbox Sent { special_use = \Sent } mailbox "Sent Messages" { special_use = \Sent } mailbox Trash { special_use = \Trash } prefix = } I monitor IMAP traffic using the MUA trojita. When I select the mailbox Drafts: >>> y10 SELECT Drafts (QRESYNC (1381746443 1)) <<< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. Flag is \Draft instead of \Drafts? When I select Sent >>> y12 SELECT Sent (QRESYNC (1381746442 7 (2 2))) <<< * OK [CLOSED] Previous mailbox closed.␍␊ <<< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft $SENT) <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft $SENT \*)] Flags permitted. Why is the flag $SENT ? http://www.faqs.org/rfcs/rfc6154.html mentiones nothing like that. When I select Spam: >>> y14 SELECT Spam (QRESYNC (1381746444 1)) <<< * OK [CLOSED] Previous mailbox closed. <<< * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) <<< * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. No flag at all? Or am I getting IMAP wrong? Thanks, Florian

1 0

[Dovecot] dovecot 2.2.x and replication with dsync and shared / public namespace
by romain 13 Oct '13

13 Oct '13

Hi, I'm trying to configure replication with dsync on Dovecot 2.2.5 (and latest nightly). I did followed the guide at http://wiki2.dovecot.org/Replication But I can get dsync-server working only if my users do not have access to shared mailboxes and / or public mailboxes which is problematic for our setup. dsync-server is trying to create folders in public/ namespace : ------------------------------------- 2013-09-23 20:34:04 dsync-server(adupont): Panic: file dsync-brain-mailbox-tree.c: line 384 (dsync_brain_mailbox_tree_add_delete): assertion failed: (other_node->ns == NULL || other_node->ns == node->ns) 2013-09-23 20:34:04 dsync-server(adupont): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x64faa) [0x7f7bf42dcfaa] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x64fee) [0x7f7bf42dcfee] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7f7bf4299299] -> dovecot/doveadm-server() [0x41ba52] -> dovecot/doveadm-server(dsync_brain_recv_mailbox_tree_deletes+0xbb) [0x41c39b] -> dovecot/doveadm-server(dsync_brain_run+0x37c) [0x41972c] -> dovecot/doveadm-server() [0x419bf8] -> dovecot/doveadm-server() [0x42ba20] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f7bf42ed3d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xaf) [0x7f7bf42ee23f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f7bf42ecf18] -> dovecot/doveadm-server() [0x416e59] -> dovecot/doveadm-server() [0x40cc77] -> dovecot/doveadm-server() [0x415ddd] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7f7bf42ed3d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xaf) [0x7f7bf42ee23f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7f7bf42ecf18] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7f7bf429e553] -> dovecot/doveadm-server(main+0x11b) [0x40c9eb] -> /lib64/libc.so.6(__libc_start_main+0xed) [0x7f7bf3f0932d] -> dovecot/doveadm-server() [0x40ca59] 2013-09-23 20:34:04 dsync-server(adupont): Fatal: master: service(doveadm): child 28131 killed with signal 6 (core dumped) ------------------------------------- dsync-server is trying to create folders in shared/ namespace : ------------------------------------- 2013-09-23 20:34:05 dsync-server(s.durant): Panic: file dsync-mailbox-tree-sync.c: line 1029 (sync_create_mailboxes): assertion failed: (node->ns == other_node->ns) 2013-09-23 20:34:05 dsync-server(s.durant): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0(+0x64faa) [0x7ffb6fd74faa] -> /usr/local/lib/dovecot/libdovecot.so.0(+0x64fee) [0x7ffb6fd74fee] -> /usr/local/lib/dovecot/libdovecot.so.0(i_fatal+0) [0x7ffb6fd31299] -> dovecot/doveadm-server() [0x426025] -> dovecot/doveadm-server(dsync_mailbox_trees_sync_init+0x139) [0x427789] -> dovecot/doveadm-server(dsync_brain_recv_mailbox_tree_deletes+0xdd) [0x41c3bd] -> dovecot/doveadm-server(dsync_brain_run+0x37c) [0x41972c] -> dovecot/doveadm-server() [0x419bf8] -> dovecot/doveadm-server() [0x42ba20] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7ffb6fd853d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xaf) [0x7ffb6fd8623f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7ffb6fd84f18] -> dovecot/doveadm-server() [0x416e59] -> dovecot/doveadm-server() [0x40cc77] -> dovecot/doveadm-server() [0x415ddd] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_call_io+0x36) [0x7ffb6fd853d6] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xaf) [0x7ffb6fd8623f] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x28) [0x7ffb6fd84f18] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x13) [0x7ffb6fd36553] -> dovecot/doveadm-server(main+0x11b) [0x40c9eb] -> /lib64/libc.so.6(__libc_start_main+0xed) [0x7ffb6f9a132d] -> dovecot/doveadm-server() [0x40ca59] 2013-09-23 20:34:05 dsync-server(s.durant): Fatal: master: service(doveadm): child 28137 killed with signal 6 (core dumped) ------------------------------------- If I run the command "doveadm -v sync -u my.user -f tcp:10.20.0.2:12345" mailboxes are sync correctly. No problem with public and shared mailboxes. If i run the command doveadm replicator replicate 's.durant' or doveadm replicator replicate '*', I get plenty of Panic / Error for all users that can access Public mailboxes or Shared mailboxes. Regards, MARIADASSOU Romain

1 1

[Dovecot] Problem with PAM, vpopmail and Roundcube
by ede＠ede.com.ec 13 Oct '13

13 Oct '13

Hello, I have a problem to which I have not been able to find a solution by myself or online. I have Dovecot running together with Qmail on a CentOS server. I need to be able to control which users are allowed IMAP access and at the same time allow IMAP access for all users when the requests are coming from a specific IP. My problem has two parts, detailed below. ----------------------------------------------------------- 1. PAM not working to allow access only for specified users ----------------------------------------------------------- Right now I am controlling IMAP access with [vmoduser -i] in Qmail which is not what I want. I need the IMAP access to be closed for everyone and then specify which users are allowed to access. I tried using [pam.d] for this as per http://wiki.dovecot.org/Authentication/RestrictAccess but although I am not getting any errors, all users are still allowed access unless I block them with [vmoduser -i]. In [dovecot.conf] I have: passdb pam { args = * } In [/etc/pam.d/imap] I have: auth required pam_listfile.so item=user sense=allow file=/etc/imapusers onerr=fail And in [/etc/imapusers] I have specified the only users that should have access. Any ideas why this isn't working? ------------------------------------------------------- 2. Allow access for all users coming from a specific IP ------------------------------------------------------- I have a Roundcube installation running on an external server and I need *all* my users to be able to use the Webmail regardless if they have IMAP or only POP access from their computer or mobile devices. Using PAM I tried in [/etc/pam.d/imap]: auth required pam_listfile.so item=user sense=allow file=/etc/imapusers onerr=fail allow_nets=127.0.0.0/8,192.168.0.0/16,1.2.3.4 ...where the webmail installation would be installed at IP [1.2.3.4]. But no luck! ------------------------------------------------------- Please - if there are anyone with ideas I could really use them. I have been going around in circles for the last couple of weeks and I don't know what to do! Sincerely, Daniel

2 2