- dovecot - dovecot.org

[Dovecot] Re: 0.99 mail env - mbox to maildir
by C.Lee Taylor 10 Sep '04

10 Sep '04

Greetings ... > I'm all sorted now, anyway... but it has inspired me to build > a mailbox conversion tool using the dovecot mail handling > code.... watch this space. mbox to maildir converter ... There are a few perl scripts which could do this ... But I like the idea of mbox to maildir in dovecot ... But I wonder if that is the right place to put it ... Mailed Lee P.S. If anybody has scripts or a system that moves mail from mbox to maildir, I would be happy to use them ... I run FC2, with procmailrc setting maildir, but it seems when the system is busy or something, my mail is still put into mbox ...

3 2

[Dovecot] ah ha!!
by Brian Hechinger 09 Sep '04

09 Sep '04

i don't know what happened, but it just started giving me better errors. i had to set first_valid_uid=100 since that's where my users start. wow, dovecot is FAST. -brian -- "The cats tend to administer themselves, and contrary to the expected facts, the house and everything in it was installed for their benefit." -- Nic Clews

1 0

[Dovecot] blank line at the top of mbox
by Brad.Allen＠edwardjones.com 09 Sep '04

09 Sep '04

I am having this same problem. We are running on a Solaris 8 server and Dovecot puts a blank line at the top of the mailbox and can no longer process until the line is deleted. Any idea how to fix this? Brad Allen IS EMS Projects and Planning

1 0

[Dovecot] Internal login failure
by Brian Hechinger 09 Sep '04

09 Sep '04

ok, so, dovecot 0.99.11, Solaris 9. i have: auth_userdb = passwd auth_passdb = shadow in my dovecot.conf, which gets me logged into dovecot in the first place, but then i get: Sep 9 09:52:41 ford.4amlunch.net imap-login: [ID 457029 mail.info] Internal login failure: wonko [10.0.1.6] in /var/log/syslog how do i track down exactly what the problem is so i can fix it? i would love to add SSL to my imap service, and don't care to mess with cyrus seeing how dovecot seems to be so nice. thanks!! -brian -- "The cats tend to administer themselves, and contrary to the expected facts, the house and everything in it was installed for their benefit." -- Nic Clews

1 0

Re: [Dovecot] 100% CPU utilisation
by Timo Sirainen 09 Sep '04

09 Sep '04

On 6.9.2004, at 03:28, Zoong Pham wrote: > > Dovecot (0.9.11) consumes 100% CPU utilisation when accessing > (either pop or imap) one of my mailboxes. It doesn't happen > with other mailboxes. > The mailbox has about 500 mails while others have many more. > They are all in mbox format. Probably because one of the lines in it is larger then 4096 bytes? Header parser doesn't really like that. I should get that fixed in 1.0-tests..

3 3

[Dovecot] Problem with mysql...
by Jacek Osiecki 08 Sep '04

08 Sep '04

Hello, I am trying to run dovecot on my Linux. I am using an exim 3.30 as the MTA with vmail-sql virtual users. I have installed latest dovecot release and ran through the config file. Some options seemed unclear to me, but generally I think it is OK. The problem is, that MySQL authentication does not work. It even does not try to authenticate! Dovecot connects correctly with MySQL database, but then no activity is shown in MySQL logs - but when I try to login manually with the telnet, i get: [root@mainframe root]# telnet localhost 143 Trying 127.0.0.1.143... Connected to localhost. Escape character is '^]'. * OK dovecot ready. 1 login [my_email] [my_password] 1 NO Authentication failed. Maybe I am doing something wrong? I have spent two days with this problem, even modifying source files could not help me localize the source of my troubles :( Here are the important (I think) entries from /etc/dovecot/dovecot.conf: ------- # Authentication process name. auth = default # Space separated list of wanted authentication mechanisms: # plain digest-md5 anonymous auth_mechanisms = plain auth_userdb = mysql /etc/dovecot/dovecot-mysql.conf auth_passdb = mysql /etc/dovecot/dovecot-mysql.conf ------- Any suggestions? Best regards, -- Jacek Osiecki joshua(a)ceti.pl Poland

3 6

[Dovecot] Mail cut on CR character
by Tom Mraz 08 Sep '04

08 Sep '04

Hi all, when I move the attached mail from local folder in Mozilla to an IMAP folder on dovecot, it is cut just before the ... characters. There is an extra CR character. I have setup the dovecot to use Maildirs. When I copy the file with the message manualy to one of the Maildir folders it is shown correctly in Mozilla however it if I move it using Mozilla to another IMAP folder the mail is cut again. Thanks for any reply, Tomas Mraz P.S. Using self compiled dovecot 0.99.11 on Fedora Core 2 >From - Wed Sep 8 08:18:55 2004 X-UIDL: 2f50f9a50ff6d9a016b79e964aa3bbg9 >From users-return-3131-t8m=centrum.cz(a)cs.openoffice.org Tue Sep 7 20:39:39 2004 Received: from localhost ([127.0.0.1]:44525 "HELO data2.centrum.cz") by mail.centrum.cz with SMTP id <S2310612AbUIGSjU>; Tue, 7 Sep 2004 20:39:20 +0200 X-Virus-Scanner: This message was checked by NOD32 Antivirus system NOD32 for Linux Mail Server. For more information on NOD32 Antivirus System, please, visit our website: http://www.nod32.com/. Received: from s002.sfo.collab.net ([64.125.133.202]:62908 "HELO openoffice.org") by mail.centrum.cz with SMTP id <S279819AbUIGSiB>; Tue, 7 Sep 2004 20:38:01 +0200 X-SpamDetected: 0 Received: (qmail 13761 invoked by uid 5302); 7 Sep 2004 18:38:05 -0000 Mailing-List: contact users-help(a)cs.openoffice.org; run by ezmlm Precedence: bulk X-No-Archive: yes list-help: <mailto:users-help@cs.openoffice.org> list-unsubscribe: <mailto:users-unsubscribe@cs.openoffice.org> list-post: <mailto:users@cs.openoffice.org> Reply-To: users(a)cs.openoffice.org Delivered-To: mailing list users(a)cs.openoffice.org Delivered-To: moderator for users(a)cs.openoffice.org Received: (qmail 29370 invoked from network); 7 Sep 2004 16:57:14 -0000 Message-ID: <413DF687.5010705(a)zoznam.sk> Date: Tue, 07 Sep 2004 18:57:27 +0100 From: Skusac <skus(a)zoznam.sk> User-Agent: Mozilla Thunderbird 0.7 (Windows/20040616) X-Accept-Language: en-us, en MIME-Version: 1.0 To: users(a)cs.openoffice.org X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-2; format=flowed Content-Transfer-Encoding: 7bit X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) Subject: CSS Styly Return-Path: <users-return-3131-t8m=centrum.cz(a)cs.openoffice.org> X-Orcpt: rfc822;t8m(a)mail3.centrum.cz Zdravim, ako sa daju pouzivat css styly v Open Office? Potrebujem aby styly boli v externom dokumente napr styly.css a v dokumente html aby bol len link na styly. Mne to vzdy link vyhodi a uklada mi styly priamo do html dokumentu. Skusal som to ukladat aj pre HTML 3.2 aj s pomocou ignore font settings, vtedy styly neuklada, ale zase popisuje farby, velkosti ... pre kazdu cast textu. Ale styly si to z externeho .css dokumentu nenatiahne. Tools->Options->Load/Save->HTML Compatibility (Sorry za anglicku verziu) Vdaka za prispevky. Alex Fischer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe(a)cs.openoffice.org For additional commands, e-mail: users-help(a)cs.openoffice.org

1 0

[Dovecot] better way to create home dirs for mail servers
by ramana 08 Sep '04

08 Sep '04

Dear all, Autodir is for creating home directories and group directories much better then pam_mkhomedir as pam_mkhomedir does suffer some limitations like, 1) There are some applications which never need to authenticate users But they need home dirs -- for example mail servers configured to use home dirs for mail delivery and storage but not configured to use pam. 2) Some do use other ways to authenticate, bypassing pam all together. 3) Servers must be root so that pam can create home dirs. Otherwise make /home similar in permissions to /tmp And there are other interesting features with Autodir like transparent backup for 24x7 online systems and many more. Autodir uses autofs kernel module to transparently create home dirs And for more information check http://www.intraperson.com/autodir/ And here is Autodir-HOWTO http://prdownloads.sourceforge.net/intraperson/Autodir-HOWTO.html?download Regards ramana -- http://www.intraperson.com

1 0

[Dovecot] Workaround for outlook UIDL handling bug ??
by Nikolaus Gerstmayr 07 Sep '04

07 Sep '04

Scenario: Using Dovecot 0.99.10.9 as pop3 server. With delete on retrival off. clients: outlook* Problem: Everytihng work perfectly, except that outlooks keeps re-downloading SOME mail over and over. Though it already got them. No obvious pattern which, but only a small percentage. First of I looked at dovecots UIDLs. Initialy I thought it's broken (see my previous thread) Sorry for even thinking that, it's ok, my bad :) Rather, outlooks UIDL handling seems to be very broken :( But I think I found an easy workaround. Dovecots UIDLS seem to be timestamp.message# eg. 1 1093990148.1 2 1093990148.2 3 1093990148.3 4 1093990148.4 5 1093990148.5 6 1093990148.6 7 1093990148.7 8 1093990148.8 9 1093990148.9 10 1093990148.10 11 1093990148.11 12 1093990148.12 The problems started with #10 -> Asumption: outlook falsy only takes a fixed numbers of chars to hold the UIDL, the rest ist ignored. Perhaps only the first 13 or so. What I did is reversing the order in UIDL generation. Instead of timestamp.message# -> message#.timestamp. Seems to work perfectly. Well, a bit too early too tell if it really works. Need to wait a couple of days and see if the problem re-appears or not. The only thing I'm 100% sure is that outlooks UIDL handling is broken. BTW: very nice source code. Very easy to follow, took me 5 minutes to find the correct .c and routine. In /pop3/command.c, list_uids() all I changed is ... mail->seq, client->uidvality, mail->uid to mail->seq, mail->uid, client->uidvality. (2 times) If anyone is interested, I'll keep you informed if the problem is really gone with this mini-patch.

2 3

[Dovecot] Comments on planned migration to Dovecot
by Rory Campbell-Lange 07 Sep '04

07 Sep '04

Our office of about 100 users is presently running its mail through an Exchange 5.5 Server. The Exchange server is protected by Linux server pass-through server running Exim4. We intend to move all of our mail and directory services to open source software, probably Exim4, Dovecot and OpenLDAP. We have a mixture of mail clients. These include Mac OS9 Entourage (about 30%), OSX Entourage (20%) and Apple Mail (50%). About 30 individuals also look in to their mailboxes using squirrelmail. Each user is permitted a mailbox of no more than 20MB in size. Project mailboxes may rise to 200MB, however, with up to 5 simultaneous users connection to each project mailbox. I would be grateful for comments on the suitability of deploying Dovecot in this production environment. I already use Dovecot for a small number of users in a different environment (Mac Eudora, XP Outlook, Squirrelmail) and it appears to work without fault. Rory -- Rory Campbell-Lange <rory(a)campbell-lange.net> <www.campbell-lange.net>

1 0

[Dovecot] [Fwd: Maildir++ support]
by Maykel Moya 07 Sep '04

07 Sep '04

> In the homepage said that dovecot doesn't yet support maildir++, but in > http://dovecot.org/doc/mail-storages.txt said 'we support maildir++'. > > My question is: does dovecot support maildir++ ? > > Regards > mike

2 1

[Dovecot] Dovecot quota support
by Alton Yu 07 Sep '04

07 Sep '04

Sorry if this question has already been answered. I'm just thought that maybe I could get an answer here faster than my research. I'm currently using squirrelmail and there's a plugin that supports quota compatible with Courier. Does dovecot have the same support? Thanks!

2 1

[Dovecot] [Fwd: dovecot bug case] Reproducably make "imap" loop.
by Grahame Bowland 07 Sep '04

07 Sep '04

Hi guys I noticed a few people talking about a bug where "imap" processes loop. Bruce has managed to reproduce the bug. Anyone know if this has been fixed in CVS, or is it an unfixed problem? Cheers Grahame

1 0

RE: [Dovecot] 100% CPU utilisation
by Zoong Pham 07 Sep '04

07 Sep '04

> -----Original Message----- > From: Timo Sirainen [mailto:tss@iki.fi] > Sent: Monday, 6 September 2004 6:34 PM > To: Zoong Pham > Cc: Dovecot mailing list > Subject: Re: [Dovecot] 100% CPU utilisation > > Probably because one of the lines in it is larger then 4096 bytes? > Header parser doesn't really like that. I should get that fixed in > 1.0-tests.. > I just check the problematic mailbox. The maximum line length is 2047 characters. Most of them are around 1300 characters. Thanks, Zoong THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy, forward, print or otherwise disseminate any information it contains. MERCY HEALTH & AGED CARE is a Catholic community benefit organisation. Each year, one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) *Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo *Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury *Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose *Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo

1 0

RE: [Dovecot] 100% CPU utilisation
by Jamie Heckford 06 Sep '04

06 Sep '04

> > Dovecot (0.9.11) consumes 100% CPU utilisation when accessing > (either pop or imap) one of my mailboxes. It doesn't happen > with other mailboxes. > The mailbox has about 500 mails while others have many more. > They are all in mbox format. > I've noticed this using maildir, luckily we have an SMP server so it doesn't affect it to much, but obviously I would like to stop it. Doesn't happen to all users and doesn't seem to be dependent on size of Maildir, sending SIGTERM makes it go away and then the user opens the mailbox again and I see normal CPU usage. However 3-4 hours later it will happen again. Using FreeBSD 4.9 and dovecot-0.99.10.4, postfix 2.0.18 as MTA. If theres any other info that would be useful (this is probably the most vauge description I can manage, but its all the info I have) then let me know and I can provide. Ta Jamie

1 0

[Dovecot] [PATCH] [RFC] epoll based ioloop handler
by Andrey Panin 06 Sep '04

06 Sep '04

Hello, this patch adds ioloop handler using Linux 2.6 epoll API. I'm not sure is it ready for inclusion right now, but it works for me and survives deadconn test with 1024 simultaneous connections. Please take a look and comment. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

3 4

Re: [Dovecot] 100% CPU utilisation
by Lasse Danielsen 06 Sep '04

06 Sep '04

I have some experience with OBSD, squirrel, vpopmail and dovecot. In my experience it would hang like that if squirrel was set up to sort/thread (or whatever the settings was named). try to turn such things off and see if that helps. -- Lasse Danielsen lasse(a)danielsen.tk -- No part of this message may reproduce, store itself in a retrieval system, or transmit disease, in any form, without the permissiveness of the author. > > Dovecot (0.9.11) consumes 100% CPU utilisation when accessing > (either pop or imap) one of my mailboxes. It doesn't happen > with other mailboxes. > The mailbox has about 500 mails while others have many more. > They are all in mbox format. > > OS: OpenBSD-3.5 with all patches > MTA: Sendmail-8.12.11 > It happened with other RCs of dovecot-0.9.11 > Configured as: ./configure --without-pam --without-shadow > --without-vpopmail --localstatedir=/var --with-ssldir=/etc/ssl > --with-ssl=openssl > > There is no strange information in /var/log/maillog except the > normal ones like: > Sep 6 10:12:40 onion imap-login: Login: zoong [127.0.0.1] > > The pop or imap clients (mutt and squirrel-1.4.3a) just stay at "opening > INBOX ...". > mutt can open directly the mailbox without any problem. > I rebooted the server and problem still happening. > > Can someone advise how to find out what's wrong here? > I guess there is some kind of corruption within the mailbox. > > Thanks, > Zoong PHAM > > ___________________________________________________________________________________ > THIS EMAIL IS CONFIDENTIAL. If you have received this email in error > please forward it to information(a)mercy.com.au. It may contain personal > information and it is intended for the addressee only. If you receive this > email in error you must not use, copy forward, print or otherwise > disseminate any information it contains. > Mercy Health & Aged Care is a Catholic community benefit organisation. > Each year one in twenty Victorian families are touched by the services we > provide. Visit www.mercy.com.au for more information. > Our services include: > * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) > * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - > Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - > Canterbury * Corporate Office - Richmond * Rice Village - Geelong * > Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for > the Aged - Bendigo * > -- Lasse Danielsen lasse(a)danielsen.tk -- No part of this message may reproduce, store itself in a retrieval system, or transmit disease, in any form, without the permissiveness of the author. Random Thought: -------------- There was a young lady named Ransom Who was rogered three times in a hansom. When she cried out for more A voice from the floor Replied, "My name is Simpson, not Samson."

