courier

Using self generated SSL (exim4 TLS/courier IMAPS) with Mail.app

Mail.app wouldn't stop asking about the certificates.

So:

  1. Remove any instances of them from Keychain Access
  2. Try to get mail - when told about the certificate choose View certificate and drag the icon to the desktop
  3. Don't add the cert to your login keychain - drag it to the X509Anchors chain instead.
  4. Mark it as always trusted (after all - you trust yourself don't you?)
  5. Repeat 2. - 4. for sending mail.

Bingo! Well - works4me at least.

Technorati logoTechnorati Tags:

courier imap/pop3 with ssl

I was using courier-imap and courier-pop until today. I've just installed the -ssl versions of both.

At install they both create a certificate for localhost based in New York. This doesn't work unless it really is localhost.

In /etc/courier there are imapd.pem, imapd.cnf, pop3d.pem and pop3d.cnf

  1. Delete the .pem files
  2. Edit the .cnf files - make sure that you set CN to be the hostname or the mail server
  3. Run mkimapdcert
  4. Run mkpop3dcert
  5. Restart the services

I left the non-ssl IMAP running but only for 127.0.0.1 for squirrel

Technorati logoTechnorati Tags:

Handling mail for non-system users with Exim4

An article popped up on debian-administration.org. I'm going to have to take a closer look at one of the comments:

http://www.debian-administration.org/articles/302#comment_6

If this can work well with courier (which I guess it should) then this will solve an issue I've had a while (and I don't want to go the route of a database for this).

Edit: Various things that have come up under discussion

courier assumes $HOME - to change this you need to change the authenticator so that it changes the value of $HOME (at least according to various google searches)

Syndicate content