- dovecot - dovecot.org

[Dovecot] Weird series of errors with dovecot-stable
by Ben Beuchler 21 Sep '05

21 Sep '05

I'm using the dovecot-stable from 7/30, authenticating against an OpenLDAP server. From time to time, dovecot stops responding to new queries. It seems to be a self-correcting problem, lasting about 20 minutes. Here's how it starts: Aug 18 19:38:23 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Aug 18 19:38:36 cliff dovecot: pop3-login: Disconnected: Inactivity [68.46.174.217] Aug 18 19:39:35 cliff dovecot: imap-login: Disconnected: Inactivity [150.253.42.12] Normally I see almost no "Disconnected: Inactivity" messages, but when this problem shows up I get an almost non-stop barrage of them. In fact, over the 20 minutes or so, there's about 150 of those entries, so I filtered them out of the log snippets. I also filtered out any "normal" activity during the time period. Here's what's left: Aug 18 19:40:29 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:40:29 cliff dovecot: child 22347 (auth) killed with signal 6 Aug 18 19:42:04 cliff dovecot: auth(ldap): ldap(vmail,150.253.80.31): unknown user Aug 18 19:42:41 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [24.26.184.219] Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:25 cliff dovecot: auth(ldap): Login process has too old (126s) requests, killing it. Aug 18 19:43:31 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (121s) requests, killing it. Aug 18 19:43:43 cliff dovecot: auth(ldap): Login process has too old (122s) requests, killing it. Aug 18 19:43:49 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:43:49 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:43:49 cliff dovecot: child 22557 (auth) killed with signal 6 Aug 18 19:43:49 cliff dovecot: child 22562 (login) returned error 89 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:31 cliff dovecot: imap-login: Master sent reply with unknown tag 1 Aug 18 19:45:32 cliff dovecot: child 22522 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22561 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22563 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22564 (login) returned error 89 Aug 18 19:45:32 cliff dovecot: child 22566 (login) returned error 89 Aug 18 19:47:54 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:47:54 cliff dovecot: child 22599 (auth) killed with signal 6 Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:48:18 cliff dovecot: imap-login: SSL_read() syscall failed: EOF [69.81.39.120] Aug 18 19:51:32 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:51:32 cliff dovecot: child 22628 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: auth(ldap): file mech.c: line 117 (auth_request_destroy): assertion failed: (request->refcount > 0) Aug 18 19:54:14 cliff dovecot: child 22655 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22683 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22686 (auth) killed with signal 6 Aug 18 19:54:14 cliff dovecot: child 22689 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22690 (login) returned error 89 Aug 18 19:54:14 cliff dovecot: child 22699 (login) returned error 89 Then, magickally, it begins working again. Any thoughts? -Ben

2 1

[Dovecot] ldap: No password in reply
by Rudy Gevaert 21 Sep '05

21 Sep '05

