14 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Problem imapd.cor...
FromSent OnAttachments
Charles LacroixAug 10, 2006 11:00 am 
Sam VarshavchikAug 10, 2006 3:21 pm 
Charles LacroixAug 14, 2006 6:41 am 
HIROSHI OOTANov 15, 2006 12:41 am 
Milan ObuchNov 15, 2006 1:46 am 
Edwin L. Culp W.Nov 15, 2006 2:57 am 
HIROSHI OOTANov 15, 2006 3:26 am 
Milan ObuchNov 15, 2006 7:12 am 
Edwin L. Culp W.Nov 20, 2006 11:05 am 
HIROSHI OOTANov 20, 2006 5:56 pm 
Mark BucciarelliNov 21, 2006 5:43 am 
Milan ObuchNov 21, 2006 7:08 am 
Milan ObuchNov 21, 2006 7:12 am 
Mark BucciarelliNov 21, 2006 7:34 am 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: [courier-users] Problem imapd.core in my Maildir directory.Actions...
From:Charles Lacroix (clac@cegep-ste-foy.qc.ca)
Date:Aug 14, 2006 6:41:49 am
List:net.sourceforge.lists.courier-users

On Thursday 10 August 2006 18:22, Sam Varshavchik wrote:

Charles Lacroix writes:

Hi,

i have a strange problem. I configured my 2nd mail server using a very similar configuration. I can check mail with pop no problem but people here use IMAP.

I get a core dump as soon as i try to select the inbox. I can send you a coredump file up on private request.

A coredump is useless to everyone except yourself, since only you have the matching executable image. You need to load the core file into gdb and obtain a backtrace.

Thanks for the backtrace tip, i didn't know about this but once i checked what was in the backtrace, i saw that it was calling FAM libraries even if i have disabled it in my configuration.

For me the solution was to install FAM and imapd started to work again. I find this strange since it wasn't a requirement for courier-imap port under freebsd.

no biggy, it's working now. Later