Re: Dovecot crashes on certain spam messages

Karl Eklund wrote:
> Kenneth Porter wrote:
> 
>> Likely, but also check that "ulimit -c" allows the process to dump 
>> core. Use ulimit to set the max core dump size before launching dovecot.
> 
> 
> 
> OK, I inserted "ulimit -c 50000" before /usr/local/sbin/dovecot in my 
> startup script, but no core file appears. I think I would need some help 
> with what you suggested, adding some more logging.

Perhaps mounting the filesystem with something else than 0 as last but 
one item in fstab solves it?

  - Jonas

--

-- 
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

  - Enden er nær: http://www.shibumi.org/eoti.htm

Re: Dovecot dies on startup????

On Fri, 2004-01-30 at 21:09, Mitchell Baker wrote:
> Jan 29 14:30:34 smtp dovecot: Dovecot starting up
> Jan 29 14:30:34 smtp dovecot: dovecot startup succeeded
> Jan 29 14:30:36 smtp dovecot: Auth process died too early - shutting
> down
> Jan 29 14:30:36 smtp dovecot: child 3517 (auth) returned error 127
> Jan 29 14:30:36 smtp imap-login: fd_send(-1) failed: Broken pipe

Usually this happens when you've compiled it with some library that
isn't in library path at the time of running it. Try:

ldd /usr/local/libexec/dovecot/dovecot-auth

it probably says something about missing libraries.

Re: MD5 ldap password schemes

On Sat, 2004-01-31 at 01:21, SAiello <at> Jentoo.com wrote:
> Looking at the possible LDAP passwords Schemes, if I wanted to use PLAIN-MD5 
> or DIGEST-MD5, what would format would I use in LDAP for the userPassword 
> field ? I have done SHA, SSHA, and MD5 before, but not sure what is 
> acceptable for the above mentioned, that dovecot can use.

PLAIN-MD5 means the field contains just the MD5 sum of the password in
hex. DIGEST-MD5 is MD5 sum of user:realm:password string. They don't
have any special format in there..

Re: Dovecot crashes on certain spam messages

Jonas Smedegaard wrote:

> Perhaps mounting the filesystem with something else than 0 as last but 
> one item in fstab solves it?

Why? The dump option seems to have something to do with a kind of backup 
system, according to man fstab. Also, it seems to be possible to get a 
core dump:

~ $ cat crash.c
main() { char *s; while(1) { *s = "a"; ++s; } }
~ $ gcc -o crash crash.c
crash.c: In function `main':
crash.c:1: warning: assignment makes integer from pointer without a cast
~ $ ulimit -c 50000
~ $ ./crash
Segmentation fault (core dumped)
~ $
-rw-------    1 ke       users       49152 Feb  2 22:19 core
~ $

Re: Dovecot crashes on certain spam messages

Sorry about this confusion, I don't know what has happened but now I get 
the core file.

Operating system: Gentoo, dovecot version 0.99.10.4, not from Gentoo.

Syslog:

Feb  2 22:23:01 kalle imap-login: Login: ke [213.114.209.34]
Feb  2 22:23:02 kalle imap(ke): file imap-bodystructure.c: line 279 
(part_parse_headers): assertion failed: (part->physical_pos >= 
input->v_offset - start_offset)
Feb  2 22:23:02 kalle dovecot: child 10144 (imap) killed with signal 6

/home/ke # gdb /usr/local/libexec/dovecot/imap core
GNU gdb 5.3
Copyright 2002 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain 
conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB.  Type "show warranty" for details.
This GDB was configured as "i686-pc-linux-gnu"...
Core was generated by `imap'.
Program terminated with signal 6, Aborted.
Reading symbols from /lib/libdl.so.2...done.
Loaded symbols for /lib/libdl.so.2
Reading symbols from /lib/libc.so.6...done.
Loaded symbols for /lib/libc.so.6
Reading symbols from /lib/ld-linux.so.2...done.
Loaded symbols for /lib/ld-linux.so.2

Re: MD5 ldap password schemes

On Mon, Feb 02, 2004 at 08:02:53PM +0200, Timo Sirainen wrote:
> On Sat, 2004-01-31 at 01:21, SAiello <at> Jentoo.com wrote:
> > Looking at the possible LDAP passwords Schemes, if I wanted to use PLAIN-MD5 
> > or DIGEST-MD5, what would format would I use in LDAP for the userPassword 
> > field ? I have done SHA, SSHA, and MD5 before, but not sure what is 
> > acceptable for the above mentioned, that dovecot can use.
> 
> PLAIN-MD5 means the field contains just the MD5 sum of the password in
> hex. DIGEST-MD5 is MD5 sum of user:realm:password string. They don't
> have any special format in there..