Greetings, I'm trying to set up dovecot with ldap (and postfix) by following the page on the wiki. I configured everything, but something is wrong: dovecot: Sep 21 12:03:59 Info: auth(default): client in: AUTH 1 PLAIN service=IMAP secured lip=157.193.40.36 rip=157.193.44.68 dovecot: Sep 21 12:03:59 Info: auth(default): client out: CONT 1 dovecot: Sep 21 12:03:59 Info: auth(default): client in: CONT 1 b2xlX3dvYmJsZQBvbGVfd29iYmxlAHdvYmJsZQ== dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): base=ou=accounts,dc=zalm,dc=UGent,dc=be scope=subtree filter=(&(objectClass=posixAccount)(uid=ole_wobble)) fields=uid,userPassword dovecot: Sep 21 12:03:59 Info: auth(default): ldap(ole_wobble,157.193.44.68): uid(user)=ole_wobble dovecot: Sep 21 12:03:59 Error: auth(default): ldap(ole_wobble,157.193.44.68): No password in reply dovecot: Sep 21 12:03:59 Info: auth(default): client out: FAIL 1 user=ole_wobble temp dovecot: Sep 21 12:04:01 Info: imap-login: Disconnected: user=<ole_wobble>, method=PLAIN, rip=157.193.44.68, lip=157.193.40.36, TLS This is my database: dn: dc=zalm,dc=UGent,dc=be objectClass: top objectClass: dcObject objectClass: organization o: Universiteit Gent dc: zalm dn: cn=admin,dc=zalm,dc=UGent,dc=be objectClass: simpleSecurityObject objectClass: organizationalRole cn: admin description: LDAP administrator userPassword:: e2NyeXB0fVpsbWpDb21kL3JSbkU= dn: ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: organizationalUnit ou: accounts dn: cn=dovecot,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person cn: dovecot sn: dovecot userPassword:: e0NSWVBUfXp6bGxQa1JoV1Nmb00= dn: uid=ole_wobble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wobble Olson sn: Olson uid: ole_wobble uidNumber: 3000 gidNumber: 8 homeDirectory: /home/postoffice userPassword:: e0NSWVBUfXBrOGN6SnlZVG5IL28= dn: uid=ole_wubble,ou=accounts,dc=zalm,dc=UGent,dc=be objectClass: top objectClass: person objectClass: posixAccount cn: Ole Wubble Olson sn: Olson uid: ole_wubble uidNumber: 3001 gidNumber: 8 homeDirectory: /home/postoffice What could be wrong? Thanks in advance, -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- Rudy Gevaert e-mail: Rudy.Gevaert(a)UGent.be Directie ICT, Afdeling Infrastructuur Groep Systemen tel: +32 9 264 4734 Universiteit Gent fax: +32 9 264 4994 Krijgslaan 281, gebouw S9, 9000 Gent, Belgie www.UGent.be -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

1 1

[Dovecot] ALL TCP/IP connection REST when one mail contains format error
by Yi Xuan 20 Sep '05

20 Sep '05

Hi, I have setup a dovecot pop3 server on IP_A and using mbox format I have 6 users behind a NATed network, the public IP is IP_B. And one mail of one user seems contain format error. He always cannot receive the 5th mail from anywhere. Then when he receive mail in the intranet, all the TCP/IP connection REST between IP_A and IP_B. http/ssh/pop/smtp etc. all NG. After I delete the 5th mail from webmail, then the services work well. 1.It seems unreasonable, Can dovecot improve it and let it donot influence other users and other service? 2.What may cause mbox format error? and how can we avoid it? Best regards,

1 0

[Dovecot] Two strange behaviours with dovecot+postfix+squirrelmail
by Francisco Neira 20 Sep '05

20 Sep '05

