- dovecot - dovecot.org

[Dovecot] saslauthd/dovecot/root
by Andrew Instone-Cowie 16 Oct '05

16 Oct '05

Hi, I am using SMTP-AUTH over TLS with sendmail, to allow remote users to authenticate and send mail via my server, and this uses saslauthd to authenticate users. I have set up saslauthd with the "MECH=rimap" mechanism, so it uses the local IMAP server, Dovecot, for authentication. I want to do this because Dovecot is set up to use /etc/passwd for user credentials (so I don't have multiple password files to manage), and Dovecot handles restricting the range of valid UIDs (including blocking root). (Using the default MECH=shadow with saslauthd allows all users to authenticate, which I don't want) For real "normal" users, this all works fine - right password = user can relay mail, wrong password = relaying denied. So far so good. If I try to authenticate as root (which I want NEVER to work), with the wrong password, Dovecot correctly refuses to allow root IMAP access and saslauthd/sendmail denies the relay. But if I try to authenticate as root with the correct password (which I still want NOT to work!), Dovecot still refuses IMAP access, and puts this in the maillog: Oct 5 14:16:18 hadrian dovecot: Logins with UID 0 not permitted (user root) Oct 5 14:16:18 hadrian imap-login: Internal login failure: root [127.0.0.1] But saslauthd seems to treat this as a successful authentication and still allows root to relay email! So: Dovecot problem or saslauthd problem? Server is running CentOS 4.1, fully patched. Packages are dovecot-0.99.11-2.EL4.1, cyrus-sasl-2.1.19-5.EL4, sendmail-8.13.1-2. Thanks Andrew

2 1

[Dovecot] Confused
by Matt Juszczak 16 Oct '05

16 Oct '05

Hi all, I really don't know where to go from here. I've traced and pasted, but never heard responses.... I'm getting the following (see bottom of this email) in a single day of dmesg....most of the time the error message in the log file is something like: Oct 5 09:21:43 mail1 dovecot: imap(*****): file mbox-save.c: line 280 (mbox_save_init_file): assertion failed: (mbox->mbox_lock_type != F_RDLCK) Some of them also have something to do with storage space. Any ideas at all? Thanks :) Regards, Matt ---dmesg snip---- pid 20905 (imap), uid 34411: exited on signal 6 pid 42237 (imap), uid 33345: exited on signal 6 pid 42757 (imap), uid 33345: exited on signal 6 pid 43036 (imap), uid 33345: exited on signal 6 pid 41987 (imap), uid 32768: exited on signal 6 pid 99572 (imap), uid 35371: exited on signal 6 pid 99759 (imap), uid 35371: exited on signal 6 pid 49474 (imap), uid 33345: exited on signal 6 pid 82739 (imap), uid 33345: exited on signal 6 pid 67938 (imap), uid 33345: exited on signal 6 pid 68042 (imap), uid 33345: exited on signal 6 pid 68115 (imap), uid 33345: exited on signal 6 pid 68169 (imap), uid 33345: exited on signal 6 pid 68869 (imap), uid 33345: exited on signal 6 pid 72285 (imap), uid 31502: exited on signal 6 pid 98711 (imap), uid 32277: exited on signal 6 pid 99429 (imap), uid 32277: exited on signal 6 pid 36768 (imap), uid 33345: exited on signal 6 pid 38110 (imap), uid 33345: exited on signal 6 pid 38115 (imap), uid 34959: exited on signal 6 pid 53649 (imap), uid 34910: exited on signal 6 pid 53943 (imap), uid 34910: exited on signal 6 pid 70003 (imap), uid 33345: exited on signal 6 pid 23368 (imap), uid 31646: exited on signal 6 pid 59048 (imap), uid 34709: exited on signal 6 pid 59164 (imap), uid 34709: exited on signal 6 pid 59347 (imap), uid 34709: exited on signal 6 pid 13848 (imap), uid 33345: exited on signal 6

2 2

[Dovecot] Dovecot error: Unknown protocol 'imap\
by Paul E Virgo 16 Oct '05

16 Oct '05

First, thanks to Timo for the patch -- fixed missing protocol name error on my Solaris box. Now, I've moved the whole distro, part and parcel, to a Centos 4.0 Linux box, with the HOPE of getting it working there. But when I've set all of it up, I get the error message, mentioned in the 'Subject' line, in my /var/log/dovecot file. Any clues? PEV

2 1

[Dovecot] Dovecot pop3 locking up
by Neil Wilson 16 Oct '05

16 Oct '05

