3 Messages
•
166 Points
License Certificate EXPIRED!
WHY IS THIS ALWAYS HAPPENING WITH HOMESTEAD? We use third-party sites to work and sent out communications with platforms and this is more of a headache than my actual job. Then, we call the new employees/freelancers at homestead act as if they know nothing of the such! Help, please Help! We were told to send screenshots of how we set up our accounts on all third-party sites (yikes, what) or we can take our business to another email provider! Wow out of 7 years doing business with HOMESTEAD we have NEVER been told to do such a thing.
techwtr
66 Messages
•
964 Points
2 years ago
My experience--on my iPad, iPhone, and iMac--has been that, if my email accounts were configured with Port 587 for the Outgoing Mail Server (SMTP), then I would get a "Not Trusted" error when trying to send email, and the details on the error would point to an expired certificate that expired May 14, 2022 at 7:00 pm. No amount of restarts of the email apps or the devices resolved the problem on any of the three devices.
However, if I changed the Port to 465 in the configuration for each email account, I no longer got the "Not Trusted" error on any of the three devices for both of my email accounts.
So, my uneducated guess is that Homestead is still providing its old, expired certificate when we attempt to send mail using Port 587, but is providing the new, renewed certificate when we send mail using Port 465.
0
0
elyzabethv
10.6K Messages
•
141.7K Points
2 years ago
Hello,
Our certificate is and has been current. It expired and was renewed with no downtime. What's happening is that some email clients are not refreshing the certificate or it's caching. Unfortunately, we have no control over this. We can only suggest troubleshooting steps like restarting your email application, restarting your entire device, or re-entering the email client settings that we provide (that do suggest first that you use port 465, like TechWtr says), which all help refresh or clear caching.
These steps have successfully resolved this issue for everyone that I've talked to.
4
0