- dovecot - dovecot.org

[Dovecot] Authenticaing in postgresql
by vmstech 17 Jul '05

17 Jul '05

Hi all - Im new to dovecot and actually all things email serverish. I spent last week wrestling with exim4, and this week its dovecots turn. I'm trying to connect as an imap user (from evolution) and not actually able to make a successful login. I have default_pass_scheme=PLAIN, and am using pass authentication in evolution client. Its the only one available after it queries the server for available types. I'm not getting any errors appear in either the postgres or dovecot log files (anymore :-) that is). I'm getting the exact query I'd like to see in the dovecot log file, after I entering the password in the client, but unfortunately it doesnt give me the reply. I can key this exact query in to the psql client and get the correct answer. dovecots logs don't tell me if I have success or failure. The auth_db query has only 1 column. I have no idea where to go from here - would love a hint thanks Glenn

1 1

Re: [Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 15 Jul '05

15 Jul '05

Peter Evans wrote: > Jeroen Scheerder (Jeroen.Scheerder(a)phil.uu.nl) wrote: > >>However, whenever a mailbox is selected, the imap subprocess dies. >>Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] >>Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 > > > You're going to have to help us to help you. 10 is bus error (I think) > which is badness. > > OS, > version of dovecot > etc. > > you might want to debug a coredump, that will tell you where/why its > dying too. I would merrily gdb into a coredump and stacktrace away, if a core dump were created. No such luck. I'm now logging directly to file using syslog, after having started dovecot. There is no limit on coredumps: % limit cputime unlimited filesize unlimited datasize unlimited stacksize 8MB coredumpsize unlimited descriptors 64 vmemorysize unlimited % more /tmp/dovecot* :::::::::::::: /tmp/dovecot-info.log :::::::::::::: dovecot: Jul 13 15:27:35 Info: Dovecot v1.0-stable starting up dovecot: Jul 13 15:28:21 Info: imap-login: Login: avank [127.0.0.1] :::::::::::::: /tmp/dovecot.log :::::::::::::: dovecot: Jul 13 15:28:21 Error: child 14882 (imap) killed with signal 10 Environmental details: Solaris 7 (sparc) dovecot 1.0-stable compiled with ldap support using gcc 3.3.4 4.0.0 4.0.1 (no difference here) configured for mbox support with locking matching procmail's delivery locking strategies with authentication using passwd/shadow native databases A header dump shows nothing suspect: % elfdump -d /phil/sunos/sparc/pkg/dovecot-1.0-stable/libexec/dovecot/imap Dynamic Section: .dynamic index tag value [0] NEEDED 0x1 libsocket.so.1 [1] NEEDED 0x117 librt.so.1 [2] NEEDED 0x140 libc.so.1 [3] NEEDED 0x397 libnsl.so.1 [4] NEEDED 0x3b3 libdl.so.1 [5] RPATH 0x3cc /phil/sw/sunos/sparc/lib [snip] Will try on Solaris 10.

4 9

[Dovecot] OS X Mail.app 2 (Tiger) + dovecot -> new mail count doubled
by Alan Schmitt 14 Jul '05

14 Jul '05

Hello, I've noticed a strange bug with Mail.app 2 (from OS X.4) and dovecot, and I'm trying to identify where it comes from. I have a bunch of mailboxes that can receive new mail (delivered by procmail) and I have Mail set up as to automatically synchronize all maiboxes. When I start up Mail, the count for new mail is doubled in every mailbox that I have not seen yet. Looking at a mailbox restores the correct count (mail is not actually duplicated, it's just the new mail counter that is wrong). Has anyone else seen this? Would this bug be from Mail.app or from dovecot? (I suspect the former.) Thanks a lot, Alan Schmitt

3 6

[Dovecot] Very slow select() command on large mailboxes
by Sebastjan Trepca 14 Jul '05

14 Jul '05

Hi, I'm trying to decide if I could use you mail server in our enviroment which has about 10k users and mailboxes size about ~1GB. So I made a few tests and it all worked quite fast, except that select command on large mailboxes. The first time I select a mailbox which has 10k messages it takes about 4s to process. I am deliberately trying this on a Celeron 850Mhz, 512 MB memory and some shitty hard-drive to maximize the times. So why is this so slow? Does it index the messages on select? It's even slower when I have some new messages in folder, more that I have more I wait. So I presume it must be something with indexing? Anyway, how could I optimize this? Why don't you index when a mail arrives instead of on select? Thanks for help and keep doing a great job with Dovecot. Sebastjan

4 3

[Fwd: Re: [Dovecot] Dovecot and ActiveDirectory]
by Chris Wakelin 14 Jul '05

14 Jul '05

Oops! Thought I'd CC'd this to the list. Sorry, Oliver! Chris -------- Original Message -------- Date: Wed, 13 Jul 2005 20:09:35 +0100 From: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> To: Jeroen Scheerder <Jeroen.Scheerder(a)phil.uu.nl> CC: Chris Wakelin <c.d.wakelin(a)reading.ac.uk> Subject: Re: [Dovecot] Dovecot and ActiveDirectory Jeroen Scheerder wrote: > Chris Wakelin (13/7/05 16:08 +0100) [Re: [Dovecot] Dovecot and > ActiveDirectory]: > > >>I've got it working via PAM and pam_ldap on Solaris. [..] > > > That's exactly what I'm striving to do. > > I've never set up LDAP authentication for Solaris itself, and actually > never used PAM before. > > If I may be so bold, could I bother you for details about your > configuration in these respects? /opt/RDGpldap/etc/ldap.conf: host xxx.rdg.ac.uk base dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk binddn cn=xxxuser,cn=users,dc=xxxxx,dc=ad,dc=rdg,dc=ac,dc=uk bindpw xxxpasswd nss_map_objectclass posixAccount user nss_map_objectclass shadowAccount user nss_map_attribute uid sAMAccountName nss_map_attribute homeDirectory unixHomeDirectory nss_map_attribute shadowLastChange pwdLastSet nss_map_objectclass posixGroup group nss_map_attribute uniqueMember member pam_login_attribute sAMAccountName pam_filter objectclass=User pam_password ad xxxuser is a read-only account in the AD. /etc/pam.conf: ... dovecot auth required /opt/RDGpldap/lib/pam_ldap.so dovecot account required /opt/RDGpldap/lib/pam_ldap.so dovecot session required /opt/RDGpldap/lib/pam_ldap.so dovecot.conf: auth_username_translation = AaBbCcDdEeFfGgHhIiJjKkLlMmNnOoPpQqRrSsTtUuVvWwXxYyZz auth default { mechanisms = plain login passdb = pam userdb = passwd user = root } The auth_username_translation is because AD users are case-insensitive but UNIX ones aren't! We have users in both AD and UNIX (but could use something like "userdb=static uid=xxxx gid=yyyy home=/var/mail/%Lu" assuming xxxx:yyyy has appropriate permissions on the spool files) pam_ldap-178 was configured with ./configure --prefix=/opt/RDGpldap \ --with-ldap-conf-file=/opt/RDGpldap/etc/ldap.conf Hope this helps, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

Re: [Dovecot] problem with server certificate: dovectot.pem
by Joseph Tam 14 Jul '05

14 Jul '05

> Date: Wed, 13 Jul 2005 23:46:33 +0300 > From: vladone <vladone(a)spaingsm.com> > Subject: [Dovecot] problem with server certificate: dovectot.pem > > I have an mail server with postfix and dovecot. > All works fine, but now is change my domain. After changed > configurations i can receive (or send) mail without STARTTLS, > but when i try to use this option i receive: > "TLS handshake failure. Invalid server certificate (Key material > mismatch)" > > I dont know what is this. > I use certificate that is generate with script for dovecot (that work > at begining). > Even i try to rebuild this certificate acording with new domain but > nothing. > Where is my problem? Yes, of course. Certificates are made out to a particular hostname (e.g. smtp.wahtever.com) and if you change your server hostname or move it to another server, a new certificate will have to be made out to the new hostname. You could also configure your client ignore certificate mismatches, but this wouldn't be the best option. Joseph Tam <tam(a)math.ubc.ca>

1 0

[Dovecot] Search with specified charset
by Chris Wakelin 14 Jul '05

14 Jul '05

I've seen a problem with searching in the Prayer webmail client that turns out to be caused by Prayer insisting on a charset called "ISO-8859-1" and Dovecot, using Solaris iconv, not recognising it (all the Solaris 8 iconv modules appear to be "ISO8859-1" etc. or just "8859-1"). This isn't a problem in Linux: % iconv --list | grep 8859.1/ 8859_1// ISO-8859-1// ISO8859-1// ISO885911// ISO_8859-1// I've hacked together a patch for Dovecot to try matching without the "ISO-" prefix if matching fails at first, which works for Solaris (as would creating an extra symbolic link in /usr/lib/iconv or hacking Prayer to use "ISO8859-1") and it doesn't break Linux, but it's not pretty :( Better may be to try substituting underscores, hyphens, spaces(?) and nothing in the string, but that makes the change much more complicated! Best Wishes, Chris --- dovecot-1.0-stable/src/lib-charset/charset-iconv.c.orig Mon Jan 31 16:37:55 2005 +++ dovecot-1.0-stable/src/lib-charset/charset-iconv.c Wed Jul 13 21:47:03 2005 @@ -36,9 +36,17 @@ ascii = FALSE; cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } } @@ -137,9 +145,17 @@ cd = iconv_open("UTF-8", charset); if (cd == (iconv_t)-1) { - if (unknown_charset != NULL) - *unknown_charset = TRUE; - return NULL; + /* Try matching charset without "ISO" prefix */ + if (strncasecmp(charset, "ISO-", 4) == 0 || + strncasecmp(charset, "ISO ", 4) == 0) + cd = iconv_open("UTF-8", charset + 4); + else if (strncasecmp(charset, "ISO", 3) == 0) + cd = iconv_open("UTF-8", charset + 3); + if (cd == (iconv_t)-1) { + if (unknown_charset != NULL) + *unknown_charset = TRUE; + return NULL; + } } if (unknown_charset != NULL) -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

1 0

[Dovecot] problem with server certificate: dovectot.pem
by vladone 13 Jul '05

13 Jul '05

Hi! I have an mail server with postfix and dovecot. All works fine, but now is change my domain. After changed configurations i can receive (or send) mail without STARTTLS, but when i try to use this option i receive: "TLS handshake failure. Invalid server certificate (Key material mismatch)" I dont know what is this. I use certificate that is generate with script for dovecot (that work at begining). Even i try to rebuild this certificate acording with new domain but nothing. Where is my problem? P.S. All works before changed my domain!!!

1 0

[Dovecot] file locks
by Obantec Support 13 Jul '05

13 Jul '05

Hi I am trying to install 1.0 stable from source on a test server running 0.99 on FC3. i did basic ./configure etc and get this result Jul 13 17:24:26 proteus4 dovecot: Dovecot v1.0-stable starting up Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): open(/var/spool/mail/.temp.proteus4.4485.e3eec7b26a559bac) failed: Permission denied Jul 13 17:24:35 proteus4 dovecot: POP3(obantec): file_lock_dotlock() failed with mbox file /var/spool/mail/obantec: Permission denied Jul 13 17:24:35 proteus4 dovecot: pop3-login: Login: obantec [192.168.0.10] when trying to access a test account. permissions all look as per old 0.99 which did work. Mark

