On 8/20/2014 5:37 AM, Timo Sirainen wrote:
On 18 Aug 2014, at 17:30, Ben Johnson b...@indietorrent.org wrote:
Ironically, the very reason for which I replaced my distro's source
repos with
deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
deb-src
On 18 Aug 2014, at 17:30, Ben Johnson b...@indietorrent.org wrote:
Ironically, the very reason for which I replaced my distro's source
repos with
deb http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
deb-src http://xi.rename-it.nl/debian/ stable-auto/dovecot-2.2 main
These are
On 8/17/2014 5:11 PM, Timo Sirainen wrote:
On 15 Aug 2014, at 21:53, Ben Johnson b...@indietorrent.org wrote:
# gdb /usr/lib/dovecot/imap /var/vmail/example.com/user/core
Reading symbols from /usr/lib/dovecot/imap...(no debugging symbols
found)...done.
[New LWP 27866]
[Thread debugging
On 8/18/2014 8:36 AM, Ben Johnson wrote:
Just an observation: I sent another message to the list a few days
before this message, describing an unhandled exit scenario where
dovecot-antispam plug-in is concerned (Re: Backtrace io_add(0x1) called
twice fd= (was Exit status code 134; what is it,
On 15 Aug 2014, at 21:53, Ben Johnson b...@indietorrent.org wrote:
# gdb /usr/lib/dovecot/imap /var/vmail/example.com/user/core
Reading symbols from /usr/lib/dovecot/imap...(no debugging symbols
found)...done.
[New LWP 27866]
[Thread debugging using libthread_db enabled]
Using host
Hello,
I upgraded Dovecot last night and have been receiving core-dumps any
time I attempt to access a mailbox (via IMAP) ever since. Logging-in
seems to work, but any attempt to access the mailbox contents
(regardless of folder) causes a core-dump.
Please let me know if I can provide any