- dovecot - dovecot.org

[Dovecot] Lots of assertion PANICs in error log
by Yates Ian Mr (ITCS) 08 Oct '08

08 Oct '08

I have just upgraded to dovecot 1.1.2 and am seeing lots of the following panic messages filling up the error logs: dovecot: Aug 29 09:34:32 Panic: IMAP(user): file index-sync.c: line 39 (index_mailbox_set_recent_uid): assertion failed: (seq_range_exists(&ibox->recent_flags, uid)) dovecot: Aug 29 09:34:32 Error: IMAP(user): Raw backtrace: imap [0x483888] -> imap [0x484293] -> imap [0x483a46] -> imap(index_mailbox_set_recent_seq+0) [0x453f80] -> imap(index_mailbox_set_recent_seq+0x43) [0x453fc3] -> imap [0x43b3e8] -> imap(mbox_sync+0x380) [0x43bdd0] -> imap [0x434bcd] -> imap(index_transaction_commit+0x3c) [0x454f3c] -> imap(cmd_copy+0x344) [0x4167d4] -> imap(cmd_uid+0x52) [0x41a6c2] -> imap [0x41b723] -> imap [0x41b6e8] -> imap [0x41b9ba] -> imap(client_input+0x63) [0x41bb93] -> imap(io_loop_handler_run+0x109) [0x48b029] -> imap(io_loop_run+0x28) [0x48a3f8] -> imap(main+0x3f2) [0x423272] -> /lib64/tls/libc.so.6(__libc_start_main+0xdb) [0x337911c40b] -> imap [0x41578a] dovecot: Aug 29 09:34:32 Error: child 25658 (imap) killed with signal 6 This is just the latest example from this morning, there are plenty to choose from! My system setup is a RHEL4.6 64bit install. I have tried clearing out the old cache files (dovecot.index, dovecot.cache etc) for all the users but I'm still seeing these crash dumps filling my logs. Help! If you require any further information please let me know. I.

4 10

[Dovecot] Dovecot 1.1.4 imap core
by Anton Zakatov 08 Oct '08

08 Oct '08

