- dovecot - dovecot.org

[Dovecot] Master Users
by Ben Watts 13 Jul '10

13 Jul '10

Greetings, My company is currently using dovecot with ldap, I am in the process of migrating this over to Exchange. However, to make the process a lot smoother I need to make use of the master user function of dovecot to enable access to other users mailboxes without needing their password. I've gone through the documentation but it looks like this might not be possible with an ldap backend. The wiki isnt exactly crystal clear on where the master user config needs to go. I've generated a passdb file with an admin user and password. Any information that would go to help would be very welcome. Cheers --

2 1

[Dovecot] Command output: Failed to write to log file
by Nick Lunt 13 Jul '10

13 Jul '10

Hi dovecot -n at end of message. Jul 13 09:41:56 findb postfix/smtpd[15996]: connect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/smtpd[15996]: 3B7EF56ABA: client=unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/cleanup[15999]: 3B7EF56ABA: message-id=<26CDBD30F4FE1D4FB6FB5F6D16BCA93E0E5B7777AD(a)RVEB1SRVMSGCCR1.c ymru.nhs.uk> Jul 13 09:41:56 findb postfix/qmgr[15667]: 3B7EF56ABA: from=<>, size=1711, nrcpt=1 (queue active) Jul 13 09:41:56 findb postfix/smtpd[15996]: disconnect from unknown[10.56.85.6] Jul 13 09:41:56 findb postfix/local[16000]: 3B7EF56ABA: to=<enduser(a)thishost.com>, relay=local, delay=0.05, delays=0.03/0.01/0/0.02, dsn=4.3.0, status=deferred (temporary failure. Command output: Failed to write to log file) Our postfix server started logging the above messages so I was thinking I had a postfix issue, but it turned out that recreating the dovecot.log file fixed the issue. Does the /var/log/dovecot.log file require special permissions or can it only grow to a certain size ? [/var/log]# dovecot -n # 1.2.10: /etc/dovecot.conf # OS: Linux 2.6.18-92.el5 x86_64 Red Hat Enterprise Linux Server release 5.2 (Tikanga) log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot.log ssl: no 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_access_groups: mail mail_privileged_group: mail mail_location: maildir:~/Maildir 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/lib/dovecot/imap mail_plugin_dir(imap): /usr/lib/dovecot/imap mail_plugin_dir(pop3): /usr/lib/dovecot/pop3 lda: postmaster_address: root@localhost mail_plugins: sieve auth default: debug: yes passdb: driver: pam userdb: driver: passwd plugin: sieve: ~/.dovecot.sieve sieve_dir: ~/ log_path: /var/log/dovecot.log Many thanks Nick . __________ Information from ESET NOD32 Antivirus, version of virus signature database 5273 (20100712) __________ The message was checked by ESET NOD32 Antivirus. http://www.eset.com

2 2

[Dovecot] Dovecot "deliver" with multiple UIDs (security question)
by Buzai Andras 12 Jul '10

12 Jul '10

Hi all, I have a question related to using the Dovecot LDA (deliver) with a multiple UID setup as described on the http://wiki.dovecot.org/LDA page in the "Multiple UIDs" section. I run Postfix (virtual mailboxes) + Dovecot using multiple UIDs (one UID per virtual domain owner). I configured Postfix to use Dovecot Deliver for the virtual transport. To overcome the problem of multiple UIDs I used the solution described on the http://wiki.dovecot.org/LDA page in the "Multiple UIDs" section. I used the "sudo" solution as described on the page. I only call the deliver with sudo from inside Postfix and the sudoer user is only allowed to sudo on the deliver binary. My question is: Is this solution secure? Can It be used on a production environment? What exactly happens in the background from the time I call "deliver" with sudo, to the time the delivery is finished? The configuration works. The emails get delivered but I am concerned about the security of this setup :(. Thank you, Buzai Andras

3 7

[Dovecot] TLS Issue
by Leander S. 12 Jul '10

12 Jul '10

Hi, I use Postfix & Dovecot with TLS / SSL - it authenticates / works fine - except I'm always getting this ugly SSL cert warning messages mit MTAs. It says that the following: "You have attempted to establish a connection with "server". However, the security certificate presented belongs to "*.server". It is possible, though unlikely, that someone may be trying to intercept your communication with this web site." Is there a serverside solution that I wont get that any more? Why is * as a wildcard not working? Iwonder How gMail or other providers solve that issue Regards

3 2

[Dovecot] deliver and root user
by Bradlee Landis 12 Jul '10

12 Jul '10

