Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
The /etc/init.d/courier script lacks a part meant to star esmtpd-ssl if properly configured. In particular I suggest ti add: # start esmtpd-ssl if so written [ -f ${sysconfdir}/esmtpd-ssl ] && source ${sysconfdir}/esmtpd-ssl case x$ESMTPDSSLSTART in x[yY]*) ebegin " Starting esmtpd-ssl" ${sbindir}/esmtpd-ssl start ;; esac in the start() function and ebegin " Stopping courier-esmtpd-ssl" ${sbindir}/esmtpd-ssl stop in the stop() function There is another error in this script, it lacks the generation of esmtpacceptmailfor.dat, so it would be useful having this line: [ -f ${sysconfdir}/esmtpacceptmailfor.dat ] || ${sbindir}/makeacceptmailfor I think that this script could be improved such as the ebuild of courier, so i would like to talk with courier ebuild mantainer Reproducible: Always Steps to Reproduce: 1. Enable esmtpd-ssl (ESMTPDSSLSTART="YES") 2. Try to restart (or start) courier service 3. As you see ssmtp has not been started!
Oddly enough the courier sysV init script doesn't start esmtpd-ssl (which is what I based the Gentoo startup script on). I'm looking into why it doesn't start it (to make sure it's not borken or something).
Okay, so the initscript in the install docs still is missing a part about esmtpd-ssl, but the one that is distributed in the most recent tarball correctly has a part about it. I've fixed this in cvs, and I'll bump the ebuild after I do some more init script cleaning and testing that's been on my todo list for awhile.
There is still a small problem: You added "case x$ESMTPDSTART in" (missing 'SSL') instead of "case x$ESMTPDSSLSTART in" to /etc/init.d/courier. So esmtpd-ssl doesn't start, even if it is configured in /etc/courier/esmtpd-ssl (ESMTPDSSLSTART=YES). (Sorry, I don't have the permission to mark this bug as REOPENED.)