Re: Users losing mail from their mailboxes

On 16/05/2025 17:06, Nikolaos Milas via dovecot wrote: Hello, We are on Dovecot 2.3.18. Some users are occasionally complaining that all mail vanishes from their inbox. However, we cannot find any indication of deletions or expunge in the log. One explanation could be that mail files are deleted

Re: lost emails - Opened mail because: snippet ?

On 24/03/2025 18:54, Michael Slusarz wrote: On 03/24/2025 9:41 AM MDT Arkadiusz Miśkiewicz via dovecot wrote: Debug: Mailbox INBOX: saving UID 0: Opened mail because: snippet (Mail not cached, highest cached seq=20 uid=31: reset_id=1742577355) "Opened mail because: snippet " -

lost emails - Opened mail because: snippet ?

Hello. I'm tracking a weird case where dovecot (it's 2.3.21.1) looses incoming emails. Email is delivered over LMTP with full success (in theory). From lmtp raw log: 1742822341.735762 250 2.0.0 +LpAG8Vb4Wc9OAAA9fPEKQ Saved 1742822341.735918 221 2.0.0 Bye Log says it got saved: Mar 24 14:

Re: Dovecot 2.4.0 multiple hosts SNI configuration regression [thousands of certs question]

On 26/02/2025 18:31, Timo Sirainen via dovecot wrote: I don't think there is much of a benefit anymore with v2.4, since the certificate and keys are accessed via mmap()ed binary config file. So although the cert/key are duplicated there, that happens only once per server, not once per process

Re: lua API and returning reason and CONTACTADMIN

} else { + } + if (str != NULL) { auth_lua_export_fields(req, str, scheme_r, password_r); } Aki On 05/02/2025 11:14 EET Arkadiusz Miśkiewicz via dovecot wrote: On 23/01/2025 16:30, Aki Tuomi wrote: I was kinda hoping it would've shown bit more details. But, looks like you've

Re: lua API and returning reason and CONTACTADMIN

in src/auth/db-lua.c:auth_lua_export_fields() splits string by space const char *const *fields = t_strsplit_spaces(str, " "); so it won't be possible to return like reason="This is the reason" Looks like another bug, right? Aki On 23/01/2025 17:20 EET Arkadiusz Miśkiewic

Re: lua API and returning reason and CONTACTADMIN

ug: Module loaded: /usr/lib64/dovecot/plugins/auth/libauthdb_lua.so Jan 23 15:10:29 webx dovecot[10752]: auth: Debug: client passdb out: FAIL 1 user=test code=user_disabled Jan 23 15:10:29 webx dovecot[10752]: imap-login: Disco Aki On 23/01/2025 13:26 EET Arkadiusz Miśkiewicz

lua API and returning reason and CONTACTADMIN

Hello. Trying to pass reason response via lua by passing it at dovecot.auth.PASSDB_RESULT_USER_DISABLED like: function auth_password_verify(request, password) return dovecot.auth.PASSDB_RESULT_USER_DISABLED, "reason=custom_message" end function auth_userdb_lookup(request) return dovecot

qp and Invalid quoted-printable input trailer: '=' not followed by two hex digits

I have a mail (attached) for which dovecot reports: imap(test): pid=<32688> session=, Error: Mailbox INBOX.test: UID=1: read() failed: read(/var/mail/test/.test/cur/1695887652.M710714P17846.mbox13:2,RS) failed: Invalid quoted-printable input trailer: '=' not followed by two hex digits an

Re: sieve processing - enable/disable per user?

On 06/10/2023 17:32, Oscar del Rio wrote: On 2023-10-06 5:12 a.m., Arkadiusz Miśkiewicz via dovecot wrote: Unfortunately it doesn't get expanded: user_query = ... , 'sieve' AS 'sieve_enabled', ... mail_plugins = $mail_plugins %{sieve_enabled} "sieve_enabl

Re: sieve processing - enable/disable per user?

On 06/10/2023 11:12, Arkadiusz Miśkiewicz wrote: On 06/10/2023 09:27, Aki Tuomi wrote: Maybe try protocol lmtp {    mail_plugins = $mail_plugins %{sieve_enabled} } and return sieve_enabled="sieve" for those users you want to enable sieve processing for. Unfortunately it doesn't get expanded

Re: sieve processing - enable/disable per user?

e' AS 'sieve_enabled', ... mail_plugins = $mail_plugins %{sieve_enabled} and dovecot[17847]: lmtp(17932): Fatal: Plugin '%{sieve_enabled}' not found from directory /usr/lib64/dovecot/plugins Aki On 06/10/2023 09:56 EEST Arkadiusz Miśkiewicz via dovecot wrote:

sieve processing - enable/disable per user?

Hi. I keep users in database and would like to enable/disable sieve for them per user. What's the approach for that? I'm looking at the sieve options and user_query setting but don't see anything that would make this possible. -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org ) _

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 28/03/2019 09:36, Timo Sirainen wrote: > On 28 Mar 2019, at 10.15, Arkadiusz Miśkiewicz > wrote: >> >>  error = 0x55e3e2b40ac0 "Fixed index file >> /var/mail/piast_efaktury/dovecot.index: log_file_seq 13 -> 15", >>  nodiskspace = true, > > This was one of the things I wa

Re: Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

On 27/03/2019 16:12, Timo Sirainen wrote: > On 27 Mar 2019, at 14.58, Timo Sirainen via dovecot > wrote: >> >>> dovecot isn't able to auto fix the indexes and manual deletion is >>> required in all such cases >> >> So if it keeps repeating, it's very strange. Could you

Panic: file mail-transaction-log-file.c: line 105 (mail_transaction_log_file_free): assertion failed: (!file->locked)

Hello. I have one account with heavy traffic (big mails) and quite often indexes get corrupted. This is dovecot 2.3.5 on local fs (xfs), Linux kernel 4.19.20, glibc 2.28. When corruption happens lmtp and pop3 segfault on accessing it like: > Mar 27 11:13:50 mbox dovecot[22370]: lmtp(24428): Co

Re: dovecot/config processes one more time - which are safe to kill?

On 14/01/2019 01:43, Timo Sirainen wrote: > On 13 Dec 2018, at 11.18, Arkadiusz Miśkiewicz wrote: >> >> >> Hello. >> >> The problem with dovecot/config processes never ending and spawning new >> one on each reload >> (https://www.dovecot.org/list/dovecot/2016-November/106058.html) is >> becoming a