Bowie Bailey writes:
Sam Varshavchik wrote:Bowie Bailey writes:I figured it out. Apparently, the upgrade removed the reference to my certificate in the config file. I replaced the TLS_CERTFILE line and everything is back to normal. The auto-generated certificate was in the default location, but didn't work for some reason.That depends on how you specified the certificate file in the configuration file. The configuration files are not exactly free-form; their contents need to follow a specific structure, in order for them to be properly updated by an upgrade.What I generally do is leave the commented default line as a reference and add my config line directly beneath it. Should that cause problems? For example, here is a section from the current config file: ##NAME: TLS_CERTFILE:0 # <lots more comments go here> # # DEFAULT SETTING from /etc/courier/imapd-ssl.dist: # #TLS_CERTFILE=/usr/lib/courier/share/imapd.pem # TLS_CERTFILE=/etc/certs/bucmail.pemI just added the last line at the end of the comments for the section. Will that get squashed on the next update? What is the correct way todo it?
That should be fine. One thing to watch out for are stray blank lines in the entire comment section. They'll mess this up. Also, the very first line in the configuration file. If it's missing or gets altered, the entire configuration file may get reset.
pgpnMfwGPgPGe.pgp
Description: PGP signature
------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
