- dovecot - dovecot.org

Re: [Dovecot] [ #14832]: Capital letters in POP3 logins
by Gerald V. Livingston II 02 Apr '05

02 Apr '05

I just tested and IMAP doesn't ignore case either. Remove the UPPER CASE maildir created by your POP3 login then do the same thing with an IMAP client. Set up the IMAP client to use an UPPER CASE username and when you log-in/refresh folders it creates the new UPPERCASE empty Maildir all over again. Crap, between this and the missing QUOTA feature I guess I'm gonna have to rip out Dovecot and use Courier. I really wanted to use Dovecot for it's speed with the indexing. What I don't understand is -- all usernames in my test database are stored in lower case -- shouldn't it simply fail to match and cause the login to fail? Can anyone point out how to force the match to be case sensitive? I'll investigate and get back to the list. It would be "nicer" though if Dovecot converted all username input to lower case before authenticating to maintain uniqueness of email addresses. Gerald On Wed, 30 Mar 2005 21:16:12 +0400 "support(a)majordomo.ru" <support(a)majordomo.ru> wrote: > Using dovecot (version 1.0-test59, with mysql-auth) I saw strange problem: > after authentication by POP3 in case that username given has capital letters, for example SupportTeam(a)majordomo.ru, > dovecot creates new maildir 'SupportTeam' for this username instead reading mails from existing maildir 'supportteam'. > Then dovecot scans created maildir 'SupportTeam' and returns 0 messages (sure:). > IMAP4 works fine in the same time. > Can I solve this problem or it is virtually "bug" of dovecot?

4 5

[Dovecot] dovecot authentication problem on OSX
by Mac Shabba 01 Apr '05

01 Apr '05

after reading good comments on dovecot i'm trying to get it going I've got an apple g4, with osx 10.3.8 Compile and install went fine. I can also start dovecot, and telnet to it...but I can't login Even before I try to auth i get this in the log: >>localhost dovecot: Dovecot starting up >>localhost imap-login: opendir(".") failed when trying to get list of authentication servers: Permission denied I can't find any reference to this error message, and I'm completely puzzled about it I just need to know how to figure out what is causing this...is it related to pam, folder permissions, server config, .... MacShabba

2 1

[Dovecot] Anybody tracking the GSSAPI patch?
by David B Harris 01 Apr '05

01 Apr '05

Hey all, I'm doing some Kerberos stuff at work, and I'm thinking it'd be nice if dovecot had GSSAPI support. I found http://dovecot.org/list/dovecot/2004-July/004039.html (thanks Colin :), but it's a long ways away from applying to the current stable tree. I'm wondering - has anybody else been keeping a local copy of this patch up to date? Thanks, Dave -- Arguing with an engineer is like wrestling with a pig in mud. After a while, you realise the pig is enjoying it. OpenPGP v4 key ID: 4096R/59DDCB9F Fingerprint: CC53 F124 35C0 7BC2 58FE 7A3C 157D DFD9 59DD CB9F Retreive from subkeys.pgp.net or risk key corruption

1 0

[Dovecot] test65 killed by SIGSEV
by Thomas Hummel 31 Mar '05

31 Mar '05

Hi, I had successfully set up dovecot-1.0-test62 + ldap pass/user db, but now I'm encoutering a SIGSEV problem with a similar set up of a brand new dovecot-1.0-test65 installation. The auth process is killed by a SIGSEV as reported in the error log file : dovecot: Mar 30 17:06:59 Error: child 28291 (auth) killed with signal 11 To be precise, the problem occurs in the "ldap_lookup_pass" function (auth/passdb-ldap.c) just before loging the ldap request parameters (auth_request_log_debug) and to actually perform the search (db_ldap_search). The signal occurs on the call of t_strarray_join(attr_names, ",") What I'm observing is that the "attr_names" array of the "passdb_ldap_conn" ldap connection doesn't seem to hold the right attributes : while in the test62 version it holded 'uid' and 'userPassword', it holds now 'uid' and 'homeDirectory'. As a matter of fact, the content of this array seem to change between the "preinit" and "init" passdb function and I'm not quite sure this is legal. So my client (actually just a test through telnet) gets a 'NO Temporary authentication failure'. Here's a gdb backtrace of the process : ------- Program received signal SIGSEGV, Segmentation fault. 0x08065bf6 in t_strarray_join (arr=0x807aa20, separator=0x8067b1a ",") at strfuncs.c:571 571 len = strlen(*arr); (gdb) bt full #0 0x08065bf6 in t_strarray_join (arr=0x807aa20, separator=0x8067b1a ",") at strfuncs.c:571 alloc_len = 8 sep_len = 1 len = 9 pos = 39 needed_space = 0 str = 0x806e488 "uid,homeDirectory,,,uidNumber,gidNumber" #1 0x080578a1 in ldap_lookup_pass (auth_request=0x8077a10, ldap_request=0x8077ab0) at passdb-ldap.c:181 conn = (struct ldap_connection *) 0x807a810 vars = (const struct var_expand_table *) 0x807a9a0 attr_names = (const char **) 0x807aa08 filter = 0x806e268 "(&(objectClass=posixAccount)(uid=dovetest))" base = 0x806e468 "ou=personnes, dc=pasteur, dc=fr" str = (string_t *) 0x806e268 #2 0x08050947 in auth_request_verify_plain (request=0x8077a10, password=0x806e198 "pass", callback=0x8054790 <verify_callback>) at auth-request.c:261 passdb = (struct passdb_module *) 0x806b9e0 result = -1077941592 cache_key = 0x646975 <Error reading address 0x646975: Bad address> __PRETTY_FUNCTION__ = "auth_request_verify_plain" ---Type <return> to continue, or q <return> to quit--- #3 0x0805486e in mech_plain_auth_continue (request=0x8077a10, data=0xffffffff <Error reading address 0xffffffff: Bad address>, data_size=6580597) at mech-plain.c:62 authenid = 0x806e181 "dovetest" error = 0xbfbfeaf8 "(ë¿¿²ø\004\b\020@\b\b\034\020\b\b(ë¿¿dø\004\b\002" pass = 0x806e198 "pass" i = 0 count = 2 #4 0x08051a80 in auth_request_handler_auth_begin (handler=0x8084010, args=0x808101c "1\tPLAIN\tservice=IMAP\tsecured\tlip=127.0.0.1\trip=127.0.0.1\tresp=AGRvdmV0ZXN0AHBhc3M=") at auth-request-handler.c:327 len = 20 mech = (struct mech_module *) 0x0 request = (struct auth_request *) 0x8077a10 list = (const char * const *) 0x806e114 name = 0x806e130 "resp" arg = 0x806e160 "\200á\006\b\016" initial_resp = 0x806e0de "AGRvdmV0ZXN0AHBhc3M=" initial_resp_data = (const void *) 0x646975 initial_resp_len = 0 id = 1 buf = (buffer_t *) 0x806e160 valid_client_cert = 0 ---Type <return> to continue, or q <return> to quit--- #5 0x0804f8b2 in auth_client_input (context=0x80785c0) at auth-client-connection.c:144 conn = (struct auth_client_connection *) 0x80785c0 line = 0x8081017 "AUTH\t1\tPLAIN\tservice=IMAP\tsecured\tlip=127.0.0.1\trip=127.0.0.1\tresp=AGRvdmV0ZXN0AHBhc3M=" #6 0x0805f8dc in io_loop_handler_run (ioloop=0x8078000) at ioloop-poll.c:184 data = (struct ioloop_handler_data *) 0x806d080 pollfd = (struct pollfd *) 0x2 tv = {tv_sec = 1, tv_usec = 999555} io = (struct io *) 0x806d5c0 t_id = 2 msecs = 0 ret = 0 call = 1 #7 0x0805f319 in io_loop_run (ioloop=0x8078000) at ioloop.c:218 No locals. #8 0x080541dd in main (argc=1, argv=0x1) at main.c:311 foreground = 0 (gdb) ------- Thanks -- Thomas Hummel | Institut Pasteur <hummel(a)pasteur.fr> | Pôle informatique - systèmes et réseau

1 2

[Dovecot] Pine and prefix - LIST command bug?
by Chris Wakelin 31 Mar '05

31 Mar '05

I've been having problems with Pine 4.62 talking to Dovecot 1.0 stable. It's fine when the folder collection path is empty, but if I have "~/mail/" or "mail/" it gives access errors (I'm using the "~/mail/", "mail/" etc. hidden namespaces for backwards compatability). It seems to me that Dovecot is not replying correctly to a "LIST" command with empty mailbox name: - Dovecot: xyz LIST "" "" * LIST (\NoSelect) "/" "" xyz LIST "~/mail/" "" * LIST (\NoSelect) "/" "" xyz LIST "mail/" "" * LIST (\NoSelect) "/" "" UW-IMAP; xyz LIST "" "" * LIST (\NoSelect) "/" "" xyz LIST "~/mail/" "" * LIST (\NoSelect) "/" ~/ xyz LIST "mail/" "" * LIST (\NoSelect) "/" mail/ RFC 2060 says: An empty ("" string) mailbox name argument is a special request to return the hierarchy delimiter and the root name of the name given in the reference. The value returned as the root MAY be null if the reference is non-rooted or is null. In all cases, the hierarchy delimiter is returned. This permits a client to get the hierarchy delimiter even when no mailboxes by that name currently exist. Mind you, it looks like at least our UW-IMAP also gets it wrong for "~/mail/". Of course, I may be misunderstanding something! 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 8

Re: [Dovecot] [ #14832]: Capital letters in POP3 logins
by Jakob Hirsch 31 Mar '05

31 Mar '05

support(a)majordomo.ru wrote: > Can I solve this problem or it is virtually "bug" of dovecot? No bug, just the "garbage in, garbage out" principle. Mysql's string matches are case-insensisitive by default, so when dovecot asks mysql for the user information of UsEr1, it will get the information of user1 and therefore assumes that UsEr1 is a valid login. It's not dovecot's fault. If you want the match case-insensitive (so UsEr1 will be rejected), add the BINARY attribute to the userid field or change your query to '... WHERE BINARY userid = "%u"' in password_query and user_query. If you want to allow logins as UsEr1 (and let him access user1's mail), you have to change your dovecot.conf, I think. Use %h instead of %u there, and let user_query return the home directory with something like 'SELECT CONCAT('/var/spool/vmail/',LOWER(userid)) AS home, ...'.

3 5

[Dovecot] [ #14832]: Capital letters in POP3 logins
by support＠majordomo.ru 30 Mar '05

30 Mar '05

Hello all! I'm newbie here :) Using dovecot (version 1.0-test59, with mysql-auth) I saw strange problem: after authentication by POP3 in case that username given has capital letters, for example SupportTeam(a)majordomo.ru, dovecot creates new maildir 'SupportTeam' for this username instead reading mails from existing maildir 'supportteam'. Then dovecot scans created maildir 'SupportTeam' and returns 0 messages (sure:). IMAP4 works fine in the same time. Can I solve this problem or it is virtually "bug" of dovecot? Thanks in advance! Vladimir

1 0

[Dovecot] [ #14832]: Capital letters in POP3 logins
by support＠majordomo.ru 30 Mar '05

30 Mar '05

Здравствуйте, Это автоматически созданное сообщение, просьба не отвечать на него. Ваше письмо, отправленное на support(a)majordomo.ru с темой "Capital letters in POP3 logins", получено почтовой системой хостинг-провайдера Majordomo.ru. Вам ответят в ближайшее время. Вашему письму присвоен номер 14832 , если в дальнейшем Вы будете связываться с нами по данному вопросу, просьба его указать. С уважением, служба техподдержки Majordomo.ru. =========================================== URL http://www.majordomo.ru phone +7 812 3200732 phone +7 095 7272278 e-mail support(a)majordomo.ru

1 0

[Dovecot] Chrooting dovecot.
by BSD Mail 30 Mar '05

30 Mar '05

Greetings, I have installed Dovecot under FreeBSD 5_3 It is pretty impressive. I got SSL working with no problem for both imap and pop3. Besides that I do still want to chroot Dovecot. I noticed that there are some options in the dovecot.conf that are intended for this. Unfortunately online resources on how to do that can't be found on google. Although I'm running the server as user dovecot. I still do have this: dovecot pop3-login 491 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 490 1 tcp4 10.0.1.4:995 *:* dovecot pop3-login 489 1 tcp4 10.0.1.4:995 *:* dovecot imap-login 488 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 487 1 tcp4 10.0.1.4:993 *:* dovecot imap-login 486 1 tcp4 10.0.1.4:993 *:* root dovecot 481 5 tcp4 10.0.1.4:993 *:* root dovecot 481 6 tcp4 10.0.1.4:995 *:* Fine for the first six lines it's doing what it's doing. But the last two lines are running as root. That is why I want to chroot the server. I would like if anyone can point me to some howto or notes on how to do so. If there is none I will have to configure a jail just for this purpose. Thanks in advance. -- Regards,

4 3

[Dovecot] Abort error in current CVS version
by Todd Burroughs 30 Mar '05

30 Mar '05

I just tried the latest version from CVS and got this error: dovecot: Mar 29 18:11:33 Error: 27526 IMAP(todd.bluegenesis.com): Corrupted index cache file /mailhome/new/t/b/todd.bluegenesis.com/.imap/INBOX/dovecot.index.cache: Duplicated field in header: hdr.RESENT-TO dovecot: Mar 29 18:11:33 Error: 27526 IMAP(todd.bluegenesis.com): file index-mail-headers.c: line 68 (index_mail_parse_header_finish): assertion failed: (match[match_idx] != mail->header_match_value + 1) dovecot: Mar 29 18:11:34 Error: child 27526 (imap) killed with signal 6 I deleted the index files, didn't help. I checked my mailbox and there aren't any mails with a duplicate "Resent-To" header. With older versions of dovecot, I still get this error, but it does not abort. (Using mbox, if it matters) Here's a backtrace: Core was generated by `imap'. Program terminated with signal 6, Aborted. #0 0xffffe410 in ?? () (gdb) bt #0 0xffffe410 in ?? () #1 0xbffff528 in ?? () #2 0x00000006 in ?? () #3 0x00006b86 in ?? () #4 0xb7ef1d41 in raise () from /lib/tls/libc.so.6 #5 0xb7ef3529 in abort () from /lib/tls/libc.so.6 #6 0x0809744a in i_internal_panic_handler ( fmt=0x6 <Address 0x6 out of bounds>, args=0x6b86 <Address 0x6b86 out of bounds>) at failures.c:374 #7 0x08097864 in i_panic ( format=0x80a3bcc "file %s: line %d (%s): assertion failed: (%s)") at failures.c:173 #8 0x080748cf in index_mail_parse_header (part=0x0, hdr=0x0, mail=0x80c2f20) at index-mail-headers.c:210 #9 0x08090963 in _read (stream=0x80c3be8) at istream-header-filter.c:170 #10 0x0809a293 in i_stream_read (stream=0x80c3c0c) at istream.c:51 #11 0x0809a4d1 in i_stream_read_data (stream=0x80c3c0c, data=0xbffff7c4, size=0xbffff7c8, threshold=58) at istream.c:229 #12 0x08092f5f in message_parse_header_next (ctx=0x80c1920, hdr_r=0xbffff7f8) at message-parser.c:735 #13 0x0809363e in message_parse_header (part=0x0, input=0x80c3c0c, hdr_size=0x0, callback=0x80757c0 <search_header>, context=0xbffff880) at message-parser.c:655 ---Type <return> to continue, or q <return> to quit--- #14 0x08075640 in index_storage_search_next (_ctx=0x80c5568, mail=0x80c2f20) at index-search.c:502 #15 0x0808b705 in mailbox_search_next (ctx=0x6, mail=0x80c2f20) at mail-storage.c:405 #16 0x08057bee in cmd_search (cmd=0x80ba980) at cmd-search.c:33 #17 0x080594f5 in _client_input (context=0x80ba940) at client.c:334 #18 0x0809c5da in io_loop_handler_run (ioloop=0x80b95b0) at ioloop-poll.c:184 #19 0x0809bcf9 in io_loop_run (ioloop=0x80b95b0) at ioloop.c:218 #20 0x080603a7 in main (argc=1, argv=0xbffffa74, envp=0xbffffa7c) at main.c:229 (gdb)

1 0