Mailserver ERR_CERT_COMMON_NAME_INVALID
-
okay so we were able to reproduce in a new test account in chat.
let's continue tomorrow. -
manitu uses Dovecot, which is a common FOSS mail server, so that's definitely something to look into
-
@teicher Do you know whether I can access to a similar test account or whether I can sign up for an email like that somewhere ?
-
@Gwen-Dragon you may share the test account credentials with @gmg
-
Hello, do we have any progress here?
Can I close/delete the test mbox?
Cheers, Tom. -
Hello, so what's the status here ? Cheers Tom.
-
So the last thing we saw is that Vivaldi can connect to the mail test account I provided, and could download the IMAP folders but not their content.
Several other mail clients, including Seamonkey, Thunderbird and Mailspring can connect and download my mails just fine. All works fine using mail.manitu.net with secure SSL, and also with mail.teicher.net with unsecure SSL (which all other clients allow).
So if we're really back to certificate discussions here, this is unfortunate and I will give up.
-
@Gwen-Dragon my mail server has a valid certificate as mail.manitu.net. this is sufficient.
I provided a test account to reproduce the problem 5 weeks ago.
Did testing against it really show that the problem is caused by SSL config? -
So the SSL is good enough for every other client, and good enough to download IMAP Folders for Vivaldi, but not good enough to download messages. Makes sense. I give up. Goodbye.
-
@teicher Yes, we're getting
INBOX: Error: Error in IMAP command UID FETCH: FETCH MODSEQ can't be used with non-permanent modseqs (0.001 + 0.000 secs).
This seems we're not handling the non-permanent modseq setting for dovecot setup correctly.
https://doc.dovecot.org/admin_manual/lua/We've made an issue for this VB-77952. In the meantime you could change the settings for the modseq, but we'll of course have to deal with this case.
Sorry for the delayed response. I was just hoping I'd get around to an actual fix before answering, but haven't found any simple fix for this yet.
-
@gmg thanks! With "change the settings for the modseq"; if you mean at the dovecot, no, it's a hosted system; if you mean inside Vivaldi - how/where ?
-
I meant inside dovecot, since that setting seems to be broken at this time for us. But then we'll just have to fix it.
-
Hello @gmg, as the bugtracker is not public, can you please let me know about progress to VB-77952 ?
Thanks Tom. -
This post is deleted! -
Hi, You are supposed to fix Mailserver ERR_CERT_COMMON_NAME_INVALID error here. There are a couple of reasons behind it so we can't be sure about that. I would suggest you to assess tour proxy settings maybe. It doesn't matter which Operating system you are using; you can gain access to your proxy settings through Google Chrome by navigating to Settings > Advanced > System > launch your computer’s proxy settings: In case you’re utilizing Windows, this will start the Internet Properties window, so just press on the Connections tab, and then select the option of LAN Settings and choose Automatically detect settings: On macOS, this will launch your Network settings window, so just tap on the option of Proxies and choose Automatic Proxy Configuration: You can now try to gain access to your site to see if the issue is fixed. This will surely help with chrome net err_cert_common_name_invalid now.