I'm running cyrus-imapd-3.4.4 on Fedora 37, having migrated it from one platform to another recently.
Part of the migration caused authentication to temporarily fail, but that issue was root-caused and fixed (I have a software patch which I'm testing and will submit for 3.9.0 shortly).
My clients are all various generations of iOS and MacOS devices, mostly current.
Looking in
/var/log/maillog
I see messages being delivered, but my mail client (Mail.app on my MacBook Air as I type this) doesn't see anything more recent than yesterday evening. It also doesn't show any subfolders.Logging into the mail server and digging around
/var/spool/imap/
... I see new messages, and subfolders, so all of that is still there.LMTP from Sendmail continues to deliver successfully.
IMAP/S as I said shows connections successfully authenticating (it's configured for TLS and uses the SASL db to authenticate users via
CRAM-MD5
or DIGEST-MD5
), but no new email shows up and the subfolders aren't visible as above."testsaslauthd" on the server succeeds, but
sieveshell
fails to connect and strace
reveals it's an authentication issue, which I've not dug into:Jun 9 14:55:27 mail cyrus/sieve[11739]: badlogin: localhost [127.0.0.1] DIGEST-MD5 authentication failure Jun 9 14:55:29 mail cyrus/sieve[11739]: Lost connection to client -- exiting
and:
[root@mail ~]# testsaslauthd -u "$USER" -p "$PASSWD" -r realm 0: OK "Success."
I'm not sure what is still broken at this point, or why I'm able to authenticate but not see new email in my INBOX nor existing folders.
The changes I made (long ago, and haven't tweaked since then) to
cyrus.conf
was to turn off imap
but leave imaps
enabled. pop3
and pop3s
are disabled, as is http
and https
. sieve
is still enabled. idled
was enabled.The changes I've made to the distro's
imapd.conf
file are:sasl_mech_list: CRAM-MD5 DIGEST-MD5 # tls_client_ca_file: /etc/pki/cyrus-imapd/cyrus-imapd-ca.pem unixhierarchysep: off tls_versions: tls1_3 tls1_2 tls_required: 1 tls_prefer_server_ciphers: 1 tls_server_dhparam: /etc/pki/tls/misc/dhparam.pem sieve_tls_required: 0 sieveallowplaintext: 1
so relatively few changes to the stock parameters.
Can anyone provide some pointers in troubleshooting this to get a smoking gun?
I'm a developer, not an admin, so I don't have a lot of experience in troubleshooting operational systems. I'm on IRC
#cyrus
as philipp64
for more real-time communication.Thanks.