- Ralf Hildebrandt Ralf.Hildebrandt@charite.de:
Maybe it worked, since I see that particular User NOT getting the errors anymore.
Seems to be a particular folder he's accessing:
Aug 18 09:57:57 postamt dovecot: IMAP(myuser): file strfuncs.c: line 165 (p_strndup): assertion failed: (max_chars != (size_t)-1) Aug 18 09:57:57 postamt dovecot: IMAP(myuser): Raw backtrace: imap [0x80c6d53] -> imap(i_fatal+0) [0x80c6795] -> imap(p_strndup+0x38) [0x80d8316] -> imap(t_strndup+0x22) [0x80d86d7] -> imap(cmd_create+0xb5) [0x8059a39] -> imap [0x805eb09] -> imap [0x805ecf9] -> imap(_client_input+0x116) [0x805ee1b] -> imap(io_loop_handler_run+0x191) [0x80cebf8] -> imap(io_loop_run+0x20) [0x80cde56] -> imap(main+0xb8) [0x8069cbf] -> /lib/i686/cmov/libc.so.6(__libc_start_main+0xe0) [0xb7dc5030] -> imap [0x8058361] Aug 18 09:57:57 postamt dovecot: child 19919 (imap) killed with signal 6
-- Ralf Hildebrandt (Ralf.Hildebrandt@charite.de) plonk@charite.de Postfix - Einrichtung, Betrieb und Wartung Tel. +49 (0)30-450 570-155 http://www.arschkrebs.de
From empirical experience, your Exchange admin needs to put down the crack pipe and open a window to disperse the fumes.