/etc/init.d/courier-imapd-ssl refuses to start unless there is a certificate as /etc/courier-imap/imapd.pem. I have editted /etc/courier-imap/imapd to point TLS_CERTFILE at my certificate (since so many pieces of software use certificates on the same host, I point them all at the same file which is /etc/certs/the.relevant.name.pem) The script should be sourcing the config file and checking $TLS_CERTFILE rather than the hard coded location. Reproducible: Always Steps to Reproduce: 1. 2. 3.
post up patches for both imapd-ssl and pop3d-ssl and i'll get to it sooner than if i need to write it up myself.
Created attachment 34132 [details, diff] this patch fixes /etc/init.d/imapd-ssl
Created attachment 34133 [details, diff] and this one /etc/init.d/courier-pop3d-ssl
Oops, I see I made a typo in my comment on the first upload. Anyway, these patches work by simply first sourcing the config file and then testing whether "${TLS_CERTFILE}" exists instead of the hardcoded location.
in cvs for the 3.0.5 release.
That is still a *long* way off. Stable is still at 3.0.2 (-r1 is still masked on x86 - what's the reason for that?). Then there is 3.0.4 (also still ~x86) only and after that 3.0.5. Is there any particular reason why these patches can't go into 3.0.4 already? Or even 3.0.2-r1?
3.0.4 was a bust upstream, it broke some more stuff, but fixed bugs that were in 3.0.2. 3.0.5 is back to where the stable line should be, so i'll be moving it into stable in a week or less, provided no further issues are reported with it.
