Well it looks like your Dovecot is setup to work with Virtualmin. What about a Server Reboot?
Could be a service waiting to update configs and needs a reboot?
just did it and no luck
I donât see how this can be configuration.
Are you sure thereâs nothing interesting in the kernel log? I almost want to guess hardware problems. You could try downgrading dovecot (if youâre already on the latest, always better to move forward, if youâre not up to date). I donât recommend uninstalling and reinstalling (ever, for any software).
You should also try connecting without OpenSSL in the loop. An unencrypted connection has a lot less code to traverse. If it works without SSL, then you can narrow down the code involved a little bit. Might be best to completely disable all TLS support in Dovecot temporarily for testing. Narrowing down the problem rather than making random configuration changes is generally best.
Also keep looking at logs. If thereâs going to be a clue, itâs probably going to be in the logs. You probably also want to increase the verbosity of logging in Dovecot: Dovecot Logging â Dovecot documentation
You need some information about WTF is going on. Everybody in this (long) thread is making wild guesses. Configuration shouldnât be able to cause a Dovecot process to crash! So, looking at configuration files probably isnât useful (as long as you havenât done something unusual and made changes that would pull in other libs or whatever from the standard Virtualmin configuration).
1 Like
thanks for the time spent on this â weâre having the data center reinstall the OS and weâll start again clean.
Please let us know if that fixes it.
this seems to have done the trick. i was able to setup the email account successfully and login. receiving and sending mail work (havenât tested with migrated cpanel account yet, but baby steps).
during setup of security procedures, i recalled that i got an error about mail not being present, and to install mailutils. i remember doing this before, and it installs postfix and mysql and a bunch of stuff. i did NOT do this this time.
no idea if this was the cause, but it definitely points to user error (itâs me: iâm the user error)
Oh no. Donât do that sort of off-roading. Start with a freshly installed, minimal, OS install of your preferred supported OS (preferably the latest supported version). The Virtualmin installer installs everything it needs. But, it wonât fix things that are broken and it wonât bring a system back into a âdefault Virtualminâ state. If you install/configure a bunch of random stuff and then install Virtualmin, nobody has any idea what state the system is in.
All that said, I donât think that explains the problem you saw. But, itâs good youâve started over with a clean state. There would have been a wide variety of weird issues otherwise, sometimes hard to diagnose (since weâre all assuming a standard installation as documented).
If you need to install other software afterward, thatâs fine, as long as you know what youâre doing. But, start with Virtualmin.
1 Like
speaking of, is mailutils okay to install? we have some bash scripts that use mail
As long as you do it after installation of Virtualmin. It depends on a bunch of stuff, and by default will pull in stuff that conflicts with what Virtualmin expects. I donât see anything in the package that would cause a problem as long as it happens after Virtualmin is up and running. Debian -- Details of package mailutils in bookworm)
ahh, looks like i donât need to â forgot mailx exists
This topic was automatically closed 8 days after the last reply. New replies are no longer allowed.