- dovecot - dovecot.org

[Dovecot] file index-mail-headers.c: line 408 (index_mail_get_header): assertion failed: (ret != 0)
by Dmitry Khrustalev 26 Jul '04

26 Jul '04

FreeBSD 4.10-RELEASE, dovecot-1.0-test29 crashes on sort and thread commands: Jul 25 15:12:08 owl dovecot: imap-login: Login: dima [81.19.64.101] Jul 25 15:12:26 owl dovecot: IMAP(dima): file index-mail-headers.c: line 408 (index_mail_get_header): assertion failed: (ret != 0) Jul 25 15:12:26 owl dovecot: child 20384 (imap) killed with signal 6 (gdb) bt #0 0x281e0fc4 in kill () from /usr/lib/libc.so.4 #1 0x2822293e in abort () from /usr/lib/libc.so.4 #2 0x8086c73 in i_internal_panic_handler ( fmt=0x8095720 "file %s: line %d (%s): assertion failed: (%s)", args=0xbfbff8cc "\tW\t\b\230\001") at failures.c:374 #3 0x8086827 in i_panic ( format=0x8095720 "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #4 0x806d0f9 in index_mail_get_header (_mail=0x80bf41c, field=0x80955ce "Date") at index-mail-headers.c:408 #5 0x806b8fd in index_mail_get_date (_mail=0x80bf41c, timezone=0x0) at index-mail.c:218 #6 0x8059b1c in mail_sort_input (ctx=0x80a1150, mail=0x80bf41c) at imap-sort.c:420 #7 0x80596ae in imap_sort (client=0x80ad180, charset=0x80b1180 "US-ASCII", args=0x80c8010, sort_program=0x80a10d0) at imap-sort.c:252 #8 0x8054ec8 in cmd_sort (client=0x80ad180) at cmd-sort.c:123 #9 0x80560ae in client_handle_input (client=0x80ad180) at client.c:318 #10 0x805614d in _client_input (context=0x80ad180) at client.c:354 #11 0x808a852 in io_loop_handler_run (ioloop=0x80ab040) at ioloop-poll.c:193 #12 0x808a245 in io_loop_run (ioloop=0x80ab040) at ioloop.c:248 #13 0x805bc5b in main (argc=1, argv=0xbfbffbb0, envp=0xbfbffbb8) at main.c:217 (gdb)

3 2

[Dovecot] dovecot.conf: default_mail_env
by Sebastien 26 Jul '04

26 Jul '04

I just installed Dovecot on Debian and everyting seems to be working fine except for the fact that it can't seem to find my mails when I log in. All my mails are stored in the file ~/mail/Inbox. In the dovecot.conf file I put: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u and it's not working. What is the part: mbox:~/mail/ for ? and what is the part: INBOX=/var/mail/%u for ? I read the documentation but I don't understand. Can anyone help me ?

3 2

[Dovecot] 1.0-test30
by Timo Sirainen 26 Jul '04

26 Jul '04

http://dovecot.org/test/ Mostly just fixes. Fixed some crashes with cache file. Fixed "randomly" occuring mbox parsing problem. Namespace handling was pretty much rewritten. Non-hidden namespaces will also show up in LIST replies now, so if you have eg.: namespace private { prefix = mboxes location = mbox:~/mail } Then clients would show "mboxes" as normal folder. Subscription file handling also changed and will probably change more.. Currently subscription file is specific to the namespace where the mailboxes are. So in above example subscribing to "mboxes/foo" would use ~/mail/.subscriptions file rather than the default. I'm not exactly sure if this is a good idea or not.. It probably needs to be configurable with some subscriptions = yes|no per-namespace setting.

1 0

[Dovecot] imap folders
by Roger D. Vargas 26 Jul '04

26 Jul '04

Until last week I was using old imap daemon, then i installed FEdora Core 2 and it was replaced by dovecot or cyrus. I decided to use dovecot, and managed to configure it. But I still have a problem, the users imap folders (stored in their home dirs) arent visible, only the inbox. How can I recover those folders? -- Roger Durañona Vargas Linux user #180787 A cada momento nos rodea lo desconocido. Es alli donde uno tiene que buscar el conocimiento. Paul Muad'Dib Atreides. Children of Dune

