- dovecot - dovecot.org

[Dovecot] Question about Client Certificates
by William Gallafent 21 Oct '10

21 Oct '10

Hi, I have a simple dovecot installation, version 1.2.12 of ubuntu 10.10. I also have a straightforward newbie question! I've hunted in the wiki and on the wider web, but not yet found a solution. Current status: I have successfully configured imap with tls, accessed on port 993, and for security require a valid client certificate to be presented, using ssl_require_client_cert and ssl_verify_client_cert. This is all working fine! Now I want to add a SquirrelMail service to the same server. This will connect using IMAP over port 143, without TLS. My question is: how do I achieve this! At the moment, I simply get the following in the logs: Aborted login (cert required, client didn't start TLS): method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured If I comment out the "ssl_require_client_cert = yes" in the auth default section, SquirrelMail then works fine … but I can also connect remotely without presenting a valid certificate, which is no good! At the moment I have a single auth section in dovecot.conf, the "auth default { ... }" section. I wondered if I need a second section, which does not have the ssl requirement inside it. Is that right? If so, how do I link one auth section to the imaps service, and the other to the imap service (listening only on localhost)? In other words, I want "ssl_require_client_cert = yes" for remote connections (on port 993), but "ssl_require_client_cert = no" for local connections using non-tls imap on port 143. Is this possible? Hope that late-night explanation makes sense, and hope somebody can point me in the right direction, thanks in advance! -- Bill Gallafent.

3 3

[Dovecot] bug with null pointer
by Tobias Daucher 21 Oct '10

21 Oct '10

Hi, we found a serious bug while testing our migration scripts. in Solaris (or other system 5) the user variable is not always set. Dsync is not very happy about that and crashes with an segmentation fault. After hours of debugging and TWOE simple lines # USER=$LOGNAME # export USER the problem was solved! The null pointer was found - so i will go home now an drink a bottle of "Erdinger"... hope this hint helps for development - and we hope that we don't find more of these bugs :) bye Tobi -- Dr. Nagler & Company GmbH Hauptstraße 9 92253 Schnaittenbach Tel : 09622-7197-38 Fax : 09622-7197-50 Web : http://www.nagler-company.com E-Mail : tobias.daucher(a)nagler-company.com Hauptsitz: Schnaittenbach Handelregister: Amberg HRB 4653 Gerichtsstand: Amberg Steuernummer: 201/118/51825 USt.-ID-Nummer: DE 273143997 Geschäftsführer: Dr. Martin Nagler, Dr. Dr. Karl-Kuno Kunze

2 1

[Dovecot] allow_nets and local sockets
by Oliver Eales 21 Oct '10

21 Oct '10

Hello, i am running dovevot 2.0.5 using ldap authentication with the allow_nets paramter to limit access to some local networks. The problem is, when i want to use the local lmtp socket from postfix *virtual_transport = lmtp:unix:private/dovecot-lmtp * i get the follwing error: *Oct 21 15:48:03 auth: Info: passdb(username): allow_nets check failed: Remote IP not known *When using the TCP socket with postfix *virtual_transport = lmtp:localhost:30025 *it is working. (i have 127.0.0.0/8 in the allow_nets list) Is there a way, other than using two different config sets to get this working together ? Something like disabling the address lookup on local passdb sockets ? Regards, Oliver

2 1

Re: [Dovecot] anti-spam+anti-malware suggestions
by Paweł Madej 21 Oct '10

21 Oct '10

On Thu, 21 Oct 2010 11:37:40 -0200, Fabricio Archanjo <farchanjo(a)gmail.com> wrote: > Does someone run dspam or just me?? > I like very much this antispam solution. > I use dspam + sqlgrey + policyd-weight to prevent spam. 60% rejects are invalid recipient drop 30% nonreturning from sqlgrey 10% goes to dspam with autolearning. -- Pozdrawiam Paweł Madej

1 0

Re: [Dovecot] Error or bug?
by Daniel Luttermann 21 Oct '10