Hello! Core was generated by `/usr/libexec/dovecot/imap'. Program terminated with signal 11, Segmentation fault. #0 0x0000003ab2279f8c in strcasecmp () from /lib64/libc.so.6 (gdb) backtrace #0 0x0000003ab2279f8c in strcasecmp () from /lib64/libc.so.6 #1 0x000000000041c30e in command_unregister (name=0x4986aa "LOGOUT") at commands.c:80 #2 0x000000000041c36d in command_unregister_array (cmdarr=0x498790, count=4818602) at commands.c:98 #3 0x000000000041c393 in commands_deinit () at commands.c:143 #4 0x00000000004233f9 in main (argc=<value optimized out>, argv=0x0, envp=0x499d37) at main.c:259 With best regards, Anton Zakatov. E-mail: anton(a)abn.ru

2 2

[Dovecot] dovecot Mstone benchmark
by Mathieu Kretchner 08 Oct '08

08 Oct '08

Hello all, I would like to bench imap with mstone but the only thing I see is imap command read login logout banner but there is no write. So I can't stress as well as with imaptest. Does anyone have a dovecot.wld or a special configuration to test with mstone ? Thanks

1 0

[Dovecot] Virtual domain aliases
by Roderick A. Anderson 07 Oct '08

07 Oct '08

As I said in a previous reply the server is going great. In fact I can even send mail via it. (On the really old server I'm moving from I couldn't get authentication for outbound to work.) I now have a couple of small issues to deal with before moving completely off the old system. Virtual domains aliases? My reading seems to indicate that Postfix only handles aliases in one place/file. Ie., I can't use a /var/mail/vhosts/domain.tld/aliases. This is probably a Postfix question but I'm asking anyway. I am pretty sure there are some Postfix people-of-significance hanging out here. :-) Thanks, Rod --

3 5

[Dovecot] IMAP and SMTP Authentication
by Roderick A. Anderson 07 Oct '08

07 Oct '08

I'm a bit further along but haven't figured out why Authentication is still failing. I've tried a telnet to port 143 and openssl connection to 993. The command I issued, per the debugging page on the wiki, is: a login info(a)aesoft-sbcs.com crap Here is a snapshot from my logs (yup second try and blank lines to make it easier for me to read). Oct 7 08:17:20 mx0 dovecot: auth(default): client in: AUTH 2 PLAIN service=imap secured lip=216.64.180.226 rip=66.193.34.88 lport=993 rport=65026 resp=AGluZm9AYWVzb2Z0LXNiY3MuY29tAGNyYXA= Oct 7 08:17:20 mx0 dovecot: auth(default): passwd-file /var/mail/vhosts/aesoft-sbcs.com/passwd: Read 3 users Oct 7 08:17:20 mx0 dovecot: auth(default): passwd-file(info(a)aesoft-sbcs.com,66.193.34.88): lookup: user=info(a)aesoft-sbcs.com file=/var/mail/vhosts/aesoft-sbcs.com/passwd Oct 7 08:17:20 mx0 dovecot: auth(default): passwd-file(info(a)aesoft-sbcs.com,66.193.34.88): unknown user Oct 7 08:17:22 mx0 dovecot: auth(default): client out: FAIL 2 user=info(a)aesoft-sbcs.com And here is the relevant line from /var/mail/vhosts/aesoft-sbcs.com/passwd info:{PLAIN}crap:5000:5000::/var/mail/vhosts/aesoft-sbcs.com/info Yes there are three users in the file. What is puzzling me is why the source connection's IP is showing up in the /lookup/. I did not create the directory /var/mail/vhosts/aesoft-sbcs.com/info/Maildir Should I? I've attached the out put from postconf -n and dovecot -n since I'm pretty sure I've got some setting wrong. Thanks for any ideas or clues. Rod -- alias_database = hash:/etc/postfix/aliases alias_maps = hash:/etc/postfix/aliases broken_sasl_auth_clients = yes config_directory = /etc/postfix default_destination_concurrency_limit = 10 disable_vrfy_command = yes header_checks = regexp:/etc/postfix/header_checks.regexp inet_interfaces = 216.64.180.226, 127.0.0.1 local_recipient_maps = local_transport = virtual message_size_limit = 20971520 mydestination = localhost mydomain = aesoft-sbcs.com myhostname = mx0.cyber-office.net mynetworks = 127.0.0.0/8 recipient_delimiter = + smtp_bind_address = 216.64.180.226 smtpd_data_restrictions = reject_unauth_pipelining, reject_multi_recipient_bounce smtpd_discard_ehlo_keywords = silent-discard, dsn smtpd_helo_required = yes smtpd_helo_restrictions = permit_mynetworks permit_sasl_authenticated reject_invalid_hostname reject_non_fqdn_hostname smtpd_recipient_restrictions = reject_invalid_helo_hostname, reject_non_fqdn_sender, reject_unknown_sender_domain, reject_unknown_recipient_domain, permit_mynetworks, reject_non_fqdn_recipient, permit_sasl_authenticated, reject_unauth_destination, reject_unlisted_recipient, permit smtpd_sasl_auth_enable = yes smtpd_sasl_local_domain = $mydomain smtpd_sasl_path = private/auth smtpd_sasl_type = dovecot smtpd_tls_cert_file = /etc/pki/tls/certs/mail.pem smtpd_tls_key_file = /etc/pki/tls/private/mail.pem smtpd_tls_security_level = may virtual_gid_maps = static:5000 virtual_mailbox_base = /var/mail/vhosts virtual_mailbox_domains = $mydomain, digitalcda.org virtual_mailbox_maps = hash:/etc/postfix/vmailbox virtual_minimum_uid = 500 virtual_transport = dovecot virtual_uid_maps = static:5000 # 1.1.3: /etc/dovecot.conf log_path: /var/log/dovecot/dovecot.log info_log_path: /var/log/dovecot/dovecot-info.log protocols: imap imaps listen: 127.0.0.1:143 ssl_listen: *:993 login_dir: /var/run/dovecot/login login_executable: /usr/libexec/dovecot/imap-login login_greeting_capability: yes valid_chroot_dirs: /var/mail first_valid_uid: 5000 last_valid_uid: 5000 first_valid_gid: 5000 last_valid_gid: 5000 mail_access_groups: mail mail_location: maildir:~/Maildir mail_debug: yes maildir_copy_preserve_filename: yes mail_plugins: acl imap_client_workarounds: outlook-idle namespace: type: private separator: . prefix: INBOX. inbox: yes list: yes subscriptions: yes auth default: mechanisms: plain login CRAM-MD5 default_realm: aesoft-sbcs.com verbose: yes debug: yes debug_passwords: yes passdb: driver: passwd-file args: /var/mail/vhosts/%d/passwd userdb: driver: passwd-file args: uid=vmail gid=vmail username_format=%n /var/mail/vhosts/%d/passwd socket: type: listen master: path: /var/run/dovecot/auth-master mode: 432 user: vmail socket: type: listen client: path: /var/spool/postfix/private/auth mode: 432 user: postfix group: postfix

3 5

[Dovecot] Dovecot 1.1.x or 1.2, which way to go for Kolab Server?
by Sascha Wilde 07 Oct '08

07 Oct '08

Hi Timo, Hi *, was written the other day we started to use Dovecot 1.2 for our Kolab with Dovecot project, but it turned out that there are quite a bunch of issues with 1.2 (which is ok, as it hasn't even been announced as beta till now). We have a customer who should get a first test installation of Kolab with Dovecot in the first week of September and for that we need the features mentioned in my other mails, especially the enhanced name spaces for shared folders. (%%h, listing of shared folders, an checkpassword like backend for userdb). So the big decision to make is: - stay with 1.1.x and port the needed shared namespace stuff back from 1.2 or - build on 1.2 and resolve all issues caused by it Timo, do you have any opinion/advice on this? How far from being production ready is 1.2 in your view? How hard would it be to get the shared folder/namespace stuff in 1.1.x? (or for that matter: who much harder than to do it in 1.2?) We are currently evaluating these questions, but I would highly appreciate your comments on this. cheers sascha -- Sascha Wilde OpenPGP key: 4BB86568 http://www.intevation.de/~wilde/ http://www.intevation.de/ Intevation GmbH, Neuer Graben 17, 49074 Osnabrück; AG Osnabrück, HR B 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner

3 5

[Dovecot] Maildir++ problem
by Claudio Prono 07 Oct '08

07 Oct '08

Hi to all, I am semi-new to the dovecot system, but i like it very much for the versatility of all the system. I have a problem: i am migrating my servers from postfix with vda patch + courier imap to dovecot. All works fine, except for one thing: i use Maildir++ format, but i don't know how to make the file maildirsize into the home of the users. This file is needed by me becouse i have a script, running every day, checking the quota status and sending me a mail of the space occuped by every mailbox on my mailserver. The format of the maildirsize file is like this: 15360000S 12393886 1 How dovecot can generate that file? I have searched into all the documentation, but i don't find anything... What parameters must be specified into the config file to generate the maildirsize file? Thank u in advance, and long life to dovecot ;) Claudio. -- ------------ Claudio Prono Systems Development @ Atpss.net Srl, Divisione Implementazione Sistemi Via San Bernardino, 17 - 10137 Torino (TO) - IT Tel +39-011.32.72.100 Fax +39-011.32.46.497 PGP Fingerprint: 75C2 4049 E23D 2FBF A65F 40DB EA5C 11AC C2B0 3647 Disclaimer: http://atpss.net/disclaimer ------------

2 3

[Dovecot] Manual verses Wiki
by Roderick A. Anderson 07 Oct '08

07 Oct '08

I know I'm looking at the answer but probably not seeing it on the Wiki? Is there a "manual" for Dovecot? Or ... where do I find all the options for the userdb and passdb options? While trying to get my head wrapped around this I noticed I might have been mixing args between the two. One example has userdb first then the next one passdb. Rod --

2 2

[Dovecot] Improvements to "Authentication failed" error
by Timo Sirainen 07 Oct '08

07 Oct '08

Probably one of the most commonly asked question is "Why does Dovecot just say authentication failed"? It would be nice to be able to get rid of these questions by having Dovecot itself point out the http://wiki.dovecot.org/WhyDoesItNotWork link. But how to do this? There are two groups of people here: 1) People who look at logs after seeing the "Authentication failed" from a client/telnet session. 2) People who don't even think about looking at logs. I'm thinking that the group 1 could be handled by having Dovecot log the link once as informational message if the first authentication attempt fails and it's from localhost. This shouldn't cause problems I think. Group 2 is more difficult though, and I fear they're also the ones asking this question more often than group 1.. I think the only solution would be to change the IMAP/POP3 error message for them. So instead of: NO Authentication failed. they'd get something more usable. So: 2a) NO Authentication failed. See http://wiki.dovecot.org/WhyDoesItNotWork. 2b) NO Authentication failed. Refer to server log for more information. 2c) NO Authentication failed. Enable auth_debug in server for more information. But there are some problems I think: - If it's done only for connections from localhost, the error messages would be different from localhost vs. elsewhere, which might confuse some log parser scripts. - Some people are running stunnel or some other proxies, causing all connections to appear from localhost. Also webmails often run in localhost. So it can't be assumed that only admins will see the error message. I think this rules out 2a) message. I'm certain I don't want end users emailing me and asking why they can't connect to their server because they saw that link. - Sending 2b) for all connections could be a solution, but it might be confusing for end users. They of course can't refer to server log.. Also unless the wiki link is logged for every failure or auth_debug is enabled, there's nothing useful in the server log. - Sending 2c) for all connections when auth_debug isn't enabled (and plain "Authentication failed" when it is) might also work, but it's again confusing to end users since they can't do that. Any thoughts?

5 7

[Dovecot] Unable telnet port 143
by satimis 07 Oct '08

07 Oct '08

Hi folks, Postfix Dovecot-imap 1.0 port 143 not working. $ telnet localhost 143[code] Trying 127.0.0.1... Connected to localhost.localdomain. Escape character is '^]'. * OK Dovecot ready. 1 login satimis mypassword 1 NO Authentication failed. * BYE Disconnected for inactivity. Connection closed by foreign host. [/code] # tail /var/log/mail.log[code] Password: Oct 6 01:05:02 xen5 dovecot: imap-login: Disconnected: user=<satimis>, method=P LAIN, rip=127.0.0.1, lip=127.0.0.1, secured Oct 6 01:17:09 xen5 postfix/smtpd[1820]: connect from 201-43-209-60.dsl.telesp. net.br[201.43.209.60] Oct 6 01:17:11 xen5 postfix/smtpd[1820]: NOQUEUE: reject: RCPT from 201-43-209- 60.dsl.telesp.net.br[201.43.209.60]: 554 5.7.1 Service unavailable; Client host [201.43.209.60] blocked using bl.spamcop.net; Blocked - see http://www.spamcop.n et/bl.shtml?201.43.209.60; from=<criticastry(a)frontier-cnc.com> to=<mail@satimis. com> proto=SMTP helo=<gvaeprbc> Oct 6 01:17:11 xen5 postfix/smtpd[1820]: lost connection after RCPT from 201-43 -209-60.dsl.telesp.net.br[201.43.209.60] Oct 6 01:17:11 xen5 postfix/smtpd[1820]: disconnect from 201-43-209-60.dsl.tele sp.net.br[201.43.209.60] Oct 6 01:20:31 xen5 postfix/anvil[1823]: statistics: max connection rate 1/60s for (smtp:201.43.209.60) at Oct 6 01:17:09 Oct 6 01:20:31 xen5 postfix/anvil[1823]: statistics: max connection count 1 for (smtp:201.43.209.60) at Oct 6 01:17:09 Oct 6 01:20:31 xen5 postfix/anvil[1823]: statistics: max cache size 1 at Oct 6 01:17:09 Oct 6 01:24:32 xen5 dovecot: auth-worker(default): mysql: Connected to 127.0.0. 1 (mailserver) Oct 6 01:26:06 xen5 dovecot: imap-login: Disconnected: Inactivity: user=<satimi s>, method=PLAIN, rip=127.0.0.1, lip=127.0.0.1, secured [/code] I suppose it uses "MySQL authorization". But I can't find /etc/dovecot/dovecot-mysql.conf # cat /etc/dovecot/dovecot.conf[code] protocols = imap imaps disable_plaintext_auth = no log_timestamp = "%Y-%m-%d %H:%M:%S " ssl_cert_file = /etc/ssl/certs/xen5.pem ssl_key_file = /etc/ssl/private/xen5.pem mail_privileged_group = mail ## ## IMAP specific settings ## protocol imap { } ## ## POP3 specific settings ## protocol pop3 { pop3_uidl_format = %08Xu%08Xv } ## ## LDA specific settings ## protocol lda { log_path = /var/vmail/dovecot-deliver.log auth_socket_path = /var/run/dovecot/auth-master postmaster_address = postmaster(a)satimis.com # Enabling Sieve plugin for server-side mail filtering mail_plugins = cmusieve global_script_path = /var/vmail/globalsieverc } ## ## Authentication processes ## auth default { # Space separated list of wanted authentication mechanisms: # plain login digest-md5 cram-md5 ntlm rpa apop anonymous gssapi mechanisms = plain login passdb sql { # Path for SQL configuration file, see /etc/dovecot/dovecot-sql.conf for example args = /etc/dovecot/dovecot-sql.conf } userdb passwd { } user = root socket listen { master { path = /var/run/dovecot/auth-master mode = 0600 # Default user/group is the one who started dovecot-auth (root) user = vmail #group = } client { # The client socket is generally safe to export to everyone. Typical use # is to export it to your SMTP server so it can do SMTP AUTH lookups # using it. path = /var/spool/postfix/private/auth mode = 0660 user = postfix group = postfix } } } dict { #quota = mysql:/etc/dovecot-dict-quota.conf } ## ## Plugin settings ## plugin { } [/code] Please help. Where can I find samples of dovecot.conf and dovecot-mysql.conf for my use. TIA B.R. satimis -- View this message in context: http://www.nabble.com/Unable-telnet-port-143-tp19831992p19831992.html Sent from the Dovecot mailing list archive at Nabble.com.

2 1