On RHEL5, dovecot 1.0.7, I have set up sendmail to use `deliver` for my local mda. It keeps giving me this error for the root user though: Jul 12 12:51:29 mail sendmail[4105]: o699225f001348: to=<root(a)localhost.localdomain>, ctladdr=<root(a)localhost.localdomain> (0/0), delay=3+08:49:26, xdelay=00:00:00, mailer=local, pri=7502879, dsn=4.0.0, stat=Deferred: local mailer (/usr/libexec/dovecot/deliver) exited with EX_TEMPFAIL I've tried to `chmod +s /usr/libexec/dovecot/deliver`, which I read might fix some of those issues, but it didn't. Anyways, here are the important changes I made in my config files for using `deliver`: == sendmail.mc == ... dnl ## Should I modify this?? define(`PROCMAIL_MAILER_PATH', `/usr/bin/procmail')dnl ... dnl ## Should I have "localhost.localdomain" here? It currently is not. LOCAL_DOMAIN(`mydomain.com') ... FEATURE(`local_procmail', `/usr/libexec/dovecot/deliver',`/usr/libexec/dovecot/deliver -d $u') MODIFY_MAILER_FLAGS(`LOCAL', `-f') ... MAILER(smtp) MAILER(procmail) MAILER(local) == END == == dovecot.conf == ... protocol lda { postmaster_address = postmaster(a)mydomain.com hostname = mydomain.com } == END == Any ideas, or do you need more information? -- Thanks, Brad Landis

4 5

[Dovecot] Dovecot + OCFS2
by Thiago Henrique 12 Jul '10

12 Jul '10

Hello, I intend to make a cluster with Dovecot + OCFS2. The tests are working with the default settings of the Dovecot. But it seems too easy to be true. Is there any special configuration of Dovecot to implement it?-- Thank you -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

2 1

[Dovecot] Dovecot-lda and Postfix virtual
by D F 12 Jul '10

12 Jul '10

Hello, I'm currently testing Dovecot 2.0RC2 and I have a problem migrating my current configuration. Current configuration is : - Dovecot as IMAP server - Postfix as SMTP/LDA with virtual users. main.cf is : #----------------------------------------------------------- # inet_protocols = all myhostname = mail.domain.tld mydomain = domain.tld myorigin = $mydomain inet_interfaces = all mydestination = localhost local_transport = virtual local_recipient_maps = hash:/etc/postfix/domain.tld virtual_mailbox_base = /home/mail virtual_mailbox_maps = hash:/etc/postfix/domain.tld virtual_mailbox_domains = domain.tld virtual_uid_maps = static:5000 virtual_gid_maps = static:5000 unknown_local_recipient_reject_code = 550 mynetworks = 127.0.0.0/8, [::1]/128 smtpd_banner = $myhostname ESMTP mailbox_size_limit = 0 message_size_limit = 0 virtual_mailbox_limit = 0 smtpd_helo_required = yes # smtpd_sasl_auth_enable = yes smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination smtpd_helo_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unknown_helo_hostname, reject_invalid_helo_hostname # debug_peer_level = 1 sendmail_path = /usr/sbin/sendmail newaliases_path = /usr/bin/newaliases mailq_path = /usr/bin/mailq setgid_group = postdrop html_directory = no manpage_directory = /usr/local/man sample_directory = /etc/postfix readme_directory = no queue_directory = /var/spool/postfix command_directory = /usr/sbin daemon_directory = /usr/libexec/postfix mail_owner = postfix alternate_config_directories = /etc/postfix #----------------------------------------------------------- /etc/postfix/domain.tld looks like : #----------------------------------------------------------- # User denis(a)domain.tld /domain.tld/denis/ # Admin root(a)domain.tld /domain.tld/denis/.system/ dnsowner(a)domain.tld /domain.tld/denis/.system/ abuse(a)domain.tld /domain.tld/denis/.system/ postmaster(a)domain.tld /domain.tld/denis/.system/ #----------------------------------------------------------- Currently, I can send mails to denis(a)domain.tld or root(a)domain.tld and they are all accepted and placed in the right IMAP folder/subfolder. Now I'd like to use Dovecot as a LDA (I want to use Sieve). I first add "mailbox_command = /usr/local/libexec/dovecot/dovecot-lda" and "virtual_transport = dovecot" to postfix.conf. Then I add "dovecot unix - n n - - pipe flags=DRhu user=nobody:nobody argv=/usr/local/libexec/dovecot/dovecot-lda -f ${sender} -d ${recipient}" to master.cf Here is my Dovecot config : #----------------------------------------------------------- listen = *, :: protocols = imap base_dir = /var/run/dovecot/ login_greeting = domain.tld IMAP ready. disable_plaintext_auth = no auth_mechanisms = plain auth_failure_delay = 2 secs mail_location = dbox:/home/mail/%d/%n default_login_user = dovenull default_internal_user = dovecot service imap-login { inet_listener imap { port = 143 } inet_listener imaps { port = 993 ssl = yes } } service auth { # Postfix smtp-auth unix_listener /var/spool/postfix/private/auth { mode = 0666 user = postfix group = postfix } unix_listener auth-userdb { mode = 0666 user = nobody group = nobody } } passdb { driver = passwd-file args = /usr/local/etc/dovecot/users.db } userdb { driver = passwd-file args = /usr/local/etc/dovecot/users.db } ssl = no #----------------------------------------------------------- /usr/local/etc/dovecot/users.db looks like : #----------------------------------------------------------- denis@domain.tld:password:5000:5000::/home/mail/domain.tld/denis #----------------------------------------------------------- If I send a mail to denis(a)domain.tld it works great, if I send a mail to root(a)domain.tld, it tells the user is non-existent. Is it possible to work the way it used to and benefit from dovecot-lda ? I read http://wiki2.dovecot.org/LDA/Postfix but it seems none of the case looks like mine. Thank you in advance, Denis