2 1

[Dovecot] Some users cannot read mail: assertion failed
by Robert Munteanu 26 Jul '04

26 Jul '04

Hi all! I am a recent user of dovecot. First of all, the migration from UW-IMAP was definitely worth it. But now I've run into some troubles. Two of my users complain that they can't read their Inboxes, but other folders work fine. The error message I get in the logs look like: lynx imap(gheorghe.bancos): file buffer.c: line 357 (buffer_set_start_pos): assertion failed: (abs_pos <= I_MIN(buf->used, buf->limit)) lynx dovecot: child 1823 (imap) killed with signal 6 The problems have been reported with both MS Outlook and SquirrelMail. What causes this problem and how can I fix it? Thank you, -- Robert Munteanu _______________________________________________________________ Connex scaneaza automat toate mesajele impotriva virusilor folosind Trend Micro VirusWall. Connex automatically scans all messages for viruses using Trend Micro VirusWall. _______________________________________________________________ Nota: Este posibil ca produsul Trend Micro VirusWall sa nu detecteze toti virusii noi sau toate variantele lor. Va rugam sa luati in considerare ca exista un risc de fiecare data cind deschideti fisiere atasate si ca MobiFon nu este responsabila pentru orice prejudiciu cauzat de decizia dvs. Disclaimer: It is possible that the Trend Micro VirusWall product may not be able to detect all new viruses and variants. Please be aware that there is a risk involved whenever opening e-mail attachments to your computer and that MobiFon is not responsible for any damages caused by your decision to do so.

2 6

[Dovecot] paypal link for donations to dovecot webpage?
by security officer 26 Jul '04

26 Jul '04

Paypal link for donations to dovecot webpage? Really good sofware ;) -- Eero

1 0

[Dovecot] Passwords in passwd-file
by Andrew Boothman 25 Jul '04

25 Jul '04

Hi! I'm trying to use MD5 hashed password in a passwd-file (not the system one). I've set auth_userdb = passwd-file /my/passwd/file auth_passdb = passwd-file /my/passwd/file auth.txt additionally describes a syntax like: auth_userdb = passwd-file[34] /my/passwd/file to denote MD5 passwords in the file, but I've been unable to get any combination of using []'s after passwd-file to work. Dovecot complains: "Unknown userdb type". How is it best to store passwords in a passwd-file using Dovecot 0.99.10.7? Ideally I want to use PHP to generate the passwords being entered into the file. Thanks for any pointers! Andrew

2 2

[Dovecot] Bug? 1.0.0-test28 NFS locking problems
by Tim Southerwood 24 Jul '04

24 Jul '04

