- dovecot - dovecot.org

[Dovecot] NetBSD pkgsrc maintanance
by tom hensel 20 Jun '03

20 Jun '03

hi all, i've taken over the maintainership of dovecot's pkgsrc on NetBSD - please send me your ideas, questions and comments related to dovecot on NetBSD. FreeBSD's port has currently some more 'features' than the pkgsrc, i'm going to add some of them - any feedback is appreciated. bye, TOM

3 2

[Dovecot] Re: dovecot Digest, Vol 2, Issue 15
by ohp＠pyrenet.fr 19 Jun '03

19 Jun '03

> >Message: 2 >Date: Wed, 18 Jun 2003 13:21:08 +0200 (CEST) >From: Andreas Aardal Hanssen <dovecot(a)andreas.hanssen.name> >Subject: Re: [Dovecot] Multiple auth howto >To: Dovecot mailing list <dovecot(a)procontrol.fi> >Message-ID: > <Pine.LNX.4.44.0306181319060.29812-100000(a)shusaku.troll.no> >Content-Type: TEXT/PLAIN; charset=US-ASCII > >On Wed, 18 Jun 2003 ohp(a)pyrenet.fr wrote: >>> Well, short answer: You can't. Put them all to one place (eg. pgsql), >>> maybe using some automated scripts. I don't know if I should even >>> consider about supporting fallbacking.. >>Hi Timo, Thanks for your answer. >>The reason I came to dovcot is that I thought it was possible. I've benn >>researching this for weeks now. First thought that cyrus would do that, it >>does but though SASL and pam whitch I don't have. >>How difficult would it be to implement a fallback? > >Does this tool do what you want? (checkpassword only though, but I bet you >will find checkpassword compatible authenticators that suit your needs): > >http://www.andreas.hanssen.name/software/multichkpwds.c It surely is interesting bu I'd rather see modules inside the server, see below > >-- >Andreas Aardal Hanssen > > > >------------------------------ >Message: 4 >Date: 18 Jun 2003 15:31:36 +0300 >From: Timo Sirainen <tss(a)iki.fi> >Subject: Re: [Dovecot] Multiple auth howto >To: dovecot(a)procontrol.fi >Message-ID: <1055939496.10262.163.camel@hurina> >Content-Type: text/plain > >On Wed, 2003-06-18 at 14:05, ohp(a)pyrenet.fr wrote: >> > Well, short answer: You can't. Put them all to one place (eg. pgsql), >> > maybe using some automated scripts. I don't know if I should even >> > consider about supporting fallbacking.. >> > >> > >> Hi Timo, Thanks for your answer. >> The reason I came to dovcot is that I thought it was possible. I've benn >> researching this for weeks now. First thought that cyrus would do that, it >> does but though SASL and pam whitch I don't have. >> >> How difficult would it be to implement a fallback? > >Not very. I'm mostly concerned about what happens if the user exists in >both authenticators. I guess normally this shouldn't happen, but you >can't really guarantee that and mistakes happen.. Yes mistakes happen. Why could'nt you (we?) do like proftpd that has a parameter that give the order of authenticators first one wins. That way you could even have the same user as a real and virtual account with differents passwords > >If fallbacking happened only when user isn't found from first >authenticator, that could work a bit more safely, but I'm not sure if I >can know with PAM if check failed because user wasn't found or because >password didn't match. I don't know either. My idea is to get rid of PAM for that's although fantastic on the paper is a Linux thing that I can't even compile here. Regards -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

1 0

[Dovecot] \0\n at end of lines
by Mike Grupenhoff 19 Jun '03

19 Jun '03

Since upgrading to -test11, mail fetched from imap has every line terminated with a nul and a newline ("\0\n"). This also happens with -test12. It seems to happen with both mbox and maildir. I'm running on NetBSD/sparc (NetBSD-current as of April 1, 1.6Q). If it matters, I have "mail_save_crlf" set to "no" and "mail_read_mmaped" also set to "no". I can't find any other options that look like they could be relevant. Any ideas? Thanks, mike