2 2

[Dovecot] SSL / TLS Problem
by Leander S. 12 Jul '10

12 Jul '10

Hi, since I upgraded to the new Thunderbird version 3.1 I can't establish a TLS/SSL connection anymore. But before the update Thunerbird was able to establish an encrypted session ... Maillog shows me the following now: server dovecot: imap-login: Disconnected (no auth attempts): rip=84.157.133.248, lip=192.168.1.100, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca Why is the CA unknowen - all of a sudden - ?! Thanks

2 4

[Dovecot] Can only see some folders of inbox
by He Llo 12 Jul '10

12 Jul '10

I've had a working system for ages now with Postfix/Dovecot/Squirrelmail. This evening the right hand pane of Squirrel Mail failed to complete with the Inbox selected but would show some of the other folders. I can also filter and access mail from the 'Invisible' inbox. Other mailboxes on the same server are fine. I've copied my version number below and the output of dovecot -n In the dovecot.log I can see lots of entries like: Warning I/O leak: 0x804d640 (13) or (15) and IMAP login killed with signal 15. I get the same behaviour if I connect with Outlook 2007 configured for IMAP. The mailbox has a lot of mail in it: easily a couple of GB. Very puzzled and would appreciate any help. Many thanks in advance, Mark. ............................................................ Using Postfix with Dovecot V1.0.9 [root@mailer log]# dovecot -n # 1.0.9: /usr/local/etc/dovecot.conf base_dir: /var/run/dovecot/ log_path: /var/log/dovecot.log info_log_path: /var/log/dovecot-info.log ssl_disable: yes disable_plaintext_auth: no login_dir: /var/run/dovecot/login login_executable: /usr/local/libexec/dovecot/imap-login login_max_processes_count: 64 mail_location: maildir:/home/vmail/%d/%n/Maildir dotlock_use_excl: yes maildir_copy_with_hardlinks: yes auth default: verbose: yes passdb: driver: passwd-file args: /etc/dovecot/passwd userdb: driver: static args: uid=vmail gid=vmail home=/home/vmail/%u _________________________________________________________________ http://clk.atdmt.com/UKM/go/197222280/direct/01/ Do you have a story that started on Hotmail? Tell us now

2 2

[Dovecot] dsync crash
by Matthias Rieber 12 Jul '10

12 Jul '10

Hi, while syncing dsync crashed: dsync-local(matthias): Panic: dsync brain state=10 dsync-local(matthias): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0xf7eed541] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x4e) [0xf7eed66e] -> /usr/local/lib/dovecot/libdovecot.so.0(i_error+0) [0xf7eed878] -> dsync [0x804e106] -> dsync [0x80539b7] -> dsync [0x8053c72] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xf7ef9bc5] -> /usr/local/lib/dovecot/libdovecot.so.0(io_loop_run+0x30) [0xf7ef8c10] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_run+0x2a) [0xf7ee629a] -> dsync(main+0x7aa) [0x804da3a] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xf7d7a455] -> dsync [0x804d0c1] I don't have a full backtrace. When I repeated the sync it seemed to work. Regards, Matthias

2 5

[Dovecot] UID FETCH returns results outside requested range
by David Woodhouse 12 Jul '10

12 Jul '10