Hi Slight problem - linux 2.4 running dovecot, Solaris 2.8 home directory server. Full lockd support etc. I had to make the following code patches (at end of mail for clarity) to get dovecot to read the users mbox files at all. 1) fcntl with F_SETLKW will not work against a Solaris 2.8 server as proved with a small test program. Other forms of fcntl (ie F_SETLK) are OK. I noticed there are some code witches, but setting mbox_lock_timeout=0 only seems to knock one of the fcntl's over to F_SETLK 2) O_CREAT | O_EXCL are documented not to work over NFS properly (see man open(2) on linux). So I knocked out the O_EXCL and combined with (1) dovecot will talk over NFS to remote mbox files. THESE ARE NOT VIABLE CODE PATCHES They illustrate a problem I found - they are hackish and totally wrong. I'm not sure of the best way to correct this problem cleanly, so I am just submitting it as a potential bug. Cheers Tim Southerwood ************************************************** --- dovecot-1.0-test28/src/lib/file-lock.c.orig 2004-07-20 14:29:47.000000000 +0100 +++ dovecot-1.0-test28/src/lib/file-lock.c 2004-07-20 14:30:15.000000000 +0100 @@ -38,7 +38,7 @@ fl.l_start = 0; fl.l_len = 0; - while (fcntl(fd, timeout != 0 ? F_SETLKW : F_SETLK, &fl) < 0) { + while (fcntl(fd, timeout != 0 ? F_SETLK : F_SETLK, &fl) < 0) { if (timeout == 0 && (errno == EACCES || errno == EAGAIN)) return 0; --- dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-lock.c.orig 2004-07-20 14:29:54.000000000 +0100 +++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-lock.c 2004-07-20 14:30:35.000000000 +0100 @@ -361,7 +361,7 @@ fl.l_start = 0; fl.l_len = 0; - wait_type = max_wait_time == 0 ? F_SETLK : F_SETLKW; + wait_type = max_wait_time == 0 ? F_SETLK : F_SETLK; while (fcntl(ctx->ibox->mbox_fd, wait_type, &fl) < 0) { if (errno != EINTR) { if (errno != EAGAIN && errno != EACCES) ************************************************** and ************************************************** diff -NaurbB dovecot-1.0-test28.orig/src/lib/file-dotlock.c dovecot-1.0-test28/src/lib/file-dotlock.c--- dovecot-1.0-test28.orig/src/lib/file-dotlock.c 2004-06-28 18:28:01.000000000 +0100+++ dovecot-1.0-test28/src/lib/file-dotlock.c 2004-07-20 14:50:33.000000000 +0100 @@ -192,7 +192,7 @@ return -1; } - fd = open(*path_r, O_RDWR | O_EXCL | O_CREAT, 0666); + fd = open(*path_r, O_RDWR | O_CREAT, 0666); if (fd != -1) return fd; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/maildir/maildir-util.c dovecot-1.0-test28/src/lib-storage/index/maildir/maildir-util.c--- dovecot-1.0-test28.orig/src/lib-storage/index/maildir/maildir-util.c 2004-06-16 01:50:41.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/maildir/maildir-util.c 2004-07-20 14:51:25.000000000 +0100@@ -241,7 +241,7 @@ if (stat(path, &st) < 0 && errno == ENOENT) { /* doesn't exist */ mode_t old_mask = umask(0); - fd = open(path, O_WRONLY | O_CREAT | O_EXCL, mode); + fd = open(path, O_WRONLY | O_CREAT, mode); umask(old_mask); if (fd != -1 || errno != EEXIST) break; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c--- dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c 2004-07-20 14:45:55.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c 2004-07-20 14:49:56.000000000 +0100@@ -386,7 +386,7 @@ int fd; /* make sure inbox file itself exists */ - fd = open(storage->inbox_path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(storage->inbox_path, O_RDWR | O_CREAT, 0660); if (fd != -1) (void)close(fd); @@ -579,7 +579,7 @@ } /* create the mailbox file */ - fd = open(path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(path, O_RDWR | O_CREAT, 0660); if (fd != -1) { (void)close(fd); return 0; diff -NaurbB dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c.mbox dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c.mbox--- dovecot-1.0-test28.orig/src/lib-storage/index/mbox/mbox-storage.c.mbox 2004-07-11 22:03:09.000000000 +0100+++ dovecot-1.0-test28/src/lib-storage/index/mbox/mbox-storage.c.mbox 2004-07-20 14:50:58.000000000 +0100@@ -386,7 +386,7 @@ int fd; /* make sure inbox file itself exists */ - fd = open(storage->inbox_path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(storage->inbox_path, O_RDWR | O_CREAT, 0660); if (fd != -1) (void)close(fd); @@ -579,7 +579,7 @@ } /* create the mailbox file */ - fd = open(path, O_RDWR | O_CREAT | O_EXCL, 0660); + fd = open(path, O_RDWR | O_CREAT, 0660); if (fd != -1) { (void)close(fd); return 0; ************************************************** -- Tim J Southerwood Senior Programmer CSG, Dept of Computing, Imperial College, London

4 19

[Dovecot] (no subject)
by Lorenzo Conti 23 Jul '04

23 Jul '04

2 1

[Dovecot] RFE: MD5 encryption with for plain text passwords
by Felix Schwarz 23 Jul '04

23 Jul '04

Hi, due to compatibility issues with mail clients I think I have to use plain text authentication. In order to secure the passwords during their transport I'll use SSL encryption. After reading some documentation I think that I'll have to store the passwords as plain text in the authdb. That is something I dislike very much as it is a (imho) good tradition for unix to store only encrypted passwords for security reasons. I would like to see the possibility in dovecot to store the passwords for plain text authentication md5 encrypted. That should be easy to implement (just one md5 encryption before comparing the given password with the stored one) and could improve security. As this would be an api change it should be made configurable (and in the first versions this setting should default to the actual behavior). How do you like this idea? Maybe I can provide a patch but I won't work on this if you won't include it within dovecot at all. And last but not least I want to thank you for your great support! I really appreciate it! :-) -- Felix

3 2

[Dovecot] CRAM-MD5
by Felix Schwarz 23 Jul '04

23 Jul '04

Hi, after getting dovecot working with PostgreSQL and plaintext passwords I tried to use md5 encrypted passwords with mozilla. www.roughtrade.net/dovecot says that Mozilla only supports CRAM-MD5 and that CRAM-MD5 is included in HEAD. Now I have two questions: 1) Is the md5 hash stored in passdb with cram-md5 the same as in digest-md5? 2) Is a new dovecot stable build planned within the next two weeks (which includes CRAM-MD5)? (I guess the answer is no :-( 3) Are there any dovecot rpms with pgsql and CRAM-md5 supprt? -- Felix

3 3

Re: [Dovecot] Dovecot auth problem on FreeBSD 4.10
by Viren Patel 22 Jul '04

22 Jul '04

> On Thu, 2004-07-22 at 20:35, Viren Patel wrote: >> Hope this helps. Should I send the entire socket.h file? > > Hmm. What would happen if in src/lib/fdpass.c you added: > > #undef CMSG_LEN > #undef CMSG_DATA > > #define CMSG_LEN(l) (sizeof(struct cmsghdr) + (l)) > #define CMSG_DATA(cmsg) ((u_char *)(cmsg) + sizeof(struct cmsghdr)) > > Yes! This did the trick. It seems to be working fine now. Thanks for your help. I can now go on to further testing and imaps/pop3s. I am seriously looking at Dovecot for our production mail server. Viren Patel University of Texas at Austin

2 1

[Dovecot] Dovecot auth problem on FreeBSD 4.10
by Viren Patel 22 Jul '04

22 Jul '04

Hello. I am trying to setup Dovecot on an Alpha running FreeBSD 4.10. I am simply trying the imap/pop3 protocols at this time. But with both protocols the log message I get is: pop3-login: fd_send(5) failed: Bad file descriptor dovecot: child 275 (login) returned error 89 or imap-login: fd_send(5) failed: Bad file descriptor dovecot: child 275 (login) returned error 89 I have tried various combinations of: auth = default|plain|pam auth_userdb = passwd auth_passdb = passwd|shadow|pam|passwd-file but nothing works. What am I doing wrong? Thanks. Viren Patel University of Texas at Austin

5 5

[Dovecot] help: The current command did not succeed. The mail server responded: Invalid mask.
by Ivo Rütsche 22 Jul '04

22 Jul '04

on your mozilla client: go to "Edit" / "Mail & Newsgroups Account Settings" / [your account] / "Server Settings" / "Advanced..." / "IMAP" / "Other Users" make sure your text box is empty (default is "~") bye ivo

1 0

[Dovecot] One final issue
by Tom Ray [Lists] 22 Jul '04

22 Jul '04

Timo- Thanks for all the help. After I changed the permissions to the virtual user I setup I had a few small issues but was able to work through them. Now IMAP is running great. But my new question is, do I need to do anything to get it to work with POP? My server refuses to respond on 110 and I'm wondering if there is something I need to do? I was under the impression that Dovecot can handle both POP/IMAP requests. TIA Tom

3 8

[Dovecot] [PATCH] add LOGIN authentication mechanism
by Andrey Panin 22 Jul '04

22 Jul '04

Hello, attached patch (1.0-test29) adds LOGIN authentication mechanism. Tested with KMail and seems working. Please consider applying. Best regards. P.S. I also have NTLM authentication working and plan to submit it RSN. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

2 1

[Dovecot] Authentification with PostgreSQL
by Felix.Schwarz＠web.de 22 Jul '04

22 Jul '04

Hi all, I found Dag Wieers' Fedora Core 2 rpm on http://dag.wieers.com/packages/dovecot/ and installed it. Now dovecot-auth isn't complaining anymore about an unknown userdb type but I can't get authentication working. /etc/dovecot.conf (...) # Authentication process name. auth = default # plain digest-md5 anonymous auth_mechanisms = plain auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_user = root auth_verbose = yes (...) /etc/dovecot-pgsql.conf connect = host=localhost dbname=xams-dovecot user=dovecot password=hallo default_pass_scheme = PLAIN password_query = SELECT password FROM users WHERE username = '%u' user_query = SELECT home, uid, gid FROM users WHERE username = '%u' If I try to login over imap (no ssl) with Mozilla Mail, authentification will always fail (username: felix(a)schwarz-online.org, password: "hallo"). /var/log/syslog Jul 22 15:48:47 steinchen postgres[2057]: [30-1] DEBUG: forked new backend, pid=2198 socket=10 Jul 22 15:48:47 steinchen postgres[2198]: [31-1] DEBUG: Passwortpaket erhalten Jul 22 15:48:47 steinchen postgres[2198]: [32-1] LOG: Verbindung authorisiert: Benutzer=dovecot Datenbank=xams-dovecot (...) Jul 22 15:51:15 steinchen dovecot(pam_unix)[2210]: check pass; user unknown Jul 22 15:51:15 steinchen dovecot(pam_unix)[2210]: authentication failure; logname= uid=0 euid=0 tty= ruser= rhost= /var/log/dovecot.log dovecot: Jul 22 15:48:46 Info: Dovecot starting up dovecot-auth: Jul 22 15:51:18 Info: PAM: pam_authenticate(felix(a)schwarz-online.org) failed: Authentication failure $ psql -d xams-dovecot dovecot xams-dovecot-> SELECT password FROM users WHERE username = 'felix(a)schwarz-online.org'; password ---------- hallo xams-dovecot=> SELECT home, uid, gid FROM users WHERE username = 'felix(a)schwarz-online.org'; home | uid | gid ----------+-----+----- /home/fs | 500 | 500 What is wrong? Password encryption? Is there a possibility to see what dovecot gets from Mozilla and what are the expected results of the sql queries? I am stuck as I don't know exactely why authentification failes... thanks for your help -- Felix

3 2

[Dovecot] [PATCH] POP3 CAPA command RFC violation
by Andrey Panin 22 Jul '04

22 Jul '04

Hello, looks like SASL capability reported by dovecot in response to POP3 CAPA command doesn't conforms with rfc2449 which says: Examples: C: CAPA S: +OK Capability list follows S: TOP S: USER S: SASL CRAM-MD5 KERBEROS_V4 S: RESP-CODES S: LOGIN-DELAY 900 S: PIPELINING S: EXPIRE 60 S: UIDL S: IMPLEMENTATION Shlemazle-Plotz-v302 S: . And later: The POP3 AUTH command [POP-AUTH] permits the use of [SASL] authentication mechanisms with POP3. The SASL capability indicates that the AUTH command is available and that it supports an optional base64 encoded second argument for an initial client response as described in the SASL specification. The argument to the SASL capability is a space separated list of SASL mechanisms which are supported. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Dovecot sends SASL capability as list of AUTH=FOO pairs. Looks like copy-paste from IMAP code. Patch attached. Best regards. -- Andrey Panin | Linux and UNIX system administrator pazke(a)donpac.ru | PGP key: wwwkeys.pgp.net

1 0

[Dovecot] namespaces and behaviour of LIST and SELECT with leading ~
by Tim Southerwood 21 Jul '04

21 Jul '04

Hi One weirdness when going through the code: (We are migrating from WU-IMAP and have users with a mixture of ~/IMAP/ and ~/Mail/ for storing mail - but all user INBOX=~/.email thankfully. IMAP client config is even more random and we have 1800 users. I have been playing with namespaces to translate various prefixes ala: default_mail_env = mbox:%h/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n # Note lack of IMAP ^^^ (So clients can use ~/IMAP or ~/Mail - we have a # historic mixture) full_filesystem_access = no namespace private { separator = / inbox = yes prefix = hidden = no location = mbox:.email } namespace private { separator = / prefix = hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = IMAP/ hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = ~/IMAP/ hidden = no location = mbox:IMAP/ } User tstest has INBOX in ~/.email and mail folders in ~/IMAP/ all in mbox format: Here's a sample conversation: * OK dovecot ready. 1 login tstest ******* 1 OK Logged in. 1 list "" % * LIST (\NoInferiors \UnMarked) "/" INBOX * LIST (\NoInferiors) "/" "Trash" * LIST (\NoInferiors) "/" "Queue" * LIST (\NoInferiors) "/" "Sent" * LIST (\NoInferiors) "/" "Drafts" * LIST (\NoInferiors) "/" "Blah" 1 OK List completed. Good 1 list "" IMAP/% * LIST (\NoInferiors) "/" "IMAP/Trash" * LIST (\NoInferiors) "/" "IMAP/Queue" * LIST (\NoInferiors) "/" "IMAP/Sent" * LIST (\NoInferiors) "/" "IMAP/Drafts" * LIST (\NoInferiors) "/" "IMAP/Blah" 1 OK List completed. Good 1 list "" ~/IMAP/% 1 OK List completed. Oops (being caught by mbox_is_valid_mask as prefix begins with ~ and the client supplied prefix is being tested, not the virtual one after namespace prefix substitution) But... 1 select Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Yes 1 select IMAP/Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Yes 1 select ~/IMAP/Blah * FLAGS (\Answered \Flagged \Deleted \Seen \Draft) * OK [PERMANENTFLAGS (\Answered \Flagged \Deleted \Seen \Draft \*)] Flags permitted.* 5 EXISTS * 0 RECENT * OK [UNSEEN 1] First unseen. * OK [UIDVALIDITY 1090326264] UIDs valid * OK [UIDNEXT 6] Predicted next UID 1 OK [READ-WRITE] Select completed. Oo - this works despite the ~ I would argue that with namespace {} directives, the behaviour of SELECT is correct. I would suggest that it may be better to test the final translated path thus: if full_filesystem_access = yes let anything go. else make sure that final translated mail path is identical OR a subpath of the default_mail_env mbox folder path. (INBOX is a special case and can be matched as well) This is a suggestion - what do you think? I'd have a go myself but I don't yet feel competant with the dovecot code. Best wishes Tim -- Tim J Southerwood

2 1

[Dovecot] dovecot-1.0-test27 crash on FETCH
by Wouter Van Hemel 21 Jul '04

21 Jul '04

Hello, I've got a crash with -test27 on a FETCH, just after logging in. Attached are the mailbox (1 message only), logs, sniffed session, testcase and core dump backtrace. If the dovecot.conf is needed, just ask (it's pretty much the default configuration). Maybe this has just been fixed in -test28, in which case you can just delete this email. :) Btw, it's rather irrelevant, but does anybody know a good way to read the qmail alias user's mailbox remotely (imap? The only way seems by assigning a password to the account... Regards, wouter

2 4

[Dovecot] Fatal: Unknown userdb type 'pgsql'
by felix.schwarz＠web.de 21 Jul '04

21 Jul '04

Hello, I'm trying to use postgres authentication with dovecot on a linux system running Fedora Core 2. Installation of dovecot was done by installing the rpm included in the fedora distribution ("yum install dovecot"). from /etc/dovecot.conf auth_userdb = pgsql /etc/dovecot-pgsql.conf auth_passdb = pgsql /etc/dovecot-pgsql.conf but the logs tell me: dovecot: Jul 21 19:28:39 Info: Dovecot starting up dovecot-auth: Jul 21 19:28:40 Fatal: Unknown userdb type 'pgsql' dovecot: Jul 21 19:28:40 Error: Auth process died too early - shutting down dovecot: Jul 21 19:28:40 Error: child 5229 (auth) returned error 89 imap-login: Jul 21 19:28:40 Fatal: fd_send(-1) failed: Broken pipe imap-login: Jul 21 19:28:40 Fatal: fd_send(-1) failed: Broken pipe I think that the fedora rpm was compiled without postgresql support. - Is the information given above sufficient for an educated guess? - Would that lead to the above error message? - What other errors may cause this behavior? - How can I check which authentification types are supported by my dovecot-auth? - Are there any other Fedora rpms compiled with postgres support available on the net? thank you for your help :-) -- Felix

3 3

RE: [Dovecot] Probably a bad idea but.....
by Mark Lidstone 21 Jul '04

21 Jul '04

Hi everyone, Just done some testing and thought I'd share the results. I've successfully moved a few test emails from a Mercury/32 Windows server to Maildirs. I created an IMAP folder for each user ".INBOX.Old\ Mail" and put the email in there. It's accessable via IMAP but does not show up as a new email when the user uses POP3 to collect their email - exactly what I was after (they're all using POP3 at the moment, but I will be pushing them to move to IMAP at a later date). I'm going to copy the rest of the email in one go overnight so if you don't get another email from me on here assume it worked. Thanks for the help Timo. 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: 21 July 2004 13:58 To: Mark Lidstone Cc: dovecot(a)dovecot.org Subject: Re: [Dovecot] Probably a bad idea but..... On Wed, 2004-07-21 at 14:11, Mark Lidstone wrote: > Mercury stores mail in a similar way to Maildirs, different folders > with separate files for each mail, stored in plaintext RFC822 format. > How sensible would it be to copy the files over from the Mercury > server to users maildirs on a Linux server? > > The filenames are in a different format but I don't know if that would > cause a problem? You'll lose message flags, but as long as the filenames don't contain ':' characters you can just copy them.

1 0

Re: [Dovecot] 1.0.0-test28 Problem with INDEX
by Tim Southerwood 21 Jul '04

21 Jul '04

On Tue, 20 Jul 2004 20:35:04 +0300 Timo Sirainen <tss(a)iki.fi> wrote: > On Tue, 2004-07-20 at 19:13, Tim Southerwood wrote: > > default_mail_env = > > mbox:%h/IMAP/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n > > > > The INBOX indexes are being built correctly in /var/cache/dovecot, > > but all other indexes for folders are still being built in the > > user's home directory. > > > > I had it working once - but it seems fragile - almost as if the > > config parser is sensitive to context??? Sorry - seems vague, but I > > can't pin this down reliably. > > Have you set full_filesystem_access = yes? That's the only thing that > I can think of that might make it use different directory (and even > then only if you access the mboxes as "~/IMAP/box"). > > OK - I've been look at the code all day and sticking debug statements in. full_filesystem_access = yes will cause the indexes to stick with the mail files and not be based under INDEX=dir. But - using default_mail_env = mbox:%h/:INBOX=%h/.email:INDEX=/var/cache/dovecot/%n # Note lack of IMAP ^^^ (So clients can use ~/IMAP or ~/Mail - we have a # historic mixture) full_filesystem_access = no namespace private { separator = / prefix = hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = IMAP/ hidden = no location = mbox:IMAP/ } namespace private { separator = / prefix = ~/IMAP/ hidden = no location = mbox:IMAP/ } Will cause the indexes to also stick with the mail files, not use INDEX=dir Bit of a problem with NFS involved. I know I could use INDEX=MEMORY, but I'm worried about what will happen if the machine exhausts it's VM (not impossible with my site). I'm happy to play with this a bit longer if you could give me a hint: where is the path to the index file computed? Cheers Tim -- Tim J Southerwood

1 0

[Dovecot] Probably a bad idea but.....
by Mark Lidstone 21 Jul '04

21 Jul '04

Hi all, I've got a few users I'm trying to migrate from a Mercury Mail server to a dovecot IMAP/POP3 setup. I was hoping to use some sort of imap-copy type script to move email from the Mercury server to dovecot server, but the Mercury box is running so slow it's impossible. Mercury stores mail in a similar way to Maildirs, different folders with separate files for each mail, stored in plaintext RFC822 format. How sensible would it be to copy the files over from the Mercury server to users maildirs on a Linux server? The filenames are in a different format but I don't know if that would cause a problem? Any help gratefully appreciated, 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] Almost there.
by Tom Ray [Lists] 21 Jul '04

21 Jul '04

Hey Timo- I got everything working now that I can log in properly...but I'm have a permissions issue and I'm not sure how to set it..I've been playing with ownership and permissions and I'm still getting this imap(tom(a)testdomain.com): mkdir_parents(/var/spool/mail/indexes/testdomain.com/tom/.imap/INBOX) failed: Permission denied What's that permission/ownership in that folder supposed to be?

2 1