3 5

[Dovecot] Minor bugs still in test77
by Chris Wakelin 13 Jul '05

13 Jul '05

Thinking of patches I always apply, I've got a couple (attached) that fix minor bugs and maybe should be applied - or implemented better and then applied ;) - to the main distribution? 1) LIST bugs: LIST "~/mail/" "" and LIST "" "~/mail/" (where "~/mail/" is a namespace prefix) don't reply the same way as UW-IMAP does and in at least the first case, still violates the spec (your fix breaks, as namespace_find() modifies its argument) The second issue breaks Pine 4.x, I think. 2) Angle-addresses If a header address is just "<someone(a)somewhere.org>" rather than "Someone <someone(a)somewhere.org>" or "someone(a)somewhere.org", then the FETCH ... ENVELOPE command responds with "" as the personal name, rather than NIL, which may confuse clients (without being wrong, technically, I think). (In case anyone's interested, I also use patches to: 1) fix the 64bit issue mentioned earlier today 2) introduce extra logging of LIST, SUBSCRIBE and UNSUBSCRIBE (for debugging during our migration from UW-IMAP) 3) rename .subscriptions to .mailboxlist and store folder names in it including the namespace prefix (to emulate UW-IMAP) 4) implement a Reading-specific hashing algorithm for the mail spool location as an extra variable modifier "%H" (e.g. "/export/mail/%Hu/%u/INBOX") 5) remove the need for /dev/urandom, which isn't available on our mail server (though there is a Solaris patch available to create it). 6) add an option to hide "AUTH=PLAIN" in the CAPABILITY string as Pine 4.x complains loudly when this is advertised on a non-SSL connection ) Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094 --- dovecot-1.0-test77.orig/src/imap/cmd-list.c Sun Apr 17 17:37:05 2005 +++ dovecot-1.0-test77/src/imap/cmd-list.c Wed Jul 13 16:10:27 2005 @@ -372,7 +372,8 @@ concept which probably no other client uses than Pine. Just try our best to emulate UW-IMAP behavior and hopefully we're fine. */ - ns = namespace_find(client->namespaces, &ref); + const char *ref_copy = t_strdup(ref); + ns = namespace_find(client->namespaces, &ref_copy); if (ns == NULL) { const char *empty = ""; ns = namespace_find(client->namespaces, &empty); @@ -405,6 +406,28 @@ } client_send_tagline(cmd, "OK List completed."); } else { + + if (*ref == '\0' && !lsub) { + /* LIST "" "something" */ + const char *mask_copy = t_strdup(mask); + ns = namespace_find(client->namespaces, &mask_copy); + if (ns == NULL) { + const char *empty = ""; + ns = namespace_find(client->namespaces, &empty); + } + if (*ns->prefix != '\0' && *mask_copy == '\0') { + /* namespace, return it */ + string_t *str = t_str_new(64); + str_printfa(str, "* LIST (\\Noselect) \"%s\" ", + ns->sep_str); + imap_quote_append_string(str, ns->prefix, + FALSE); + client_send_line(client, str_c(str)); + client_send_tagline(client, "OK List completed."); + return TRUE; + } + } + ctx = p_new(cmd->pool, struct cmd_list_context, 1); ctx->ref = ref; ctx->mask = mask; --- dovecot-1.0-test77.orig/src/lib-mail/message-address.c Fri Apr 8 12:16:36 2005 +++ dovecot-1.0-test77/src/lib-mail/message-address.c Wed Jul 13 16:15:15 2005 @@ -140,6 +140,10 @@ return -1; ctx->addr.name = p_strdup(ctx->pool, str_c(ctx->str)); + if (*ctx->addr.name == '\0') { + /* Cope with "<address>" without display name */ + ctx->addr.name = NULL; + } if (parse_angle_addr(ctx) < 0) { /* broken */ ctx->addr.domain = p_strdup(ctx->pool, "SYNTAX_ERROR");

1 0

[Dovecot] Dovecot and ActiveDirectory
by Hoffmann, Oliver 13 Jul '05

13 Jul '05

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi! Is there a solution to auth dovecot against an windows active directory? i've tried this config: - --- # Space separated list of LDAP hosts to use. host:port is allowed too. hosts = dc.foo.bar # Distinguished Name - the username used to login to the LDAP server dn = cn=oh,cn=Users,dc=foo,dc=bar # Password for LDAP server dnpass = password # LDAP protocol version to use. Likely 2 or 3. ldap_version = 3 # LDAP base base = cn=Users,dc=foo,dc=bar # Dereference: never, searching, finding, always #deref = never # Search scope: base, onelevel, subtree scope = subtree # User attributes in order: user_attrs = uid,homeDirectory,,,uidNumber,gidNumber # Filter for user lookup. Some variables can be used: #user_filter = (&(objectClass=posixAccount)(uid=%u)) # Password checking attributes in order: pass_attrs = uid,userPassword # Filter for password lookups #pass_filter = (&(objectClass=posixAccount)(uid=%u)) # Default password scheme. "{scheme}" before password overrides this. #default_pass_scheme = CRYPT # You can use same UID and GID for all user accounts if you really want # to. # If the UID/GID is still found from LDAP reply, it overrides these values. #user_global_uid = #user_global_gid = - --- but got this error: - --- dovecot-auth: Jul 13 16:42:09 Error: ldap(oh): unknown user - --- thx & greets oliver -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (MingW32) iD8DBQFC1S162+wHtX4o3oARAo+SAJ9EGVQPXBG+gtZmcbkOjMiy0xF2JACgigDs +6q+EW0zjsICqME310Ky41M= =sMRS -----END PGP SIGNATURE-----