00 SELECT INBOX * OK [CLOSED] Previous mailbox closed. * FLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk $Label1 $Label2 $Label3 $Label4 $Label5 receipt-handled NotJunk NonJunk $MDNSent $has_cal unknown-6 OldNotJunk $Forwarded) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft Junk $Label1 $Label2 $Label3 $Label4 $Label5 receipt-handled NotJunk NonJunk $MDNSent $has_cal unknown-6 OldNotJunk $Forwarded \*)] Flags permitted. * 7126 EXISTS * 0 RECENT * OK [UNSEEN 16] First unseen. * OK [UIDVALIDITY 1154089803] UIDs valid * OK [UIDNEXT 152280] Predicted next UID * OK [HIGHESTMODSEQ 22137] Highest 00 OK [READ-WRITE] Select completed. 01 UID FETCH 152280:* (UID) * 7126 FETCH (UID 152279) 01 OK Fetch completed. Dovecot 1.2.11 on Fedora 12 with Maildir mailboxen. Why is it returning the message with UID 152279, when asked for the range 152280:* ? Is there some reason it has to return at least one result? -- dwmw2

2 2

[Dovecot] Loggin! Exception.
by Henrique Fernandes 12 Jul '10

12 Jul '10

It is possible to make dovecot do not log any request from a determined host? Because, we gonna use ldirectord for foward request and etc. He makes an connection every 2 sec i guess, and dovecot logs its. The logs get too many info that we don need! Any ideias ? Thanks! * *[]'sf.rique

1 0

Re: [Dovecot] I can receive but not send
by Dennis Clarke 12 Jul '10

12 Jul '10

>> Am I missing something obvious here ? >> > > Yes, Dovecot is not an SMTP server, it provides POP3 and IMAP which are > for mail retrieval. Common SMTP servers are Exim, Postfix, Sendmail and > Qmail. Well that tells me dovecot is working fine but sendmail is not listening to roaming mail clients. Sending of message failed. The message could not be sent because connecting to SMTP server foo.domainname.ca failed. The server may be unavailable or is refusing SMTP connections. Please verify that your SMTP server settings are correct and try again, or contact the server administrator. However I can telnet to the port 25 just fine ... bizarre. -- Dennis

2 1

[Dovecot] Command died with signal 6
by Gourav Joshi 12 Jul '10

12 Jul '10

Hi, We have dovecot 1.1.20 running on Fedora 7 with mail and indexes on NFS. On our delivery server we are getting "status=bounced (Command died with signal 6: "/usr/local/libexec/dovecot/deliver")" We are fetching these mails from another server which has Centos 5.2 installed. We have mail_nfs*=yes and mmap_disable=yes settings in dovecot.conf. Please let me know why the above error coming in dovecot logs? Regards, Gourav Joshi

2 2

[Dovecot] maildir / deliver question
by Martin Waschbuesch 12 Jul '10

12 Jul '10

Hi all, I have the following situation: On a qmail toaster I am running (with dovecot 1.2.12 as the IMAP server), spam mail gets automatically put into a 'this might be spam' folder (per user). Now, every user has the opportunity to move that mail into either a 'learn as spam' or a 'this was ham' folder and the mail items will be treated accordingly. As a cronjob, I run a script that loops through all the users' folders and either learns as spam and deletes or learns as ham and moves back to the user's inbox. My questions now are these: 1.) Is there any danger regarding maildir consistency in directly moving mail items about? 2.) Could I somehow use deliver to move the mails? I think I can recall that other LDAs (maildrop?) allow for that? This would of course be preferred as the maildir cache would also still be optimized after the operation. If anyone has any suggestions, I'd really appreciate this. Thanks a lot for your help and this great tool! Martin -- "The nice thing about being a celebrity is that when you bore people, they think it's their fault." Henry Kissinger

2 2

[Dovecot] Doveadmn Quota
by Steven King 12 Jul '10

12 Jul '10

Hey Everyone, I am running the new Dovecot 2.0 RC2. When I try to run 'doveadm quota recalc -A' I just get the usage info for doveadm. Running 'doveadm help quota' gives me the man page for the quota command, and I follow the man page examples as is. Is this feature not implemented yet? Or am I doing something wrong? I know quota is a "plugin" for the doveadm program, but there is no documentation on how to get this to load of if it needs to be loaded at all. Thanks! -- Steve King Senior Linux Engineer - Advance Internet, Inc. Cisco Certified Network Associate CompTIA Linux+ Certified Professional CompTIA A+ Certified Professional

2 6

[Dovecot] SSL / TLS Problem
by Leander S. 11 Jul '10

11 Jul '10

P.S. Postfix TLS/SSL works still fine ... I don't understand why dovecot doesn't want to work with the new thunderbird version ... Hi, since I upgraded to the new Thunderbird version 3.1 I can't establish a TLS/SSL connection anymore. But before the update Thunerbird was able to establish an encrypted session ... Maillog shows me the following now: server dovecot: imap-login: Disconnected (no auth attempts): rip=84.157.133.248, lip=192.168.1.100, TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca Why is the CA unknowen - all of a sudden - ?! Thanks