Hi all, About a week ago I was forced to migrate my main (production) email server from RH9 to Centos4.1. The installation has dovecot-0.99.11 + postfix-2.1.5 and >600 mbox accessed email accounts. Number 1. Some users accessing thru squirremail (installed in my webserver) can read their INBOX at /var/spool/mail directory but when trying to delete a message they receive the following error message from squirrelmail: ERROR: Could not complete request. Consulta: COPY 1279 "mail/Trash" Reason Given: Internal error occured. Error report written to server log. [2005-09-16 15:08:04] and the error logged is the following: Sep 16 15:09:27 mail imap(username): mkdir_parents(/home/username//mail/.imap/Trash) failed: Permission denied I never stated that .imap/Trash when configuring dovecot and the strangest thing is that my account, as most of others, can delete messages moving from /var/spool/mail/my_name to /home/my_name/mail/Trash Number 2. Randomly, some users connecting from Mozilla Thunderbird via IMAP get an error message telling that there has been an error connecting to INBOX. Watching the maillog I found the following: Sep 16 13:07:43 mail imap(otheruser): File isn't in mbox format: /var/spool/mail/otheruser I accessed the user's inbox file with vi and found that there was a "--604" at the beginning of the file. In other case I found that the file was beginning with a truncated email message. Trying to "walk on the safer side", I changed the mbox_lock setting from "fcntl" to "dotlock" in the /etc/dovecot.conf file. Any suggestions and comments about his will be highly appreciated. Forgive me about my English, it is not my native lanaguage. Regards, -- Francisco Neira B. Administrador de Red Defensoria del Pueblo Lima, Peru, -05:00 UTC

2 1

[Dovecot] NO: Unsupported authentication mechanism
by Steve [Dovecot] 19 Sep '05

19 Sep '05

I'm happily using dovecot as my IMAP server and accessing mails using Thunderbird... but I want to use the Net::IMAP facilities in the Ruby standard library to write some scripts to automate various spam-related tasks & housekeeping. My Ruby script: require "net/imap" imap = Net::IMAP.new('localhost') imap.authenticate('LOGIN','myuser','mypassword') # More stuff using imap... From the documentation LOGIN uses plaintext authentication - which I understand is always acceptable for Dovecot when connecting from localhost. On the 3rd line I get a "NO response" exception raised (indicating that the IMAP server replied "NO") and the error message "Net::IMAP::NoResponseError: Unsupported authentication mechanism" If I change 'LOGIN' to 'CRAM-MD5' (the other value supported by Net::IMAP) then I get a similar (but not identical) error: "Net::IMAP::NoResponseError: Authentication failed: Unsupported authentication mechanism" If I use anything other than either 'LOGIN' or 'CRAM-MD5' I get an error from the Net::IMAP library saying "Unknown auth type" - which is reasonable. N.B. I've tried both where 'myuser' and 'mypassword' are valid - and not... this doesn't affect the error messages. There doesn't seem to be anything of interest in /var/log/messages... Can anyone tell me what is going wrong, and how to resolve this?

4 5

[Dovecot] FreeBSD port
by David King 19 Sep '05

19 Sep '05

FreeBSD users: I notice that the version of Dovecot in the FreeBSD ports system is back at .99. Are there any objections to my submitting an update to the FreeBSD ports for version 1.0a? Is it better to wait for 1.0 to be progressed a little or is it considered to be ready? 1.0a compiles and seems to run fine (on 5.3), so are there any obvious patches that would be needed for the FreeBSD build? -- Don't forget that 19 September is National Talk-Like-A-Pirate Day! http://www.talklikeapirate.com/piratehome.html

2 1

[Dovecot] 1.0alpha2: two asserts/cores
by Jeff A. Earickson 19 Sep '05

19 Sep '05

Hi, Two cores over the weekend, same assert message in syslog: imap(user): file message-body-search.c: line 393 (message_body_search_ctx): assertion failed: (input->v_offset <= part->physical_pos) Setup: Solaris 9, imap usage only, mbox format, dovecot compiled with gcc 4.0.1. gdb sessions of the two core files attached. Let me know if you need further analysis of the cores. Jeff Earickson Colby College

1 0

[Dovecot] vmailmgr user database
by Mij 19 Sep '05

19 Sep '05

hola guys Is a module for vmailmgr userdb being under work by someone? If not, i'd like to help out. Is there a standard API to implement or such? Is there some further documentation to avoid a full inspection of the sources? thank you

2 2

[Dovecot] Very minor feature request
by Steffen Kaiser 19 Sep '05

19 Sep '05

Hello, I'd suggest a way to get to know the "capabilities" of a compiled Dovecot. The background is that I've run the sequence ./configure --with-ldap && make && make install twice, all three commands tell me that all is fine (ldap is listed in the modules), but still dovecot told me that ldap is no Usedb module. A "make clean" before solved the problem -- well, something one should anyway. Besides, the "dovecot --capabilities" should also list all the defaults. Bye, -- Steffen Kaiser

3 4

[Dovecot] support multiple files.
by David Willoughby 19 Sep '05

19 Sep '05

i currently use procmail to sort my different mailing lists into differnet files for sanity puproses is there a way dovecot can find all these files? i have default_mail_env set to mbox:~/Mail/ could i use *:~/Mail/ as every file in /Mail is a mail file? -- David Willoughby email: dlw(a)d1w.org icq: 1852393

1 0