IDNetters Forums

Technical News & Discussion => IDNet Help => Topic started by: Stevescat on Jul 07, 2010, 19:28:34

Title: IDNet Certificate mismatch!
Post by: Stevescat on Jul 07, 2010, 19:28:34
I have a pop3 email account. When getting new mail I get this alert (I'm on a Mac).

Mail can't verify the identity of "idnet.com". The certificate for this server is invalid. You might be connecting to a server that is pretending to be idnet.com which could put your confidential information at risk. Do you want to connect anyway?

I've tried deleting the account and starting again with the same results.

When viewing the certificate, it fails when it gets to: idnet.net

I can get around this by choosing "Always Trust" the certificate, I just wondered what you guys thought.
For what it's worth, I can receive mail on my iPod Touch without any problems.

Thanks in advance for any ideas.
Title: Re: IDNet Certificate mismatch!
Post by: Steve on Jul 07, 2010, 19:32:47
I get the same, always have for the last 18 months and I use the same work around
Title: Re: IDNet Certificate mismatch!
Post by: Stevescat on Jul 07, 2010, 19:40:11
Thanks Steve. Question asked, answer within 5 minutes!
Title: Re: IDNet Certificate mismatch!
Post by: Steve on Jul 07, 2010, 19:54:18
If I remember I'll ask IDNet why?
Title: Re: IDNet Certificate mismatch!
Post by: mchunt_idnet on Jul 08, 2010, 08:01:36
What servername are you using to connect with? For secure mail connections you should be using securemail.idnet.com any other address will lead to an invalid certificate error.

If you are using the address and getting the problem then there is likely to be an issue that is local to your machine/mail client and the best way is to just 'Always Trust' the certificate.

We renewed the ssl certificate yesterday morning so some users who had explicitly trusted the previous certificate will have to now trust the new one.
Title: Re: IDNet Certificate mismatch!
Post by: Ronnie on Jul 08, 2010, 08:10:22
i was getting the same with my phone even when i got it to except the certificate for ever.

i have changed my pop3.idnet.com to securemail.idnet.com and all working
Title: Re: IDNet Certificate mismatch!
Post by: Gary on Jul 08, 2010, 08:31:35
Quote from: mchunt_idnet on Jul 08, 2010, 08:01:36
What servername are you using to connect with? For secure mail connections you should be using securemail.idnet.com any other address will lead to an invalid certificate error.

If you are using the address and getting the problem then there is likely to be an issue that is local to your machine/mail client and the best way is to just 'Always Trust' the certificate.

We renewed the ssl certificate yesterday morning so some users who had explicitly trusted the previous certificate will have to now trust the new one.
Does securemail.idnet.com apply to smtp as well, like mail.idnet.net.uk does Simon?
Title: Re: IDNet Certificate mismatch!
Post by: Steve on Jul 08, 2010, 08:44:43
Quote from: mchunt_idnet on Jul 08, 2010, 08:01:36
What servername are you using to connect with? For secure mail connections you should be using securemail.idnet.com any other address will lead to an invalid certificate error.

If you are using the address and getting the problem then there is likely to be an issue that is local to your machine/mail client and the best way is to just 'Always Trust' the certificate.

We renewed the ssl certificate yesterday morning so some users who had explicitly trusted the previous certificate will have to now trust the new one.

Thanks that explains everything and why those us who 'always trusted' have had a reminder.
Title: Re: IDNet Certificate mismatch!
Post by: Gary on Jul 08, 2010, 09:28:47
I thought idnet.com did not support SSL on pop3 or smtp, but the .net addresses did  :dunno: I know my domain does support SSL through IDNet.
Title: Re: IDNet Certificate mismatch!
Post by: mchunt_idnet on Jul 08, 2010, 10:13:26
smtp.idnet.com is on a completely different server (we split idnet.com pop/imap & smtp onto seperate boxes when trevor decided to be a naughty boy) and will accept both smtp, smtp+tls & smtps on the main address. We also installed an upgraded smtp.idnet.com server and renewed certificate yesterday.

Quote from: Gary on Jul 08, 2010, 08:31:35
Does securemail.idnet.com apply to smtp as well, like mail.idnet.net.uk does Simon?
Title: Re: IDNet Certificate mismatch!
Post by: Simon on Jul 08, 2010, 10:16:44
Thanks, Martin, that's good news.  :)
Title: Re: IDNet Certificate mismatch!
Post by: Gary on Jul 08, 2010, 10:33:31
Quote from: mchunt_idnet on Jul 08, 2010, 10:13:26
smtp.idnet.com is on a completely different server (we split idnet.com pop/imap & smtp onto seperate boxes when trevor decided to be a naughty boy) and will accept both smtp, smtp+tls & smtps on the main address. We also installed an upgraded smtp.idnet.com server and renewed certificate yesterday.

Cheers for that, I now have secure mail on all my idnet.com addresses as well as my domain mail  :thumb:
Title: Re: IDNet Certificate mismatch!
Post by: Steve on Jul 08, 2010, 10:59:58
If you check in your IDNet customer portal all the relevant email settings available are shown
Title: Re: IDNet Certificate mismatch!
Post by: Gary on Jul 08, 2010, 11:12:25
Quote from: Steve on Jul 08, 2010, 10:59:58
If you check in your IDNet customer portal all the relevant email settings available are shown
I had not looked for ages Steve, I was quite surprised at the proliferation of new settings, saying that I feel better having SSL on idnet.com addresses with securemail.idnet.com and SMTP.idnet.com now. Its odd how it was never an issue with my iPhone though.
Title: Re: IDNet Certificate mismatch!
Post by: Steve on Jul 08, 2010, 12:51:17
I'd not noticed until directed by Martin to the customer portal, if I recall my iPhone complained about the IDNet mail server recently it may have been yesterday.I forward most of my mail to Mobile Me so pop/imap@idnet.com is rarely checked
Title: Re: IDNet Certificate mismatch!
Post by: Stevescat on Jul 08, 2010, 19:13:27
Like others have said, hadn't noticed the email info on the customer portal. Problem now solved!

Thanks again all,
Steve.