I can receive, but not send email.

[x17Andrew71x]

I appreciate the help, but i don't feel that starting fresh every time is the right answer. 

I fixed it a bit ago, something caused the passwords in the passwords.txt and all the various config files in /etc/sentora/configs/dovecot folder to not match. Either the passwords.txt changed or all the configs changed. Maybe dovecot got installed over and the configs got replaced. 

Anyway, now i can launch the webmail and log in and i can receive mail, but not send. 
My ISP is blocking 25.

Upgrading to a business plan with a static ip and 25 unblocked. Hopefully it resolves that issue.

[fearworks]

I appreciate the help, but i don't feel that starting fresh every time is the right answer. 

I fixed it a bit ago, something caused the passwords in the passwords.txt and all the various config files in /etc/sentora/configs/dovecot folder to not match. Either the passwords.txt changed or all the configs changed. Maybe dovecot got installed over and the configs got replaced. 

Anyway, now i can launch the webmail and log in and i can receive mail, but not send. 
My ISP is blocking 25.

Upgrading to a business plan with a static ip and 25 unblocked. Hopefully it resolves that issue.

I am not sure you understand quite how Sentora is working, and I don't see how dovecot would "maybe" get installed over without you doing something to make that happen, but if you are happy to keep chipping away at issues when they arise on your server then so be it.

It's not a strategy I would use or recommend, but good luck!

Keith.

[x17Andrew71x]

I am not sure you understand quite how Sentora is working, and I don't see how dovecot would "maybe" get installed over without you doing something to make that happen, but if you are happy to keep chipping away at issues when they arise on your server then so be it.

It's not a strategy I would use or recommend, but good luck!

I don't claim to be a Sentora expert, but i do know a little bit. I was messing with other mail systems, its very possible it overwrote dovecot/postfix accidentally. 
This is not a production environment. So "chipping away" at issues is a fantastic way to learn and get better with the system, both OS and cpanel. 
Wiping your server any time an issue comes up is not a strategy i would recommend. In fact, in a production environment I would say it isn't a very viable solution either.
To be able to learn how to resolve these issues is important for any server admin. The ability to troubleshoot problems and find solutions is an important skill to have.