2 1

[Dovecot] 0.99.10-test12
by Timo Sirainen 19 Jun '03

19 Jun '03

http://dovecot.procontrol.fi/test/ I should have released 0.99.10 already I think.. There's just two annoying problems that I think should be fixed first: - PAM: If user gives a wrong password, dovecot-auth process sleeps for two seconds, blocking everyone else who are trying to authenticate at the time. So using PAM isn't very good idea at the moment. - OpenSSL problems. Are they really my fault? I have no idea what I could be doing wrong. Maybe some compile option is wrong? Also I should try to use pkg-config to get compile flags if it exists in configure. The new things in -test12 then: - We sync mailbox less often. Only NOOP and CHECK will force a mailbox sync now. Other commands do it also but only if mailbox hasn't been synced in last 5 seconds. Maybe this reduces some I/O. At least a bit less stat() calls :) - Dirty maildir flag flushing work now. Meaning that if you change message flags but rename() fails because you're out of quota, the flags are changed in index file and dirty-flag is set. Once in a while it tries to flush the dirty flags by rename()ing the file again. - IMAP RFC requires that NUL characters are never sent to client. We do now the same as UW-IMAP by sending ascii 128 chars instead.

5 11

[Dovecot] 0.99.10-test13
by Timo Sirainen 18 Jun '03

18 Jun '03

http://dovecot.procontrol.fi/test/ - Hopefully OpenSSL is fixed :) - We sometimes produced invalid ENVELOPE with 8bit headers. That could really have broken things (broke it in test12). So, what's left is to make PAM work well..

4 3

[Dovecot] Multiple auth howto
by ohp＠pyrenet.fr 18 Jun '03

18 Jun '03

Howdi. I'm new to dovcot (just succeded in compiling on unixware 713 today) I'm noww configuring for tests on other port. The sample configuration file is pretty well documented, however, I don't understand how I can firstt authenticate against passwd/shadow if not found against pgsql. What's the syntax? Please cc responses as I'm subscribed to digest TIA Reghards -- Olivier PRENANT Tel: +33-5-61-50-97-00 (Work) Quartier d'Harraud Turrou +33-5-61-50-97-01 (Fax) 31190 AUTERIVE +33-6-07-63-80-64 (GSM) FRANCE Email: ohp(a)pyrenet.fr ------------------------------------------------------------------------------ Make your life a dream, make your dream a reality. (St Exupery)

3 4

[Dovecot] imaps now works!
by Farkas Levente 18 Jun '03

18 Jun '03

thanks! -- Levente "Si vis pacem para bellum!"

1 0

[Dovecot] SASL Support
by Ken Crain 16 Jun '03

16 Jun '03

I need to support Outlook/Outlook Express users of Sendmail with SMTP Authorization. From what I can see, the LOGIN method available in Outlook/Outlook Express is the only applicable way to go at this time. It appears it is not supported in Dovecot right now. Is this correct and, if so, how would I go about adding this support?

2 1

[Dovecot] crash on LIST command
by Wouter Van Hemel 16 Jun '03

16 Jun '03

