- dovecot - dovecot.org

[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

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

10 Jul '10

>> Am I missing something obvious here ? > > Dovecot isn't a SMTP-Server/MTA. > See also: http://wiki.dovecot.org/MailServerOverview > That figures ... it had to be my sendmail config of all things. Geez .. I hate sendmail configuration. OKay .. thanks. -- Dennis

2 1

[Dovecot] I can receive but not send
by Dennis Clarke 09 Jul '10

09 Jul '10

I'm not too sure where to look here. I can access my mail via Dovecot and there is an initial requirement to accept an SSL key ( self signed ) however after I look in my inbox and read a piece of email ( via SeaMonkey eMail client ) I can not send. I simply get told that the server would not accept the smtp connection. I was hoping for a smtps connection but I'll take what I can get. Am I missing something obvious here ? -- Dennis

3 2

[Dovecot] Dovecot 2.0 with LMTP
by Thiago Henrique 09 Jul '10

09 Jul '10

Hello, I'm testing Dovecot 2.0. I plan to use Dovecot 2.0 with thousands of domains per server. My user base is under virtual MySQL. Is there a way to make the LMTP not make query to MySQL for each message delivered ? I'm afraid that the MySQL server does not support the load. Best Regards -- []'s Thiago Henrique Network Administration Digirati Networks K8 Networks

5 5

[Dovecot] Dovecat crash signal 11 core dump
by Ray Kirby 09 Jul '10

09 Jul '10

Vpopmail 5.5.0 Dovecot -n # 2.0.rc1: /usr/local/etc/dovecot/dovecot.conf # OS: Linux 2.6.31.5-127.fc12.i686.PAE i686 Fedora release 12 (Constantine) auth_debug = yes auth_debug_passwords = yes auth_verbose = yes debug_log_path = /var/log/dovecot default_internal_user = vpopmail disable_plaintext_auth = no log_path = /var/log/dovecot mail_debug = yes mail_gid = 508 mail_location = maildir: /home/vpopmail/domains/%d/%n/Maildir mail_uid = 508 passdb { args = cache_key=%u%s:backend=%q driver = vpopmail } service auth { unix_listener auth-userdb { group = vpopmail user = vpopmail } } ssl = no userdb { driver = vpopmail } protocol imap { imap_client_workarounds = tb-extra-mailbox-sep mail_max_userip_connections = 20 } Problem: Jul 08 12:35:08 auth: Debug: Loading modules from directory: /usr/local/lib/dovecot/auth Jul 08 12:35:08 auth: Debug: new auth connection: pid=5514 Jul 08 12:35:08 auth: Debug: client in: AUTH 1 PLAIN service=imap lip=30.30.14.22 rip=192.168.0.100 lport=143 rport=53112 Jul 08 12:35:08 auth: Debug: client out: CONT 1 Jul 08 12:35:08 auth: Debug: client in: CONT 1 AHJraXJieaBteUxprmV1cC5jb20AYWJzcmNr Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 auth: Debug: client out: OK 1 user=user(a)mydomain.com Jul 08 12:35:08 auth: Debug: master in: REQUEST 1 5514 1 4a87d9ed9185eb0794667c5f7adb724f Jul 08 12:35:08 auth: Debug: vpopmail(user(a)mydomain.com,192.168.0.100): lookup user=user domain=mydomain.com Jul 08 12:35:08 master: Error: service(auth): child 5516 killed with signal 11 (core dumped) Jul 08 12:35:08 master: Error: service(auth): command startup failed, throttling Jul 08 12:35:08 imap-login: Info: Internal login failure (auth failed, 1 attempts): user=<user(a)mydomain.com>, method=PLAIN, rip=192.168.0.100, lip=30.30.14.22, mpid=5517 Thanks

3 2

Re: [Dovecot] Sieve user info log (was: problems with sieve under 2.0)
by Stephan Bosch 08 Jul '10

08 Jul '10

Hi Perry, Perry E. Metzger wrote: > By the way, I've noticed that there doesn't seem to be a good way for > the user to get information on what email message gets filed where by > sieve -- syslog information seems to be the sole data source > available. > Right. There is a per-user <main-script>.log file (e.g. .dovecot.sieve.log), but that will only be written when there are any errors. Info logging is indeed only available in the syslogs. > procmail has a facility where you can ask it to log every action it > takes. I looked around for a similar facility for sieve and I didn't > seem to see it. Did I miss something, or is it absent? > I DO see the merit of this. However, configuring this behavior is an interesting issue. If the user log verbosity is configured in the Dovecot userdb, it may in many cases still only be configurable by the administrator. An alternative solution would be to provide the logging configuration directly in the Sieve script; analogous to the way Procmail handles this. This would give users direct control. However, the Sieve specification and its extensions currently define no such facility. In fact, both Sieve and ManageSieve don't provide any means for the user to control what is logged during script execution. This would require some new or custom (vnd.dovecot.) Sieve or ManageSieve extension. However, defining a new extension like that is rarely useful unless clients implement support for it. Another problem is that users need filesystem access or some other custom (HTTP) interface to read the logs. This can be problematic when virtual users are involved. This too could be mended with an extension to the ManageSieve protocol. Alternatively, the Pigeonhole TODO list mentions a solution that writes logs as messages in a special IMAP-accessible folder, but I'm still not sure how practical that is. The above considerations may warrant starting a draft RFC on controlling and accessing Sieve runtime logs. But, I'm deviating from the original issue... what is it that you truly need right now? And for the Dovecot list, any other ideas on the above? Regards, Stephan.

2 1