2 1

[Dovecot] New to dovecot, little luck - signal 10 death for imap
by Jeroen Scheerder 13 Jul '05

13 Jul '05

Hi, I'm a new prospective dovecot user. I'm planning to migrate a medium-scale mail site (a few thousand users) from UW to something better. I've set up dovecot on a test system. I can connect and authenticate just fine. IMAP clients get to see the right mailboxes. However, whenever a mailbox is selected, the imap subprocess dies. The log shows: Jul 13 14:52:05 localhost dovecot: imap-login: Login: js [127.0.0.1] Jul 13 14:52:07 localhost dovecot: child 8082 (imap) killed with signal 10 When I either telnet to it manually or run the "imap" process in a terminal window, everything seems to work: ---- Snip ---- * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as js x select INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1300 EXISTS * 0 RECENT * OK [UNSEEN 2] First unseen. * OK [UIDVALIDITY 1119092680] UIDs valid * OK [UIDNEXT 1590] Predicted next UID x OK [READ-WRITE] Select completed. x fetch 1 full * 1 FETCH (FLAGS (\Seen) INTERNALDATE "18-Jun-2005 05:00:02 +0200" RFC822.SIZE 1773 ENVELOPE ("Sat, 18 Jun 2005 05:00:01 +0200 (MET DST)" "Waarschuwing: uw inbox overschrijdt 80% van de groottelimiet (18-06-2005)" (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) (("Super-User" NIL "helpdesk" "phil.uu.nl")) ((NIL NIL "js" "phil.uu.nl")) NIL NIL NIL "<20050618030001.B5F3952048(a)goedel.admin.phil.uu.nl>") BODY ("text" "plain" ("charset" "us-ascii") NIL NIL "7bit" 1082 25)) x OK Fetch completed. x fetch 1 body[text] * 1 FETCH (BODY[TEXT] {1082} Beste Jeroen Scheerder, [...] Met vriendelijke groet, het systeembeheer. ) x OK Fetch completed. x list * * * LIST (\Noselect \HasChildren) "/" "Archive/" [...] * LIST (\Unmarked) "/" "INBOX" x OK List completed. ---- Snip ---- I'm at a loss here, and no amount of logging or sniffing with tcpdump has revealed anything interesting so far. Does anyone else see these "signal 10" aborts? Is there any way in which I can force a coredump (in case it's *really* a bus error)? Regards, Jeroen.

1 0

Re: [Dovecot] mysql
by John Peacock 13 Jul '05

13 Jul '05

Peter Evans wrote: > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. I think you need to take your biases and go someplace else. If you don't like MySQL because of some personal bias, then don't use it. Anyone halfway competent can build Dovecot themselves and not rely on some third-party RPM's that have dependencies. This is a discussion list for Dovecot. Please try and stay on topic... John -- John Peacock Director of Information Research and Technology Rowman & Littlefield Publishing Group 4720 Boston Way Lanham, MD 20706 301-459-3366 x.5010 fax 301-429-5747

1 0

Re: [Dovecot] mysql
by Andrew Hutchings 13 Jul '05

13 Jul '05

Peter Evans wrote: > Dominic Marks (dom(a)goodforbusiness.co.uk) wrote: > > Because you might, just possibly want performance that > doesn't resemble mollasses in midwinter? > Optionally, you might even want something where the response > time is deterministic. > > Points at the company mail system here for a prime example > of why not to use mysql. But then again, this is actually > a prime example of "it works, but we don't know how." > > P > > We use mysql here as it makes a perfect integration with the rest of our systems, we have over 6000 mail accounts (probably closer to 7000 now) on it and the mysql lookup time is pretty much instant, the load never goes above 0.5 on the systems (2x1GHz Epias on round robin with replicated databases on each) and most of that is because the POP/IMAP servers are also round robin MX servers so Exim can take a chunk out of the CPU. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ A-Wing Internet Services - http://www.a-wing.co.uk/ Random quote 2: "In most countries selling harmful things like drugs is punishable. Then howcome people can sell Microsoft software and go unpunished?" - Hasse Skrifvars

1 0

[Dovecot] Headers "missing" in new CVS version
by Todd Burroughs 13 Jul '05

13 Jul '05

We're experiencing an odd problem with dovecot "losing" headers. This started happening with the CVS release as of July 4 and still happens with July 12. It was working properly June 28. It does not happen using pine or thunderbird. It happens using webmail (twig). When you open the inbox, you see subject, etc. When you open a mail, all of the headers are gone. Returning to the inbox, all the headers are missing. It seems to cache this as well. After returning to the older dovecot, all of the headers are missing. Deleting the cache files fixes this and there does not seem to be any mbox corruption. It does not log any errors or crash. Todd Burroughs

2 1

[Dovecot] separate SSL certificates for pop3s and imaps
by Michael Weiser 13 Jul '05

13 Jul '05

Hi, I'm migrating a uw-imap installation to dovecot. With uw-imap I had different SSL certificates and keys for ipop3d and imapd. How can I configure dovecot to do the same with its pop3s and imaps services? Thanks in advance, -- _________________________creating IT solutions Michael Weiser science + computing ag bei Eisenbahn und Haefen Postfach 11 02 63 Hagellocher Weg 71-75 47142 Duisburg 72070 Tuebingen, Germany phone +49 203 52 26341 www.science-computing.de

2 2

[Dovecot] add inotify support to dovecot
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, attached patch against test76 adds inotify support and the --with-notify=... configure option that defaults to the current check for dnotify using no special method if dnotify cannot be compiled, and can be set to none, dnotify and inotify. If it is set to dnotify or inotify, failure to compile a test program results in an error. Also, it adds | file change notification method ..... : <method> to the output at the end of configure. The only thing I don't like about this patch is the fact that I had to add a field notify_context to struct io, but I didn't see a different way to handle this. Also, the patch doesn't support the condition parameter, it simply always asks for all the relevant changes. I don't really see that it is useful for in the context of file system notifications anyway. I modeled this after ioloop-notify-dn.c with my other patch applied to it, if you don't like the other patch you'll want to "revert" that change in the new ioloop-notify-inotify.c file as well. Oh, and obviously I didn't include patches to configure and all the Makefiles, so of course you'll have to run automake. But you already knew that :) I only tested this with maildir. I did add IN_MODIFY so I think it should work with mbox too, but someone should probably verify. Have fun, johannes

2 2

[Dovecot] sorting question
by Johannes Berg 13 Jul '05

13 Jul '05

Hi, If I understand the thread sorting algorithm correctly (from draft-ietf-imapext-sort-17.txt and the code), it will sort like this (where I use numbers instead of dates with higher numbers being newer mails) 4 10 3 11 2 12 1 13 etc into all the lower levels. Thunderbird will actually sort this like this: 1 13 2 12 3 11 4 10 where threads are sorted by the newest child in them. Now, I am thinking that evolution simply uses dovecot's THREAD feature and doesn't implement anything itself, so that if I wanted to have that kind of threading, I'd have to implement it in dovecot. Would this be easy? I'm thinking that I should just treat all nodes as if they were dummy nodes in sort_root_nodes, but that only fixes the first level afaict, because later dates are not propagated up. Essentially, I think what the algorithm tb uses does is not use a nodes date as it's sorting criterion, but it's newest child, and apply this rule recursively. Does anyone else think this feature would be useful? I regularly end up almost missing mail because it is sorted at such a low position and I don't see the thread at all.. johannes

4 5

[Dovecot] Dovecot runs as ...
by Matt Juszczak 13 Jul '05

13 Jul '05

Hi all, We're using LDAP 100% for everything ... So does that mean that for the following user, I can put another user, like nobody? user = root I guess that user still has to be able to access /var/mail and such, correct?

2 1

[Dovecot] 1.0-test77
by Timo Sirainen 13 Jul '05

13 Jul '05