Hello, I'm experiencing a reproducable crash in the imap daemon of dovecot 0.99.9.1 when running the next commands (sniffed from a sylpheed session): [cocaine:~] telnet ice 143 Trying 192.168.196.1... Connected to ice. Escape character is '^]'. * OK dovecot ready. 1 NOOP 1 OK NOOP completed. 2 LOGIN wouter password 2 OK Logged in. 3 NAMESPACE 3 BAD Error in IMAP command: Unknown command 'NAMESPACE' 4 LIST "" "" * LIST (\Noselect) "/" "" 4 OK List completed. 5 LIST "" "%" Connection closed by foreign host. [cocaine:~] _ The log shows this: Jun 16 02:48:09 ice imap-login: Login: wouter [192.168.196.5] Jun 16 02:48:19 ice dovecot: child 1870 (imap) killed with signal 11 Looks like a segfault. [...] Core was generated by `imap'. Program terminated with signal 11, Segmentation fault. Reading symbols from /usr/lib/libc.so.4...done. Reading symbols from /usr/libexec/ld-elf.so.1...done. #0 0x8058469 in mbox_list_inbox (ctx=0x8098080) at mbox-list.c:333 333 if (ctx->dir->virtual_path != NULL) (gdb) bt #0 0x8058469 in mbox_list_inbox (ctx=0x8098080) at mbox-list.c:333 #1 0x805809e in mbox_list_mailbox_next (ctx=0x8098080) at mbox-list.c:193 #2 0x804b75a in list_unsorted (client=0x8096080, ctx=0x8098080, reply=0x807ed06 "LIST", sep=0xbfbffac4 "/", listext=0) at cmd-list.c:234 #3 0x804b9fa in _cmd_list_full (client=0x8096080, lsub=0) at cmd-list.c:341 #4 0x804ba8b in cmd_list (client=0x8096080) at cmd-list.c:365 #5 0x804d39e in client_handle_input (client=0x8096080) at client.c:306 #6 0x804d43d in _client_input (context=0x8096080) at client.c:342 #7 0x8078c87 in io_loop_handler_run (ioloop=0x808d060) at ioloop-poll.c:210 #8 0x8078745 in io_loop_run (ioloop=0x808d060) at ioloop.c:295 #9 0x80524a9 in main (argc=1, argv=0xbfbffc2c, envp=0xbfbffc34) at main.c:166 #10 0x8049eb5 in _start () (gdb) _ This crash happens when adding an imap account to the sylpheed mailer. I also noticed other problematic log entries, which might or might not be related: Jun 16 00:28:36 ice imap-login: Login: wouter [192.168.196.5] Jun 16 00:28:36 ice imap(wouter): open() failed with file /usr/home/wouter/.mail/.imap/INBOX/.customflags: No such file or directory Jun 16 00:28:36 ice imap(wouter): Can't create temp index /usr/home/wouter/.mail/.imap/INBOX/.temp.hostname.domainname.tld.1728: No such file or directory ... this happens when an imap user connects and opens his/her INBOX for the first time, and the /usr/home/username/.mail/ directory doesn't exist yet. My DEFAULT_MAIL_ENV settings: #default_mail_env = mbox:~/.mail:INBOX=/var/mail/%u default_mail_env = mbox:/usr/home/%u/.mail:INBOX=/var/mail/%u (tried both) Manually adding the ~/.mail directory with mkdir takes care of the problem, but shouldn't this directory be created automatically when it doesn't exist? I can't expect every user to log in and first make this mail directory before they can use their mail account. Dovecot also refuses to show any folders at all, such as the INBOX, when it can't find it's mail(folders) directory. Is this intentional? Dovecot is running on a pretty standard (i386) FreeBSD 4.4 test machine with postfix and normal mbox-formatted inbox files. Thanks for any suggestions, wouter

3 6

[Dovecot] Dovecot will not run on secure kernel.
by Ola Garstad 16 Jun '03

16 Jun '03

I am trying to run Dovecot on RH 7.3 with Linux kernel 2.4.20 + GrSecurity patch. I downloaded the RPM yesterday and installed it. When I start Dovecot the kernel reports: kernel: grsec: From 192.168.1.22: attempt to overstep process limit by (dovecot:14491) UID(0) EUID(0), parent (dovecot:23872) UID(0) EUID(0) I have never seen this problem in the 3 years I have used GrSecurity together with a lot of programs. GrSecurity explains: "Enforce RLIMIT_NPROC on execs. Users with a resource limit on processes will have the value checked during execve() calls. The current system only checks the system limit during fork() calls." Any ideas why Dovecot causes this problem? -- Ola

2 1