21 Oct '10

Robby Gunawan wrote on 10/21/2010: > how do I install / update to my system? Normally you should patch the file(s) in the source package. You can compile Dovecot from the official sources (apply the patch before), download/install Dovecot from Mercurial (hg.dovecot.org) or open a bugreport for the package maintainer so that the bug can be fixed for your distribution. -- Daniel

1 0

[Dovecot] Error or bug?
by Robby Gunawan 21 Oct '10

21 Oct '10

Dear all, Please help me, I just change from vm-pop3d to dovecot, installed from rpm that provided by dovecot.org, I got this error for random email user Command died with signal 11: "/usr/libexec/dovecot/deliver" Below is my dovecot.conf # 2.0.5: /etc/dovecot/dovecot.conf # OS: Linux 2.6.9-34.ELsmp i686 Red Hat Enterprise Linux release 4 ext3 debug_log_path = /var/log/dovecot.log disable_plaintext_auth = no first_valid_uid = 1 info_log_path = /var/log/dovecot-info.log listen = * mail_location = maildir:/var/spool/mail/%u mbox_write_locks = fcntl passdb { driver = pam } protocols = pop3 service pop3-login { service_count = 0 vsz_limit = 96 M } service pop3 { process_limit = 512 } ssl = no ssl_cert = </etc/pki/dovecot/certs/dovecot.pem ssl_key = </etc/pki/dovecot/private/dovecot.pem userdb { driver = passwd } this is my postconf -n 2bounce_notice_recipient = netadmin(a)mydomain.com alias_maps = hash:/etc/aliases bounce_queue_lifetime = 12h bounce_size_limit = 10485760 broken_sasl_auth_clients = yes command_directory = /usr/sbin command_time_limit = 3h config_directory = /etc/postfix daemon_directory = /usr/libexec/postfix debug_peer_level = 2 default_destination_concurrency_limit = 50 default_privs = mail delay_warning_time = 1 header_checks = regexp:/etc/postfix/header_checks home_mailbox = Maildir/ html_directory = no inet_interfaces = all initial_destination_concurrency = 100 mail_owner = postfix mail_spool_directory = /var/spool/mail mailbox_command = /usr/libexec/dovecot/deliver mailbox_delivery_lock = dotlock mailbox_size_limit = 1048576000 mailq_path = /usr/bin/mailq manpage_directory = /usr/share/man maximal_backoff_time = 30s maximal_queue_lifetime = 12h message_size_limit = 8388608 minimal_backoff_time = 10s mydestination = localhost.localdomain, localhost, $mydomain, $myhostname, mail.asiatex.co.id, asiatex.co.id mydomain = mydomain.com myhostname = mail.mydomain.com mynetworks = 127.0.0.0/8, xxx.xxx.xxx.xxx/32 mynetworks_style = subnet myorigin = $mydomain newaliases_path = /usr/bin/newaliases notify_classes = 2bounce queue_directory = /var/spool/postfix queue_run_delay = 1m readme_directory = no sample_directory = /etc/postfix sendmail_path = /usr/sbin/sendmail setgid_group = postdrop smtp_sasl_auth_enable = yes smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd smtp_sasl_security_options = noanonymous permit_mynetworks, check_helo_access hash:/etc/postfix/helo_access,permit check_client_access hash:/etc/postfix/access, permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, check_policy_service inet:127.0.0.1:11026, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining smtp_sender_dependent_authentication = yes smtpd_banner = mydomain eMail Server. smtpd_recipient_restrictions = check_sender_access hash:/etc/postfix/restrictedsenders, permit_sasl_authenticated, permit_mynetworks, reject_unauth_destination, check_policy_service inet:127.0.0.1:11026, reject_unknown_sender_domain, reject_unknown_recipient_domain, reject_unauth_pipelining, reject_rbl_client cbl.abuseat.org, reject_rbl_client zen.spamhaus.org smtpd_reject_unlisted_sender = yes smtpd_restriction_classes = localonlyclass smtpd_sasl_auth_enable = yes smtpd_sasl_authenticated_header = yes smtpd_sasl_local_domain = $myhostname smtpd_sasl_security_options = noanonymous smtpd_sender_restrictions = hash:/etc/postfix/sender_access unknown_local_recipient_reject_code = 550 -- Thanks, Robby Gunawan S