1 0

[Dovecot] IMAPS log analyzer
by James 11 Jul '10

11 Jul '10

I want something like awstats for dovecot IMAPS so I can see how much usage it takes.

1 0

[Dovecot] Dovecot 2.0 RC1 and OpenBSD 4.7
by D F 10 Jul '10

10 Jul '10

Hello all, I'm currently doing some tests with Dovecot 2.0 RC1 and OpenBSD4.7 (socppc or i386 architectures) and I can't compile it : I "./configure" with default options and then "make" : $ make [...] Making all in doc Making all in man make: don't know how to make doveadm.1. Stop in /home/mail/dovecot-2.0.rc1/doc/man. *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1/doc (line 386 of Makefile). *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1 (line 505 of Makefile). *** Error code 1 Stop in /home/mail/dovecot-2.0.rc1 (line 328 of Makefile). $ Is there any thing I can try ? Thank you in advance, Denis

5 10

[Dovecot] --with-PACKAGE is not recognized (dovecot 2.0.rc2)
by Sven Kirmess 10 Jul '10

10 Jul '10

The build process/configure script does not recognize the --with-PACKAGE option. Unfortunately I have no experience with autoconfigure/automake but maybe someone on the list knows how to fix this? I assume it should be an easy fix as most software recognizes the --with-PACKAGE flag. :) This is how I build dovecot: LDFLAGS=-L/opt/openssl \ CPPFLAGS=-I/opt/openssl \ ./configure --prefix=/opt/dovecot-2.0.rc2 --sysconfdir=/etc/opt/dovecot --localstatedir=/var/opt/dovecot --datarootdir=/opt/dovecot-2.0.rc2 --docdir=/opt/dovecot-2.0.rc2/doc --with-rundir=/var/opt/dovecot/run --with-statedir=/var/opt/dovecot/state --with-PACKAGE=no --with-ssl=openssl --with-ssldir=/etc/opt/dovecot; \ /usr/sfw/bin/gmake And I get the following warning: configure: WARNING: unrecognized options: --with-PACKAGE Same for --without-PACKAGE: configure: WARNING: unrecognized options: --without-PACKAGE This results in dovecot installing in the following wrong directories: /etc/opt/dovecot/dovecot /opt/dovecot-2.0.rc2/include/dovecot /opt/dovecot-2.0.rc2/lib/dovecot /opt/dovecot-2.0.rc2/libexec/dovecot The argument --with-PACKAGE=no should be usable to disable these interemiate dovecot directories which are only useful if you install all software in /usr/local. Thanks, Sven $ find /opt/dovecot-2.0.rc2 /var/opt/dovecot/ /etc/opt/dovecot -type d /opt/dovecot-2.0.rc2/man /opt/dovecot-2.0.rc2/man/man1 /opt/dovecot-2.0.rc2/man/man7 /opt/dovecot-2.0.rc2/doc /opt/dovecot-2.0.rc2/doc/wiki /opt/dovecot-2.0.rc2/doc/example-config /opt/dovecot-2.0.rc2/doc/example-config/conf.d /opt/dovecot-2.0.rc2/include /opt/dovecot-2.0.rc2/include/dovecot /opt/dovecot-2.0.rc2/aclocal /opt/dovecot-2.0.rc2/sbin /opt/dovecot-2.0.rc2/lib /opt/dovecot-2.0.rc2/lib/dovecot /opt/dovecot-2.0.rc2/lib/dovecot/auth /opt/dovecot-2.0.rc2/lib/dovecot/doveadm /opt/dovecot-2.0.rc2/libexec /opt/dovecot-2.0.rc2/libexec/dovecot /opt/dovecot-2.0.rc2/bin /var/opt/dovecot/ /var/opt/dovecot/run /var/opt/dovecot/run/empty /var/opt/dovecot/run/login /var/opt/dovecot/state /etc/opt/dovecot /etc/opt/dovecot/dovecot /etc/opt/dovecot/dovecot/private /etc/opt/dovecot/dovecot/conf.d /etc/opt/dovecot/dovecot/certs

2 4

[Dovecot] dsync duplicates messages/crashed if a 'large' number of messages has been deleted
by Matthias Rieber 10 Jul '10

10 Jul '10