http://dovecot.org/ It's hot in here. Something like 25-30c for many days now. My brains don't work in that heat. So, this is still not an 1.0-alpha1. I'll put it out when I think the release will actually be fully working :) Changes since test76: - Fixes to FETCHing MIME body parts, especially with message/rfc822 attachments. We hadn't been handling this entirely correctly ever (this part of IMAP spec was pretty difficult for me to understand earlier..). This also caused Dovecot to sometimes disconnect clients fetching [n.MIME] body parts earlier, if someone had that problem. - Maildir: Several bugs fixed with APPEND/COPYing mails - mbox: Keywords weren't stored to index with APPEND - inotify patch by Johannes Berg (and possibly broken by me). Can be enabled with --with-notify=inotify parameter to configure. - SEARCH now doesn't fail if a messageset outside valid range is given to it. Some mobile IMAP client was broken because this didn't work. - Cache mail headers when saving mails to mbox. We should cache everything, but this is a start.. - And other cache file fixes/optimizations

2 3

[Dovecot] PERMANENTFLAGS bug?
by Nils Henrik Tvetene 12 Jul '05

12 Jul '05

Hi, Im new to the list, so might be a FAQ allthough I havent found it anywhere: When I try to connect to dovecot/imap from snappermail (palm), I get a IMAP protocol error. The complaint is about: OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft ) \*)] Flags permitted. As you can see, theres an extra " )" after "Draft". Any clues on how to fix/bypass this? Regards, Nils Henrik Tvetene

3 5

[Dovecot] Dovecot 1.0-stable mbox performance and disconnections
by Chris Wakelin 12 Jul '05

12 Jul '05

I've got some of our busiest users now using Dovecot instead of UW-IMAP with mbox-format mailboxes and predominantly Outlook Express as the client. Doing some perfomance monitoring (with Solaris 8 process accounting), it looks like Dovecot needing to read only 30-50% of the disk blocks needed by UW-IMAP, but I was hoping for better! What seems to happen, is that most of the connections use only a small number of blocks (due to Dovecot indexes, presumably) but occassionally a process will read lots of blocks, sometimes even more than a UW-IMAP session. Is this expected, or is something going wrong with the index updates? I have the default sync settings, I think (mbox_dirty_syncs = yes, mbox_very_dirty_syncs = no, mbox_lazy_writes = yes) My INBOX is an extreme example with ~10,000 messages and most processes reading a few hundred blocks but a couple using 20,000 or so! Also, Dovecot seems to be dropping connections, sometimes, for no good reason (putting some extra i_info lines suggests for "inactivity"). Thunderbird tends to reconnect automatically, though. It seems it may be happening at the end of an IDLE command, something like:- 4 IDLE + idling * 1005 EXISTS DONE * 1005 EXPUNGE but then the expected 4 OK Idle completed never comes. Has anybody else seen this? Best Wishes, Chris -- --+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+---+- Christopher Wakelin, c.d.wakelin(a)reading.ac.uk IT Services Centre, The University of Reading, Tel: +44 (0)118 378 8439 Whiteknights, Reading, RG6 2AF, UK Fax: +44 (0)118 975 3094

2 2

[Dovecot] newbie questions
by Stewart Dean 12 Jul '05

12 Jul '05

Thanks in advance for your patience and assistance. Since a system administrator's work is most successful when nobody knows you've done anything....(ugly that...you get neither raises nor equipment funding as a result), I prefer to learn from other's experiences rather than fail in the same pits. We are considering a switch from UW to Dovecot, since our users persist in using the INBOX as a file cabinet (maybe 25% use homedir folders) and we currently have, I think, .mbox INBOXes which are thus getting massively unmanageable and fragile. Machine config: Running IBM AIX 5.2/5.3 on an F80 with 4GB memory (may be upgraded to 16GB), with IBM's sendmail binary at V8.11.6p2, hand compiled procmail at 3.22, 64-bit binary from C for AIX V6.0 Some questions I couldn't find answered in the docs: 1) Crispin of UW has a formats.txt file in which he lists and evaluates the various formats. He calls the INBOX format type we use .unix (one big honking flat file). Q1: Is this what is described in the Dovecot docs mail-storages.txt file as .mbox? 2) Authentication: The DC docs don't mention using NIS/yp for authentication, that I can find. Q2: Does DC support NIS/yp authentication? I guess I could periodically do a ypcat passwd to a file and point DC at it... 3) on IBM's AIX Unix... Q3: Is there anyone out there running DC on AIX? 5.x or 4.3.3? JFS or JFS2? 4) Inbox location/format: = I will want to move from our legacy .mbox format to, I suppose, the DC default of Maildir++. = I will want to do this in groups over time, rather than all at once, so both formats will have to work = The legacy location of INBOXes has been /var/spool/mail/<userid>. The docs appear to say that Maildir format INBOXes should be in ~/Maildir. Q4:Can the INBOXes be in two location, the converted new Maildirs in ~, and the old unconverted in vsm? Or will I have to override the DC cfg'ed INBOX location to be VSM until I get them all converted and then move them all to ~/Maildir and change the DC config to that? 5) Some mention was made of procmail configuration issues Q5: Can procmail support both formats/locations, or will I have to put changes in the migrated users' procmailrc (what fun!)? Again, thanks! -- ==== Stewart Dean, Unix System Admin, Henderson Computer Resources Center of Bard College, Annandale-on-Hudson, New York 12504 sdean(a)bard.edu voice: 845-758-7475, fax: 845-758-7035

5 4

[Dovecot] mysql
by Jim Edwards 12 Jul '05

12 Jul '05

Hello, Does dovecot require mysql in order to work? Fedora rpms are claiming mysql dependencies. I'm sure you're aware of the long-lived arguement of postgresql v. mysql. If it wasn't your intention to force this, then please snarl at Red Hat. If it was your intention, then grrrrr! Thanks for this product. I like it for it's speed and stability. Jim Edwards

4 3

[Dovecot] bug: very strange behavior with pop3
by Yannick Majoros 12 Jul '05

12 Jul '05

Hello, We have some strange problem which could be related to authentication here. All our user info is in an openldap directory. We normally use pam/getpwent in dovecot to access our user accounts, via nss_ldap/pam_ldap, but we tried to connect directly to the ldap server, with the very same results. We have one user (out of 100) which just cannot use dovecot with pop3. His login/password are accepted, and then dovecot doesn't say anything. I am sure it isn't a client issue: same result with Eudora, Thunderbird and while directly connecting through openssl to POP3s port and "talking POP3". Here is some session transcript: +OK dovecot ready. USER rinstalle +OK PASS M=/)p365 +OK Logged in. And it then stops responding (without giving a reason, breaking the connection). Nothing in the logs, it sees this as a regular login and that's all... Now, it seems that when I copy this user in ldap, the new one occasionaly works. I first thought it did depend on the user name (uid or dn), but it doesn't seem to be the case. I think it is just random. Here is an ldif of this user: dn: uid=rinstalle,ou=divers,ou=login,ou=Autres,ou=Personnes,dc=inma,dc=ucl,dc= ac,dc=be uid: rinstalle cn: compte foireux homeDirectory: /home/xx sn: xxxx uidNumber: 9999 objectClass: top objectClass: person objectClass: inetOrgPerson objectClass: posixAccount gidNumber: 999 ... And getent result (with nss_ldap): #getent passwd rinstalle rinstalle:x:9999:999:compte foireux:/home/xx: To be complete, I should mention that it _does_ work when using local password files... I solved the user problem just by copying his entry a few times. Now, I don't think it is purely ldap-related, as the login _is_ accepted. Is there some guru out here who could help us? Thank you, -- ---------------------------------------------------------------------- Yannick Majoros http://www.inma.ucl.ac.be/~majoros Informaticien AUTO-INMA/FSA/UCL CSAM 4, avenue G. Lemaître B-1348 Louvain-la-Neuve Belgium Tel: +32-10-47.80.10 Fax: +32-10-47.21.80 #JAPH : http://www.inma.ucl.ac.be/~majoros/japh.txt Si vous avez des problèmes pour afficher ce message (accents qui ne passent pas, signature électronique, ...) votre système de mail n'est pas conforme aux standards, voir http://www.inma.ucl.ac.be/~majoros/email.html ----------------------------------------------------------------------

2 4

[Dovecot] weird IDLE behaviour
by Johannes Berg 12 Jul '05

12 Jul '05