1 0

[Dovecot] POP3 and big mailboxes
by Sergey Matveychuk 06 Sep '04

06 Sep '04

Hello. Today one of my users has returned from vacation and his mailbox has grown to 67 Mbyte in 1705 e-mails. dovecot can't index this mailbox with this message (i've changed username with 'xxx'): pop3-login: Sep 06 10:03:43 Info: Login: xxx [172.16.4.9] pop3(xxx): Sep 06 10:03:43 Error: Error indexing mbox file /var/mail/xxx: LF not found where expected pop3(xxx): Sep 06 10:03:43 Error: Error indexing mbox file /var/mail/xxx: LF not found where expected pop3(xxx): Sep 06 10:03:43 Warning: I/O leak: 0x8050600 (0) pop3(xxx): Sep 06 10:03:43 Warning: I/O leak: 0x80858f0 (1) pop3(xxx): Sep 06 10:03:43 Warning: Timeout leak: 0x8065b90 Is it a bug in dovecot? PS. dovecot-0.99.10.9 on FreeBSD 5.2-CURRENT (a month before BETA1 released). -- Sem.

3 3

[Dovecot] v0.99.11 released
by Timo Sirainen 06 Sep '04

06 Sep '04

v0.99.11 2004-09-04 Timo Sirainen <tss(a)iki.fi> + 127.* and ::1 IP addresses are treated as secured with disable_plaintext_auth = yes + auth_debug setting for extra authentication debugging + Some documentation and error message updates + Create PID file in /var/run/dovecot/master.pid + home setting is now optional in static userdb + Added mail setting to static userdb - After APPENDing to selected mailbox Dovecot didn't always notice the new mail immediately which broke some clients - THREAD and SORT commands crashed with some mails - If APPENDed mail ended with CR character, Dovecot aborted the saving - Output streams sometimes sent data duplicated and lost part of it. This could have caused various strange problems, but looks like in practise it rarely caused real problems.

6 7

[Dovecot] 100% CPU utilisation
by Zoong Pham 06 Sep '04

06 Sep '04

Dovecot (0.9.11) consumes 100% CPU utilisation when accessing (either pop or imap) one of my mailboxes. It doesn't happen with other mailboxes. The mailbox has about 500 mails while others have many more. They are all in mbox format. OS: OpenBSD-3.5 with all patches MTA: Sendmail-8.12.11 It happened with other RCs of dovecot-0.9.11 Configured as: ./configure --without-pam --without-shadow --without-vpopmail --localstatedir=/var --with-ssldir=/etc/ssl --with-ssl=openssl There is no strange information in /var/log/maillog except the normal ones like: Sep 6 10:12:40 onion imap-login: Login: zoong [127.0.0.1] The pop or imap clients (mutt and squirrel-1.4.3a) just stay at "opening INBOX ...". mutt can open directly the mailbox without any problem. I rebooted the server and problem still happening. Can someone advise how to find out what's wrong here? I guess there is some kind of corruption within the mailbox. Thanks, Zoong PHAM ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

[Dovecot] Plaintext Authentication from Localhost
by Paul C. Bryan 06 Sep '04

06 Sep '04

Hi: It appears that at least at one time, Dovecot supported plaintext authentication from localhost, even if disable_plaintext_auth = yes. To wit, the example configuration file reads: # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. #disable_plaintext_auth = yes On brief inspection of the code, there doesn't seem to be any such support. This is corroborated by the fact that 0.99.10 (Debian package) behaves by disallowing plaintext authentication via connections on localhost. This is a particularly useful feature, as local webmail clients can safely authenticate via the local interface without requiring secure authentication. So, the question is, is Dovecot supposed to support plaintext auth via localhost even if disallowed in dovecot.conf? If so, any suggestions as to what I may be doing wrong? Yours truly, Paul C. Bryan email(a)pbryan.net

2 4

[Dovecot] pam_access
by Programmer 05 Sep '04

05 Sep '04

I've discoverd when I add the line pam_access for access authentication, It always denys a login, even when access.conf accepts everything. I've tested this with other programs, and they work okay. Any ideas?

1 0

[Dovecot] file ostream-file.c: assertion failed with v1.0-test38
by Wouter Van Hemel 05 Sep '04

05 Sep '04

Hello, I've some troubles logging in after upgrading to -test38. The error in the logs says: Sep 4 02:34:38 hostname dovecot: imap-login: Login: username [123.123.123.123] Sep 4 02:34:48 hostname dovecot: IMAP(username): file ostream-file.c: line 105 (update_buffer): assertion failed: (size <= used) Sep 4 02:34:48 hostname dovecot: child 28966 (imap) returned error 1 Regards, wouter

2 3

[Dovecot] 1.0-test39
by Timo Sirainen 04 Sep '04

04 Sep '04

http://dovecot.org/test/ Fixes several crashes. Apparently can still break with mboxes, although it works with me..

2 2

[Dovecot] 0.99.11-rc3
by Timo Sirainen 04 Sep '04

04 Sep '04

http://dovecot.org/rc/ Maybe this one works? :)

3 8

[Dovecot] link() problem with dovecot-imapd
by James Ray 04 Sep '04

04 Sep '04

I'm having a few problems with dovecot-imapd (installed from debian unstable) and am after some much needed help, all is set up and configured, except for this final problem of when I try and move or copy a message from one Maildir to another. I have the option "maildir_copy_with_hardlinks = no" in the the dovecot.conf file but it still seems to be trying to link() the file instead of doing a proper copy. There is a log fragment below for when I try to do a move, the FS that my Maildir is on doesn't support link() hence the problem. It seems to be doing a proper copy to get it into the tmp/ part of the Maildir and then a link() to put it in new/. Any ideas on how to cure this? Log output;l -- Sep 2 18:44:29 indulgence imap(jamesr): link(/home/jamesr/Mail/Maildir/.INBOX.Trash/tmp/1094147066.P2339Q0M915274.indulgence, /home/jamesr/Mail/Maildir/.INBOX.Trash/new/1094147066.P2339Q0M915274.indulgence:2,Sa) failed: Operation not permitted James 'BR' Ray - EMail : jamesr(a)pethippo.co.uk (Primary) - EMail : j.ray(a)herts.ac.uk (University) - Web : http://www.pethippo.co.uk/ - PGP : http://www.pethippo.co.uk/in.php/pgp

3 4

RE: [Dovecot] file ostream-file.c: assertion failed with v1.0-test38
by dovecot 04 Sep '04

04 Sep '04

Hi, > IMAP(username): file ostream-file.c: line 105 > (update_buffer): assertion failed: (size <= used) Sep 4 Same error occurs here, using test38 on Fedora Core 1. For me, the error occurs only using Outlook (2003 in my case). Horde's WebMail client IMP and OpenNMS' IMAP poller work fine though. Reverting back to test32 helped, after I found out about a recent change in ostream-file.c in CVS aroung August 15. BTW, test32 fixes the mbox 'empty lines at beginning of file' corruption problem someone reported here lately too. Regards, Martin

1 0

[Dovecot] "not listening" errors fdpass.c
by christian sherwood 04 Sep '04

04 Sep '04

I'm getting a flood of errors that look like: Sep 3 13:27:02 localhost dovecot: login: received another "not listening" notification (if you can't login at all, see src/lib/fdpass.c) every few minutes. Versions: Dovecot: 0.99.10.9 Exim: 4.34 Debian Linux 2.6.8-1-686-smp Squirrelmail: 1.4.3a Although the majority of users (99%) have no problems logging in and reading their mail, occasionally one user gets timeouts when trying to access their mailbox, seems to correlate with the errors. I can't locate fdpass.c, so what does this error indicate?

1 0

[Dovecot] isync with dovecot
by tino.keitel＠gmx.de 03 Sep '04

03 Sep '04

Hi folks, I use isync, an IMAP sync tool (Debian package isync 0.9.2-2) together with dovecot (dovecot-imapd 0.99.10.8-0.backports.org.1). Everytime when isync wants to upload a new mail from the client to the server I got messages like this: Mailbox outbox Selecting IMAP mailbox... >>> 16 SELECT "outbox" * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1580 EXISTS * 0 RECENT * OK [UIDVALIDITY 1092995697] UIDs valid * OK [UIDNEXT 1581] Predicted next UID 16 OK [READ-WRITE] Select completed. 1580 messages, 0 recent Reading IMAP mailbox index >>> 17 UID FETCH 1:* (FLAGS) * 1 FETCH (UID 1 FLAGS (\Seen)) * 2 FETCH (UID 2 FLAGS (\Seen)) [...] * 1579 FETCH (UID 1579 FLAGS (\Seen)) * 1580 FETCH (UID 1580 FLAGS (\Seen)) 17 OK Fetch completed. Synchronizing Uploading messages.>>> 18 APPEND outbox (\Seen) {360} + OK 18 OK Append completed. >>> 19 UID SEARCH HEADER X-TUID 4136367cd15e45705 * SEARCH IMAP error: incomplete SEARCH response 19 OK Search completed. warning: no UID for new messge 1094071902.22258_2.thinkpad:2,S 1 messages. Fetching new messages... 0 messages My concern is the line "IMAP error: incomplete SEARCH response". I already saw this mesage with old versions of courier-imap, which won't return an APPENDUID tag so the client doesn't know which UID will be used for the uploaded message (this was the explanation I got). Is there any way to get dovecot to return the UID when a message is uploaded? Regards, Tino

3 2

Re: [Dovecot] 0.99.11-rc2
by Timo Sirainen 03 Sep '04

03 Sep '04

