This error usually occurs when a mail client is using a secure connection to the mail server under a custom hostname.

For example, this could occur where you have imap.yourdomain.com pointing to imap.beebll.com. This allows you to make a secure IMAP connection, but the SSL certificate installed on our mail servers uses the '*.beebll.com' hostname - and not 'yourdomain.com

It's nothing to worry about, the certificate for '*.beebll.com' is expected so you can trust the certificate with the knowledge that the connection will remain encrypted. Once the certificate is trusted you should not receive any further warnings, unless the certificate changes.

To avoid the warning altogether, you could change the mail client to use the beebll.com hostnames. These are: imap.beebll.com, pop3.beebll.com or smtp.beebll.com for IMAP, POP3 or SMTP respectively.

Was this answer helpful? 2 Users Found This Useful (2 Votes)

Most Popular Articles

Can I use ‘mail.domain’ in my mail client?

For scale and redundancy reasons we operate each service from its own hostname. So we always...
How do I add SRV records for Office 365?

SRV records - service records used in Office 365 - can be added via our DNS Management interface...
How do I migrate emails to Beebll?

To migrate your emails and mailboxes to beebll, Create a ticket and we will handle the rest.
Why do I get “Mailbox does not exist” bounceback from a brand new mailbox?

Getting a 'mailbox does not exist' message can be frustrating, we know. You just need to give it...
Why can’t I send emails?

There a few reasons why you may not be able to send emails: Your ISP is blocking port 25 If you...