On Wed, 22 Jan 2025, Marco Fioretti via dovecot wrote:
sorry, I must be missing something. Why would postfix be talking directly to dovecot? Or play middleman between some external entity and dovecot? Or did you mean something else?
Postfix (which is likely to be your SMTP server) uses (very often) Dovecot for the SASL authentication.
The communication between Postfix and Dovecot is usually via a Unix socket and not IMAP, which explains why it was (always) working even if IMAP wasn't working.
Check postconf -n and you will likely have something like
.. smtpd_sasl_type = dovecot smtpd_sasl_path = private/auth ..
I'd advise you to put the server offline (or firewalled appropriately) until you have everything set up, to avoid making things worse.
Good luck! Bernardo
Thanks
Il giorno mer 22 gen 2025 alle ore 07:35 Aki Tuomi < aki.tuomi@open-xchange.com> ha scritto:
On 22/01/2025 07:49 EET Marco Fioretti via dovecot <dovecot@dovecot.org> wrote:
Il giorno mer 22 gen 2025 alle ore 06:37 Aki Tuomi < aki.tuomi@open-xchange.com> ha scritto:
On 22/01/2025 07:26 EET Marco Fioretti via dovecot < dovecot@dovecot.org> wrote:
Now the question is, OK, that attempt may be some attacker trying to get in, this happens but... HOW is he succeeding to TRY to connect, if dovecot doesn't appear to be listening at all??? And of course, does this help in any way to figure out what is wrong with my configuration?
Thanks, Marco
Try adding
protocols = imap
Aki
Hi Aki,
adding this right before the service imap-login part of dovecot.conf worked, thanks!
Now, what about that authorization attempt? What happened, why, how... and is that as sign of some weakness in the system, and how should I fix it?
Thanks, Marco
I'd guess it's coming via postfix.
Aki
dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-leave@dovecot.org