Crosswords: easy and difficult

Perhaps it's consequence of the bank holiday, but I found both yesterday's and today's cryptic crosswords enjoyably straightforward. Which is in total contrast to this week's quiptic, set by Nutmeg, which I found considerably and enjoyably tough...

ETA: I'd expected Paul's puzzle on Wednesday to break my run, but it was actually well within my reach. There were a couple of nasties, including "Spiced drink, say, drunk by setter, not going down (5)" which I managed to solve despite having no idea what a negus was until afterwards, and some fantastic puns: "Reproduce artist, say, for the royal issue (8,4)" for Princess Anne!

Fixing fetchmail SSL trust problems

As an aide-memoire, here is a quick way to prevent fetchmail from logging Server certificate verification error: certificate not trusted messages.

1. Create a certificates directory
   mkdir -p /usr/local/etc/fetchmail/certs
2. Change to a temporary directory
   cd $TMPDIR
3. Get the certificate from your POP3 server
   echo | openssl s_client -connect <pop server>:993 -showcerts > info
   where <pop server> is your mail server
4. Extract the security certificate
   sed -n "/^--*BEGIN/,/^--*END/{p;/^--*END/q;};d" info > /usr/local/etc/fetchmail/certs/<pop server>.pem
5. Find the certificating authority
   grep issuer= /tmp/info
6. Get the appropriate root certificate, for example:
   wget http://www.geotrust.com/resources/root_certificates/certificates/GeoTrust_Global_CA.pem
7. Move the root certificate into place
   mv GeoTrust_Global_CA.pem /usr/local/etc/fetchmail/certs
8. Create hashed symlinks
   c_rehash /usr/local/etc/fetchmail/certs
9. Append the following to the fetchmail configuration file
   sslcertck sslcertpath /usr/local/etc/fetchmail/certs
10. Restart the fetchmail daemon

And, obviously, check the logs to confirm the validity of the change and send a few test mails from a remote server to check that everything is working as expected...