Hi, So I was testing things with inotify notifications enabled and noticed that when I a) select a mailbox other than the inbox b) IDLE c) copy mail into the /new folder in that mailbox nothing happens! So I straced it and it always opens the inbox's new/ and cur/ directories for notifications. Is that the correct behaviour? I assumed that if I select some mailbox other than the inbox, IDLE should inform me of status updates in that box, since RFC 2177 says: The Internet Message Access Protocol [IMAP4] requires a client to poll the server for changes to the selected mailbox (new mail, deletions). Now, I get this behaviour by applying the attached patch. But even if I'm wrong, dovecot doesn't implement any sensible behaviour, as it only ever creates *any* notifications during IDLE when the INBOX is selected. [hm. note that I'm only testing maildir] johannes

2 1

[Dovecot] xinetd + dovecot
by vlad 12 Jul '05

12 Jul '05

Hello dovecot, Help me running imapd & pop3d server on xinetd. My file: # cat /etc/xinetd.d/pop-3 service pop3 { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/pop3-login } ####################################### # cat /etc/xinetd.d/imap service imap { disable = no socket_type = stream protocol = tcp wait = no user = root server = /usr/libexec/dovecot/imap-login flags = IPv4 log_type = FILE /var/log/mail/dovecot log_on_success = PID HOST USERID } ####################################### But... # nmap 192.168.1.1 Starting nmap 3.70 ( http://www.insecure.org/nmap/ ) at 2005-07-12 16:53 YEKST Interesting ports on myhost.ru (192.168.1.1): (The 1653 ports scanned but not shown below are in state: closed) PORT STATE SERVICE 25/tcp open smtp 80/tcp open http 110/tcp open pop3 143/tcp open imap 3128/tcp open squid-http ########### # telnet 192.168.1.1 143 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. # telnet 192.168.1.1 110 Trying 192.168.1.1... Connected to 192.168.1.1. Escape character is '^]'. Fatal: EOF while reading environment from master Connection closed by foreign host. Help :) -- With best wishes, vlad mailto:faktroot@mail.ru System/Network Administrator TV/Video Engineer ICQ 163227020 ---------------------------------------------- В любом из нас спит гений. И с каждым днем все крепче...

2 1

[Dovecot] POP retrieval, then reading, of mail does not udpate server status.
by Paul Vatta 12 Jul '05

12 Jul '05

We are currently using the version of Dovecot (0.99.11) that comes with Redhat Enterpise Linux version 4, running on an IBM x445 server (8 CPU, hyperthreading on, 14GB RAM) using the maildir format. We have had to patch this with a change from 0.99.12 so that it doesn't incorrectly report SASL capability upon connection but otherwise it is the version supplied with the OS (we do this to ensure that we don't deviate from the supplied packages too much). The problem encountered is the status of emails on the server isn't being updated. The POP client (Eudora 6.2 in this instance) will retrieve the message, have the message read, apparently update the status on the server (via the "Check Mail" function), but yet the status on the server has not been updated as read (verified by going into our IMP Webmail client, and looking at the mail message in the mailstore - there is no ".S" extension). Using the IMAP protocol doesn't bring about this behaviour. The inconsistency The inconsistency between POP clients and the server status doesn't occur when it comes to deleting messages. Is this a bug, or have we misunderstood how the POP protocol works. Looking at the following: http://www.eudora.com/techsupport/kb/2587hq.html I'm guessing that the POP protocol doesn't update the status? Your confirmation would be most appreciated. Thanks, Paul P.S. As an aside, if you are hesitant about the move from mbox to maildir, don't consider this an obstacle. Our migration was painless and the benefits far outweigh the conversion effort. Dovecot has introduced huge improvements over our Qpopper/UW-IMAP configuration.

2 1

[Dovecot] Calypso or Opera Mail problem?
by Obantec Support 12 Jul '05

12 Jul '05

Hi Are there any know issues with dovecot using pop3 & (Calypso or Opera Mail) ? Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): File isn't in mbox format: /var/spool/mail/cambcom_brianlj Jul 11 09:14:47 proteus2a pop3(cambcom_brianlj): Couldn't open INBOX: Internal error occurred. Error report written to server log. [2005-07-11 09:14:47 there is a file cambcom_brianlj and using webmin or neomail the mails can be read. Mark -- Obantec Support

2 1

Re: [Dovecot] mysql
by Dominic Marks 12 Jul '05

12 Jul '05

On Tuesday 12 July 2005 14:55, Peter Evans wrote: > Tomi Hakala (tomi.hakala(a)clinet.fi) wrote: > > Jim Edwards wrote: > > > Does dovecot require mysql in order to work? > > > > For common email serving with IMAP and POP3, no. > > For IMAP and POP3 session proxying with 1.0-test releases, yes. > > Ew, YUCK. > Why does everyone think $DATABASE is the panacea for all ills? Why you think this is a misuse of a database? Shared network storage might not have been the original purpose, but most DBs can do a pretty good job of this. > Just because they can't/won't cope with multiplicity, does not > mean that X megabytes of general purpose database and all the > overheads have to be used. I can't tell if you have a problem with databases in general, or just the MySQL implementation from this. I guess that you could modify the code easily to use another DBMS which is much smaller such as sqlite. > If it's just proxying, why can't it speak LDAP, or even just a > plain file ... Why write code from scratch when you can use an API for a trusted piece of software which is likely to be available on most systems already? > P > > (I haven't looked at 1.0-test-903 yet, I think I'm still on 70 > something, but no way am I installing mysql ...) Cheers, -- Dominic Marks

1 0

[Dovecot] Mail spools keep getting corrupted with .99.x
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, My mail spools (mbox format) keep getting corrupted with .99.x. I was thinking of running dovecot-stable-20050709.tar.gz ... is this fairly stable? Also, can I use the .99 config file with that code? Thanks! -MAtt

2 1

[Dovecot] Dovecot without a chroot
by Matt Juszczak 12 Jul '05

12 Jul '05

Hi all, We're running dovecot without a chroot (mail admin's request), but we're running it as a non-priv'd user with proper firewall setup. Does this seem to be an OK and average setup? Or is it considered a MUST to chroot something like the imapd daemon, etc. Thanks! -Matt

2 1

[Dovecot] multiple instances of dovecot ?
by Flavien 12 Jul '05

12 Jul '05

Hello, I got a dovecot server running on a Debian Linux machine. I'd like to run another instance of it. I start it with another config file with debug output on stderr. The auth parameters are different : dovecot1: Imapd only, listens on 143, auth=/etc/passwd dovecot2: Imapd only, listens on 144, auth=mysql It kinda works... But... How does one instance of it recognizes the right "imap-login" it should talk to ? What happens in my tests, you guess it: dovecot1 talks to imap-login2, trying to authenticate users that are in /etc/password against mysql... # dovecot -F -c dovecot-config2.conf dovecot: Jul 05 22:49:03 Info: Dovecot starting up dovecot-auth: Jul 05 22:49:04 Info: MySQL: connected to localhost dovecot-auth: Jul 05 22:49:04 Info: Login process 6 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 6 sent handshake: PID 26368 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 connected dovecot-auth: Jul 05 22:49:04 Info: Login process 7 sent handshake: PID 26369 dovecot-auth: Jul 05 22:49:04 Info: Login process 8 sent handshake: PID 26370 dovecot-auth: Jul 05 22:49:27 Info: Login process 9 connected dovecot-auth: Jul 05 22:49:27 Info: Login process 9 sent handshake: PID 26374 dovecot-auth: Jul 05 22:50:02 Info: Login process 10 connected dovecot-auth: Jul 05 22:50:02 Info: Login process 10 sent handshake: PID 26402 dovecot-auth: Jul 05 22:50:02 Info: MySQL: Performing query: SELECT password FROM users WHERE uid='flavien' dovecot-auth: Jul 05 22:50:02 Info: mysql(flavien): Unknown user 'flavien' is not known to the sql db. It's thunderbird trying to get my regular mail using the config1 on port 143, and it has nothing to do with the instance 2 whose output I'm just looking at !!! Any hint ? A+ Flavien.

2 1

[Dovecot] Connection dropped by imap server Query: CAPABILITY
by Srinivas 12 Jul '05

12 Jul '05

Hi all, I have installed squirrelmail-1.4.4 and dovecot 0.9.11 on a debian sarge machine. The tls/ssl support is disabled from both squirrelmail and dovecot imap server. When i try to login i get the following error message: ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY If i give wrong password, it gives the message Unknown user or password incorrect. which is fine. The file /var/log/mail.err, is appended with the following message: Jul 5 18:40:20 server dovecot: chdir(/home/username) failed with uid 1240: Permission denied Jul 5 18:40:20 server dovecot: child 20807 (imap) returned error 89 when i run the command: dovecot -c /etc/dovecot.conf it gives the following error: Fatal: listen(143) failed: Address already in use Later i enabled tls in squirrelmail and dovecot.conf. i got the following error: Warning: fgets(): SSL: fatal protocol error in /usr/share/squirrelmail/functions/imap_general.php on line 88 ERROR: ERROR : Connection dropped by imap-server. Query: CAPABILITY Any suggestions? Thank you Srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

