/usr/lib/courier-imap/gentoo-pop3d.rc sources both /etc/courier-imap/pop3d and /etc/courier-imap/pop3d-ssl files. This results in settings from pop3d-ssl overriding settings from pop3d, as well as settings from pop3d that we might not want in the pop3d-ssl server. This same issue affects the imapd.rc, imapd-ssl.rc, and pop3d-ssl.rc files. gentoo-pop3d.rc should source the pop3d config file ONLY. gentoo-pop3d-ssl.rc should source the pop3d-ssl config file ONLY. gentoo-imapd.rc should source the imapd config file ONLY. gentoo-imapd-ssl.rc should source the imapd-ssl config file ONLY. Reproducible: Always Steps to Reproduce: 1. emerge courier-imap. 2. Configure imap, imap-ssl, pop3, and pop3-ssl services. 3. Observe that running configuration of services is the union of the settings in the normal and ssl files. If the same setting exists in both files (normal and ssl), the ssl file setting wins. Actual Results: normal service and ssl service both run with ssl settings. Expected Results: normal service runs with non-ssl settings, while ssl service runs with ssl settings.
At the risk of being a nuisance, is this going to be fixed, or has it just fallen off the face of the planet? :)
Well seriously, ping! Anyone of the huge net-mail herd alive there?
INVALID. > This results in settings from pop3d-ssl overriding settings > from pop3d, as well as settings from pop3d that we might > not want in the pop3d-ssl server. Look at the order of the settings. The ssl version reads (normal, ssl). The normal version reads (ssl, normal). The normal settings in the normal version will always override the settings from the SSL config file. jakub: I haven't forgotten about courier-imap, but aside from having some minor open security issues, it isn't actually broken, so it's _very_ low on my priority list at the moment, and it will remain there until I get my own new mailserver up in 3-4 weeks.