2 1

[Dovecot] Director and CRAM-MD5
by Martin Spuetz 20 Oct '10

20 Oct '10

Hello, i have a setup with two director servers pointing to two backends. I don't care that much for load balancing, my main goal is high availability. CRAM-MD5 auth is working fine if I connect directly to the backends, but the director only supports AUTH=PLAIN because of the static passdb. director config: > passdb { > driver = static > args = nopassword=y proxy=y > } > > director_servers = director1 director2 > director_mail_servers = backend1 backend2 backend config: > passdb { > driver = vpopmail > args = > } > > userdb { > driver = vpopmail > } It seems that the director is only working, if I use the static passdb?! How can I use the director with other passdb drivers than the static one? Greetings, Martin

2 6

[Dovecot] 2.0.3 crashes
by Mike Abbott 20 Oct '10

20 Oct '10

One system running dovecot-2.0.3 assert-crashed in a few ways recently. I know 2.0.3 < 2.0.5 but these have not been reported (or, presumably, fixed) since 2.0.3. Here are some logs: Fri Oct 15 21:50:00 server3 dovecot[349]: lda(pid 349 user user10): Error: Transaction log file /Volumes/mail/user10/dovecot.index.log: marked corrupted Fri Oct 15 21:50:00 server3 dovecot[348]: lda(pid 348 user user10): Error: Transaction log file /Volumes/mail/user10/dovecot.index.log: marked corrupted Fri Oct 15 21:50:00 server3 dovecot[348]: lda(pid 348 user user10): Error: Corrupted index file /Volumes/mail/user10/dovecot.index: messages_count too large (329591 > 329505) Fri Oct 15 21:50:00 server3 dovecot[348]: lda(pid 348 user user10): Warning: fscking index file /Volumes/mail/user10/dovecot.index Fri Oct 15 21:50:00 server3 dovecot[348]: lda(pid 348 user user10): Error: Fixed index file /Volumes/mail/user10/dovecot.index: log_file_seq 840 -> 841 Fri Oct 15 21:50:00 server3 dovecot[349]: lda(pid 349 user user10): Error: Corrupted index file /Volumes/mail/user10/dovecot.index: messages_count too large (329591 > 329505) Fri Oct 15 21:50:00 server3 dovecot[349]: lda(pid 349 user user10): Warning: fscking index file /Volumes/mail/user10/dovecot.index Fri Oct 15 21:50:00 server3 dovecot[349]: lda(pid 349 user user10): Error: Fixed index file /Volumes/mail/user10/dovecot.index: log_file_seq 840 -> 841 Fri Oct 15 21:50:06 server3 dovecot[348]: lda(pid 348 user user10): Error: Fixed index file /Volumes/mail/user10/dovecot.index: messages_count 329591 -> 329505 Fri Oct 15 21:50:06 server3 dovecot[349]: lda(pid 349 user user10): Error: Fixed index file /Volumes/mail/user10/dovecot.index: messages_count 329591 -> 329505 Fri Oct 15 21:50:07 server3 dovecot[349]: lda(pid 349 user user10): Error: Index /Volumes/mail/user10/dovecot.index: Lost log for seq=1 offset=0 Fri Oct 15 21:50:07 server3 dovecot[349]: lda(pid 349 user user10): Warning: fscking index file /Volumes/mail/user10/dovecot.index Fri Oct 15 21:50:07 server3 dovecot[349]: lda(pid 349 user user10): Error: Fixed index file /Volumes/mail/user10/dovecot.index: log_file_seq 1 -> 841 Fri Oct 15 21:50:07 server3 dovecot[349]: lda(pid 349 user user10): Panic: file mail-index-write.c: line 59 (mail_index_recreate): assertion failed: (map->hdr.indexid == index->indexid) Fri Oct 15 21:50:07 server3 dovecot[349]: lda(pid 349 user user10): Error: Raw backtrace: 2 libdovecot.0.dylib 0x00000001005d3887 i_set_failure_file + 241 -> 3 libdovecot.0.dylib 0x00000001005d2d50 i_syslog_error_handler + 0 -> 4 libdovecot.0.dylib 0x00000001005d3040 i_debug + 0 -> 5 libdovecot-storage.0.dylib 0x0000000100515f9d mail_index_set_fsync_mode + 0 -> 6 libdovecot-storage.0.dylib 0x0000000100503146 mail_index_fsck + 3214 -> 7 libdovecot-storage.0.dylib 0x000000010050c355 mail_index_sync_map + 370 -> 8 libdovecot-storage.0.dylib 0x000000010050481c mail_index_map + 2629 -> 9 libdovecot-storage.0.dylib 0x000000010051676d mail_index_refresh + 90 -> 10 libdovecot-storage.0.dylib 0x0000000100516ab7 mail_index_open + 296 -> 11 libdovecot-storage.0.dylib 0x0000000100532d32 index_storage_mailbox_open + 208 -> 12 libdovecot-storage.0.dylib 0x000000010053cc0f maildir_get_uidvalidity_next + 2042 -> 13 libdovecot-storage.0.dylib 0x000000010053cc5e maildir_get_uidvalidity_next + 2121 -> 14 lib20_zlib_plugin.so 0x00000001006b9932 zlib_plugin_deinit + 2731 -> 15 libdovecot-storage.0.dylib 0x00000001004f578c mailbox_create_fd + 596 -> 16 libdovecot-lda.0.dylib 0x00000001005a809a mail_deliver_save_open + 263 -> 17 libdovecot-lda.0.dylib 0x00000001005a846f mail_deliver_save + 146 -> 18 libdovecot-lda.0.dylib 0x00000001005a877a mail_deliver + 131 -> 19 dovecot-lda 0x00000001004e9341 main + 2577 -> 20 dovecot-lda 0x00000001004e8928 start + 52 Fri Oct 15 21:50:10 server3 dovecot[348]: lda(pid 348 user user10): Error: rename(/Volumes/mail/user10/dovecot.index.tmp, /Volumes/mail/user10/dovecot.index) failed: No such file or directory Fri Oct 15 21:50:10 server3 dovecot[348]: lda(pid 348 user user10): Error: unlink(/Volumes/mail/user10/dovecot.index.tmp) failed: No such file or directory Fri Oct 15 21:50:10 server3 dovecot[348]: lda(pid 348 user user10): Error: Index (in-memory index): Lost log for seq=1 offset=0 Fri Oct 15 21:50:10 server3 dovecot[348]: lda(pid 348 user user10): Warning: fscking index file (in-memory index) Fri Oct 15 21:50:10 server3 dovecot[348]: lda(pid 348 user user10): Error: Fixed index file (in-memory index): log_file_seq 1 -> 842 Fri Oct 15 21:50:18 server3 dovecot[348]: lda(pid 348 user user10): Panic: file mail-transaction-log.c: line 133 (mail_transaction_log_close): assertion failed: (log->files == NULL) Fri Oct 15 21:50:18 server3 dovecot[348]: lda(pid 348 user user10): Error: Raw backtrace: 2 libdovecot.0.dylib 0x000000010aff7887 i_set_failure_file + 241 -> 3 libdovecot.0.dylib 0x000000010aff6d50 i_syslog_error_handler + 0 -> 4 libdovecot.0.dylib 0x000000010aff7040 i_debug + 0 -> 5 libdovecot-storage.0.dylib 0x000000010af40c32 mail_transaction_log_move_to_memory + 0 -> 6 libdovecot-storage.0.dylib 0x000000010af3b92a mail_index_close + 61 -> 7 libdovecot-storage.0.dylib 0x000000010af2720d mail_index_alloc_cache_index_opened + 168 -> 8 libdovecot-storage.0.dylib 0x000000010af2729a mail_index_alloc_cache_index_opened + 309 -> 9 libdovecot-storage.0.dylib 0x000000010af14714 mail_namespace_get_storage_name + 161 -> 10 libdovecot-storage.0.dylib 0x000000010af1487e mail_namespaces_deinit + 29 -> 11 libdovecot-storage.0.dylib 0x000000010af1bef6 mail_user_alloc + 358 -> 12 lib10_quota_plugin.so 0x000000010b07c104 quota_mail_user_created + 287 -> 13 dovecot-lda 0x000000010af0e446 main + 2838 -> 14 dovecot-lda 0x000000010af0d928 start + 52 An imap process also crashed just before the above: Date/Time: 2010-10-15 21:49:43.955 -0700 Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000010 0 libdovecot-storage.0.dylib 0x000000010fc30540 mail_index_move_to_memory + 174 1 libdovecot-storage.0.dylib 0x000000010fc30b79 mail_index_open + 490 2 libdovecot-storage.0.dylib 0x000000010fc4cd32 index_storage_mailbox_open + 208 3 libdovecot-storage.0.dylib 0x000000010fc56c0f maildir_get_uidvalidity_next + 2042 4 libdovecot-storage.0.dylib 0x000000010fc56c5e maildir_get_uidvalidity_next + 2121 5 lib20_zlib_plugin.so 0x000000010fd83932 zlib_plugin_deinit + 2731 6 libdovecot-storage.0.dylib 0x000000010fc0f78c mailbox_create_fd + 596 7 imap 0x000000010fbe7891 cmd_select_full + 1818 8 imap 0x000000010fbe454a cmd_examine + 14 9 imap 0x000000010fbe9d88 client_command_input + 36 10 imap 0x000000010fbe9f04 client_command_input + 416 11 imap 0x000000010fbe9fdf client_handle_input + 134 12 imap 0x000000010fbe94e0 client_input + 118 13 libdovecot.0.dylib 0x000000010fce47e9 io_loop_handler_run + 234 14 libdovecot.0.dylib 0x000000010fce52bb io_loop_run + 56 15 libdovecot.0.dylib 0x000000010fcdaf98 master_service_run + 27 16 imap 0x000000010fbf1d6d main + 689 17 imap 0x000000010fbe17d8 start + 52 The backtraces may be obfuscated by compilation optimizations.