2 1

[Dovecot] cannot download eMails from POP3
by Bastian 12 Jul '05

12 Jul '05

Hi dovecot users, IŽve got a problem with downloading emails: dovecot is installed and configured, I can login but I cannot download mails wich are at my harddisc. After trying to download an email thatŽs in the logfile: pop3-login: Jul 05 10:41:00 Info: Login: webmaster(a)myDomain.de [xx.xxx.xx.xxx] dovecot-auth: Jul 05 10:41:00 Info: Login process 9 disconnected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 connected dovecot-auth: Jul 05 10:41:00 Info: Login process 9 sent handshake: PID 5754 QueryŽs are successfully, like they are required in dovecot-mysql.conf: First password clear, then home directory (/var/opt/vmail/myDomain.de/webmaster), uid and gid. My eMails are at /var/opt/vmail/myDomain.de/webmaster/Maildir/new, does dovecot automatically search for emails in Maildir/new? IŽve no idea, why I cannot download any eMails :( Can you help me? Thank you Bye, Bastian

2 1

[Dovecot] Altering newly created mailboxes
by Thomas Wouters 12 Jul '05

12 Jul '05

There seems to be a bug in updating uid/uidvalidity when copying mail to an empty or newly created mailbox: <new connection> . OK Logged in. . CREATE testfolder4 . OK Create completed. . SUBSCRIBE testfolder4 . OK Subscribe completed. . SELECT otherfolder * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 3 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121171128] UIDs valid * OK [UIDNEXT 4] Predicted next UID . OK [READ-WRITE] Select completed. . UID COPY 1 testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:45] . SELECT testfolder4 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:05:49] <wait a while, doing nothing else> . SELECT testfolder4 * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1121173545] UIDs valid * OK [UIDNEXT 2] Predicted next UID . OK [READ-WRITE] Select completed. The errorlog entries for those two errors are: Jul 12 15:05:45 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:05:49 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder4/dovecot.index: uid_validity = 0, next_uid = 2 I also managed to trigger an assertion failure this way, by trying another COPY after that first failure: . UID COPY 1 testfolder6 . NO Internal error occured. Refer to server log for more information. [2005-07-12 15:16:54] . UID COPY 1 testfolder6 Connection closed by foreign host. The errors for that connection are: Jul 12 15:16:54 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): Corrupted index file /var/run/dovecot-index/ynnoz/.testfolder6/dovecot.index: uid_validity = 0, next_uid = 2 Jul 12 15:17:01 dovecot0 dovecot: IMAP(ynnoz): file mail-index-transaction.c: line 128 (mail_index_buffer_convert_to_uids): assertion failed: (*seq != 0) Jul 12 15:17:01 dovecot0 dovecot: child 6666 (imap) killed with signal 6 Another assertion error I triggered was by trying another SELECT right after the failed SELECT (after the failed COPY): Jul 12 15:14:04 dovecot0 dovecot: IMAP(ynnoz): Maildir /var/spool/mail/.4a/S/tmp/ynnoz/.testfolder5 sync: UIDVALIDITY changed (1121174026 -> 1121174044) Jul 12 15:14:09 dovecot0 dovecot: IMAP(ynnoz): Corrupted transaction log file /var/run/dovecot-index/ynnoz/.testfolder5/dovecot.index.log: Append with UID 1, but next_uid = 2 Jul 12 15:14:12 dovecot0 dovecot: IMAP(ynnoz): file mail-index-view.c: line 595 (mail_index_view_open): assertion failed: (index->map != NULL) Jul 12 15:14:12 dovecot0 dovecot: child 6654 (imap) killed with signal 6 I was able to reproduce this on a near-virgin test76 -- it has one patch that should not interfere; we use default_mail_env = maildir:%Nu:INDEX=/var/run/dovecot-index/%u where %N is a new var_expand character that looks up the argument in a NIS map (we store actual maildir location there, for scalability.) The INDEX setting we use might matter, though. But it feels like a missing update-uid or invalidate-uid call somewhere, I just don't know where :) -- Thomas Wouters <thomas(a)xs4all.net> Hi! I'm a .signature virus! copy me into your .signature file to help me spread!

1 0

[Dovecot] Re: separate SSL certificates for pop3s and imaps
by sean finney 11 Jul '05

11 Jul '05

On Thu, Jul 07, 2005 at 08:58:35PM +0300, dovecot-request(a)dovecot.org wrote: > Hi, > > I'm migrating a uw-imap installation to dovecot. With uw-imap I had > different SSL certificates and keys for ipop3d and imapd. How can I > configure dovecot to do the same with its pop3s and imaps services? i run dovecot in a multihomed server with three different names: mail.foo.edu smtp.foo.edu imap.foo.edu which, for ssl purposes, means we need three different certs to keep applications happy. my approach is to start a seperate dovecot process for each address, and manage the configuration in three seperate files, each one telling dovecot to specifically bind to only one address, and use a seperate runtime directory specific to that address. so for example, in my initscript, instead of just doing something like: start() { echo -n $"Starting $prog: " daemon $prog -c /etc/dovecot.conf RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } i do something like: start() { echo -n $"Starting $prog: " for s in imap mail smtp; do mkdir -p /var/run/dovecot/${s}.foo.edu daemon $prog -c /etc/dovecot/${s}.foo.edu.conf done RETVAL=$? echo [ $RETVAL -eq 0 ] && touch /var/lock/subsys/$prog return $RETVAL } where the value of the ssl cert config is different in each of the files. you could extend this to also have one config file to only listen for pop and the other only for imap. hth, sean

4 5

[Dovecot] Creating encrypted passwords for new users /etc/imap.passwd
by John_R._McWade 09 Jul '05

09 Jul '05

Hello. I've been attempting to locate information on how to actually create the encrypted passwords for a new user in /etc/imap.passwd file. Im really going into this blindly, not having ever used dovecot before, and really just need to be pointed to any existing resources on this topic. This is a setup of dovecot (w/ sendmail,squirrelmail) on FC2. I've got one successful auth so far as a test user, with their info cut/pasted directly from /etc/passwd (it works) whereas using {PLAIN}password causes dovecot to drop the connection with an aborted login. So what I'm actually looking for is a resource or a quick response regarding the actual creation of the encrypted password in /etc/passwd style. Any clues on where I should look for this info? John

2 1

[Dovecot] io leak when dnotify is enabled but not available
by Johannes Berg 08 Jul '05

08 Jul '05

Hi, When dnotify is enabled, but not in the kernel, there's an io leak: $ /sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes a select inbox * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 787 EXISTS * 0 RECENT * OK [UIDVALIDITY 1106061449] UIDs valid * OK [UIDNEXT 790] Predicted next UID a OK [READ-WRITE] Select completed. b IDLE imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument imap(johannes): Error: fcntl(F_NOTIFY) failed: Invalid argument + idling DONE b OK Idle completed. q logout * BYE Logging out q OK Logout completed. imap(johannes): Warning: I/O leak: 0x10068ff0 (8) Attached patch fixes it, I hope the patch is correct :) johannes

1 0

[Dovecot] stat() failed with mbox /var/mail/%u
by Jungshik Shin 08 Jul '05

08 Jul '05