On 3.9.2004, at 02:45, Zoong Pham wrote: > I started dovecot the same way > as dovecot-0.99.10.9 and with the same config file. > The return code is 0 but there are no dovecot processes at all. > And the POP3 client can't connect. netstat reports port 110 (for POP3) > is not listening. Dovecot probably crashed while trying to create the pid file and didn't start at all. I was wondering today that no-one noticed this, but I also noticed it only after trying to run it in Solaris, with Linux it worked fine. (I hate t_strconcat() API but I just can't get myself to stop using it.)

2 1

RE: Re[2]: [Dovecot] 0.99.11-rc2
by Zoong Pham 03 Sep '04

03 Sep '04

> -----Original Message----- > From: Nikolaus Gerstmayr [mailto:Nikolaus_Gerstmayr@gmx.at] > Sent: Friday, 3 September 2004 9:49 AM > To: Zoong Pham > Cc: dovecot(a)dovecot.org > Subject: Re[2]: [Dovecot] 0.99.11-rc2 > > > Currently, I restored the backup of dovecot-0.99.10.9 > binary and everying > > works again. > > > Having EXACLTY the same problem. > > no error message whatsoever. > no dovecot process. > > "reverted" to 0.99.10.9 My "backup" of dovecot-0.99.10.9 is giving me this error: Sep 3 12:13:31 onion pop3(user1): Timeout while waiting for release of shared fcntl() lock for index file /var/www/htdocs/user1/Mail/.imap/INBOX/.imap.index Sep 3 12:18:31 onion pop3(user1): Timeout while waiting for release of fcntl() lock for mbox file /var/mail/user1 Sep 3 12:18:31 onion pop3: I/O leak: 0x1c00866c (0) Sep 3 12:18:31 onion pop3: I/O leak: 0x1c03441c (1) How can I remove the lock? Can I simply remove the file /var/www/htdocs/user1/Mail/.imap/INBOX/.imap.index and start dovecot again ? Thanks, Zoong ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

RE: [Dovecot] 0.99.11-rc2
by Zoong Pham 03 Sep '04

03 Sep '04

> -----Original Message----- > From: dovecot-bounces(a)dovecot.org > [mailto:dovecot-bounces@dovecot.org]On > Behalf Of Timo Sirainen > Sent: Thursday, 2 September 2004 9:01 PM > To: Dovecot mailing list > Subject: [Dovecot] 0.99.11-rc2 > > > http://dovecot.org/rc/ > > Changes since rc1: > > + Create PID file in /var/run/dovecot/master.pid > - THREAD and SORT commands crashed with some mails I configured, compiled and installed the RC2 the same way as dovecot-0.99.10.9. There were no error at all. Here is how I configured: ./configure --without-pam --without-shadow --without-vpopmail --localstatedir=/var --with-ssldir=/etc/ssl --with-ssl=openssl I also ran these: - mkdir /var/run/dovecot - chown _dovecot:_dovecot /var/run/dovecot I started dovecot the same way as dovecot-0.99.10.9 and with the same config file. The return code is 0 but there are no dovecot processes at all. And the POP3 client can't connect. netstat reports port 110 (for POP3) is not listening. What's wrong here? How can I turn on debugging with dovecot? Currently, I restored the backup of dovecot-0.99.10.9 binary and everying works again. Thanks, Zoong ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

2 1

[Dovecot] mail location questions
by Chris 02 Sep '04

02 Sep '04

Hi all, I'm reading the docs and confs and it's not quite sinking in, mostly cuz I've been reading IMAP docs for a week now trying to find one that I want. :) I have a mail server that will have about 800 webmail users without actual home directories. Can I set up the IMAP dir in another location, like /var/imap, where everyone can read/store their mail? Or just use the /var/spool/mail/<user> mbox file and make a sub dir for the indexing files? Sorry if this is basic, all I saw was ~/Maildir locs. :P Thanks! -- C

2 1

[Dovecot] What version am I running
by Mark Lidstone 02 Sep '04

02 Sep '04

Hi all, This is probably a silly question, but is there an easy way to get the dovecot executable to report it's version number? Many thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== ==

3 2

[Dovecot] 1.0-test38
by Timo Sirainen 02 Sep '04

02 Sep '04

http://dovecot.org/test/ - Recent flag fixes - saving/copying mails into maildir which didn't have index files was broken - output stream fix - pop3 crashfix - mbox_dirty_syncs fixes, also disabling it didn't work before - etc. There are still some crashes and I don't remember if I fixed a problem with mboxes where expunging mails while new mails were coming caused some breakages.. but I can't reproduce it anymore. Anyway I think that could be fixed with disabling dirty syncs.

2 1

RE: [Dovecot] Dovecots pop3-UIDL command impl. not RFC compliant ?
by Mark Lidstone 02 Sep '04

02 Sep '04

Errr. 0x21-0x7E is !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefgh ijklmnopqrstuvwxyz{|}~ I can see 0-9 and \. in there. Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: mymailingslists(a)gmx.at [mailto:mymailingslists@gmx.at] Sent: 02 September 2004 14:15 To: dovecot(a)dovecot.org Subject: [Dovecot] Dovecots pop3-UIDL command impl. not RFC compliant ? Hi ! POP3-RFC (1939) speaks about UIDL command: The unique-id of a message is an arbitrary server-determined string, consisting of one to 70 characters in the range 0x21 to 0x7E, which uniquely identifies a message within a maildrop and which persists across sessions. When I issue an UIDL command (dovecot 0.99.10.9) I get replies like 1 1093990148.1 2 1093990148.2 3 1093990148.3 ... . You see the problem ? '0'-'9' and '.' are not in range 0x21-0x7E ! ---------------------------------------------------------------------- Currently I'm tracking down a nasty problem with Outlook 2003 together with dovecot acting as pop3 server. Multile pop3 accounts, with 'leave mail on server' on. (cant turn it off) for no apparent reason, a couple of mails (just a few out of thousands/hundrets) get re-downloaded again, and again, and again ... as if client had not seen it before. Might be a client problem ... while trying to find out the reason for this behaviour if found this UIDL thing. I fear it might not be the true reason/problem for my problems with outlook redownloading certian mails forevr, but I thought it doesnt hurt to report it ;)

2 1

[Dovecot] starting multiples instances of dovecot listening on same port
by mymailingslists＠gmx.at 02 Sep '04

02 Sep '04

Of course it's useless and this just can't work ... if I try it returns with an error message. Can't bind to port xy. No problem, that's the way it should be, but further strange things worth mentioning happen. After the second instance quits with error msg, the currently running instance doesn't accept any client connections anymore. Needs to be restarted. (currently I'm only using dc 0.99.10.9 as pop3 server) That's really no problem, but strange :> (I admit I'm somewhat curious if this problem is specific to my setup or if its happening everywhere)

1 0

[Dovecot] mutt polling imap mailboxes
by Martin Ehmsen 02 Sep '04

02 Sep '04

Hi... I have the exact same problem as being described in this posting from february: http://www.dovecot.org/list/dovecot/2004-February/002950.html That mutt in combination with dovecot dosen't show correctly which folders contains new messages. It is starting to bug me very much, so i'm willing to do about everything to help fix this problem. The problem is, that I don't know if it's a mutt or dovecot problem? I'm not a novice c-hacker, so I shoud be able to test about every idea that someone has about where this problem comes from. Hope someone will help me in my quest to crush this bug. Thanks in advance Martin

2 3

[Dovecot] Dovecots pop3-UIDL command impl. not RFC compliant ?
by mymailingslists＠gmx.at 02 Sep '04

02 Sep '04

Hi ! POP3-RFC (1939) speaks about UIDL command: The unique-id of a message is an arbitrary server-determined string, consisting of one to 70 characters in the range 0x21 to 0x7E, which uniquely identifies a message within a maildrop and which persists across sessions. When I issue an UIDL command (dovecot 0.99.10.9) I get replies like 1 1093990148.1 2 1093990148.2 3 1093990148.3 ... . You see the problem ? '0'-'9' and '.' are not in range 0x21-0x7E ! ---------------------------------------------------------------------- Currently I'm tracking down a nasty problem with Outlook 2003 together with dovecot acting as pop3 server. Multile pop3 accounts, with 'leave mail on server' on. (cant turn it off) for no apparent reason, a couple of mails (just a few out of thousands/hundrets) get re-downloaded again, and again, and again ... as if client had not seen it before. Might be a client problem ... while trying to find out the reason for this behaviour if found this UIDL thing. I fear it might not be the true reason/problem for my problems with outlook redownloading certian mails forevr, but I thought it doesnt hurt to report it ;)

1 0

[Dovecot] dovecot+postifx+ldap
by venne 02 Sep '04

02 Sep '04