Hi, I try to mirror two dovecots with: dsync -v -f -u login mirror ssh -o IdentityFile=/etc/dovecot/dsync.d/id_rsa root@shrike dsync -u login This usually works, but if I delete a certain number of emails, I get this messages: dsync-local(mailverwalter): Info: Posteingang: Ignored 178 modseq changes dsync-local(mailverwalter): Info: Posteingang: Couldn't keep all uids dsync-local(mailverwalter): Warning: Mailbox changes caused a desync. You may want to run dsync again. after a second try I get: dsync-local(mailverwalter): Panic: dsync brain state=10 dsync-local(mailverwalter): Error: Raw backtrace: /usr/local/lib/dovecot/libdovecot.so.0 [0xf7e44541] -> /usr/local/lib/dovecot/libdovecot.so.0(default_fatal_handler+0x4e) [0xf7e4466e] -> /usr/local/lib/dovecot /libdovecot.so.0(i_error+0) [0xf7e44878] -> dsync [0x804f4d6] -> dsync [0x80537c7] -> dsync [0x8053a82] - > /usr/local/lib/dovecot/libdovecot.so.0(io_loop_handler_run+0xf5) [0xf7e50bc5] -> /usr/local/lib/dovecot /libdovecot.so.0(io_loop_run+0x30) [0xf7e4fc10] -> /usr/local/lib/dovecot/libdovecot.so.0(master_service_ run+0x2a) [0xf7e3d29a] -> dsync(main+0x732) [0x804db32] -> /lib/libc.so.6(__libc_start_main+0xe5) [0xf7cd 1455] -> dsync [0x804d0c1] Regards, Matthias

2 5

[Dovecot] Mercurial dovecot-2.0 branch change
by Timo Sirainen 10 Jul '10

10 Jul '10

I got tired of seeing the HEAD branch name in hg.dovecot.org (caused by the initial import from CVS), so I finally switched to "default" branch name where it doesn't show it. But apparently now everyone using dovecot-2.0 hg needs to switch to the default branch. You should see something like: ~/cvs/dovecot-2.0% hg pull -u .. not updating, since new heads added (run 'hg heads' to see heads, 'hg merge' to merge) Now give a command: hg up -C default Hopefully there won't be other problems with the change.

1 0

[Dovecot] TLS handshaking error: unknown ca
by Ben Jordan 10 Jul '10

10 Jul '10

