Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. crt.sh | example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:kasdivi.com
I ran this command:
I try to reinstalll my email account on my iPhone and iPad. It never give me a chance to trust it
It produced this outputI
no out out just no action
My web server is (include version):
apache 2.4.5.1
The operating system my web server runs on is (include version):
FreeBSD 13.1
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don't know):
yes
I'm using a control panel to manage my site (no, or provide the name and version of the control panel):
no
The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):
certbot 1.13.0
The trust certificate for Apple iOS. 2022070700 Includes ISRG Root X2 which I thinks the root for LetsEncyptt
I think it may ba having issue with my certificate covering serval domains. but I have no issue adding email account with another domain , theoceanwindow.com
I know this is an Apple problem but I have gotten no leads except to delete and reinstall which is my new morning routine.
I have been able to send email using this sever using on line tools
I guess my only fix is figure iOS is dead to me and go back to android
mail.kssdivi.com. This hs been a continuing problem. It will work a while and trust goes away. My server hasn't changed just another iOS update or tweak I imagine
There are no public DNS records for that hostname, but comparing to your OP it's apparently just a typo. If I check mail.kasdivi.com, it returns this certificate:
Once again, that hostname doesn't seem to exist--there aren't any public DNS records for that hostname. But it (along with www. theoceanwindow.com) is part of the cert I gave above, so it's to be expected that it would be trusted.
The way certificate validation works really is pretty straightforward: if you're connecting to $HOSTNAME, the certificate presented needs to cover $HOSTNAME. If you're trying to connect to mail.kasdivi.com, and the cert doesn't includes that name (which it currently doesn't), you're going to get an error. If you're trying to connect to theoceanwindow.com (once its DNS records exist again), and the cert presented does include that name, then no error.
Ok I re-learned the process.. update the certificate... pretty much induced everything in it and Apple MAIL on the iOS devices will not verify the smtp under ssl. Ok so I turned of ssl on Apple Mal for that account and changed port to 25, the old insecure smtp port an outgoing mail works fine. BTW my hostname is triggerfish.theoceanwindow.com.
Got me beat. Like I said my desktop has now issues with this or any other account
Interesting, it does for me. I obviously don't have credentials to log in, but my iPhone doesn't give me any cert warnings when I try to set up an account there.
after I put all the server information in I get "cannot connect Using SSL". I tried reinstalling the account this morning. , ignored that warning and it seems to work ok including sending mail. Thanks. Just more joy dealing with Apple. Thanks for the tips