- dovecot - dovecot.org

Re: [Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

>Only two things I can think of: >1. Dovecot was not configured for imap with ssl (check that >ssl_disable is not set to yes). Also check the protocols statement >that it supports imaps. > >2. Check that you do not have access lists blocking off 993 to your >squirrelmail. This is often encountered if using tcp wrappers and >you're running dovecot through (x)inetd. > >Regards, Neil The ssl_disable is set to no and the protocols statement contains all the four protocols: imap pop3 imaps pop3s. But i couldn't make out the 2nd point, you suggested.Can you, please, describe it a little more ? Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

3 2

[Dovecot] error while connecting from squirrelmail
by Srinivas 01 Jul '05

01 Jul '05

Hi all, I am new to dovecot and squirrelmail and I am trying to configure squirrelmail with dovecot as its imap server. When i disable "Secure Imap (TLS)" option (2-A-7) from squirrelmail configure menu, it's working fine. But when i try to enable tls support, squirrelmail is giving the following error: Warning: fsockopen(): unable to connect to 192.xx.xx.xx:993 in /usr/share/squirrelmail/functions/imap_general.php on line 445 ERROR Error connecting to IMAP server: tls://192.xx.xx.xx. 111 : Connection refused Go to the login page The port numbers of the imap server are as follows: imap_listen 143 pop3_listen 110 imaps_listen 993 pop3s_listen 995 Squirrelmail and the dovecot imap server are running on different machines, so it is essential to enable tls support. All the machines are running Debian Sarge. Can anyone suggest a solution for the above problem ? Thank you. Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] root login is refused, but....
by Roberto Tagliaferri 01 Jul '05

01 Jul '05

If i try to connect as root (dovecto 1.0) with wrong password doveco exit with an auth error robyt:~# telnet dns pop3 Trying x.x.x.x Connected to dns. Escape character is '^]'. +OK Dovecot ready. user root +OK pass [wrong] -ERR Authentication failed. but if the password is correct dovecot exit but with another error: user root +OK pass [correct] -ERR [IN-USE] Internal login failure. Refer to server log for more information. Connection closed by foreign host. robyt:~# Why dovecot don't close the connection at user root? With this system i may know the root password.. -- Roberto Tagliaferri Responsabile Progettazione & Produzione TosNet s.r.l. - Internet Service Provider r.tagliaferri(a)tosnet.it www.tosnet.it

3 3

[Dovecot] Dovecot doesn't use vchkpw properly :(
by Casey Allen Shobe 01 Jul '05

01 Jul '05

Hey all, It seems that dovecot does NOT call vchkpw properly when using vpopmail-style authentication, I can only guess that it reads the vpasswd{,.cdb} files directly. This is indicated by the syslog log for the mail facitily which reads: Jun 30 16:51:30 [vpopmail] vchkpw-smtp: (PLAIN) login success blah@blah.com:24.17.153.137 Jun 30 17:16:25 [pop3-login] Login: blah(a)blah.com [24.17.153.137] Jun 30 17:47:42 [imap-login] Login: blah(a)blah.com [216.57.201.58] pop3-login and imap-login are dovecot processes - vchkpw is never called or there would also be log entries for it. I've verified this with the vpopmail list, who agree that the problem lies within dovecot. This might not be quite so annoying, but we are using vpopmail compiled with the --enable-learn-passwords option, which will populate the password files with cleartext versions of the passwords where they are missing. Because of dovecot not calling vchkpw, this doesn't work for POP3/IMAP logins, only SMTP (using qmail-smtpd). People don't send mail from every account they poll, and we need to get all of the passwords in cleartext form so that we can complete migration to a PostgreSQL password database which multiple applications will use to authenticate. Are there plans to make dovecot use vchkpw in the normal checkpassword manner? If not, I'd like to request it. We will probably switch back to qmail-pop3d and bincimap for the time being to finish collecting passwords if we can't get a quick fix...I think we can do that without much impact. Cheers, -- Casey Allen Shobe | http://casey.shobe.info cshobe(a)seattleserver.com | cell 425-443-4653 AIM & Yahoo: SomeLinuxGuy | ICQ: 1494523 SeattleServer.com, Inc. | http://www.seattleserver.com

2 3

RE: [Dovecot] LF not found where expected
by Miles Mawyer 01 Jul '05

01 Jul '05

Thanks for the reply. I think I'd found the issue. It seems to be the empty line that is ending up at the top of mail file. I removed that blank line out of one of the mail box files, and it started working without an issue. I'm not sure what is causing the empty line in the mbox file however. Most of my clients use pop3 to download their messages through dovecot. Could this be happening if the client only downloads part of their messages? Pretty easy for me to straighten out, but I didn't know if this was a bug that needed to be addressed. ... Miles Mawyer -=- Webmaster . Centralva.net ... ... mmawyer(a)rosecomputers.com ... ... 434.385.5053 ... -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: Tuesday, June 28, 2005 7:52 AM To: Miles Mawyer Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] LF not found where expected On 27.6.2005, at 18:45, Miles Mawyer wrote: > pop3(mjmurray): Jun 27 11:16:38 Error: Error indexing mbox file > /var/mail/mjmurray: LF not found where expected These usually happen because the mbox file has two adjacent From-line, ie: From foo ... From bar ... Message-headers: ... That shouldn't happen normally though. Sounds like something is wrong with how your mails are written. Are all the software that are writing to the mbox using same lock methods? Anyway, 1.0-test/stable versions of Dovecot can handle the adjacent From-lines too without failing.

2 1

[Dovecot] How to lock a user out?
by Kai Wang 29 Jun '05

29 Jun '05

Hi, We are considering to migrate to Dovecot. We can running uw-imap and have a local path which allow us to lock a user by creating a .lockdir directory in the user home directory and put our warning message to .lockdir/mbox. The locked user can still receive messages in ~/mbox. But can not access any messages except ~/.lockdir/mbox. I wonder if Dovecot has any similar feature which we can use to lock a user out without affecting the mail delivery? Kai Wang University of Calgary

2 4

[Dovecot] 1.0-test74
by Timo Sirainen 29 Jun '05

29 Jun '05

http://dovecot.org/test/ Not much has happened, but the APPEND bugfix is important since it was broken in test73 (at least). Summer makes me tired and lazy. :( I've been trying to get keywords implemented in maildir. Hopefully works soon.. After that I'll create 1.0-stable2 (ugh. any other naming ideas?) branch of the code before merging the new master/config code. - Fixed APPEND .. I hope? At least works much better than before - pop3_uidl_format = %m now doesn't return broken 0 MD5 sums when the MD5 sum wasn't written in indexes for some reason (eg. appended/copied to INBOX with IMAP and trying to access mail with POP3). - Authentication cache wasn't working when Dovecot was used for proxying - Index cache file wasn't keeping track of how much of the file was deleted, so it may not have ever shrinked - Maildir+NFS: Fixed skipping mails when moving files from new/ to cur/ - Maildir: We didn't notice if messages were directly deleted from new/

3 2

[Dovecot] imap corrupted indexes
by Emmett Pate 28 Jun '05

28 Jun '05

I've searched the archives and find a lot of references to corrupted indexes but can't seem to find any solutions. It seems like folks either have the problem or they don't. We recently migrated from a RedHat Linux server to an OpenBSD 3.7 server (both using dovecot). Imap was working flawlessly on the RedHat box but now gives numerous index errors. I then upgraded to dovecot-1.0-test66 compiled from ports - still no luck. Here's an example of the errors: Jun 27 12:02:23 mail dovecot: IMAP(epate): Corrupted transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log: Keyword record UIDs are broken Jun 27 12:02:24 mail dovecot: IMAP(epate): Lost transaction log file /home/epate/mail/.imap/INBOX/dovecot.index.log seq 7 I found references to "disabling indexing" but they don't say how. Would this be a reasonable temporary solution? Any other suggestions? Thanks for your help, Emmett Pate

3 3

[Dovecot] Sudden IMAP problem - UID Errors
by Jamie Heckford 28 Jun '05

28 Jun '05

Hi, We have quite happily been running dovecot with no issues at all for approx. two years now and have had no problem whatsoever. Great work :) BUT (there is always a but!).... yesterday one of our users started complaining that they were having issues with their mail. I checked and although they can still view their IMAP mailbox ok it constantly throws up error messages such as: "The UID of a message changed unexpectedly. This typically indicates a server bug. Your program may not function properly after this. MsgSeqNum 131: Previous UID: 21402, New UID: 21555 Protocol: IMAP" and "Your server has reported a UID which does not comply with the IMAP standard. This typically indicates a server bug. Your program may not function properly after this." This is using Outlook 2003 as the IMAP client, and is only affecting a single user. Server is dovecot-0.99.14 running on FreeBSD 4.9-RELEASE #1: Thu Apr 15 10:00:08 GMT 2004 Anybody seen this before or have any suggestions? Also is there a way I can make the logging more verbose as I only get info on date/user/ip when they login. I did see a --raw-log or similar compile flag, is this whats needed? I suspect this is Outlook being stupid and not dovecot though. Any help would be greatly received. Many thanks! -- Jamie Heckford Network Manager Trident Microsystems Ltd. t: +44(0)1737-780790 f: +44(0)1737-771908 w: http://www.trident-uk.co.uk/

