fetchmail and incorrect SSL Certificates with Office 365

reetp — Thu, 11 Oct 2012 17:07:47 GMT

This post refers :

http://business.forums.bt.com/t5/Email/security-certificate-cannot-be-verified/m-p/44928

Just wanted to make a note in case someone else comes across this.

If you get an error like this its because it would appear that M$ haven't sorted their certificates correctly (There is loads of stuff online about it) :

fetchmail : Server CommonName mismatch: outlook.com != pop.outlook.com

The upshot is that they should have got this sorted properly, but haven't bothered and left it to the user to manage. That might be fine with M$ own products but then we don't all use them.

I believe the error varies with fetchmail versions. One machine has it but another doesn't. It doesn't appear to affect actual collection on the machines, but I believe in some cases it might.

Enjoy

Re: fetchmail and incorrect SSL Certificates with Office 365

DaveA — Fri, 26 Oct 2012 13:52:55 GMT

Hi,

First off you need to make sure you're on Outlook Service Pack 3, which is mentioned in the thread you linked to.

If that doesn't help then try using port 25 on the outgoing server.

And should that fail then contact the Helpdesk.

Dave

topic fetchmail and incorrect SSL Certificates with Office 365 in Archive

fetchmail and incorrect SSL Certificates with Office 365

Re: fetchmail and incorrect SSL Certificates with Office 365