Hi guys and girls, I am having a problem with Dovecot. It seems like it's the dovecot auth daemon that is locking up(I'm guessing) I am running SuSe 9.3 Pro, and Dovecot 0.99.14 Everything works perfectly for a few days, and then eventually I end up with tons of what look to be "stale" processes.(I'm guessing roughly 300 like below.) 4204 ? S 0:00 dovecot-auth 24722 ? S 0:00 pop3-login 24723 ? S 0:00 pop3-login 24724 ? S 0:00 dovecot-auth 24921 ? S 0:00 dovecot-auth When I "telnet 127.0.0.1 110" I get a login, and I can type "User blabla" I get an "OK" then I type in "pass blabla" and then I don't get any response, and I have to kill my session with "Ctrl ]" and then "quit". I am using both POP3 and IMAP, but it seems to be only the POP3 daemon that dies. There are roughly 60 users on the network, and it dies after roughly 5 days of usage, and I then have to restart Dovecot by running /etc/init.d/dovecot stop and then start Any help would be appreciated. Thanks. -- Neil Wilson

2 2

[Dovecot] deliver: select destination folder
by Dominik Werder 16 Oct '05

16 Oct '05

Hello, I wanted a commandline switch within deliver to select the destination folder within an IMAP account, so I added the -f switch, heres the diff, the implementation is only "proof of concept" hehe, I didnt checked if theres any security riscs in doing this. Could we add something like this to dovecot? diff deliver.c.orig deliver.c 342c342 < const char *destination, *mail; --- > const char *destination, *mail, *folder; 355a356 > folder = NULL; 364a366,373 > } else if (strcmp(argv[i], "-f") == 0) { > /* destination folder */ > i++; > if (i == argc) { > i_fatal_status(EX_USAGE, > "Missing folder argument"); > } > folder = argv[i]; 378a388,391 > if (folder == NULL) { > folder = "INBOX"; > } > 449c462 < if (save_mail(storage, "INBOX", input) < 0) --- > if (save_mail(storage, folder, input) < 0) bye! Dominik

2 1

[Dovecot] Problem with pop3 and alpha3
by Alfonso Sparano 16 Oct '05

16 Oct '05

I don't know. I'm not tried with a real client but only with telnet. I would like to be sure that everything is correct before try with outlook/Eudora/thunderbird at all. -----Messaggio originale----- Da: dovecot-bounces(a)dovecot.org [mailto:dovecot-bounces@dovecot.org] Per conto di Andrew Hutchings Inviato: domenica 16 ottobre 2005 10.21 A: dovecot(a)dovecot.org Oggetto: Re: [Dovecot] Problem with pop3 and alpha3 On Sun, 2005-10-16 at 10:06 +0200, aspar(a)unisa.it wrote: > Hi all, I have a problem with dovecot-alpha3 and pop3 protocol (on a tru64 > 5.1a...) > > In my Maildir/cur there are 8144 mails and if I use pop3 protocol I receive in > the output 8146 line instead of 8144. The problem is that 2 mails are > duplicated . The output of "List" command is like: > > 1 51265 > 2 261783 > . > . > . > 2987 30291 > 2987 30291 (duplicated line) > 2988 16631 > .. > 4601 1231 > 4602 8921 > 4602 8921 (Another duplicated line) > 4603 1313 > . > > I've deleted dovecot.* and dovecot-uidlist in the Maildir path but the problem > remains. > > Suggest? Is a bug? > I've tried also to remove the first 1000 messages but the problem now is on the > mail number 2635 and not 1987 like I can think. > > Alfonso Is the client generating mail not found errors when this happens? If so it may be related to the problem I am seeing. Regards Andrew -- Andrew Hutchings (A-Wing) - Linux Guru Netserve Consultants - http://www.domaincity.co.uk/ Linux CDs and DVDs - http://www.linuxiso.co.uk/ Random quote 37: "Now, with penguins, (cuddly such), "contented" means it has either just gotten laid, or it's stuffed on herring. Take it from me, I'm an expert on penguins, those are really the only two options." - Linus Torvalds

1 0

[Dovecot] new to dovecot
by John O'Loughlin 15 Oct '05

15 Oct '05

Hello all I'm new to dovecot (and imap in general!) having installed only only today. My current set up is exim as MTA with procmail delivering /var/spool/mail/%user (which gets nfs exported). We also have a pop3 server running as well. I'm moving to new machine and though I'd look at dovecot and squirrelmail. In /etc/dovecot.conf I'm confused by the default_mail_env, what exactly are we trying to set here? We have $MAIL set already, so for example what does the line: default_mail_env = mbox:~/mail/:INBOX=/var/mail/%u try to set Cheers John

2 2

[Dovecot] Does anyone have SQL working in 1.03?
by Jonathan 15 Oct '05

15 Oct '05

This just isn't working for me. I've tried everything. Trailing the logs with debug and vebose... we connect fine === Oct 15 22:51:35 rsrr1 dovecot: Killed with signal 15 Oct 15 22:51:37 rsrr1 dovecot: Dovecot v1.0.alpha3 starting up Oct 15 22:51:38 rsrr1 dovecot: auth(default): pgsql: Connected to vmail === and then we die: === Oct 15 23:02:07 rsrr1 dovecot: auth(default): sql (username(a)domain.com,69.86.67.250) query: SELECT password FROM accounts WHERE local_part = 'username' AND domain = 'domain.com' AND active = 'Y' LIMIT 1; Oct 15 23:02:07 rsrr1 dovecot: auth(default): client out: OK 1 user=username(a)domain.com Oct 15 23:02:07 rsrr1 dovecot: auth(default): master in: REQUEST 24 33278 1 Oct 15 23:02:07 rsrr1 dovecot: auth(default): passwd (username(a)domain.com,69.86.67.250) unknown user Oct 15 23:02:07 rsrr1 dovecot: auth(default): passdb (username(a)domain.com,69.86.67.250) passdb didn't return userdb entries Oct 15 23:02:07 rsrr1 dovecot: auth(default): userdb (username(a)domain.com,69.86.67.250) user not found from userdb Oct 15 23:02:07 rsrr1 dovecot: auth(default): master out: NOTFOUND 24 Oct 15 23:02:07 rsrr1 dovecot: imap-login: Internal login failure: user=<username(a)domain.com>, method=PLAIN, rip=69.86.67.250, lip=66.250.131.114, TLS === I've tried both of these selects on the password: password_query = SELECT local_part || '@' || domain as user, password FROM accounts WHERE local_part = '%n' AND domain = '%d' AND a ctive = 'Y' ; password_query = SELECT password FROM accounts WHERE local_part = '%n' AND domain = '%d' AND active = 'Y' LIMIT 1; and this, and some variants, on the user user_query = SELECT home_dir AS home, uid, gid FROM accounts WHERE local_part = '%n' AND domain = '%d' LIMIT 1; all mimic the functionality of the conf example files.

2 1

[Dovecot] Same email recieved
by Bob Hope 14 Oct '05

14 Oct '05

Some of my users seem to be receiving the same e-mail over and over. This doesn't happen all the time, just once in a while it seems to get stuck in a loop. Is it possible that dovecot is the culprit here or is this a problem with something else? I'm running Postfix/amavisd/dovecot on Slackware 10.1. Regards, Savage

2 3

[Dovecot] 1.0a3: assert and core dump
by Jeff A. Earickson 14 Oct '05

14 Oct '05

Timo, A rare assert and core dump out of 1.0alpha3. My setup: Solaris 9, mbox format, using imap only. Built dovecot with gcc 4.0.1. The syslog for this was: Oct 14 11:57:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: user=<epmccull>, method=PLAIN, rip=137.146.210.59, lip=137.146.210.52, TLS Oct 14 11:58:56 emerald dovecot: [ID 107833 mail.info] imap-login: Login: user=<epmccull>, method=PLAIN, rip=137.146.210.59, lip=137.146.210.52, TLS Oct 14 11:59:03 emerald dovecot: [ID 107833 mail.error] imap(epmccull): Corrupted index cache file /home/students/e/epmccull/.imap/INBOX/dovecot.index.cache: invalid record size Oct 14 11:59:38 emerald dovecot: [ID 107833 mail.error] imap(epmccull): Corrupted index cache file /home/students/e/epmccull/.imap/INBOX/dovecot.index.cache: Cache record offset 1768 points outside file Oct 14 11:59:39 emerald dovecot: [ID 107833 mail.error] imap(epmccull): Corrupted index cache file /home/students/e/epmccull/.imap/INBOX/dovecot.index.cache: used_file_size too small Oct 14 11:59:39 emerald dovecot: [ID 107833 mail.error] imap(epmccull): file mbox-lock.c: line 518 (mbox_lock): assertion failed: (lock_type == F_RDLCK || mbox->mbox_lock_type != F_RDLCK) Attached is a gdb session on the core dump. Thanks. Jeff Earickson Colby College

1 0