Hello, Over the last 12 hours or so, I've been wrestling with a mysterious dovecot issue. After upgrading a mail server I'm helping my friend with maintaining from Fedora Core1 to Fedora Core4, I realized that I couldn't use UW-IMAP4 anymore (well, I can compile it myself, but it turned out that UW-IMAP was the main cause of the server's having load average as high as 30 from time to time so that I decided to move onto dovecot). Although I loved to migrate to maildir, I didn't dare to tackle the migration (I have a lot more important things to do :-)) to maildir. Instead, I thought that dovecot's indexing of mbox files should make the performance of the server a lot better than UW-IMAP. (in addition, we upgraded the HW from P3 800MHz single to P4 dual 3GHz). Last night, I experimented with several mboxes of one user's account (INBOX in /var/mail/<userid> and others in ~/mail/) and it worked perfectly well. So, I moved mboxes of other users and launched 'dovecot' informing users that the mail server is back up again. However, it didn't work with inbox (for IMAP) and POP3. There's no problem accessing mail folders in '~/mail', but accessing /var/mail/%u (inbox for IMAP) and using the same folder with POP3 didn't work. The error I got in the log file is: Jul 8 01:17:24 biosoft dovecot: pop3-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 01:17:24 biosoft dovecot: POP3(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: auth(default): Error sending status request (Operation not permitted) Jul 8 00:34:45 biosoft dovecot: imap-login: Login: xyz123 [::ffff:1xx.2yy.zz.178] Jul 8 00:34:45 biosoft dovecot: IMAP(xyz123): stat() failed with mbox file /var/mail/xyz123: Permission denied ls -ld / /var /var/mail/ /var/mail/xyz123 drwxr-xr-x 23 root root 4096 Jul 7 19:28 / drwxr-xr-x 26 root root 4096 Jul 7 23:35 /var drwxrwxrwt 2 root mail 4096 Jul 8 00:36 /var/mail/ -rw-rw---- 1 xyz123 mail 130751237 Jul 7 23:37 /var/mail/xyz123 I tried various combinations of permissions and ownerships for /var/mail (1777, 2775) and /var/mail/<userid>, but nothing made any difference. I also tweaked mbox locking methods ('dotlock fcntl' or 'fcntl' alone) When I came across this problem with the latest stable (2005-07-06), I went back to FC4's default package (0.99??), but with a slightly different error message in the log file, basically I had the same problem. I kept the default values for most configuration parameters. What I changed are listed below: mail_extra_groups = mail pop3_uidl_format = %08Xv%08Xu protocols = imap imaps pop3s default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u Also attached is the entire /etc/dovecot.conf I'm really desperate to get some enlightening answers on this problem, for which I'll really appreciate you. Thanks tons in advance, Jungshik ## 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=/usr/share/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 imaps pop3s # 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 = no # 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/share/ssl/certs/dovecot.pem #ssl_key_file = /usr/share/ssl/private/dovecot.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 = yes # 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. # http://wiki.dovecot.org/Rootless #login_chroot = yes # 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. # Note that this user is NOT used to access mails. # http://wiki.dovecot.org/UserIds #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 # Greeting message for clients. #login_greeting = Dovecot ready. ## ## 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 = 500 #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 = mail_extra_groups = mail # ':' 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 for # specific users in user database by giving /./ in user's home directory # (eg. /home/./user chroots into /home). Note that usually there is no real # need to do chrooting, Dovecot doesn't allow users to access files outside # their mail directory anyway. #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 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 = default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u # If you need to set multiple mailbox locations or want to change default # namespace settings, you can do it by defining namespace sections: # # You can have private, shared and public namespaces. The only difference # between them is how Dovecot announces them to client via NAMESPACE # extension. Shared namespaces are meant for user-owned mailboxes which are # shared to other users, while public namespaces are for more globally # accessible mailboxes. # # REMEMBER: If you add any namespaces, the default namespace must be added # explicitly, ie. default_mail_env does nothing unless you have a namespace # without a location setting. Default namespace is simply done by having a # namespace with empty prefix. #namespace private { # Hierarchy separator to use. You should use the same separator for all # namespaces or some clients get confused. '/' is usually a good one. #separator = / # Prefix required to access this namespace. This needs to be different for # all namespaces. For example "Public/". #prefix = # Physical location of the mailbox. This is in same format as # default_mail_env, which is also the default for it. #location = # There can be only one INBOX, and this setting defines which namespace # has it. #inbox = yes # If namespace is hidden, it's not advertised to clients via NAMESPACE # extension or shown in LIST replies. This is mostly useful when converting # from another server with different namespaces which you want to depricate # but still keep working. For example you can create hidden namespaces with # prefixes "~/mail/", "~%u/mail/" and "mail/". #hidden = yes #} # Space-separated list of fields to initially save into cache file. Currently # these fields are allowed: # # flags, date.sent, date.received, size.virtual, size.physical # mime.parts, imap.body, imap.bodystructure # # Different IMAP clients work in different ways, so they benefit from # different cached fields. Some do not benefit from them at all. Caching more # than necessary generates useless disk I/O, so you don't want to do that # either. # # Dovecot attempts to automatically figure out what client wants and it keeps # only that. However the first few times a mailbox is opened, Dovecot hasn't # yet figured out what client needs, so it may not perform optimally. If you # know what fields the majority of your clients need, it may be useful to set # these fields by hand. If client doesn't actually use them, Dovecot will # eventually drop them. # # Usually you should just leave this field alone. The potential benefits are # typically unnoticeable. #mail_cache_fields = # Space-separated list of fields that Dovecot should never save to cache file. # Useful if you want to save disk space at the cost of more I/O when the fields # needed. #mail_never_cache_fields = # 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 # Locking method for index files. Alternatives are fcntl, flock and dotlock. # Dotlocking uses some tricks which may create more disk I/O than other locking # methods. #lock_method = fcntl # 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 # 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 mbox_read_locks = fcntl mbox_write_locks = 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 # When mbox changes unexpectedly we have to fully read it to find out what # changed. If the mbox is large this can take a long time. Since the change # is usually just a newly appended mail, it'd be faster to simply read the # new mails. If this setting is enabled, Dovecot does this but still safely # fallbacks to re-reading the whole mbox file whenever something in mbox isn't # how it's expected to be. The only real downside to this setting is that if # some other MUA changes message flags, Dovecot doesn't notice it immediately. # Note that a full sync is done with SELECT, EXAMINE, EXPUNGE and CHECK # commands. #mbox_dirty_syncs = yes # Like mbox_dirty_syncs, but don't do full syncs even with SELECT, EXAMINE, # EXPUNGE or CHECK commands. If this is set, mbox_dirty_syncs is ignored. #mbox_very_dirty_syncs = no # Delay writing mbox headers until doing a full write sync (EXPUNGE and CHECK # commands and when closing the mailbox). This is especially useful for POP3 # where clients often delete all mails. The downside is that our changes # aren't immediately visible to other MUAs. #mbox_lazy_writes = yes # 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 = "%Us(%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 # Send IMAP capabilities in greeting message. This makes it unnecessary for # clients to request it with CAPABILITY command, so it saves one round-trip. # Many clients however don't understand it and ask the CAPABILITY anyway. #login_greeting_capability = no # 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. # netscape-eoh: # Netscape 4.x breaks if message headers don't end with the empty "end of # headers" line. Normally all messages have this, but setting this # workaround makes sure that Netscape never breaks by adding the line if # it doesn't exist. This is done only for FETCH BODY[HEADER.FIELDS..] # commands. Note that RFC says this shouldn't be done. # tb-negative-fetch: # Thunderbird sometimes messed up some calculations and wants to read # the message past it's end, giving negative size to FETCH BODY[]<..> # command. This workaround just hides the error message. #imap_client_workarounds = outlook-idle } ## ## 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 or seen 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_no_flag_updates = no # Support LAST command which exists in old POP3 specs, but has been removed # from new ones. Some clients still wish to use this though. Enabling this # makes RSET command clear all \Seen flags from messages. #pop3_enable_last = no # POP3 UIDL format to use. You can use following variables: # # %v - Mailbox UIDVALIDITY # %u - Mail UID # %m - MD5 sum of the mailbox headers in hex (mbox only) # %f - filename (maildir only) # # If you want UIDL compatibility with other POP3 servers, use: # UW's ipop3d : %08Xv%08Xu # Courier version 0 : %f # Courier version 1 : %u # Courier version 2 : %v-%u # Cyrus (<= 2.1.3) : %u # Cyrus (>= 2.1.4) : %v.%u # # Note that Outlook 2003 seems to have problems with %v.%u format which is # Dovecot's default, so if you're building a new server it would be a good # idea to change this. %08Xu%08Xv should be pretty fail-safe. pop3_uidl_format = %08Xv%08Xu # 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. # oe-ns-eoh: # Outlook Express and Netscape Mail breaks if end of headers-line is # missing. This option simply sends it if it's missing. #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 # Authentication cache size in kilobytes. #auth_cache_size = 0 # Time to live in seconds for cached data. After this many seconds a cached # record is forced out of cache. #auth_cache_ttl = 3600 # 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 character translations before it's looked up from databases. The # value contains series of from -> to characters. For example "#@/@" means # that '#' and '/' characters are translated to '@'. #auth_username_translation = # 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 # Even more verbose logging for debugging purposes. Shows for example SQL # queries. #auth_debug = no auth default { # Space separated list of wanted authentication mechanisms: # plain digest-md5 cram-md5 apop anonymous mechanisms = plain # Password database specifies only the passwords for users. # http://wiki.dovecot.org/Authentication # 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 # sql <config path>: SQL database, see doc/dovecot-sql.conf passdb = pam # User database specifies where mails are located and what user/group IDs # own them. For single-UID configuration use "static". # http://wiki.dovecot.org/Authentication # http://wiki.dovecot.org/VirtualUsers # 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 # sql <config path>: SQL database, see doc/dovecot-sql.conf userdb = passwd # 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. Note that this user is NOT used to access mails. # That user is specified by userdb above. 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 2

[Dovecot] "Leave a copy on server" not marking messages as read...
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, Our customers who have "Leave a copy on server" with POP3 continue to check their email, and each time they check it it re-downloads all emails (so it doesn't seem to be updating those messages already downloaded). Any ideas? Thanks! -Matt

1 0

[Dovecot] IMAP Folders
by Matt Juszczak 07 Jul '05

07 Jul '05

Hi all, We're using the mbox format and I tried setting up IMAP on my boss's computer tonight. He likes subfolders, and although they work, he can't seem to remove subfolders once he created them, nor create new folders without using something other than his mail client (like mkdir from the command line). Any ideas on this? Does dovecot just not officially support IMAP and subfolders with the mbox format? Or could it be a permissions issue? -Matt

2 1

[Dovecot] RE: dovecot not able to access sentmail folder in home directory(chdir)
by vineet 07 Jul '05

07 Jul '05

problem is solved the problem was with the access permissions to the folder having the users' folders make sure that dovecot has the permission to access the folders containg the users' folders vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] test76 segfaults?
by Johannes Berg 06 Jul '05

06 Jul '05

Hi, I was just trying to port my dspam plugin to the latest test release but ran into trouble so I decided to test the code itself first. I have the following maildir: johannes:~/.mail$ find . ./cur ./new ./new/test ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/tmp Now I run $ exec /usr/sbin/dovecot --exec-mail imap * PREAUTH [CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN NAMESPACE LOGIN-REFERRALS] Logged in as johannes A SELECT INBOX * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted. * 1 EXISTS * 1 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1120680468] UIDs valid * OK [UIDNEXT 2] Predicted next UID A OK [READ-WRITE] Select completed. B COPY 1 SPAM imap(johannes): Error: Corrupted index file /home/johannes/.mail/.SPAM/dovecot.index: uid_validity = 0, next_uid = 2 Segmentation fault However, it actually did copy something: johannes:~/.mail$ find . ./cur ./cur/test:2, ./new ./tmp ./.SPAM ./.SPAM/cur ./.SPAM/new ./.SPAM/new/1120680473.P1535Q0M900310.johannes ./.SPAM/tmp ./.SPAM/dovecot.index ./.SPAM/dovecot-uidlist ./.SPAM/dovecot-uidlist.lock ./.SPAM/dovecot.index.log.2 ./.SPAM/dovecot.index.log ./dovecot.index.log ./dovecot.index ./dovecot.index.cache ./dovecot-uidlist The mail in that, for reference, is just this: --- A: xxx Subject: hallo! From: johannes X-DSPAM-Signature: asdf wow! --- johannes