I'm running Ubuntu 10.04, recently upgraded. My dovecot version is 1.2.9. My SSL/TLS authentication with dovecot from non-local IP's has stopped working, and I can no longer access my mail securely. I have changed all entries to refer to my server as "host". I am the only user, and am OK with the a self-signed cert. When I try to connect using Thunderbird, the certificate window says "unable to obtain identification status for the given site". This action generates the entry in /var/log/mail.log: TLS handshaking: SSL_accept() failed: error:14094418:SSL routines:SSL3_READ_BYTES:tlsv1 alert unknown ca I am using self-signed certificates, generated using: openssl genrsa -out server.key 1024 openssl req -new -x509 -key server.key -out server.pem -days 1826 If I use openssl s_client -connect host:993 to connect, I get the following output: CONNECTED(00000003) depth=0 /C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com verify error:num=18:self signed certificate verify return:1 depth=0 /C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com verify return:1 --- Certificate chain 0 s:/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555@gmail.com i:/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555@gmail.com --- Server certificate -----BEGIN CERTIFICATE----- MIIDdTCCAt6gAwIBAgIJAIMqhTeSqt7PMA0GCSqGSIb3DQEBBQUAMIGEMQswCQYD VQQGEwJVUzELMAkGA1UECBMCTUExEjAQBgNVBAcTCUNhbWJyaWRnZTEQMA4GA1UE ChMHSGFydmFyZDEMMAoGA1UECxMDT0VCMQ8wDQYDVQQDEwZNQ1IyRDIxIzAhBgkq hkiG9w0BCQEWFGJqb3JkYW41NTVAZ21haWwuY29tMB4XDTEwMDcxMDE0MjYyMFoX DTE1MDcxMDE0MjYyMFowgYQxCzAJBgNVBAYTAlVTMQswCQYDVQQIEwJNQTESMBAG A1UEBxMJQ2FtYnJpZGdlMRAwDgYDVQQKEwdIYXJ2YXJkMQwwCgYDVQQLEwNPRUIx DzANBgNVBAMTBk1DUjJEMjEjMCEGCSqGSIb3DQEJARYUYmpvcmRhbjU1NUBnbWFp bC5jb20wgZ8wDQYJKoZIhvcNAQEBBQADgY0AMIGJAoGBAJ8m09I2TR9J93lRzYvi mvo7WoZsjEI9kJbJwrJo3xc662w5yLGiolkxvuul8TN0PaDcJsjTAKPuiU2hmYku 9OmCtGlWtkVGmUPCyUok97rC7N81vBdIwUPoMRI4AA1s/Ubu22QIRnnmB8H+BNfs BqTA6E9q4cHUEhVlt3CMTk9tAgMBAAGjgewwgekwHQYDVR0OBBYEFFh0Xj1WtJmZ ZUKijH/JqVgsF4KCMIG5BgNVHSMEgbEwga6AFFh0Xj1WtJmZZUKijH/JqVgsF4KC oYGKpIGHMIGEMQswCQYDVQQGEwJVUzELMAkGA1UECBMCTUExEjAQBgNVBAcTCUNh bWJyaWRnZTEQMA4GA1UEChMHSGFydmFyZDEMMAoGA1UECxMDT0VCMQ8wDQYDVQQD EwZNQ1IyRDIxIzAhBgkqhkiG9w0BCQEWFGJqb3JkYW41NTVAZ21haWwuY29tggkA gyqFN5Kq3s8wDAYDVR0TBAUwAwEB/zANBgkqhkiG9w0BAQUFAAOBgQArUj++GxWm b7hPaB9cBC6DP4uj6D1/xWRovcnaMhniR47Hrm1qVc6Rt6Lvn82KAsmBcmgc58W4 aV5h4tqqSeHh/TqBg3361qLp3DiOk08M66MbSDl1bHWG5te/JaxeiJLbfpuCg1xX j8dK4ilp5neshaKozl/X+1Et71KESGuT0w== -----END CERTIFICATE----- subject=/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com issuer=/C=US/ST=MA/L=city/O=org/OU=unit/CN=host/emailAddress=bjordan555(a)gmail.com --- No client certificate CA names sent --- SSL handshake has read 1453 bytes and written 316 bytes --- New, TLSv1/SSLv3, Cipher is DHE-RSA-AES256-SHA Server public key is 1024 bit Compression: NONE Expansion: NONE SSL-Session: Protocol : TLSv1 Cipher : DHE-RSA-AES256-SHA Session-ID: CABB8909A462A3B6FB65AB556D5ABF6A632691BB81F8F994ED0C8098448FD3DE Session-ID-ctx: Master-Key: BF53FCA25DEA893EFF8C152A99A62A304229C8FA811ACE757233326826543340EF1FC1F433F95B9505E823D5CF289793 Key-Arg : None Start Time: 1278774437 Timeout : 300 (sec) Verify return code: 18 (self signed certificate) --- * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE AUTH=PLAIN] Dovecot ready. The output of dovecot -n is: # 1.2.9: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-23-generic x86_64 Ubuntu 10.04 LTS ssl_cert_file: /etc/ssl/certs/ssl-cert-snakeoil.pem ssl_key_file: /etc/ssl/private/ssl-cert-snakeoil.key login_dir: /var/run/dovecot/login login_executable: /usr/lib/dovecot/imap-login mbox_write_locks: fcntl dotlock auth default: passdb: driver: pam userdb: driver: passwd

1 0

[Dovecot] LDA ignored
by Leander S. 10 Jul '10

10 Jul '10

