MTA and MSA cannot be configured independantly: START_MSA configuration variable missing from config file

[Bilge]

Examining the /etc/init.d/courier-mta file indicates that support for starting and stopping the MTA and MSA independently of one another has been provisioned, and yet there exists no configuration parameter in the files in /etc/courier to make use of this feature, and the script is misconfigured to take advantage of this support.

/etc/courier/esmtpd contains the variable ESMTPDSTART at the end of the file, but this affects both the MTA and MSA at the same time due to the way that the init.d script has been written.

I have made simple modifications to both the esmptd config and init.d scripts and can confirm that the MTA and MSA can operate independently of one another, is it appears was the original intention of the script.

Further, it seems weak that the init.d script checks for the setting of these variables to determine what services to stop. For example, if I use the init.d script to start courier services and then change the value of ESMTPDSTART to 'no', followed by using the same init.d script to then stop courer, it will not shut down the same services it started. I would have thought it better that the script check what services are running rather than rely on the settings of these variables for the purposes of stopping services.

[Clint Byrum (clint-fewbar)]

Hello Bilge, Thanks for taking the time back in 2008 to file this bug report and help make Ubuntu better.

I'm struggling to see a test case here, and there are multiple issues reported.

The ESMTPDSTART variable is set and read from both /etc/courier/esmtpd and /etc/courier/esmtpd-msa, so that suggestion may have been fixed in subsequent releases. As such, this would appear to invalidate that part of the bug report.

The bit about stopping what we've started already is true, however this would be solved just by having an upstart job, and so should be reported as a feature request to provide upstart jobs for esmtpd and esmtpd-msa.

Closing as Invalid. Please feel free to reopen (set status to New) this if you have a repeatable test case which will demonstrate the bugs you've reported.