1 0

[Dovecot] Error: sql dict iterate question
by Robert Schetterer 20 Oct '10

20 Oct '10

Hi Timo, perhaps silly question... should i care of this ? dovecot: dict: Error: sql dict iterate: Invalid/unmapped path: shared/shared-boxes/anyone/ dovecot 2.0.5 -- Best Regards MfG Robert Schetterer Germany/Munich/Bavaria

2 2

[Dovecot] Campo de quota en LDAP
by Antonio Perez-Aranda 20 Oct '10

20 Oct '10

En un principio, en los ldif que tenemos de los usuarios de prueba, tenemos el campo mailQuota. Sin embargo, si nos vamos a los schemas de qmail medianamente, con algo más de 3 años, se cambió mailQuota por mailQuotaSize y mailQuoatCount. Esto se debe entre otras cosas a que en la cabecera del fichero maildirsize del buzón, tenemos esta información, es decir, máximo tamaño ocupado y máximo número de mensajes. En el ldap de producción se sigue usando mailQuota? En el courier que tenemos montados aquí, misma versión y misma configuración que la existente en desbuz03, cuando no existe la quota del maildir directamente no da información sobre quota. ¿Estamos usando la quota de ldap? O al entregar un correo mediante Exim, se actualiza el fichero maildirsize con los valores de mailQuota. En este caso, podemos seguir con este comportamiento, o podemos utilizar la información que viene de ldap si no hay nada en el maildirsize.

1 1