Hi, my final goal is it to make use Dovecot's sieve modul - but unfortunately I'm not getting the LDA running as it is described in the Dovecot's wiki pages ... ;/ I've more and more getting the feeling that the LDA section in the configuration is completely ignored, cause whatever change I do in there is not being recognized at all - I could just type wildly arround in there - restart Dovecot and it will work. But the dovecot.conf is being used by Dovecot - cause changes to other sections are affecting Dovecot's behaviour ... it's really just the LDA section. I configured and compiled Dovecot with LDA & Managesieve. Otherwhise Dovecot / Postfix setup is running quite well - mail is being scanned by amavis and Spamassassin and delivered as it did before I added / changed the configs to the sieve related options ... It's very weired. I activated "mail_debug = yes" and the following shows up when I start Dovecot: Starting dovecot. ILoading modules from directory: /usr/local/lib/dovecot/imap IModule loaded: /usr/local/lib/dovecot/imap/lib10_quota_plugin.so IModule loaded: /usr/local/lib/dovecot/imap/lib11_imap_quota_plugin.so IEffective uid=65534, gid=65534, home=/tmp Iquota: No quota setting - plugin disabled IEffective uid=65534, gid=65534, home=/tmp It doesn't say a thing about sieve / lda ... ;( The proof that Dovecot is running: Server # ps aux | grep dove root 29355 0.0 0.1 5944 1768 ?? Ss 10:02PM 0:00.05 /usr/local/sbin/dovecot -c /usr/local/etc/dovecot.conf nobody 29356 0.0 0.3 17372 3512 ?? S 10:02PM 0:00.03 dovecot-auth dovecot 29359 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.04 managesieve-login dovecot 29360 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.05 managesieve-login dovecot 29361 0.0 0.3 9816 3256 ?? I 10:02PM 0:00.03 managesieve-login dovecot 29362 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.03 pop3-login dovecot 29363 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.05 pop3-login dovecot 29364 0.0 0.3 9816 3248 ?? I 10:02PM 0:00.03 pop3-login dovecot 29365 0.0 0.3 9812 3260 ?? I 10:02PM 0:00.03 imap-login dovecot 29366 0.0 0.3 9812 3260 ?? I 10:02PM 0:00.03 imap-login dovecot 29367 0.0 0.3 9812 3448 ?? S 10:02PM 0:00.03 imap-login: imap-login [192.168.1.233 TLS] (imap-login) dovecot 29374 0.0 0.3 9812 3260 ?? I 10:03PM 0:00.02 imap-login The last lines of Postfix master.cf: dovecot unix - n n - - pipe flags=DRhu user=dovecot:dovecot argv=/usr/local/libexec/dovecot/deliver -f ${sender} -d ${recipient} # AMaVIs interface smtp-amavis unix - - n - 2 smtp -o smtp_data_done_timeout=1200 -o disable_dns_lookups=yes 127.0.0.1:10025 inet n - n - - smtpd -o content_filter= -o local_recipient_maps= -o relay_recipient_maps= -o smtpd_restriction_classes= -o smtpd_client_restrictions= -o smtpd_helo_restrictions= -o smtpd_sender_restrictions= -o smtpd_recipient_restrictions=permit_mynetworks,reject -o mynetworks=127.0.0.0/8 -o strict_rfc821_envelopes=yes -o smtpd_error_sleep_time=0 -o smtpd_soft_error_limit=1001 -o smtpd_hard_error_limit=1000 and finally some more out of the dovecot.conf: [...] protocols = imap imaps pop pop3s managesieve lda [...] mail_debug = yes [...] protocol lda { mail_plugins = sieve # ... other plugins like quota mail_plugin_dir = /usr/local/lib/dovecot/lda # If there is no user-specific Sieve-script, global Sieve script is # executed if set. sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve postmaster_address = admin(a)server.netocean sendmail_path = /usr/local/sbin/sendmail log_path = /var/log/dovecot-deliver.log info_log_path = /var/log/dovecot-deliver.log } [...] plugin { ## # NOTE: %variable expansion works only with Dovecot v1.0.2+ ## sieve = /var/sieve-scripts/%u.sieve # quota = maildir # The location of the users active script: sieve = ~/.dovecot.sieve # If the user has no personal active script (i.e. if the file # indicated in sieve= does not exist), use this one: #sieve_global_path = /usr/local/etc/dovecot/sieve/default.sieve # The include extension fetches the :personal scripts from this # directory. When ManageSieve is used, this is also where scripts # are uploaded. # sieve_dir = ~/sieve # The include extension fetches the :global scripts from this # directory. Extension hamm wir nicht aktiviert. # sieve_global_dir = /usr/local/etc/dovecot/sieve/global/ # Scripts executed before the user's script. # E.g. handling messages marked as dangerous # sieve_before = /var/lib/dovecot/sieve/discard-virusses.sieve # Scripts executed after the user's script (if keep is still in effect) # E.g. default mail filing rules. # sieve_after = /var/lib/dovecot/sieve/after.d/ } [...] Any suggestions of what I'm doing wrong? Thx

7 14

Re: [Dovecot] Command died with signal 6
by गौरव जोशी 10 Jul '10

10 Jul '10

Hi Timo, Thank you for the response. I've sorted out my problem with the help of it. There was a big error i could find in error logs. =========================================================================== Jul 09 11:22:10 Error: Raw backtrace: /usr/local/libexec/dovecot/deliver [0x80c7c50] -> /usr/local/libexec/dovecot/deliver(default_fatal_handler+0x33) [0x80c7d33] -> /usr/local/libexec/dovecot/deliver [0x80c756c] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8524d] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f900d7] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f8fee2] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_eval_bc+0x205) [0xb7f91135] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(sieve_execute_bytecode+0xf3) [0xb7f96ba3] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so(cmu_sieve_run+0x311) [0xb7f868d1] -> /usr/local/lib/dovecot/lda/lib90_cmusieve_plugin.so [0xb7f844e4] -> /usr/local/libexec/dovecot/deliver(main+0x123d) [0x805bd5d] -> /lib/libc.so.6(__libc_start_main+0xe0) [0x327f70] -> /usr/local/libexec/dovecot/deliver [0x8059821] =========================================================================== It was sieve plugin which was not compatible with dovecot version. I upgraded the sieve plugin from 1.1.6 to 1.1.8 and the error stopped to come. Have a nice time, Gourav Joshi http://www.linuxquestions.in

1 0