20 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Maildrop ALWAYS f...
FromSent OnAttachments
Hanford, SethNov 19, 2004 6:42 am 
Hanford, SethNov 19, 2004 6:56 am 
Sam VarshavchikNov 19, 2004 3:41 pm 
Dew EdihoNov 19, 2004 6:43 pm 
Dew EdihoNov 20, 2004 4:36 am 
Hanford, SethNov 20, 2004 11:51 am 
Sam VarshavchikNov 20, 2004 5:20 pm 
Hanford, SethNov 22, 2004 6:20 am 
Sam VarshavchikNov 22, 2004 4:04 pm 
Hanford, SethNov 22, 2004 4:45 pm 
Sam VarshavchikNov 22, 2004 4:56 pm 
Greg EarleNov 22, 2004 5:23 pm 
Hanford, SethNov 22, 2004 6:43 pm 
Sam VarshavchikNov 23, 2004 4:05 am 
Hanford, SethNov 23, 2004 6:05 am 
Sam VarshavchikNov 23, 2004 4:24 pm 
Hanford, SethNov 24, 2004 7:11 am 
Jerry AmundsonNov 24, 2004 8:43 am 
Hanford, SethNov 24, 2004 11:32 am 
Sam VarshavchikNov 24, 2004 4:52 pm 
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] Maildrop ALWAYS failling with 0x06Actions...
From:Hanford, Seth (shan@ckure.com)
Date:Nov 20, 2004 11:51:41 am
List:net.sourceforge.lists.courier-users

Hanford, Seth writes:

maildrop: signal 0x06

You'll have to look up what's signal 6 on OpenBSD. On Linux it's SIGABRT, which obviously is not what it is on OpenBSD.

Once you know what the signal is, then you can try to figure out why you're getting it.

Signal 6 is SIGABRT on OpenBSD. I compiled maildrop-1.7.0 by hand and the same results are found in it. Anything I can do to help watch what is going on?

Thanks, Seth