popmay
June 27, 2024, 12:23pm
21
With your pro license you can open a support ticket and get direct support with staff.
There have been some instances that a data center installed OS created unexpected problems and they have specific experience with that and everything related to their software.
If you post the results back here it can be helpful to others.
Link also here:
We understand that managing servers can be complex, but you’re not alone. Our team is dedicated to helping you utilize our products to their fullest potential. Whether you’re troubleshooting, need quick solutions, or require in-depth assistance, the...
You might find something helpful in this:
Email functionality in Virtualmin involves various components, making it a complex system. Key elements include a Postfix mail transfer agent, a Procmail mail delivery agent, Dovecot IMAP/POP3 retrieval, ClamAV anti-virus, SpamAssassin anti-spam, and...
2 Likes
yeah, i sent a PM about it. will update further.
thanks for the assist
Joe
June 27, 2024, 5:12pm
23
psanders:
pam(pms@lilswervy.com ,71.61.201.159,<+QthzMsbdfhHPcmf>): lookup service=dovecot
Jun 26 10:26:55 hosting100 dovecot: auth: Error: auth-worker: Aborted PASSV request for pms@lilswervy.com : Worker process died unexpectedly
That’s unusual. So unusual that I’ve literally never seen it, and I’ve seen just about everything.
Do you have plenty of memory? Check the kernel log (dmesg
) for OOM killer messages.
I’m not sure what else would cause dovecot processes to die unexpectedly. I don’t think any configuration error would cause it, as configuration is parsed on start, if it were invalid, it would just log an error and exit.
1 Like
checked the kern.log and didn’t see anything, but I am not an expert. the box has 64gb
Joe
June 27, 2024, 5:32pm
25
psanders:
the box has 64gb
OK, definitely not memory.
@jimr1 mentioned this earlier.
Hello,
After updating the server, I can't see the content of e-mail accounts. Mail to accounts arrives fine, but cannot be seen with imap.
I see in the logs:
serwer dovecot: service=imap, user=user@domain.ex, ip=[any.ip.add.res]. Fatal: master:...
Can you get a good dovecot config and compare it to yours?
or do like they did - uninstalling dovecot and deleting/etc/dovecot and reinstalling?
There are modifications that virtualmin does such as SASL integration (I think) and other stuff that would get lost.
I have Ubuntu 22.04 (need to double check) if there is no security keys etc… on it I can maybe copy the files needed.
1 Like
After the Virtualmin Install and setup process after logging in, did you run the Re-Check Configuration?
Also, did you go through the whole setup wizard? Did you specify whether passwords are plain or hashed?
yes. and the passwords are hashed
Does everything checkout ok when you re-check configuration?
Under Virtualmin Tab → System Settings → Re-Check Configuration
no problems, says it’s ready
psanders:
says it’s ready
Cool,
Is this a new installation of Virtualmin? Is this only happening to the migrating sites?
Does this also happens to newly created Virtualservers?
Are you hosting the DNS records for these domains?
Do they have an DNS A record for mail.domain.tld
Added note: Does restarting dovecot service make any difference?
yes
no - fresh site does same
yes
yes
not at all
What version of dovecot is installed on your ubuntu 22.04 server?
Ok,
Look in your Webmin Tab for Servers → Dovecot IMAP/POP3 Server
Click on edit config files:
In drop down locate /etc/dovecot/conf.d/10-auth.conf
Make sure that these lines below are the only lines that do not have a # in front of them
You should only have three settings in this file, everything else should be off.
disable_plaintext_auth = no
auth_mechanisms = plain
!include auth-system.conf.ext
1 Like
ok, it showed the rest and this was
auth_mechanisms = plain login
switched to auth_mechanisms = plain
neither worked – same issue. also ran the virtualmin re-check and passed
In the same drop down locate /etc/dovecot/conf.d/auth-system.conf.ext
Make sure the settings are pointing to pam as shown below.
passdb {
driver = pam
# [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=<n>]
# [cache_key=<key>] [<service name>]
#args = dovecot
}
userdb {
# <doc/wiki/AuthDatabase.Passwd.txt>
driver = passwd
# [blocking=no]
#args =
# Override fields from passwd
#override_fields = home=/home/virtual/%u
}
If all this is good as it should, I would also check as to how you have your settings on the email client setup.
one approach would be
IMAP server: mail.domain.tld Port: 993 with SSL/TLS
SMTP server: mail.domain.tld Port: 587 with STARTTLS
Both settings with authenticate password.
those settings are all what we have - including multiple mail clients