2 2

[Dovecot] UID confusion
by Andrew Hutchings 28 Jun '05

28 Jun '05

Hi, 2 or 3 customers have reported that they are having problems downloading their mail via. POP3. I have attached the rawlogs of their transactions and the UID list at the time. Is this because I am using an incompatible UID format or is something else at fault? Deleting the UID list and indexes fixes the problem. I am using Test72. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 148: "We had planned to integrate a Web browser with our operating system as far back as 1993" - Microsoft (27 Jul 1998, filing its first court responses to federal antitrust) STAT UIDL DELE 12 DELE 13 DELE 14 DELE 15 DELE 16 DELE 17 DELE 18 DELE 19 DELE 20 DELE 21 DELE 22 DELE 23 DELE 24 DELE 25 DELE 26 DELE 27 DELE 28 DELE 29 DELE 30 DELE 31 DELE 32 DELE 33 DELE 34 DELE 12 DELE 31 DELE 20 DELE 14 DELE 32 DELE 19 DELE 21 DELE 33 DELE 23 DELE 28 DELE 22 DELE 34 DELE 27 DELE 30 DELE 24 DELE 18 DELE 17 DELE 29 DELE 26 DELE 25 DELE 15 +OK 37 3133628 +OK 1 1102086912.6586 2 1102086912.6604 3 1102086912.6606 4 1102086912.6607 5 1102086912.6613 6 1102086912.6614 7 1102086912.6624 8 1102086912.6627 9 1102086912.6628 10 1102086912.6637 11 1102086912.6638 12 1102086912.6642 13 1102086912.6643 14 1102086912.6644 15 1102086912.6645 16 1102086912.6646 17 1102086912.6647 18 1102086912.6649 19 1102086912.6650 20 1102086912.6651 21 1102086912.6652 22 1102086912.6653 23 1102086912.6655 24 1102086912.6656 25 1102086912.6657 26 1102086912.6658 27 1102086912.6659 28 1102086912.6660 29 1102086912.6661 30 1102086912.6662 31 1102086912.6663 32 1102086912.6664 33 1102086912.6665 34 1102086912.6666 35 1102086912.6668 36 1102086912.6669 37 1102086912.6670 . +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. +OK Marked to be deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Message is deleted. -ERR Too many bad commands. 1 1102086912 6671 6586 1119365297.H428351P22768.svr34.nsnoc.com:2,S 6604 1119430792.H16069P15059.svr34.nsnoc.com:2,S 6606 1119435803.H269574P27211.svr34.nsnoc.com:2,S 6607 1119438782.H651475P11876.svr34.nsnoc.com:2,S 6613 1119444180.H435092P3752.svr34.nsnoc.com:2,S 6614 1119446623.H168979P14147.svr34.nsnoc.com:2,S 6624 1119519980.H840253P23730.svr34.nsnoc.com:2,S 6627 1119534126.H915877P9542.svr34.nsnoc.com:2,S 6628 1119534129.H58338P9545.svr34.nsnoc.com:2,S 6637 1119590807.H77202P16581.svr34.nsnoc.com:2,S 6638 1119594010.H314838P14558.svr34.nsnoc.com:2,S 6642 1119631309.H826676P15985.svr34.nsnoc.com:2,S 6643 1119634096.H108358P8422.svr34.nsnoc.com:2,S 6644 1119651249.H740483P15403.svr34.nsnoc.com:2,S 6645 1119652382.H85165P25444.svr34.nsnoc.com:2,S 6646 1119662861.H891233P15682.svr34.nsnoc.com:2,S 6647 1119666011.H343203P9515.svr34.nsnoc.com:2,S 6648 1119678421.H726408P9343.svr34.nsnoc.com:2,S 6649 1119682873.H656272P7774.svr34.nsnoc.com:2,S 6650 1119709610.H933163P23969.svr34.nsnoc.com:2,S 6651 1119711088.H95605P27225.svr34.nsnoc.com:2,S 6652 1119717756.H183955P3515.svr34.nsnoc.com:2,S 6653 1119726592.H247339P1807.svr34.nsnoc.com:2,S 6654 1119727779.H102401P8785.svr34.nsnoc.com:2,S 6655 1119749596.H731030P9216.svr34.nsnoc.com:2,S 6656 1119760115.H508676P14834.svr34.nsnoc.com:2,S 6657 1119761702.H762025P27895.svr34.nsnoc.com:2,S 6658 1119774991.H8003P28710.svr34.nsnoc.com:2,S 6659 1119780623.H432714P11671.svr34.nsnoc.com:2,S 6660 1119797027.H333204P330.svr34.nsnoc.com:2,S 6661 1119799332.H700308P15617.svr34.nsnoc.com:2,S 6662 1119800637.H600428P30602.svr34.nsnoc.com:2,S 6663 1119807991.H64209P14572.svr34.nsnoc.com:2,S 6664 1119808834.H473596P22065.svr34.nsnoc.com:2,S 6665 1119838893.H830072P23165.svr34.nsnoc.com:2,S 6666 1119838934.H873217P23186.svr34.nsnoc.com:2,S 6667 1119860409.H899984P26859.svr34.nsnoc.com:2, 6668 1119860596.H249033P27907.svr34.nsnoc.com 6669 1119867953.H904781P22645.svr34.nsnoc.com 6670 1119867978.H374439P22691.svr34.nsnoc.com

2 4