Currently if you type in the name of the domain for webmail (mail.mywebsitename.com) it will take you to an unsecure page to login and view your email even after setting up cname record. Yes the user can go to the https://mail.b.hostedemail.com/ or https://mail.mailconfig.net/ versions to login but the first method is much easier for client to remember. BC allows for this but just forwards that to the secure URL address automatically. Treepl should allow for the same.
Out of curiosity, was there ever a change/update made for the unsecure login page when using a subdomain to reach webmail? I have a client that just brought this up and I just want to make sure I didn’t miss an update or a workaround for this so that clients can continue to use mail.domain.com to access webmail without the security notice. Thank you!
No change as far as I know. I have just been redirecting the mail.domain.com to https://mail.b.hostedemail.com/ This has worked for my clients I only have two that use the hosted email.
Okay, thank you @Rhatch ! It sounds like this particular client is getting the error in Outlook, so I’m thinking she just used the subdomain in the server settings rather than the mail.b.hostedemail.com domain for the server settings. Hopefully I can get on a screen share with her and walk her through those server settings and swap out the subdomain for the with the mail.b… domain. That’s a good idea though for their staff that uses webmail directly, so thank you!