4 messages in net.sourceforge.lists.courier-users[courier-users] Re: Courier Bench
FromSent OnAttachments
Derrick T. WoolworthApr 24, 2003 2:07 am 
Jon NelsonApr 24, 2003 7:10 am 
Sam VarshavchikApr 24, 2003 7:22 am 
Derrick T. WoolworthApr 24, 2003 12:40 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:[courier-users] Re: Courier BenchActions...
From:Sam Varshavchik (mrs@courier-mta.com)
Date:Apr 24, 2003 7:22:14 am
List:net.sourceforge.lists.courier-users

Derrick T. Woolworth writes:

Regardless, the crashing of couriertcpd still seems prevalent. Sam - question, could it even be couriertcpd? If couriertcpd crashed, wouldn't courieresmtpd go away completely? I didn't have a lot of time to spend in the code, but just from a design perspective, does couriertcpd fork on incoming connections, or just use exec() ? If couriertcpd isn't forking then it'd be difficult for it to crash without taking down smtp completely.

It does fork, but not a lot happens before it exec. If anything would fault it would be the parent process, which would indeed stop all incoming esmtp. Which is why I'm skeptical that your logs are telling the truth.

Try building --without-ipv6. In the past there were some issues with IPv6 support.