hi, i'm trying to set a dovecot/pop + postfix couple with ldap authentification. and i'v got a lots of troubles. hers's my dovecot.conf protocols = pop3 login = imap login = pop3 first_valid_gid = 1000 last_valid_gid = 0 mail_extra_groups = mail default_mail_env = maildir:/var/mail/%1u/%u/Maildir mbox_locks = dotlock flock auth = default auth_mechanisms = plain auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf auth_verbose = yes here's dovecot-ldap.conf hosts = 192.168.128.1 dn = cn=manager,o=dental-on-line dnpass = dolmaster ldap_version = 3 base = ou=002f83,ou=machines,ou=fr,o=dental-on-line deref = never scope = subtree user_attrs = uid user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid,userPassword pass_filter = (&(objectClass=posixAccount)(uid=%u)) default_pass_scheme = PLAIN user_global_uid = 1000 user_global_gid = 1000 and, a ldif exempl: dn: uid=mwerly, ou=002F83, ou=machines, ou=fr, o=dental-on-line displayName: WERLY Marc shadowExpire: -1 mobile: 000 objectClass: top objectClass: person objectClass: organizationalPerson objectClass: inetOrgPerson objectClass: posixAccount objectClass: shadowAccount userPassword:: eHh4 shadowLastChange: 10000 facsimileTelephoneNumber: 01.43.21.54.75 uid: mwerly uidNumber: 12164 cn: Marc WERLY shadowInactive: -1 loginShell: /bin/bash shadowMin: 0 gidNumber: 100 shadowMax: 999999 gecos: mwerly homeDirectory: /home/mwerly sn: Marc shadowWarning: 99 1 it seems unable to authenticate with pop3-login: Login: mwerly [192.168.1.7] Aug 31 17:47:35 dental01 pop3: I/O leak: 0x8050d70 (0) Aug 31 17:47:35 dental01 pop3: I/O leak: 0x8084db0 (1) :o( 2 if I comment user_global_uid = 1000 user_global_gid = 1000 dovecot can't get uidnumber from ldap, in spite of its presence in ldap entry :'o( 3 postfix seem able to send messages to local virtual users(thanks of ldap/pam ldap authentification). the /var/mail/%u files are up2dated by postfix, but I simply can't get any mails with thoses dovcot logs: pop3-login: Login: mwerly [192.168.1.7] Aug 31 17:47:35 dental01 pop3: I/O leak: 0x8050d70 (0) Aug 31 17:47:35 dental01 pop3: I/O leak: 0x8084db0 (1) :`o[[[[[ please help

3 6

[Dovecot] 0.99.11-rc2
by Timo Sirainen 02 Sep '04

02 Sep '04

http://dovecot.org/rc/ Changes since rc1: + Create PID file in /var/run/dovecot/master.pid - THREAD and SORT commands crashed with some mails If nothing new comes up, this is the final release tomorrow.

1 0

Re: [Dovecot] File isn't in mbox format: /var/mail/user1
by Timo Sirainen 02 Sep '04

02 Sep '04

On 2.9.2004, at 09:09, Zoong Pham wrote: > Sep 1 11:12:31 onion pop3(tekciz): File isn't in mbox format: > /var/mail/user1 .. > Does anyone know what's happening? Dovecot probably has left an extra empty line at the beginning of the mbox file and after that it treats it as invalid. This happens sometimes with 0.99 code, 1.0-tests have much better mbox implementation.

1 0

[Dovecot] corrupted .imap.index.log
by Fredrick Backman 02 Sep '04

02 Sep '04

Hi, I'm using version 0.99.10.8 on debian 2.4.26 and am getting this problem, can someone please shed some light over this? Aug 31 13:58:58 xxx imap(someone): file_wait_lock() failed with modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: Resource temporarily unavailable and then: Aug 31 14:00:58 xxx imap(someone): Couldn't lock modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log and finally: Aug 31 14:26:35 xxx imap(someone): Corrupted modify log file /var/mail/someone_new/Maildir/.INBOX/.imap.index.log: used_file_size larger than real file size (4096 vs 2576) MTA is qmail 1.03 (with procmail v3.22) TIA, Fredrick -- Systemadministration EsPresto AG ----------------------------------------------------------------- backman(a)espresto.com Breite Str. 30-31 Tel/Fax: +49.30.90 226.750/.760 10178 Berlin/Germany

2 2

[Dovecot] Assertion failed in buffer.c
by news.gmane.org 02 Sep '04

02 Sep '04

dovecot-0.99.10.5-0.FC2 I have had a report from a user that when accessing their inbox, the connection is suddenly dropped. Dovecot reports the following:- imap(user): file buffer.c: line 357 (buffer_set_start_pos): assertion failed: (abs_pos <= I_MIN(buf->used, buf->limit)) From searching the list, I found an indication that it is a problem with an individual message. As the user has rather a large number of emails, how can I isolate the message? Regards -- Chris Hills IT Services North East Worcestershire College

2 3

RE:UPDATE: [Dovecot] File isn't in mbox format: /var/mail/user1
by Zoong Pham 02 Sep '04

02 Sep '04

> -----Original Message----- > From: dovecot-bounces(a)dovecot.org > [mailto:dovecot-bounces@dovecot.org]On > Behalf Of Zoong Pham > Sent: Thursday, 2 September 2004 4:09 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] File isn't in mbox format: /var/mail/user1 > > I lately see lots of message like this in my maillog: > > Sep 1 11:12:31 onion pop3-login: Login: user1 [203.11.35.29] > Sep 1 11:12:31 onion pop3(tekciz): File isn't in mbox > format: /var/mail/user1 > Sep 1 11:12:31 onion pop3(tekciz): File isn't in mbox > format: /var/mail/user1 Oop, I changed the login name from tekciz to user1 to protect the client's privacy but I missed the above lines :-( > Sep 1 11:12:31 onion pop3: I/O leak: 0x1c00881c (0) > Sep 1 11:12:31 onion pop3: I/O leak: 0x1c034f1c (1) > Sep 1 11:12:31 onion pop3: Timeout leak: 0x1c01a3e8 > > I have: > - OS: OpenBSD-3.5 with all the patches. > - Sendmail 8.12.11 > - dovecot-0.99.10.9 The POP3 client is MDaemon (http://www.altn.com/) Thanks ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

[Dovecot] File isn't in mbox format: /var/mail/user1
by Zoong Pham 02 Sep '04

02 Sep '04

I lately see lots of message like this in my maillog: Sep 1 11:12:31 onion pop3-login: Login: user1 [203.11.35.29] Sep 1 11:12:31 onion pop3(tekciz): File isn't in mbox format: /var/mail/user1 Sep 1 11:12:31 onion pop3(tekciz): File isn't in mbox format: /var/mail/user1 Sep 1 11:12:31 onion pop3: I/O leak: 0x1c00881c (0) Sep 1 11:12:31 onion pop3: I/O leak: 0x1c034f1c (1) Sep 1 11:12:31 onion pop3: Timeout leak: 0x1c01a3e8 I have: - OS: OpenBSD-3.5 with all the patches. - Sendmail 8.12.11 - dovecot-0.99.10.9 (configured like this: ./configure --without-pam --without-shadow --without-vpopmail --localstatedir=/var --with-ssldir=/etc/ssl --with-ssl=openssl Does anyone know what's happening? Thanks, Zoong PHAM ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

[Dovecot] sig11 with test36/37 on some emails
by Peter Hessler 01 Sep '04

01 Sep '04

Sometimes I'll get an email from a luser which will cause the POP3 daemon to sig11. The email "appears" to be legal. The sig11s only happen on specific emails, and once I remove the emails from the server, the rest can be downloaded. I gzipped the email, and its at http://theapt.org/bogusemail.gz. While this example is international spam, the sig11s happen with real emails too. -- Entropy isn't what it used to be.

3 4

[Dovecot] Strange behavior
by DR 01 Sep '04

01 Sep '04

Hi, I'm using dovecot under fedora core 2. Nearly everything seems to work. Dovecot was easily to configure and is a really smart program. BUT ... I figured out a problem. Whenever I fetch my mails (pop3s) using Outlook, TheBat or Pegasus, the mails on the server will not be marked as read. Sometimes I don't have a nice GUI mail client, than I use pine (I love it, but I won't feed the trolls ;-)). All messages, which I have already received are marked as new in pine or my webinterface squirrelmail. It seems, that dovecot doesn't mark the messages as read after fetching them. There are no strange entries in the logs, nothing which seems to be mysterious. Can anyone help me? This problem teases me. Cheers, DuRu

3 2

[Dovecot] starting/stopping Dovecot
by Tom Metro 31 Aug '04

31 Aug '04

http://www.dovecot.org/doc/INSTALL > Once everything is configured, there's two ways to start Dovecot: > > 1) Run "dovecot" binary which does everything. > > 2) Start it via inetd or similiar by executing "imap-login" or "pop3-login" > binaries. If you're listening in SSL port, add --ssl parameter. What are the pros and cons of using 'dovecot' vs. inetd. This may seem silly, but I noticed that there isn't any documentation saying what is the proper way to kill Dovecot. I assume it is to kill the 'dovecot' process. This is indirectly addressed in the Wiki: 6. Why can't I change the log location? http://wiki.dovecot.org/moin.cgi/QuestionsAndAnswers#head-c9650f53dd4f7ca2b… though the first few examples refer to <pid> without identifying the pid of what. Maybe adding a "How do I start Dovecot?" and "How do I stop Dovecot?" as the first two items on that page would be a good idea, and then the log file question and "7.1 Dovecot isn't running." and "8. Why doesn't Dovecot listen on localhost (127.0.0.1)?" could refer to those. (If this sounds reasonable, I'll update the Wiki.) Any plans to support a /var/run/dovecot/pid file or similar? What are your thoughts on including an init.d script in the distribution. I know some of the binary distributions will have platform-specific scripts included, but it might be good to include a generic one for those who build from source. -Tom

4 4

[Dovecot] 0.99.11 release candidate
by Timo Sirainen 31 Aug '04

31 Aug '04

http://dovecot.org/rc/ So, we're back into 3 digit version numbers, 0.99.10.10 would have looked too ugly. Originally I was planning on making 0.99.10.x series only for a few months and leave 0.99.11 for the larger changes, but 1.0- tests are now used for that. Version numbering is difficult. So, assuming there are no problems found from this RC, I'll release 0.99.11 tomorrow. Changes are: + 127.* and ::1 IP addresses are treated as secured with disable_plaintext_auth = yes + auth_debug setting for extra authentication debugging + Some documentation and error message updates - If APPENDed mail ended with CR character, Dovecot aborted the saving - Output streams sometimes sent data duplicated and lost part of it. This could have caused various strange problems, but looks like in practise it rarely caused real problems.

1 0

[Dovecot] User Auth problems
by Nikolaus Gerstmayr 31 Aug '04

31 Aug '04

Hi ! Problem: Auth doesn't work, can't figure out why :( More precisely: setup: dovecot 0.99.10.9 pop3 only Userdb + Passwd via passwd-file. Anything plaintext. (communication client server, passwords in passwd-file, well, for first tests non public server... if I get it working, I'll try better ways - of course) non standard parts of my config: protocols = pop3 ssl_disable = yes auth = default auth_mechanisms = plain auth_userdb = passwd-file /passwd_file auth_passdb = passwd-file /passwd_file auth_verbose = yes /passwd_file content: nick#sales.blabla:{PLAIN}test:500:500::::/mail/nick well, syntax is not 100% obvious from docu, but that's the way I understood it. (examples would be nice) That's how I understood semantics: If client sends user nick#sales.blabla and password test, dovecot accesses /mail/nick (maildir) with UID 500, GID 500 ???? problem: Auth fails. In logfiles I get this: dovecot-auth: Aug 30 22:36:20 Info: mech-plain(nick#sales.blabla): invalid username. (So no typo in mail client account setup or anytihng like this). Of course clients says auth fialed as well. Well, nick#sales.blabla is not a user on the test machine, but that's on purpose. It IS in /passwd-file :/ Anyone any idea ? Thx i.A for help !

2 1

[Dovecot] [PATCH] [RFC] epoll based ioloop handler (now with patch)
by Andrey Panin 30 Aug '04

30 Aug '04

Sorry, I forgot to attach patch to previous mail. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] [PATCH] NTLM fixes
by Andrey Panin 30 Aug '04

30 Aug '04

Hello, attached patch contains small NTLM fixes: - open code ntlmssp_des_encrypt_triad() function; - add two missing safe_memset(). It's not safe to leave NTLM hashes on the stack, because they are plain password equivalents. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] Problems with registering new emails - imap/jfs/maildir
by Trond Eivind Glomsrød 29 Aug '04

29 Aug '04

After changing a mailserver from using mbox/ext3 (RHL9) to Maildir/jfs (RHEL 3), dovecot 0.99.10 no longer reports new email even if asked... I have to restart the mail client and do a fresh login to notice new email. This happens with multiple mail clients on multiple platforms, and didn't happen before the conversion... any suggestions on workarounds? -- Trond Eivind Glomsrød Senior Software Engineer Scali - www.scali.com High Performance Clustering

2 6

[Dovecot] permission denied?
by Alex 29 Aug '04

29 Aug '04

I configured dovecot with Postfix with mysql Now I have directory /home/mail/virtual User/group postfix.postfix I added one domain, and one user. I login is successful but it gets interupted because of this. pop3(xx(a)private-projects.net): Aug 11 00:48:53 Error: lstat(/home/mail/virtual/private-projects.net/xx@private-projects.net/cur) failed: Permission denied pop3(xx(a)private-projects.net): Aug 11 00:48:53 Error: lstat(/home/mail/virtual/private-projects.net/xx@private-projects.net/cur) failed: Permission denied pop3(xx(a)private-projects.net): Aug 11 00:48:53 Warning: I/O leak: 0x8050cc0 (0) pop3(xx(a)private-projects.net): Aug 11 00:48:53 Warning: I/O leak: 0x8084e90 (1) [root@octalys dovecot]# ls -la /home/mail/virtual/private-projects.net/xx\(a)private-projects.net/cur/ total 8 drwxrw---- 2 postfix postfix 4096 Aug 2 21:47 . drwxrw---- 5 postfix postfix 4096 Aug 2 21:47 .. [root@octalys dovecot]# I added dovecot user to postfix group. I even tried chmod -R 777 * in virtual. It doesn't work. Whats the problem ?

3 5

[Dovecot] MySQL passdb, auth_verbose, and documentation
by tmetro+dovecot＠vl.com 28 Aug '04

28 Aug '04

I've been playing around with Dovecot for the past few months for testing (on a Debian 3.0 system), and initially it was easy to setup and worked well. Recently I upgraded to 0.99.10.9, and when I rebuilt it I enabled MySQL and SSL. The first problem I ran into was upon startup it complained that there was no certificate, which makes sense, except that I hadn't enabled imaps in the config file. It would make more sense not to require SSL support files if SSL isn't being used. But this is minor. I encountered more serious problems when I tried migrating from real user accounts to virtual accounts via MySQL. Has anyone written a howto on setting up Dovecot with MySQL? (Just pointing to dovecot-mysql.conf leaves out a lot.) If not, I'll volunteer to write something up. I set up dovecot-mysql.conf as I thought it should be, created a database, added a record with a digest-md5 password, and changed some dovecot.conf directives as follows: default_mail_env = maildir:/var/mail/%d/%n/ auth_mechanisms = digest-md5 auth_default_realm = example.com auth_userdb = static uid=5000 gid=5000 home=/var/mail/%d/%n/ auth_passdb = mysql /etc/dovecot-mysql.conf For the static auth_userdb I wasn't quite sure what to put after home= as I wasn't really defining a home directory location. I initially tried making it identical to default_mail_env, but later learned that it clearly didn't like the "maildir:" prefix. Some questions the documentation left unanswered: Is home= required if default_mail_env will suffice for virtual users? Can mail= be used instead, as implied by the database documentation? Practically speaking, is there any difference between the two in the case of virtual user accounts? I tried to access Dovecot from a mail client and repeatedly received a login failure. Unfortunately, this is typical of what I saw in the log file: Aug 8 03:53:50 lex dovecot: Dovecot starting up Aug 8 03:53:52 lex dovecot-auth: MySQL: connected to localhost Aug 8 03:55:13 lex imap-login: Disconnected: Inactivity [192.168.0.200] I enabled auth_verbose: auth_verbose = yes and checked my syslog.conf to make sure all priorities were being logged: mail.* /var/log/syslog/mail.log but still no additional verbosity. How should things look different when auth_verbose is enabled? Checking MySQL's log I could see that Dovecot was successfully connecting to the database server, but never executing any queries. I was going to next turn on logging of all IMAP traffic, but noticed the Wiki suggested trying a manual session, which I did: % telnet localhost imap * OK dovecot ready. 1 LOGIN tmetro(a)example.com password 1 NO Login failed: Unsupported authentication mechanism Isn't this the kind of thing that should appear in the log when auth_verbose is enabled? That seemed odd, as 'digest-md5' is mentioned right in dovecot.conf as a valid choice. In retrospect, I gather what the message above is trying to tell me is that Dovecot wasn't configured to accept a 'plain' authentication, which is apparently what I was using in my manual session. It would be nice if the error message could express that a bit better. I did have some suspicion that it might be the that plain text authentication was being prevented, as at that point I didn't know what auth_mechanisms applied to, but I looked at dovecot.conf and found disable_plaintext_auth = no, which seemed to imply that plain text at the IMAP protocol level should have been permitted. Might it be clearer if that attribute was incorporated into the auth_mechanisms settings or at least moved into the auth section? I switched it to 'plain-md5', as mentioned in auth.txt, and tried again. That resulted in: Aug 8 21:11:53 lex dovecot-auth: Unknown authentication mechanism 'plain-md5' Aug 8 21:11:53 lex dovecot: Auth process died too early - shutting down Aug 8 21:11:53 lex dovecot: child 10293 (auth) returned error 89 Aug 8 21:11:53 lex imap-login: fd_send(-1) failed: Broken pipe That got me wondering whether there were two different areas where authentication terms apply - one being the password exchange in the IMAP protocol, and the other being how the password is stored on the server - yet the discussion of the two seems to be mixed together in the documentation. I tried switching to: auth_mechanisms = plain and finally got something more expected: Aug 8 21:20:44 lex dovecot-auth: mysql(tmetro(a)example.com): Password mismatch I tried putting the password into the database unencrypted, but that didn't work (probably because of my default_pass_scheme setting?). Generating a PLAIN-MD5 per auth.txt finally worked. This leads to some questions: auth_mechanisms doesn't seem to be describing the way in which the password is stored, so what does it describe? In dovecot-mysql.conf I had: default_pass_scheme = DIGEST-MD5 and didn't change it. What purpose does it serve? Is it only to identify the encryption used when there isn't a {SCHEME} tag present? For DIGEST-MD5, which encrypts "user:realm:pass", does realm include the @? Does user include @realm? I assumed no in both cases, yet it didn't work. In other matters...during one of my login attempts I got: * OK dovecot ready. 1 LOGIN tmetro(a)example.com password 1 OK Logged in. Connection closed by foreign host. The abrupt disconnect after an apparently successful login seemed odd. The log file showed: Aug 8 21:23:47 lex dovecot: chdir(maildir:/var/mail/example.com/tmetro/) failed with uid 5000: Permission denied Aug 8 21:23:47 lex dovecot: child 10315 (imap) returned error 89 which is the problem I discussed above, but is it reasonable for Dovecot to disconnect the IMAP socket and not send an error message to the client? At the end of the dovecot-example.conf is: #auth = digest_md5 #auth_methods = digest-md5 #auth_realms = #auth_userdb = passwd-file /etc/passwd.imap #auth_passdb = passwd-file /etc/passwd.imap #auth_user = imapauth #auth_chroot = Is auth_methods an alias for auth_mechanisms? Aside from the insufficient detail in the log, most of the difficulty I encountered could be avoided with better documentation and comments in the config files. I'd be happy to submit clarified comments once I get some answers to the above questions and confirm my understanding of how things work. -Tom

10 22

[Dovecot] Authentication and Startup/Shutdown error.
by Andrew Lietzow 28 Aug '04

28 Aug '04

Hello and ... help! I am using Redhat FC2. I was looking for a simple POP3 compatible application package that would allow growth into secure mailboxes, and it looks like dovecot can fill the bill, and then some. I am a newbie. I scanned the Wiki but am as confused by it as I am by my problems. Fortunately for me, I don't need 7 different authentication schemes; I just need something simple that works with Thunderbird and Outlook Express. Is there a HOW-TO around that shows simple pop3 setup on Linux? #1) I had the pop3-login working for a bit, but now it has stopping starting up. When I attempt a <./dovecot stop>, I get a message that the stop has [FAILED]. I believe this is because it is leaving a lock in the /var/lock/subsys directory. I delete that file and try again, same problem. The system starts okay, but there are no longer any pop3-login processes being started up. <ps -elf | egrep pop3*> returns nothing but the grep process. #2) I need a simple method to access email. Nothing fancy as I only have a couple of users. Terrorists woud be wasting their time to monkey with my server. In the dovecot.conf file, here are a few of my settings. pop3_executable = /usr/libexec/dovecot/pop3 pop3_process_size = 256 auth = passwd auth_mechanisms = plain auth_realms = auth_default_realm = auth_userdb = passwd: /etc/passwd auth_passdb = passwd: /etc/passwd auth_executable = /usr/libexec/dovecot/dovecot-auth auth_process_size = 256 auth_user = root auth_count = 2 Any help would be greatly appreciated, of course. I'll keep scanning the web site while I am at your mercy. TIA, Andrew L. in Iowa _____________________________________________________________________ Get your own family web site at www.MyFamily.com!

4 3

[Dovecot] 1.0-test37
by Timo Sirainen 28 Aug '04

28 Aug '04

http://dovecot.org/test/ - Added mbox_dirty_syncs setting, defaulting to yes. This means that while mbox is opened and new mails come, it only reads the new mails instead of the whole mbox. Then there's several checks that make sure this is safe to do and if something doesn't look right it fallbacks to syncing the whole mbox again. - dovecot-auth was leaking memory (not same bug as with 0.99/ldap) - Some other fixes

1 0

[Dovecot] 1.0-test36
by Timo Sirainen 28 Aug '04

28 Aug '04

http://dovecot.org/test/ Fixes mostly. Seems to be working quite well with me nowadays with mboxes. If you see any crashes or other problems please report.

2 1

[Dovecot] ldap without bind
by Cedric Foll 28 Aug '04

28 Aug '04

Is it possible to connect to the ldap server without bind (ie anonymous access). How can I do that ? Regards.

2 1

Re: [Dovecot] Authentication and Startup/Shutdown error.
by Andrew Lietzow 28 Aug '04

28 Aug '04

Tim, Thanks for the reply. I did check the maillog quite a bit. Fortunately, I had kept an orig of the dovecot.conf file so I rolled back to the example I found on the dovecot.org website and now it's up and running. It's all smoke and mirrors to me, mostly, but at least it's working for now. I'll come back to this question of implementing TLS or SSL later, in my voluminous spare time. It appears to be a very powerful program and should carry me through to the next millenium... Ciao and Muchos Gracias, Andrew in Iowa, USA -----Original Message----- From: Tim Miller <tim(a)gem.win.co.nz> Sent: Friday, August 27, 2004 10:33 PM To: Andrew Lietzow <alietzow(a)myfamily.com> Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] Authentication and Startup/Shutdown error. On Fri, 27 Aug 2004, Andrew Lietzow wrote: > Hello and ... help! (snip of problem) When setting up Dovecot, I found that a lot of helpfull information was put into /var/log/maillog (or wherever syslogd sends mail logs on your system). Since you didn't post anything from that file, I'm not sure if you consulted it. Best, Tim M. _____________________________________________________________________ Get your own family web site at www.MyFamily.com!

1 0

[Dovecot] dovecot-1.0-test32-error
by jls＠tj.se.gov.br 28 Aug '04

28 Aug '04

I installed dovecot-1.0-test32 and I present the following error in some users: Error: IMAP(user): Buffer full (46) How to solve this problem?

2 1

[Dovecot] Just installed with Fedora 2
by Michael J. Pawlowsky 26 Aug '04

26 Aug '04

I just upgraded my RH9 installation to Fedora 2. To my surprise, imapd seems to be gone from the core. I noticed there are now two IMAP servers docevot and cyrus. After reading brief descriptions of both, dovecot would seem to be more compatible with my setup. Especially since I'm using mbox's. I have 2 questions. It seems like dovecot does not support mailboxes inside of a directories. Am I right in thinking this? Second I get the error message: The current command did not succeed. The mail server responded: Error in IMAP command MYRIGHTS: Unknown command. My client is Thunderbird. Any work around for this? Thanks, Mike

4 4

[Dovecot] 0.99.10.x auth memory leak?
by Christian Balzer 26 Aug '04

26 Aug '04

Hello, running 0.99.10.6 (but seen it before that, too). Also (quite obviously) running 5 auth processes, given the fact that this is a pretty busy box and I didn't want to introduce any artificial bottlenecks. Alas with them eating up half of the free memory (which would go to a much better use as FS cache) I'm getting sorta concerned. If it's not a leak, it's caching something rather needlessly and inefficiently (the LDAP DB memory footprint for ALL users is less than this and the box below just serves half of those). This box sees about 0.5 million POP3/IMAP logins/day. --- PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 31235 root 16 0 220m 216m 5560 S 0.0 10.7 25:01.54 dovecot-auth 31234 root 16 0 205m 202m 5560 S 0.0 10.0 24:08.84 dovecot-auth 31231 root 16 0 200m 196m 5560 S 0.7 9.7 23:25.37 dovecot-auth 31232 root 16 0 196m 192m 5560 S 0.0 9.5 23:10.44 dovecot-auth 31233 root 15 0 179m 175m 5560 S 0.3 8.6 22:13.07 dovecot-auth --- So, I guess my questions to Timo are: Think it's leaky and any idea where? Given the load, would a single auth process be a bad idea? (it is a quite fast dual opteron box) Regards, Christian Balzer -- Christian Balzer Network/Systems Engineer NOC chibi(a)gol.com Global OnLine Japan/Fusion Network Services http://www.gol.com/

3 5

[Dovecot] [PATCH] pass struct io * to io_loop_handle_add()/io_loop_handle_remove()
by Andrey Panin 25 Aug '04

25 Aug '04

Hello, currently I'm working on new ioloop handler which uses epoll(4) API introduced in Linux kernel 2.6. In this API each fd added to fd set by epoll_ctl system call can be accompanied with user supplied data (integer or void pointer). epoll_wait syscall reports arrived events as an array of structures containing event mask and user data. Attached patch replaces fd and condition parameters passed to io_loop_handle_add() with struct io pointer. Now io_loop_handle_add() can pass this pointer as user data to epoll_ctl syscall and when event arrives we will have corresponding io structure pointer for free withiot traversing possibly long ioloop->ios list. Please take a look. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 5

[Dovecot] FreeBSD - dovecot: We couldn't drop root group privileges
by Igor B. Bykhalo 25 Aug '04

25 Aug '04

Hi, I installed Dovecot on FreeBSD 4-STABLE machine and have a problem. MTA is postfix delivering to ~/Maildir, runs perfectly. Dovecot is configured to use plaintext auth, config file is at the end of this mail. When trying to get mail via IMAP, I'm getting the following errors: /var/log/dovecot.log > Aug 24 12:00:35 Info: Dovecot starting up > Aug 24 12:00:51 Info: Login: goshik [193.233.44.234] /var/log/maillog > Aug 24 12:00:51 banka dovecot: We couldn't drop root group privileges > Aug 24 12:00:51 banka imap(goshik): child 2045 (imap) returned error 89 Am I missing something? What was done incorrectly? Help please, Igor -------------------------------------------- /usr/local/etc/dovecot.conf > ## Dovecot 1.0 configuration file > > #base_dir = /var/run/dovecot/ > > protocols = imap pop3 > imap_listen = 193.233.44.213 > pop3_listen = 193.233.44.213 > ssl_disable = yes > > #disable_plaintext_auth = no > > #log_path = > info_log_path = /var/log/dovecot.log > #login_dir = /var/run/dovecot/login > #login_chroot = yes > > login = imap > login_user = dovecot > > login = pop3 > > #max_mail_processes = 1024 > verbose_proctitle = yes > #verbose_ssl = no > #first_valid_uid = 500 > #last_valid_uid = 0 > first_valid_gid = 0 > #last_valid_gid = 0 > > valid_chroot_dirs = /var/mail > #mail_chroot = > > default_mail_env = maildir:%h/Maildir > > #mail_cache_fields = MessagePart > #mail_never_cache_fields = > > client_workarounds = oe6-fetch-no-newmail outlook-idle outlook-pop3-no-nuls > > #mail_full_filesystem_access = no > #mail_max_flag_length = 50 > #mail_save_crlf = no > #mail_read_mmaped = no > > #maildir_stat_dirs = no > maildir_copy_with_hardlinks = yes > #maildir_check_content_changes = no > > #umask = 0077 > > mail_drop_priv_before_exec = no > > #imap_executable = /usr/local/libexec/dovecot/imap > #imap_process_size = 256 > #imap_use_modules = no > #imap_modules = /usr/local/lib/dovecot/imap > > #pop3_executable = /usr/local/libexec/dovecot/pop3 > #pop3_process_size = 256 > #pop3_use_modules = no > #pop3_modules = /usr/local/lib/dovecot/pop3 > > auth = default > auth_mechanisms = plain > #auth_realms = > #auth_default_realm = > auth_userdb = passwd > auth_passdb = passwd > #auth_executable = /usr/local/libexec/dovecot/dovecot-auth > #auth_process_size = 256 > auth_user = root > #auth_chroot = > #auth_count = 1 > #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ > #auth_anonymous_username = anonymous > auth_verbose = yes > > #auth = digest_md5 > #auth_methods = digest-md5 > #auth_realms = > #auth_userdb = passwd-file /etc/passwd.imap > #auth_passdb = passwd-file /etc/passwd.imap > #auth_user = imapauth > #auth_chroot =

2 4

[Dovecot] UIDPLUS Status?
by Chris Alexander 25 Aug '04

25 Aug '04

I saw in the archives that UIDPLUS had been removed from dovecot back in June. Are there any plans to re-implement? I have a Windows/Eudora user that wants UIDPLUS so the client side spam filtering works. Thanks. -- Chris Alexander UNIX Network Administrator, Information Networks and Systems Division Communications Research Centre [ http://www.crc.ca ] Government of Canada [ http://www.gc.ca ]

2 1

[Dovecot] Problem with emails larger than 10k
by Peter Hessler 25 Aug '04

25 Aug '04

I cannot download emails that are larger than 10k. I can download them fine with test32. I am running test35 on OpenBSD/macppc -current. I am downloading the files with Sylpheed-Claws 0.9.9claws on OpenBSD/macppc -current (different machines), over pop3-ssl on IPv6. Problem still occurs with IPv4. On the large files, the download hangs at 4.0k. Multiple small emails work fine. -- A day for firm decisions!!!!! Or is it?

2 1

[Dovecot] [PATCH] move highest_fd calculations to ioloop-select.c
by Andrey Panin 25 Aug '04

25 Aug '04

Hello, ioloop->highest_fd is used by ioloop-select.c only, so its handling can be moved out of generic ioloop code. Attached patch (agains -test35) does exactly this. Please consider applying. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] Re: ssl_ca_file
by jan＠weitan.org 24 Aug '04

24 Aug '04

> I am using 0.99.10.7-1 on Debian, and I'm having some trouble with SSL. I > purchased a certificate from Thawte and I can't figure out how to tell > dovecot about the CA cert. Adding ssl_ca_file to my configuration produces > "Unknown setting: ssl_ca_file" on dovecot startup. > > Postfix has a smtpd_tls_CAfile argument and that part is working fine. > > Is this a Debian-specific problem or is ssl_ca_file newer than 0.99.10.7? I guess ssl_ca_file is newer than 0.99. I have the same settings (debian -sarge) and i am using ssl_cert_file and ssl_key_file to get the certificate working. I checked ssl_ca_file and i got the same error, nevertheless it's in the recent dovecot.conf file from 1.x.testing, therefore it should be newer than 0.99.

1 0

[Dovecot] Unknown setting: ssl_ca_file
by Jacob Elder 24 Aug '04

24 Aug '04

I am using 0.99.10.7-1 on Debian, and I'm having some trouble with SSL. I purchased a certificate from Thawte and I can't figure out how to tell dovecot about the CA cert. Adding ssl_ca_file to my configuration produces "Unknown setting: ssl_ca_file" on dovecot startup. Postfix has a smtpd_tls_CAfile argument and that part is working fine. Is this a Debian-specific problem or is ssl_ca_file newer than 0.99.10.7? -- Jacob Elder

1 0

[Dovecot] Underquoted macros in aclocal (was: MIME structure intermittently lost)
by Kenneth Porter 24 Aug '04

24 Aug '04

--On Monday, August 23, 2004 6:50 PM +0900 Jim Tittsler <jt(a)OnJapan.net> wrote: > You can get dovecot-0.99.10.9-1.FC3.2.src.rpm from the > Fedora Core development tree. (Seems to be working well for us.) I just built this and it has a lot of complaints about underquoted macros in aclocal. Red Hat refers developers to this reference: <http://sources.redhat.com/automake/automake.html#Extending%20aclocal>

1 0

[Dovecot] 1.0-test35
by Timo Sirainen 23 Aug '04

23 Aug '04

http://dovecot.org/test/ Test33/34 weren't usable for very long. Test35 fixes several problems in them.

1 0

[Dovecot] Newbie: dovecot not running.
by Simon Waters 23 Aug '04

23 Aug '04

Okay, sure it must be trivial.... I have old Redhat box, want a quick and dirty IMAP server, thought good time to try out dovecot (I'd rather it had Debian on too ;). Downloaded and compiled from source - no options to configure. Auth data is in /etc/passwd and /etc/shadow (as well as NIS). vi /usr/local/etc/dovecot.conf as expected. Disable ssl in conf. Basically email is in mbox format in /var/spool/mail/%u Should go somewhere ~%u/mail is fine, as would be ~%u/Mail (I don't care at the moment). created a user "dovecot..." to run as and edited conf file. If I run /usr/local/sbin/dovecot it terminates without errors, the fork is completing I think, and the main program returns as expect. Running imap-auth from xinetd gets me a greeting banner, but then the connection is closed. Trying to run "imap" directly just dies in a blizarrd of "dot locking" errors and the like, where it seems to ignore the locking directives (should I set an env or some such?), but I think that it is basically running (it creates indexes in ~/mail/...mumble) but complains about the dotlocking, and then spews an internal error (which it claims is logged to server log?). I'm off to try auth_verbose, but any tips or hints appreciated. I'm assuming /usr/local/sbin/dovecot is what was called "master" given it is in the master src directory. Simon

1 1

[Dovecot] 1.0-test33
by Timo Sirainen 23 Aug '04

23 Aug '04

http://dovecot.org/test/ I think I found and fixed the last bug that was giving me problems. Now that Dovecot has been successfully working for a few hours, time for a new test release :) This release has major changes, so there might still be some bugs left. Be careful. If you're upgrading from previous 1.0-test release, you must delete all existing dovecot.index.log files or you will get errors. So, the changes are: - All network sockets are nonblocking now and all the waiting is done in a single event loop. This required tons of changes all over the code. - Transaction log file doesn't use locks for reading anymore - Some mbox fixes - search text was broken

2 2

[Dovecot] MIME structure intermittently lost
by Kenneth Porter 23 Aug '04

23 Aug '04

I'm using Dovecot-0.99.10.5-0.FC2 on Fedora Core 2 on the server, and Mulberry 3.1.6 over Win2kSP4 on the client. Intermittently messages with multiple parts show up as a single text part. I'm not sure if it's Mulberry or Dovecot. I just turned on IMAP logging and restarted Mulberry and a message with two text/plain parts that wasn't showing the 2nd part is now displaying it correctly. I hate heisenbugs!

3 3

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 23 Aug '04

23 Aug '04

Ahh! Now you've explained it, it makes a lot of sense. Many thanks, Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Timo Sirainen [mailto:tss@iki.fi] Sent: 23 August 2004 09:07 To: Mark Lidstone Cc: dovecot(a)dovecot.org Subject: RE: [Dovecot] Unusual behaviour On Mon, 2004-08-23 at 08:48 +0100, Mark Lidstone wrote: > Is it supposed to give the current time and date in the error message. > I've no problem with it giving an "internal error" message to the > client, but I am a little confused about the time being in there. > That's all I'm asking about. Client should never see any "real" error messages to make sure no extra information about the system gets leaked. So any time something unexpected happens, Dovecot gives the "internal error" message to user while writing the real error to log file. The timestamp is there to help sysadmin find the real error message from log files when user gives a copy&pasted internal error message. Instead of timestamp I guess there could be also some unique identifier which could be grepped from logs but I think timestamp is better. And about the original problem of giving "internal error" when Dovecot process didn't have access to some maildir.. Maybe it could have replied "Permission denied" to client in that case. It already does in several cases, but I guess the problem here was that it was trying to create the missing dirs but couldn't. I'll look over all these permission issues properly when creating real shared folder support.

1 0

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 23 Aug '04

23 Aug '04

OK, last try. Is it supposed to give the current time and date in the error message. I've no problem with it giving an "internal error" message to the client, but I am a little confused about the time being in there. That's all I'm asking about. Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Andrew Boothman [mailto:andrew@mux.org.uk] Sent: 20 August 2004 18:09 To: Dovecot list Subject: Re: [Dovecot] Unusual behaviour Mark Lidstone wrote: > I thought that Dovecot was supposed to handle that kind of thing? > Reading from the website: > > "Any kind of crash is considered as bug and will be fixed - even if > it happens only by deliberately poking the index files." > > I've done it in the past by just creating the bare folders - they > appear in the IMAP folder list then when they're used Dovecot seems to > create the sub folders anyway. > > The issue I'm asking about here is, should the error message say > "Internal Error [date time]" rather than something useful? Did Dovecot actually crash? Did it log a more sensible error message to syslog? I think Dovecot quite often reports an "internal error" to the client but then writes a more sensible error message to syslog. Which is probably no bad thing as you may well not want clients to see detailed error messages - there's nothing they can do about it anyway. Andrew

2 1

[Dovecot] Multiple dovecot processes stepping on each other
by Peter Hessler 23 Aug '04

23 Aug '04

I have two instances of dovecot running, one for v6 and one for v4 connections. The only differences in the config files are: --- /etc/dovecot-ip6.conf Wed Aug 18 11:15:43 2004 +++ /etc/dovecot-ip4.conf Wed Aug 18 11:09:17 2004 @@ -10,7 +10,7 @@ # *** NOTE *** Some values HAVE been changed for OpenBSD use. # Base directory where to store runtime data. -base_dir = /var/dovecot-v6/ +base_dir = /var/dovecot-v4/ # Protocols we want to be serving: # imap imaps pop3 pop3s @@ -23,7 +23,7 @@ # "host:port", although with multiple protocols you probably want to move # this setting inside protocol imap/pop3 { ... } section, so you can # specify different ports for IMAP/POP3. -listen = [::] +listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. For the most part it is working, but every so often, the auth freaks out for one (random) account. The error for one example is below: Aug 18 11:13:12 gir dovecot: login: Authentication process 21082 doesn't exist Aug 18 11:13:12 gir dovecot: pop3-login: Internal login failure: phessler [208.201.244.164] This happens on both v4 and v6 connections, but infrequently. If you try again immediatly, it works. If I do a `ps -p 21082` I can see the process (dovecot-auth). This does not happen when I have only one dovecot process running. What is the best way to have multiple dovecot processes without them stepping on each others toes? This is on OpenBSD/macppc -current, running dovecot-1.0-test32. -- Mosher's Law of Software Engineering: Don't worry if it doesn't work right. If everything did, you'd be out of a job.

2 4

[Dovecot] Dovecot stop accepting command When reading disk quota (soft)
by Chan Min Wai 23 Aug '04

23 Aug '04

Hello all, I've face some problem here and I think it should be the way. 1) I'm running Dovecot version 0.99.10.4 (fc1 release) on RH9 2) One of the users have reach the soft disk quota limits 3) Dovecot stop the users from deleting email. What I think was, dovecot should let the user continue to use the services until it reach the hard limits, but pop up message each and every time ;). Anyone have that problem before? Thank You Chan Min Wai

3 3

[Dovecot] Sent, Drafts, Trash folders
by Jason M. Wilde 23 Aug '04

23 Aug '04

I am hosting imap mail for a new affiliate and am offering webmail via squirrelmail as well. Squirrelmail created INBOX.Sent, INBOX.Trash, etc by default and I would like to use these folders for my Dovecot imap users. I am using the mbox format, Postfix and users retrieve mail via the Outlook client remotely in addition to webmail access. Thank you for any help. Jason

2 1

[Dovecot] What about saving your INBOX at ~/mbox ?
by Nico Kadel-Garcia 23 Aug '04

23 Aug '04

Hi, folks. I'm testing out RedHat's "Fedora Core 2" release, which has switched from the old WashU imapd to dovecot-0.99.10. Overall, this looks like a really, really good move on their part: it looks like a very sweet little tool without some of the ingrained idiocy of Mark Crispin insisting that every home directory consist of nothing but mbox files and allowing you to use a configurable subdirectory by default, ~/mail. Cool. There is one feature of the old WashU imapd that I miss, though. That daemonn could be configured to automatically transfer the user's email to the "~/mbox" upon activation of the daemon, effectively reducing the size of the /var/spool/mail/{username}" mail spool and helping keep the user's disk usage in their home directories, not in /var/spool/mail. This can be a good thing for various reasons. But I don't see any way to enable that behavior for dovecot. Is there something I'm missing, or do folks feel it would be reasonable to add? -- Nico Kadel-Garcia Systems Engineer Mitsubish Electric Research Lab <nkadel(a)merl.com>

4 6

[Dovecot] Is 1.0-test stabilising?
by Curtis Maloney 23 Aug '04

23 Aug '04

Has Timo backed off work, and been busy with something else, or has 1.0 really stabilised that much? Seems to me just a couple of weeks ago we were seeing a new test release every few days... now there's been nothing all month... I'm hoping it's ready for release... but if it's just that Timo's busy, well, I can understand that. We're about to receive some new servers, and I hope to migrate from 0.99 to 1.0 as we migrate to the new machines. -- Curtis Maloney

3 3

RE: [Dovecot] Unusual behaviour
by Mark Lidstone 20 Aug '04

20 Aug '04

I thought that Dovecot was supposed to handle that kind of thing? Reading from the website: "Any kind of crash is considered as bug and will be fixed - even if it happens only by deliberately poking the index files." I've done it in the past by just creating the bare folders - they appear in the IMAP folder list then when they're used Dovecot seems to create the sub folders anyway. The issue I'm asking about here is, should the error message say "Internal Error [date time]" rather than something useful? Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== == -----Original Message----- From: Keith Edmunds [mailto:keith@midnighthax.com] Sent: 20 August 2004 12:42 To: dovecot(a)dovecot.org Subject: Re: [Dovecot] Unusual behaviour On Fri, 20 Aug 2004 11:26:44 +0100 "Mark Lidstone" <mlidstone(a)bmtseatech.co.uk> wrote: > I've just noticed something strange in dovecot 0.99.10.5. I created > some IMAP folders from the command line (mkdir .INBOX.Folder1) No: you created a directory. IMAP folders need cur/ tmp/ and new/ as subdirectories under the new folder directory. Keith -- ---------------------------------------------------------------------- Small business computer support: http://www.tiger-computing.co.uk Linux consultancy: http://www.TheLinuxConsultancy.co.uk ----------------------------------------------------------------------

2 1

[Dovecot] Unusual behaviour
by Mark Lidstone 20 Aug '04

20 Aug '04

Hi, I've just noticed something strange in dovecot 0.99.10.5. I created some IMAP folders from the command line (mkdir .INBOX.Folder1) as a different user to the owner of the mailbox. Obviously when I tried to view them via IMAP I got an error message, but the message to the client was "internal error[date time]" where date and time appeared to be the current date and time. Is this correct behaviour? Dovecot was running on FC2, and the client was Mozilla Thunderbird under Windows. Mark Lidstone IT and Network Support Administrator BMT SeaTech Ltd Grove House, Meridians Cross, 7 Ocean Way Ocean Village, Southampton. SO14 3TJ. UK Tel: +44 (0)23 8063 5122 Fax: +44 (0)23 8063 5144 E-Mail: mailto:mark.lidstone@bmtseatech.co.uk Website: www.bmtseatech.co.uk ======================================================================== == Confidentiality Notice and Disclaimer: The contents of this e-mail and any attachments are intended only for the use of the e-mail addressee(s) shown. If you are not that person, or one of those persons, you are not allowed to take any action based upon it or to copy it, forward, distribute or disclose the contents of it and you should please delete it from your system. BMT SeaTech Limited does not accept liability for any errors or omissions in the context of this e-mail or its attachments which arise as a result of Internet transmission, nor accept liability for statements which are those of the author and not clearly made on behalf of BMT SeaTech Limited. ======================================================================== ==

2 1

[Dovecot] Question: email system architecture
by Gland Vador 18 Aug '04

18 Aug '04

Hi, I have a question about how to implement a mail system, but I don't know where to ask. Until now, I have a mail system who receive mail by postfix and transport it through procmail to the /var/spool/mail/username mailbox. From here it is retrieved through dovecot (POP3). Now I have two more users, I want to implement a IMAP server, and also provide a webmail (squirrelmail) interface. And in order to filter spam, I want to install spamassassin. Until now it was thunderbird who made the filterring, but with a webmail interface it's no more possible. So suppose that I have configured procmail to deliver "good" mail in an Inbox folder and "spam" in a SPAM folder. This for each user mailbox. I also have configured dovecot as IMAP server and any IMAP client can see the two folder with spam and ham. And here comes my implementation problem. If a user see a "good" mail in his spam folder (or vice-versa) he will take this mail and move to his inbox folder. But, I want to be able to say to spamassassin to learn that this message is ham, with the command sa-learn, and also remove the x-spam* headers. And I don't see a good way to do that. In my opinion, it should be the MUA task, but spamassassin is server based. It's any way that dovecot when it moves the mail between tho folders can call an external script who will make this job in fonction of source/destination folder? Maybe it's a silly question (I don't know IMAP and his possibilities). In this case, can anyone explain (or point to) me a way to do that ? Sorry for this long message. Edd.

4 5

[Dovecot] We couldn't drop root group privileges.
by Greg M 16 Aug '04

16 Aug '04

Hello all, This is my first post to this list. I have tried finding this answer online but while it seems that there are some people out there asking, I cant seem to get an answer to it. I have installed Dovecot some many month ago, and just recently I have been getting an error while trying to log into one of my accounts that I used all the time. The error that comes up is pop3: We couldn't drop root group privileges I have seen where someone else has asked this same question, but there was no response to the list. Anyone have any ideas? I use squirrel mail to check the account as well as KMail (IMAP), and have even tried logging in through telnet to port 110 to see if it was a client issue, but it appears to be dovecot. I am using BSD 4.9 and Exim if that helps any. Thanks a bunch, for now I have to ssh into the machine to check my mail via PINE or mail. -Greg M.

2 1

[Dovecot] Imap process killed
by Yann Rouillard 16 Aug '04

16 Aug '04

Hi, I get the following message each time I try to access a mailbox. dovecot: [ID 684838 mail.error] child 27041 (imap) killed with signal 11 Using dovecot 1.0-test32 under Solaris 9. Using truss I get the following lines: 27041: read(0, " 2 s e l e c t " I N".., 4096) = 18 27041: open64("/var/mail/toto", O_RDWR|O_CREAT|O_EXCL, 0660) Err#17 EEXIST 27041: time() = 1092672589 27041: open64("", O_RDWR) Err#14 EFAULT 27041: Incurred fault #6, FLTBOUNDS %pc = 0xFF1B347C 27041: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 27041: Received signal #11, SIGSEGV [default] 27041: siginfo: SIGSEGV SEGV_MAPERR addr=0x00000000 I attached the complete result of the truss command and my configuration file. Any idea what is the problem ? Cheers, Yann ## Dovecot 1.0 configuration file # '#' character and everything after it is treated as comments. Extra spaces # and tabs are ignored. If you want to use either of these explicitly, put the # value inside quotes, eg.: key = "# char and trailing whitespace " # Default values are shown after each value, it's not required to uncomment # any of the lines. Exception to this are paths, they're just examples # with real defaults being based on configure options. The paths listed here # are for configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var # --with-ssldir=/etc/ssl # Base directory where to store runtime data. base_dir = /var/run/dovecot/ # Protocols we want to be serving: # imap imaps pop3 pop3s protocols = imap # IP or host address where to listen in for connections. It's not currently # possible to specify multiple addresses. "*" listens in all IPv4 interfaces. # "[::]" listens in all IPv6 interfaces, but may also listen in all IPv4 # interfaces depending on the operating system. You can specify ports with # "host:port", although with multiple protocols you probably want to move this # setting inside protocol imap/pop3 { ... } section, so you can specify # different ports for IMAP/POP3. #listen = * # IP or host address where to listen in for SSL connections. Defaults # to above if not specified. #ssl_listen = # Disable SSL/TLS support. ssl_disable = yes # PEM encoded X.509 SSL/TLS certificate and private key. They're opened before # dropping root privileges, so keep the key file unreadable by anyone but # root. Included doc/mkcert.sh can be used to easily generate self-signed # certificate, just make sure to update the domains in dovecot-openssl.cnf ssl_cert_file = /usr/local/public/ssl/certs/imapd.pem ssl_key_file = /usr/local/public/ssl/certs/imapd.pem # File containing trusted SSL certificate authorities. Usually not needed. #ssl_ca_file = # Request client to send a certificate. #ssl_verify_client_cert = no # SSL parameter file. Master process generates this file for login processes. # It contains Diffie Hellman and RSA parameters. #ssl_parameters_file = /var/run/dovecot/ssl-parameters.dat # How often to regenerate the SSL parameters file. Generation is quite CPU # intensive operation. The value is in hours, 0 disables regeneration # entirely. #ssl_parameters_regenerate = 24 # SSL ciphers to use #ssl_cipher_list = all:!low # Disable LOGIN command and all other plaintext authentications unless # SSL/TLS is used (LOGINDISABLED capability). Note that 127.*.*.* and # IPv6 ::1 addresses are considered secure, this setting has no effect if # you connect from those addresses. disable_plaintext_auth = no # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). #log_path = # For informational messages, use this logfile instead of the default #info_log_path = # Prefix for each line written to log file. % codes are in strftime(3) # format. #log_timestamp = "%b %d %H:%M:%S " ## ## Login processes ## # Directory where authentication process places authentication UNIX sockets # which login needs to be able to connect to. The sockets are created when # running as root, so you don't have to worry about permissions. Note that # everything in this directory is deleted when Dovecot is started. #login_dir = /var/run/dovecot/login # chroot login process to the login_dir. Only reason not to do this is if you # wish to run the whole Dovecot without roots. login_chroot = no # User to use for the login process. Create a completely new user for this, # and don't use it anywhere else. The user must also belong to a group where # only it has access, it's used to control access for authentication process. #login_user = dovecot # Set max. process size in megabytes. If you don't use # login_process_per_connection you might need to grow this. #login_process_size = 32 # Should each login be processed in it's own process (yes), or should one # login process be allowed to process multiple connections (no)? Yes is more # secure, espcially with SSL/TLS enabled. No is faster since there's no need # to create processes all the time. #login_process_per_connection = yes # Number of login processes to create. If login_process_per_user is # yes, this is the number of extra processes waiting for users to log in. #login_processes_count = 3 # Maximum number of extra login processes to create. The extra process count # usually stays at login_processes_count, but when multiple users start logging # in at the same time more extra processes are created. To prevent fork-bombing # we check only once in a second if new processes should be created - if all # of them are used at the time, we double their amount until limit set by this # setting is reached. This setting is used only if login_process_per_use is yes. #login_max_processes_count = 128 # Maximum number of connections allowed in login state. When this limit is # reached, the oldest connections are dropped. If login_process_per_user # is no, this is a per-process value, so the absolute maximum number of users # logging in actually login_processes_count * max_logging_users. #login_max_logging_users = 256 ## ## Mail processes ## # Maximum number of running mail processes. When this limit is reached, # new users aren't allowed to log in. #max_mail_processes = 1024 # Show more verbose process titles (in ps). Currently shows user name and # IP address. Useful for seeing who are actually using the IMAP processes # (eg. shared mailboxes or if same uid is used for multiple accounts). #verbose_proctitle = no # Show protocol level SSL errors. #verbose_ssl = no # Valid UID range for users, defaults to 500 and above. This is mostly # to make sure that users can't log in as daemons or other system users. # Note that denying root logins is hardcoded to dovecot binary and can't # be done even if first_valid_uid is set to 0. first_valid_uid = 200 last_valid_uid = 0 # Valid GID range for users, defaults to non-root/wheel. Users having # non-valid GID as primary group ID aren't allowed to log in. If user # belongs to supplementary groups with non-valid GIDs, those groups are # not set. #first_valid_gid = 1 #last_valid_gid = 0 # Grant access to these extra groups for mail processes. Typical use would be # to give "mail" group write access to /var/mail to be able to create dotlocks. #mail_extra_groups = # ':' separated list of directories under which chrooting is allowed for mail # processes (ie. /var/mail will allow chrooting to /var/mail/foo/bar too). # This setting doesn't affect login_chroot or auth_chroot variables. # WARNING: Never add directories here which local users can modify, that # may lead to root exploit. Usually this should be done only if you don't # allow shell access for users. See doc/configuration.txt for more information. #valid_chroot_dirs = # Default chroot directory for mail processes. This can be overridden by # giving /./ in user's home directory (eg. /home/./user chroots into /home). #mail_chroot = # Default MAIL environment to use when it's not set. By leaving this empty # dovecot tries to do some automatic detection as described in # doc/mail-storages.txt. There's a few special variables you can use, eg.: # # %u - username # %n - user part in user@domain, same as %u if there's no domain # %d - domain part in user@domain, empty if user there's no domain # %h - home directory # # See doc/variables.txt for full list. Some examples: # # default_mail_env = maildir:/var/mail/%1u/%u/Maildir # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # default_mail_env = mbox:/var/mail/%d/%n/:INDEX=/var/indexes/%d/%n # default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u:INDEX=MEMORY # Space-separated list of fields to cache for all mails. Currently these # fields are allowed followed by a list of commands they speed up: # # Envelope - FETCH ENVELOPE and SEARCH FROM, TO, CC, BCC, SUBJECT, # SENTBEFORE, SENTON, SENTSINCE, HEADER MESSAGE-ID, # HEADER IN-REPLY-TO # Body - FETCH BODY # Bodystructure - FETCH BODY, BODYSTRUCTURE # MessagePart - FETCH BODY[1.2.3] (ie. body parts), RFC822.SIZE, # SEARCH SMALLER, LARGER, also speeds up BODY/BODYSTRUCTURE # generation. This is always set with mbox mailboxes, and # also default with Maildir. # # Different IMAP clients work in different ways, that's why Dovecot by default # only caches MessagePart which speeds up most operations. Whenever client # does something where caching could be used, the field is automatically marked # to be cached later. For example after FETCH BODY the BODY will be cached # for all new messages. Normally you should leave this alone, unless you know # what most of your IMAP clients are. Caching more fields than needed makes # the index files larger and generate useless I/O. # # With maildir there's one extra optimization - if nothing is cached, indexing # the maildir becomes much faster since it's not opening any of the mail files. # This could be useful if your IMAP clients access only new mails. #mail_cache_fields = MessagePart # Space-separated list of fields that Dovecot should never set to be cached. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # Dovecot can notify client of new mail in selected mailbox soon after it's # received. This setting specifies the minimum interval in seconds between # new mail notifications to client - internally they may be checked more or # less often. Setting this to 0 disables the checking. # NOTE: Evolution client breaks with this option when it's trying to APPEND. #mailbox_check_interval = 0 # Like mailbox_check_interval, but used for IDLE command. #mailbox_idle_check_interval = 30 # Allow full filesystem access to clients. There's no access checks other than # what the operating system does for the active UID/GID. It works with both # maildir and mboxes, allowing you to prefix mailboxes names with eg. /path/ # or ~user/. #mail_full_filesystem_access = no # Maximum allowed length for mail keyword name. It's only forced when trying # to create new keywords. #mail_max_keyword_length = 50 # Save mails with CR+LF instead of plain LF. This makes sending those mails # take less CPU, especially with sendfile() syscall with Linux and FreeBSD. # But it also creates a bit more disk I/O which may just make it slower. #mail_save_crlf = no # Use mmap() instead of read() to read mail files. read() seems to be a bit # faster with my Linux/x86 and it's better with NFS, so that's the default. # Note that OpenBSD 3.3 and older don't work right with mail_read_mmaped = yes. #mail_read_mmaped = no # Don't use mmap() at all. This is required if you store indexes in remote # filesystems (NFS or clustered filesystem). #mmap_disable = no # Don't write() to mmaped files. This is required for some operating systems # which use separate caches for them, such as OpenBSD. #mmap_no_write = no # Don't use fcntl() locking. Alternatives are dotlocking and other tricks # which may be slower. Required for NFS. fcntl_locks_disable = yes # By default LIST command returns all entries in maildir beginning with dot. # Enabling this option makes Dovecot return only entries which are directories. # This is done by stat()ing each entry, so it causes more disk I/O. # (For systems setting struct dirent->d_type, this check is free and it's # done always regardless of this setting) #maildir_stat_dirs = no # Copy mail to another folders using hard links. This is much faster than # actually copying the file. This is problematic only if something modifies # the mail in one folder but doesn't want it modified in the others. I don't # know any MUA which would modify mail files directly. IMAP protocol also # requires that the mails don't change, so it would be problematic in any case. # If you care about performance, enable it. #maildir_copy_with_hardlinks = no # Check if mails' content has been changed by external programs. This slows # down things as extra stat() needs to be called for each file. If changes are # noticed, the message is treated as a new message, since IMAP protocol # specifies that existing messages are immutable. #maildir_check_content_changes = no # Which locking methods to use for locking mbox. There's four available: # dotlock: Create <mailbox>.lock file. This is the oldest and most NFS-safe # solution. If you want to use /var/mail/ like directory, the users # will need write access to that directory. # fcntl : Use this if possible. Works with NFS too if lockd is used. # flock : May not exist in all systems. Doesn't work with NFS. # lockf : May not exist in all systems. Doesn't work with NFS. # # You can use multiple locking methods; if you do the order they're declared # in is important to avoid deadlocks if other MTAs/MUAs are using multiple # locking methods as well. Some operating systems don't allow using some of # them simultaneously. #mbox_read_locks = fcntl #mbox_write_locks = dotlock fcntl # Maximum time in seconds to wait for lock (all of them) before aborting. #mbox_lock_timeout = 300 # If dotlock exists but the mailbox isn't modified in any way, override the # lock file after this many seconds. #mbox_dotlock_change_timeout = 30 # umask to use for mail files and directories #umask = 0077 # Drop all privileges before exec()ing the mail process. This is mostly # meant for debugging, otherwise you don't get core dumps. It could be a small # security risk if you use single UID for multiple users, as the users could # ptrace() each others processes then. #mail_drop_priv_before_exec = no # Set max. process size in megabytes. Most of the memory goes to mmap()ing # files, so it shouldn't harm much even if this limit is set pretty high. #mail_process_size = 256 # Log prefix for mail processes. See doc/variables.txt for list of possible # variables you can use. #mail_log_prefix = "%Up(%u): " ## ## IMAP specific settings ## protocol imap { # Login executable location. #login_executable = /usr/libexec/dovecot/imap-login # IMAP executable location #mail_executable = /usr/libexec/dovecot/imap # This would write rawlogs into ~/dovecot.rawlog/ directory: #mail_executable = /usr/libexec/dovecot/rawlog /usr/libexec/dovecot/imap # Maximum IMAP command line length in bytes. Some clients generate very long # command lines with huge mailboxes, so you may need to raise this if you get # "Too long argument" or "IMAP command line too large" errors often. #imap_max_line_length = 65536 # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/imap # Workarounds for various client bugs: # oe6-fetch-no-newmail: # Never send EXISTS/RECENT when replying to FETCH command. Outlook Express # seems to think they are FETCH replies and gives user "Message no longer # in server" error. Note that OE6 still breaks even with this workaround # if synchronization is set to "Headers Only". # outlook-idle: # Outlook and Outlook Express never abort IDLE command, so if no mail # arrives in half a hour, Dovecot closes the connection. This is still # fine, except Outlook doesn't connect back so you don't see if new mail # arrives. #imap_client_workarounds = } ## ## POP3 specific settings ## protocol pop3 { # Login executable location. #login_executable = /usr/libexec/dovecot/pop3-login # POP3 executable location #mail_executable = /usr/libexec/dovecot/pop3 # Don't try to set mails non-recent with POP3 sessions. This is mostly # intended to reduce disk I/O. With maildir it doesn't move files from # new/ to cur/, with mbox it doesn't write Status-header. #pop3_mails_keep_recent = no # Support for dynamically loadable modules. #mail_use_modules = no #mail_modules = /usr/lib/dovecot/pop3 # Workarounds for various client bugs: # outlook-no-nuls: # Outlook and Outlook Express hang if mails contain NUL characters. # This setting replaces them with 0x80 character. #pop3_client_workarounds = } ## ## Authentication processes ## # You can have multiple authentication processes. With plaintext authentication # the password is checked against each process, the first one which succeeds is # used. This is useful if you want to allow both system users (/etc/passwd) # and virtual users to login without duplicating the system users into virtual # database. # Executable location #auth_executable = /usr/libexec/dovecot/dovecot-auth # Set max. process size in megabytes. #auth_process_size = 256 # Space separated list of realms for SASL authentication mechanisms that need # them. You can leave it empty if you don't want to support multiple realms. # Many clients simply use the first one listed here, so keep the default realm # first. #auth_realms = # Default realm/domain to use if none was specified. This is used for both # SASL realms and appending @domain to username in plaintext logins. #auth_default_realm = # List of allowed characters in username. If the user-given username contains # a character not listed in here, the login automatically fails. This is just # an extra check to make sure user can't exploit any potential quote escaping # vulnerabilities with SQL/LDAP databases. If you want to allow all characters, # set this value to empty. #auth_username_chars = abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@ # Username to use for users logging in with ANONYMOUS SASL mechanism #auth_anonymous_username = anonymous # More verbose logging. Useful for figuring out why authentication isn't # working. #auth_verbose = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Where user database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # passwd-file <path>: passwd-like file with specified location # static uid=<uid> gid=<gid> home=<dir template>: static settings # vpopmail: vpopmail library # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # mysql <config path>: a MySQL database, see doc/dovecot-mysql.conf userdb = passwd # Where password database is kept: # passwd: /etc/passwd or similiar, using getpwnam() # shadow: /etc/shadow or similiar, using getspnam() # pam [<service> | *]: PAM authentication # checkpassword <path>: checkpassword executable authentication # passwd-file <path>: passwd-like file with specified location # vpopmail: vpopmail authentication # ldap <config path>: LDAP, see doc/dovecot-ldap.conf # pgsql <config path>: a PostgreSQL database, see doc/dovecot-pgsql.conf # mysql <config path>: a MySQL database, see doc/dovecot-mysql.conf passdb = pam # User to use for the process. This user needs access to only user and # password databases, nothing else. Only shadow and pam authentication # requires roots, so use something else if possible. Note that passwd # authentication with BSDs internally accesses shadow files, which also # requires roots. user = root # Directory where to chroot the process. Most authentication backends don't # work if this is set, and there's no point chrooting if auth_user is root. #chroot = # Number of authentication processes to create #count = 1 # Require a valid SSL client certificate or the authentication fails. #ssl_require_client_cert = no } # PAM doesn't provide a way to get uid, gid or home directory. If you don't # want to use a separate user database (passwd usually), you can use static # userdb. #auth onlypam { # mechanisms = plain # userdb = static uid=500 gid=500 home=/var/mail/%u # passdb = pam # user = dovecot-auth #} #auth ldap { # mechanisms = plain # userdb = ldap /etc/dovecot-ldap.conf # passdb = ldap /etc/dovecot-ldap.conf # user = dovecot-auth #} #auth virtualfile { # mechanisms = plain digest-md5 # userdb = passwd-file /etc/passwd.imap # passdb = passwd-file /etc/passwd.imap # user = dovecot-auth #} # It's possible to export the authentication interface to other programs, # for example SMTP server which supports talking to Dovecot. Client socket # handles the actual authentication - you give it a username and password # and it returns OK or failure. So it's pretty safe to allow anyone access to # it. Master socket is used to a) query if given client was successfully # authenticated, b) userdb lookups. # listener sockets will be created by Dovecot's master process using the # settings given inside the auth section #auth default_with_listener { # mechanisms = plain # passdb = passwd # userdb = pam # socket listen { # master { # path = /var/run/dovecot/auth-master # #mode = 0600 # # Default user/group is the one who started dovecot-auth (root) # #user = # #group = # } # client { # path = /var/run/dovecot-auth-client # mode = 0660 # } # } #} # connect sockets are assumed to be already running, Dovecot's master # process only tries to connect to them. They don't need any other settings # than path for the master socket, as the configuration is done elsewhere. # Note that the client sockets must exist in login_dir. #auth external { # socket connect { # master { # path = /var/run/dovecot/auth-master # } # } #}

2 1

[Dovecot] no local users - mbox all under /var/spool/mail/
by Daniel 15 Aug '04

15 Aug '04

Hi there, im new to dovecot but I made my way trough configuring it. I almost get it running at least for one IMAP user. The problem is I got no local user thus no home directories, all Mailboxes are in mbox format under: /var/spool/mail: Looks like this: -SNIP- drwx------ 3 web1p2 poponly 19 2004-08-13 00:05 indexes -rw------- 1 nobody nobody 0 2004-03-26 21:51 nobody -rw------- 1 root root 0 2004-03-26 21:51 root -rw------- 1 web1p2 poponly 14 2004-08-13 00:10 .subscriptions -rw------- 1 web1p2 poponly 8571 2004-08-13 00:10 Trash -rw-rw---- 1 web0p1 root 23068262 2004-08-12 21:27 web0p1 -rw-rw---- 1 web0p2 root 17749 2004-08-12 23:55 web0p2 ... -SNAP I´ve set up the mail-environment this way: default_mail_env = mbox:/var/spool/mail/:INBOX=/var/spool/mail/%u:INDEX=/var/spool/mail/indexes/%u The problem is, that the directory "indexes" has permisions that only the owner can write to (well, I could change permissions, but?) and that the ".subscription" file and "Trash" folder is directly in this directory. So if I add a second user (e.g. web0p1) I got error messages imho due to the use of the "same" folder....? What would be the proposed setup for this system with mostly non-local users without real home directories and all their mbox in a shared directory? Thanks for your time! Daniel

2 1

[Dovecot] LDAP-auth not working
by Roger Bystrom 15 Aug '04

15 Aug '04

I have set up dovecot to use ldap authentication, but it only results in dovecot crashing without any error message that would indicate why this is the case. I have spent *many* hours trying to fix this problem, but not found any solution as to why it should crash. maillog: Aug 15 10:05:08 era dovecot: Dovecot starting up Aug 15 10:05:09 era dovecot: Auth process died too early - shutting down Aug 15 10:05:09 era dovecot: child 20833 (auth) killed with signal 11 Aug 15 10:05:09 era imap-login: fd_send(-1) failed: Broken pipe Settings to indicate ldap in dovecot.conf: auth_userdb = ldap /etc/dovecot-ldap.conf auth_passdb = ldap /etc/dovecot-ldap.conf Basically, the settings in dovecot-ldap.conf is: hosts = localhost:389 dn = cn=dovecot,ou=servers,dc=remiss,dc=org dnpass = nada base = dc=remiss,dc=org deref = never scope = subtree user_attrs = uid,homeDirectory,,,uidNumber,gidNumber user_filter = (&(objectClass=posixAccount)(uid=%u)) pass_attrs = uid,userPassword using ldapsearch -x -D "cn=dovecot,ou=servers,dc=remiss,dc=org" -w nada .... is successful. Therefor I am wondering what in the world that causes "Auth process" to die too early. Output of strace -f dovecot -F is available from http://remiss.org/download/log Pid of auth-process here is 23286. Any help is appreciated. Thanks, Roger.

2 2

[Dovecot] Dovecot Local Delivery Agent
by news.gmane.org 12 Aug '04

12 Aug '04

Hi I noticed in a post that Timo might start work on a LDA Great! If so, here is something I would really like included. Support for PAM There is quite a lengthy reason behind this. In my organisation, user accounts are created on ldap. It is up to the services to create home directories whenever the user first uses them. For instance, Samba will do this the first time they connect to their windows home share. This achieved in other places using pam, using the pam_mkhomedir module. The MTA we run, Exim, is incapable of creating the home directory automatically, or using PAM for local delivery, thus we have the problem that when an account is created in the LDAP directory, it cannot receive email until the user first logs in through IMAP - Dovecot calls pam, which creates the home directory :-) Also attributing to this is the fact that exim is configured to deliver email into $home using maildir format rather than a mbox mail spool. We needed to do this because of the huge size of some of the inboxes of our users. This caused a severe amount of i/o blocking. So far, I have been unable to find a LDA capable of doing this. Since we migrated to dovecot, performance has improved ten-fold. I will give it a week then show you the graphs to prove it! Keep up the great work! Regards -- Chris Hills IT Services North East Worcestershire College

6 10

Re: [Dovecot] Newbie about Mbox or Maildir
by alan premselaar 11 Aug '04

11 Aug '04

Zoong Pham wrote: > > >>-----Original Message----- >>From: dovecot-bounces(a)dovecot.org >>[mailto:dovecot-bounces@dovecot.org]On >>Behalf Of nino(a)swiftdsl.com.au >>Sent: Tuesday, 10 August 2004 3:07 PM >>To: dovecot(a)dovecot.org >>Subject: [Dovecot] Newbie about Mbox or Maildir > > >>Thanks in advance. I am not sure if my system is setup to use >>'mbox' or >>'maildir'. How do I find this out? > > >>I am running an OpenBSD (v3.5) box with an Intel P3 >>motherboard. I have >>installed the OpenBSD port of Dovecot (0.99.10) and have >>manually started >>dovecot and configured the ssl certificates as per the >>documentation. As >>far as I can tell there is no problems but I am confused >>about 'mbox' and >>'maildir' > > > It's mbox. > The default MTA of OpenBSD is Sendmail. > More specifically, this is related to your local delivery agent (LDA). Although I'm not extremely familiar with default OpenBSD installations, it's been typical for default RedHat installations (up to and including RH 9) to have sendmail installed and configured to use procmail for its LDA. while recent versions of procmail can support maildir format, it defaults to using mbox format. alan

2 2

[Dovecot] mkdir imap with user@domain.com
by wiki kaha 11 Aug '04

11 Aug '04

I have a bit a problem. In a virtual domain enviroment i use for login "user(a)domain.com" and the password. in the mysql authentication it works beautiful with %d and %u placeholder. Now when is whould like ad a folder via imap i get an error imap(user(a)domain.com): mkdir(/var/mail/domain.com/user@domain.com/.test) failed: No such file or directory It should be mkdir(/var/mail/domain.com/user/.test) Is there a way to configure this? Thanks Regards Karl-Heinz __________________________________ Do you Yahoo!? New and Improved Yahoo! Mail - Send 10MB messages! http://promotions.yahoo.com/new_mail

2 2

[Dovecot] [PATCH] RPA authentication mechanism
by Andrey Panin 10 Aug '04

10 Aug '04

Hello all, attached patch implements Compuserve RPA athentication mechanism. Tested with: - Eudora 6 (uses Compuserve "Virtual Key" RPA software); - TheBat! 2.11 (uses it's own RPA implementation). I hope it can be useful for someone. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 2

FW: [Dovecot] dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type'mysql'
by Alex Low (e-wise) 10 Aug '04

10 Aug '04

After better looking in the config.log, We found this, mysql wasn't compiled because of this; /usr/lib/mysql/libmysqlclient.a(my_compress.o)(.text+0xd8): In function `my_compress_alloc': : undefined reference to `compress' /usr/lib/mysql/libmysqlclient.a(my_compress.o)(.text+0x171): In function `my_uncompress': : undefined reference to `uncompress' I am using Fedora Core 2, using own compiled mysql 4.x rpm's. Timo Sirainen wrote: It looks like it's needed to be linked with zlib. Hmm. I haven't heard this to be necessary before. It seems to be statically linked in my mysql library. I think it'd work with: LDFLAGS=-lz ./configure --with-mysql And indeed adding -lz to LDFLAGS= in the spec file helped. Anyways I have dovecot rpm for Fedora Core 2 compiled with mysql 4. So if anybody want it, mail away. Greets, Alex _____ From: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] On Behalf Of Alex Low (e-wise) Sent: woensdag 4 augustus 2004 11:15 To: dovecot(a)dovecot.org Subject: [Dovecot] dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type'mysql' Hi, I am trying this way(mailinglist), as I cant find good 'support'/howto/tutorials on the website. I am running Fedora Core II, using postfix with mysql, and I want to use dovecot as imap server. Now I installed Dovecot using dag wieers SRPM, I compiled it with mysql, pgsql; %configure \ --with-ssl="openssl" \ --with-ssldir="%{_datadir}/ssl" \ --with-ldap \ --with-pgsql \ --with-mysql \ --with-cyrus-sasl2 \ --with-rawlog %{__make} %{?_smp_mflags} After compiling it, I installed the rpm. No problem at all. I configure the dovecot.conf like this; #auth = plain digest-md5 #auth_methods = plain digest-md5 auth_userdb = mysql /etc/dovecot-mysql.conf auth_passdb = mysql /etc/dovecot-mysql.conf default_mail_env = maildir:/home/mail/virtual/%d/%n # Use this logfile instead of syslog(). /dev/stderr can be used if you want to # use stderr for logging (ONLY /dev/stderr - otherwise it is closed). log_path = /tmp/dovecot/log1 # For informational messages, use this logfile instead of the default info_log_path = /tmp/dovecot/log2 Then I try run it: [root@octa SPECS]# cat /tmp/dovecot/log1 dovecot-auth: Aug 04 10:48:29 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 10:48:29 Error: Auth process died too early - shutting down dovecot: Aug 04 10:48:29 Error: child 2118 (auth) returned error 89 imap-login: Aug 04 10:48:29 Fatal: fd_send(-1) failed: Broken pipe dovecot-auth: Aug 04 11:04:39 Fatal: Unknown userdb type 'mysql' dovecot: Aug 04 11:04:39 Error: Auth process died too early - shutting down dovecot: Aug 04 11:04:39 Error: child 11137 (auth) returned error 89 imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe imap-login: Aug 04 11:04:39 Fatal: fd_send(-1) failed: Broken pipe [root@octalys SPECS]# cat /tmp/dovecot/log2 dovecot: Aug 04 10:48:28 Info: Dovecot starting up dovecot: Aug 04 11:04:38 Info: Dovecot starting up [root@octalys SPECS]# Can anyone tell me whats wrong please ? Thank you in advance, Alex

1 0

RE: [Dovecot] Newbie about Mbox or Maildir
by Zoong Pham 10 Aug '04

10 Aug '04

> -----Original Message----- > From: dovecot-bounces(a)dovecot.org > [mailto:dovecot-bounces@dovecot.org]On > Behalf Of nino(a)swiftdsl.com.au > Sent: Tuesday, 10 August 2004 3:07 PM > To: dovecot(a)dovecot.org > Subject: [Dovecot] Newbie about Mbox or Maildir > Thanks in advance. I am not sure if my system is setup to use > 'mbox' or > 'maildir'. How do I find this out? > I am running an OpenBSD (v3.5) box with an Intel P3 > motherboard. I have > installed the OpenBSD port of Dovecot (0.99.10) and have > manually started > dovecot and configured the ssl certificates as per the > documentation. As > far as I can tell there is no problems but I am confused > about 'mbox' and > 'maildir' It's mbox. The default MTA of OpenBSD is Sendmail. I have similar configuration here. Let me know if you need any help. Cheers, Zoong PHAM UNIX systems Administrator ICT - Information, Communications & Technology Mercy Health & Aged Care 678 Victoria Street Richmond 3121 ___________________________________________________________________________________ THIS EMAIL IS CONFIDENTIAL. If you have received this email in error please forward it to information(a)mercy.com.au. It may contain personal information and it is intended for the addressee only. If you receive this email in error you must not use, copy forward, print or otherwise disseminate any information it contains. Mercy Health & Aged Care is a Catholic community benefit organisation. Each year one in twenty Victorian families are touched by the services we provide. Visit www.mercy.com.au for more information. Our services include: * Mercy Hospital for Women - East Melbourne (moving to Heidelberg in 2005) * Werribee Mercy Hospital - Werribee * Mount Alvernia Mercy Hospital - Bendigo * Mercy Hospice - Western suburbs * O'Connell Family Centre - Canterbury * Corporate Office - Richmond * Rice Village - Geelong * Tullamore Mercy - Montrose * Eventide Mercy - Colac * Bethlehem Home for the Aged - Bendigo *

1 0

[Dovecot] Newbie about Mbox or Maildir
by nino＠swiftdsl.com.au 10 Aug '04

10 Aug '04

Hi, Thanks in advance. I am not sure if my system is setup to use 'mbox' or 'maildir'. How do I find this out? I am running an OpenBSD (v3.5) box with an Intel P3 motherboard. I have installed the OpenBSD port of Dovecot (0.99.10) and have manually started dovecot and configured the ssl certificates as per the documentation. As far as I can tell there is no problems but I am confused about 'mbox' and 'maildir' Any assistance is appreciated. Thankyou NS

1 0

[Dovecot] Debian sarge release and dovecot
by Jaldhar H. Vyas 10 Aug '04

10 Aug '04

In what must surely be the first sign of the apocalypse, Debian is actually freezing in preperation for a new release. Probably the last day for uploads will be August 17. Is there likely to be another dovecot release by then? In the event of 0.99.10.9 being the released version, are there any other patches Debian users would like me to include? -- Jaldhar H. Vyas <jaldhar(a)debian.org> La Salle Debain - http://www.braincells.com/debian/

3 4

[Dovecot] Problem moving folders with Thunderbird
by Loek 10 Aug '04

10 Aug '04

I can move around folders to sub-folders in an IMAP account on my dovecot server, but when I try to move a sub-folder back to the top-level (by dragging it to the account name), I get an error: "The current command did not succeed. The mailserver responded: Mailbox exists." It doesn't exist on the server though, and I can create a folder with that name on the top-level. But it is a little annoying. I am using TB 0.7.2. I tried different IMAP server settings in Thunderbird under the account options, but without success. Loek

3 3

[Dovecot] Both mbox and Maildir
by Yann Rouillard 09 Aug '04

09 Aug '04

Hi, I would like to know if it's possible to configure dovecot so that it use mbox file format for the INBOX mailbox but Maildir format for all the subfolders. My problem is I would like an IMAP server which allow to easily create folders and subfolders of folders, but at the same time I don't want to break all MUA which rely on /var/mail/johndoe in mbox format. Thanks in advance. Yann

2 1