5 messages in net.sourceforge.lists.courier-usersRe: [courier-users] Re: esmtpd won't ...
FromSent OnAttachments
Michael JinksMay 2, 2003 4:30 pm 
Michael JinksMay 2, 2003 4:40 pm 
Gordon MessmerMay 2, 2003 5:01 pm 
Sam VarshavchikMay 2, 2003 5:12 pm 
Michael JinksMay 3, 2003 12:30 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] Re: esmtpd won't bind to network?Actions...
From:Michael Jinks (mji@uchicago.edu)
Date:May 3, 2003 12:30:03 am
List:net.sourceforge.lists.courier-users

On Fri, May 02, 2003 at 08:09:28PM -0400, Sam Varshavchik wrote:

You didn't start the esmtp server. Read "Starting and stopping Courier" in INSTALL. The entire section, not just the first paragraph.

It was a little more than that. I did follow the INSTALL docs pretty carefully, went pretty smoothly through the testing section of the installation guide, up to the point of running (from courier's sbin)

# ./courier start # ./esmptpd start /bin/bash: line 8: 13665 Killed /opt/mj/courier-0.42.0/sbin/couriertcpd -stderrlogger=/opt/mj/courier-0.42.0/sbin/courierlogger -user=mail -group=mail -access=/etc/courier/smtpaccess.dat -maxprocs=40 -maxperc=5 -maxperip=5 -pid=/var/lib/courier/tmp/esmtpd.pid smtp /opt/mj/courier-0.42.0/sbin/courieresmtpd >/dev/null 2>&1 </dev/null

I made the mistake of ignoring this when I saw that a "courieresmtp" was in the process table, but a second look makes it obvious that's a different beast. If, instead of the script, I run the couriertcpd command line by hand, I get a listening esmtp server.

So now I'm up to wondering why the script fails, and who's issuing that "Killed" message. But it looks like things are close to working.

Thanks, -mrj