There is a certain impedence mismatch between RFC2307's idea of {MD5}
and Dovecot's.  I tinkered a while ago with this quirk and the resulting
patch is attached. (also available from http://www.roughtrade.net/dovecot/)

Caveat emptor: it is totally untested beyond my workstation, it is
unchanged from months ago, has not been reviewed by Timo and is not in
the CVS tree.  I've only just confirmed that it compiles with 0.99.10.4.
Let me know if it's of any use.

Regards
Joshua.

--

-- 
Joshua Goodall                           "as modern as tomorrow afternoon"
joshua <at> roughtrade.net                                       - FW109

--- dovecot-0.99.10.4/src/auth/passdb-ldap.c.orig	Fri Mar 21 02:55:57 2003
+++ dovecot-0.99.10.4/src/auth/passdb-ldap.c	Tue Feb  3 12:19:17 2004

Re: Dovecot crashes on certain spam messages

I'm also seeing this - I wasn't able to get a core dump, but was able to get
info from strace/lsof to track down the message:

strace shows in a continuous read loop, as it's trying to go past EOF.

pread(9, "", 3502, 30524)               = 0
pread(9, "", 3502, 30524)               = 0
pread(9, "", 3502, 30524)               = 0

I've attached the problem message (gzipped).

-D
--

-- 
<dr.pox> does whistling in the dark make me go blind faster?

Re: Dovecot crashes on certain spam messages

On 2004.02.02 22:21, Karl Eklund wrote:
> Jonas Smedegaard wrote:
> 
> > Perhaps mounting the filesystem with something else than 0 as last but 
> > one item in fstab solves it?
> 
> 
> Why? The dump option seems to have something to do with a kind of backup 
> system, according to man fstab. Also, it seems to be possible to get a 
> core dump:
> 
> ~ $ cat crash.c
> main() { char *s; while(1) { *s = "a"; ++s; } }
> ~ $ gcc -o crash crash.c
> crash.c: In function `main':
> crash.c:1: warning: assignment makes integer from pointer without a cast
> ~ $ ulimit -c 50000
> ~ $ ./crash
> Segmentation fault (core dumped)
> ~ $
> -rw-------    1 ke       users       49152 Feb  2 22:19 core

50000 is a bit small for a core file. They usually are tens of megabytes,
as the internal memory and mapped files are dumped as well.

Use "ulimit -c unlimited" to enable coredumps instead.

Mike.

Dovecot died due to some SSL related error

Hi,
Dovecot (pre-compiled version of Fedora Core 1, configured for Maildir)
is running fine for me since a few days. It happened now twice to me
that dovecot died with the following error message in /var/log/maillog:

Feb  4 11:18:27 hundehuette imap-login: RAND_bytes() failed:
error:24064064:random number generator:SSLEAY_RAND_BYTES:PRNG not
seeded
Feb  4 11:18:27 hundehuette dovecot: Login process died too early -
shutting down

As these previous log messages indicate the login was working before
without any problem:
Feb  4 11:02:37 hundehuette imap-login: Login: andrea [192.168.2.138]
Feb  4 11:05:56 hundehuette last message repeated 30 times
Feb  4 11:09:02 hundehuette last message repeated 15 times
Feb  4 11:12:08 hundehuette last message repeated 15 times
Feb  4 11:15:15 hundehuette last message repeated 15 times
Feb  4 11:18:21 hundehuette last message repeated 15 times
Feb  4 11:18:26 hundehuette last message repeated 12 times

Dovecot is running as user "dovecot" who does not have a ~/.rnd file

Any idea?

Thanks,
Christof

Newbie question: How to make dovecot read /var/mail/user while using Maildir

Hi

I've been trying to figure out how to make dovecot read the system 
standard /var/mail/user, which is in mbox-format, while at the same 
time using Maildir as the preferred method of storage. When in 
Maildir-mode, I can store mail on the server without a hitch, but I 
don't receive mails. When in mbox-format, I can read and write, but the 
risk of corrupting mails is to high for me to consider mbox as an 
option.

I would appreciate to hear from anyone who has a possible solution to 
this.

Info about my system:

MacOSX 10.2 Jaguar
Apache 2.0.47 running Squirrelmail 1.4.2
PHP 4.3.2
Sendmail 8.12.9
Procmail v3.21

/Lars