1 1

[Dovecot] I need sleep (dovecot auth / postfix 2.3)
by /dev/rob0 06 Jul '05

06 Jul '05

I need the new sleep feature (smtpd_*_restrictions) of Postfix 2.3 snapshots, but I'm using the Dovecot auth patch. The 2.2.1 patch had problems in the snapshots I tried. Fortunately the problems were very simple. rob0@room101:~/src/mail/postfix-2.3-20050630$ patch -p1 < ~/dl/postfix-2.2.1-dovecot-auth.patch [snip] patching file src/smtpd/Makefile.in Hunk #1 FAILED at 1. Hunk #2 FAILED at 296. 2 out of 2 hunks FAILED -- saving rejects to file src/smtpd/Makefile.in.rej patching file src/smtpd/smtpd.c Hunk #1 FAILED at 854. Hunk #2 succeeded at 1006 (offset 16 lines). Hunk #3 succeeded at 1173 (offset 1 line). Hunk #4 succeeded at 1306 (offset 20 lines). Hunk #5 succeeded at 1562 (offset 33 lines). Hunk #6 succeeded at 1692 (offset 54 lines). Hunk #7 succeeded at 1834 (offset 72 lines). Hunk #8 succeeded at 2918 (offset 135 lines). Hunk #9 succeeded at 2952 (offset 73 lines). Hunk #10 succeeded at 3262 (offset 152 lines). Hunk #11 succeeded at 3301 (offset 73 lines). Hunk #12 succeeded at 3551 (offset 154 lines). 1 out of 12 hunks FAILED -- saving rejects to file src/smtpd/smtpd.c.rej [snip] I fixed the failures manually. Attached is a patch which only changes those two files ... it's a supplement to the existing patch as provided by Timo: http://dovecot.org/patches/postfix/postfix-2.2.1-dovecot-auth.patch I have not yet tested either sleep or AUTH, because I *do* need sleep for real. :) But it did compile with no errors nor [noted] warnings. I do have this running. -- mail to this address is discarded unless "/dev/rob0" or "not-spam" is in Subject: header

1 1

[Dovecot] Username mapping
by nodata 06 Jul '05

06 Jul '05

Hello. We're using dovecot with mysql for authentication, with postfixadmin for the admin web interface. We are moving users from passwd file usernames to email@domain style logins. Is there a better way to allow both sets of usernames (old and new) to work with dovecot than by adding extra copies of rows to the mailboxes table and changing the username? i.e. does dovecot support some kind of username mapping or aliasing? Thanks a lot

3 2

[Dovecot] dovecot not able to access sentmail folder in home directory(chdir)
by vineet 06 Jul '05

06 Jul '05

using dovecot version 0.99.11 while accessing through squirrelmail or even connecting manually(using openssl) to the server dovecot is not able to access the folder the mail.err log file has the following entry: dovecot: (/home/user) permission denied error no 89 returned by child process the squirrel mail error was connection dropped by imap server Query capability thanks vineet _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0

[Dovecot] dovecot 1 for production? which one?
by Jeff A. Earickson 06 Jul '05

06 Jul '05

Hi, I've been lurking on the list since Spring, planning to replace UW-IMAP with dovecot 1.0 sometime this summer. The recent thread on "1.0" has not given me a good feeling about seeing it before summer's end. So I wonder if I should use dovecot-1.0-test-xx code or dovecot-stable-[date] code (which seems to change every day, how stable is that???). This is confusing, advice please. My setup: Solaris 9, mbox format. Jeff Earickson Colby College

2 1

[Dovecot] Root password or key access to pop3?
by Matt Juszczak 05 Jul '05

05 Jul '05

Hi all, We're an ISP, and are currently looking for a way for our tech support guys to access customer's email without having shell access to the server, or knowing the customer's password. We'd like to install a custom webmail client that would only show the user's inbox and the ability to delete the messages. The problem is, that we would have to know the user's password in order for my PHP pop3 code to go out and fetch the mail. Is there a way I can setup and/or patch dovecot so that any connection from <said IP address> can use the password "jq3erjq3535" for any account, and it will authenticate them? Or is this some kind of custom patch I would need to write? Thanks! -Matt

3 5

[Dovecot] error connecting dovecot from squirrelmail
by Srinivas 04 Jul '05

04 Jul '05

the problem is: 1. the error in the mailerr file is: Jul 4 19:42:26 obelix dovecot: chdir(/home/user) failed with uid 1229: Permission denied Jul 4 19:42:26 obelix dovecot: child 16385 (imap) returned error 89 2. the error msg given by Squirrelmail is: ERROR: connection dropped by imapserver QUERY: CAPABILITY the dovecot and squirrelmail settings are same on both the servers 3. the mailbox settings in dovecot.conf: default_mail_env = mbox:~/mail:INBOX=/var/spool/mail/%u OS: Debian Sarge stable thanks srinivas _______________________________________________ No banners. No pop-ups. No kidding. Make My Way your home on the Web - http://www.myway.com

1 0