I was talking about the ESMTPDSTART="NO" configuration
in the esmtpd config file.
However rereading the config informs me that these variables
only affect the startup script. The FreeBSD startup script
is following the example scripting in the esmtpd file. So
this is probably an issue then for the FreeBSD port, which
mentions a setup proceedure before running Courier for the
first time.
Having said that, a FAQ item would ne nice, IMAPD and POP3D
get a FAQ item for their respective START configs. Perhaps
they could be combined into a general "Why doesn't a
certain Courier module start?" FAQ entry.
Thanks for the help. I am reading into the Courier configs
and becoming more familiar with it as I seen the Qmail and
sendmail concepts being repeated. Hopefully no more silly
questions :-)
P.S. Does running maildirmake in an existing maildir clobber
it? If not it would be ideal to put it in the default
delivery instructions to create the Maildir directory, if it
doesn't exist, before delivering the mail. To stop mbox files
being created for new accounts.
Cheers.
Sam Varshavchik wrote:
John Saunders writes:
ESMTP server doesn't start by default. I had
actually giving up on this and moved on to IMAP.
While reading the IMAP docs it mentioned a config
to start the IMAP daemon. I wondered if ESMTP had
the same option and found it. The install docs and
FAQ do not mention this rather important item.
Yes, they do. From INSTALL:
The commands courierfilter start, courierfilter stop,
esmtpd start, esmtpd
stop, esmtpd-msa start, esmtpd-msa stop, pop3d start,
pop3d stop, imapd
start, and imapd stop (all commands are installed in the
sbin directory)
are used to start or stop their respective daemons, and
they should be
added to your system startup and shutdown scripts, where required.
Warning: Copyright ResMed. Where the contents of this email and/or attachment
includes materials prepared by ResMed, the use of those
materials is subject exclusively to the conditions of engagement between ResMed
and the intended recipient.