Re: Panic: file mail-index-transaction-finish.c: line 185

[tobisworld]

Aki

sorry for not being specific enough. I already use director on my two
public-facing dovecots. Although the mailboxes on my dovecot backend
are in nfs there is only one backend dovecot accessing the mailboxes. I
had two backends long ago and the the nfs is a relict of that time. But
atm only have one dovecot instance that accesses the mailboxes on the
nfs share.

Cheers

tobi


On Wed, 2021-12-29 at 12:05 +0200, Aki Tuomi wrote:
> 
> > On 29/12/2021 11:40 tobiswo...@gmail.com wrote:
> > 
> >  
> > On Wed, 2021-12-29 at 11:26 +0200, Aki Tuomi wrote:
> > > 
> > > 
> > > Do you have multiple backends with concurrent access via e.g.
> > > nfs?
> > > 
> > > Aki
> > > 
> > 
> > Aki,
> > 
> > yes all mailboxes are in a nfs share. Concurrent access could be
> > possible as I have several MUA (my desktop and my mobiles).
> > Although
> > only the client on my desktop (evolution) is currently doing
> > something.
> > My mobiles are "sleeping" atm.
> > 
> > Do you think the nfs share could be the culprit?
> > 
> > Cheers
> > 
> > tobi
> 
> Concurrent access to mailboxes on different backends is not supported
> and is considered dangerous. You need to use something, e.g. dovecot
> director, to ensure all sessions for a user end up in same backend.
> 
> Aki
> 

Re: Panic: file mail-index-transaction-finish.c: line 185

[tobisworld]

On Wed, 2021-12-29 at 11:26 +0200, Aki Tuomi wrote:
> 
> 
> Do you have multiple backends with concurrent access via e.g. nfs?
> 
> Aki
> 

Aki,

yes all mailboxes are in a nfs share. Concurrent access could be
possible as I have several MUA (my desktop and my mobiles). Although
only the client on my desktop (evolution) is currently doing something.
My mobiles are "sleeping" atm.

Do you think the nfs share could be the culprit?

Cheers

tobi

Panic: file mail-index-transaction-finish.c: line 185

[tobisworld]

Hi list

I have weird issue with my Dovecot 2.3.17.1 (476cd46418)
When deleting a certain amount of messages from my INBOX via my MUA
(Evolution) all over sudden dovecot starts to panic

Panic: file mail-index-transaction-finish.c: line 185
(mail_index_transaction_get_uid): assertion failed: (seq <= t->view-
>map->hdr.messages_count)

imap(REDACTED)<24075>: Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42)
[0x7f09274d4142] ->
/usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7f09274d424e]
-> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7f09274e22fe] ->
/usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7f09274e23a1] ->
/usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7f0927430e38] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7f092789d38d] -
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7f092789d3da]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_finish+0x177) [0x7f092789da87] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7f09278a2ad6] -
> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7f09278a2fad]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_commit+0x1c) [0x7f09278a306c] ->
/usr/lib64/dovecot/libdovecot-
storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7f092788c921]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7f09277fbbbd] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7f09278233e9] -
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7f09278236b0]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_get_physical_size+0x38) [0x7f09277e8ba8] ->
/usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465)
[0x7f09263dd465] ->
/usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+
0x5c) [0x7f09265e13ec] ->
/usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7f09265e25d4]
-> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae)
[0x7f09269f92ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e)
[0x7f0926c10f3e] -> /usr/lib64/dovecot/libdovecot-
storage.so.0(+0x50c4c) [0x7f09277f9c4c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58)
[0x7f09277f9ec8] -> dovecot/imap(+0x1175b) [0x55a2c0ea575b] ->
dovecot/imap(command_exec+0x64) [0x55a2c0eb3f04] ->
dovecot/imap(+0x1dde2) [0x55a2c0eb1de2] -> dovecot/imap(+0x1de71)
[0x55a2c0eb1e71] -> dovecot/imap(+0x1e039) [0x55a2c0eb2039] ->
dovecot/imap(client_handle_input+0x205) [0x55a2c0eb22f5] ->
dovecot/imap(client_input+0x79) [0x55a2c0eb28d9]

imap(REDACTED)<24075>: Fatal: master: service(imap):
child 24075 killed with signal 6 (core dumps disabled -
https://dovecot.org/bugreport.html#coredumps)


>From that point on ANY access to INBOX from my MUA causes the error.
The only way that I found to get around is to unsubscribe the INBOX
folder and subscribe again. Then the error is gone until I delete a
bunch of messages again.
The error only occurs if I delete the messages within short time or
select multiple (about 20msg at once). If I delete them one-by-one
always waiting for expunge message in dovecot logs to appear then I can
delete as many as I want.

I have not verified with other MUA but in Evolution I can reproduce the
issue.

Cheers and have a good one

tobi

Re: dovecot panic

[tobisworld]

Sorry to reply to myself ;-) but I found a way around this panic.

After unsubscribe and subscribe again to my inbox folder the panics in
maillog suddenly stopped. Before I got the panic on EVERY click on my
inbox in MUA.
I was cleaning up my mailbox (moved and deleted a log of messages) when
the error first occured today. Maybe related to that?

Anyway problem "solved" for me although I think that "something" on the
client should not be able to trigger such an error on server ;-) 

Cheers and have a good one

tobi

On Mon, 2021-12-27 at 11:15 +0100, tobiswo...@gmail.com wrote:
> Hi list
> 
> since today I receive dovecot panics in my mail logs, whenever I want
> to access on my inbox in my mailclient (evolution)
> 
> Details:
> 
> dovecot --version
> 2.3.17.1 (476cd46418)
> 
> Centos 7 (latest updates)
> 
> x86 architecture
> 
> mailbox stored in NFS
> 
> 
> > Panic: file mail-index-transaction-finish.c: line 185
> (mail_index_transaction_get_uid): assertion failed: (seq <= t->view-
> > map->hdr.messages_count)
> 
> > Error: Raw backtrace:
> /usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42)
> [0x7fb86f592142] ->
> /usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e)
> [0x7fb86f59224e]
> -> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7fb86f5a02fe] ->
> /usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7fb86f5a03a1] ->
> /usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb86f4eee38] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7fb86f95b38d]
> -
> > /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da)
> > [0x7fb86f95b3da]
> -> /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_index_transaction_finish+0x177) [0x7fb86f95ba87] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7fb86f960ad6]
> -
> > /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_index_transaction_commit_full+0x9d)
> [0x7fb86f960fad]
> -> /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_index_transaction_commit+0x1c) [0x7fb86f96106c] ->
> /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_cache_set_seq_corrupted_reason+0x61)
> [0x7fb86f94a921]
> -> /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7fb86f8b9bbd] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7fb86f8e13e9]
> -
> > /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0)
> > [0x7fb86f8e16b0]
> -> /usr/lib64/dovecot/libdovecot-
> storage.so.0(mail_get_physical_size+0x38) [0x7fb86f8a6ba8] ->
> /usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465)
> [0x7fb86e49b465] ->
> /usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_cop
> y+
> 0x5c) [0x7fb86e69f3ec] ->
> /usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4)
> [0x7fb86e6a05d4]
> -> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae)
> [0x7fb86eab72ae] ->
> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e)
> [0x7fb86eccef3e] -> /usr/lib64/dovecot/libdovecot-
> storage.so.0(+0x50c4c) [0x7fb86f8b7c4c] ->
> /usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58)
> [0x7fb86f8b7ec8] -> dovecot/imap(+0x1175b) [0x55a2b1a5375b] ->
> dovecot/imap(command_exec+0x64) [0x55a2b1a61f04] ->
> dovecot/imap(+0x1dde2) [0x55a2b1a5fde2] -> dovecot/imap(+0x1de71)
> [0x55a2b1a5fe71] -> dovecot/imap(+0x1e039) [0x55a2b1a60039] ->
> dovecot/imap(client_handle_input+0x205) [0x55a2b1a602f5] ->
> dovecot/imap(client_input+0x79) [0x55a2b1a608d9]
> 
> I attached output from dovecot-sysreport here to this report
> 
> 
> Best regards
> 
> tobi
> 
> 

dovecot panic

[tobisworld]

Hi list

since today I receive dovecot panics in my mail logs, whenever I want
to access on my inbox in my mailclient (evolution)

Details:

dovecot --version
2.3.17.1 (476cd46418)

Centos 7 (latest updates)

x86 architecture

mailbox stored in NFS


> Panic: file mail-index-transaction-finish.c: line 185
(mail_index_transaction_get_uid): assertion failed: (seq <= t->view-
>map->hdr.messages_count)

> Error: Raw backtrace:
/usr/lib64/dovecot/libdovecot.so.0(backtrace_append+0x42)
[0x7fb86f592142] ->
/usr/lib64/dovecot/libdovecot.so.0(backtrace_get+0x1e) [0x7fb86f59224e]
-> /usr/lib64/dovecot/libdovecot.so.0(+0xf72fe) [0x7fb86f5a02fe] ->
/usr/lib64/dovecot/libdovecot.so.0(+0xf73a1) [0x7fb86f5a03a1] ->
/usr/lib64/dovecot/libdovecot.so.0(i_fatal+0) [0x7fb86f4eee38] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0xf438d) [0x7fb86f95b38d] -
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0xf43da) [0x7fb86f95b3da]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_finish+0x177) [0x7fb86f95ba87] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0xf9ad6) [0x7fb86f960ad6] -
> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_commit_full+0x9d) [0x7fb86f960fad]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_index_transaction_commit+0x1c) [0x7fb86f96106c] ->
/usr/lib64/dovecot/libdovecot-
storage.so.0(mail_cache_set_seq_corrupted_reason+0x61) [0x7fb86f94a921]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_set_mail_cache_corrupted+0xed) [0x7fb86f8b9bbd] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a3e9) [0x7fb86f8e13e9] -
> /usr/lib64/dovecot/libdovecot-storage.so.0(+0x7a6b0) [0x7fb86f8e16b0]
-> /usr/lib64/dovecot/libdovecot-
storage.so.0(mail_get_physical_size+0x38) [0x7fb86f8a6ba8] ->
/usr/libexec/dovecot//lib20_mail_log_plugin.so(+0x2465)
[0x7fb86e49b465] ->
/usr/libexec/dovecot//lib15_notify_plugin.so(notify_contexts_mail_copy+
0x5c) [0x7fb86e69f3ec] ->
/usr/libexec/dovecot//lib15_notify_plugin.so(+0x25d4) [0x7fb86e6a05d4]
-> /usr/libexec/dovecot//lib10_quota_plugin.so(+0x102ae)
[0x7fb86eab72ae] -> /usr/libexec/dovecot//lib01_acl_plugin.so(+0xef3e)
[0x7fb86eccef3e] -> /usr/lib64/dovecot/libdovecot-
storage.so.0(+0x50c4c) [0x7fb86f8b7c4c] ->
/usr/lib64/dovecot/libdovecot-storage.so.0(mailbox_move+0x58)
[0x7fb86f8b7ec8] -> dovecot/imap(+0x1175b) [0x55a2b1a5375b] ->
dovecot/imap(command_exec+0x64) [0x55a2b1a61f04] ->
dovecot/imap(+0x1dde2) [0x55a2b1a5fde2] -> dovecot/imap(+0x1de71)
[0x55a2b1a5fe71] -> dovecot/imap(+0x1e039) [0x55a2b1a60039] ->
dovecot/imap(client_handle_input+0x205) [0x55a2b1a602f5] ->
dovecot/imap(client_input+0x79) [0x55a2b1a608d9]

I attached output from dovecot-sysreport here to this report


Best regards

tobi




dovecot-sysreport-scanner01.inet4.tech-1640599767.tar.gz
Description: application/compressed-tar

Re: end-to-end encryption

[tobisworld]

Yes the server need to know the pubKey for encryption and the client
need access to the privKey to decrypt.
The correct pubKey is determined from gpg based on the rcpt address

Cheers

tobi

Am 16.05.2018 um 11:30 schrieb Gandalf Corvotempesta:
> Il giorno mer 16 mag 2018 alle ore 11:19  ha scritto:
>> I personally use gpgit https://github.com/EtiennePerot/gpgit
>> Which does the encryption of messages. Then I use a sieve script which
>> calls gpgit for every msg and encrypts before saving into mailbox
> 
> If I understood properly, for this to work, a public key must be stored on
> server,
> so that every message is encrypted. Then, on each MUA, the private key must
> be
> present, so that each MUA is able to decrypt the encrypted message, right ?
> 

Re: end-to-end encryption

[tobisworld]

Hi

I personally use gpgit https://github.com/EtiennePerot/gpgit
Which does the encryption of messages. Then I use a sieve script which
calls gpgit for every msg and encrypts before saving into mailbox

Cheers

tobi

Am 16.05.2018 um 10:24 schrieb Gandalf Corvotempesta:
> Il giorno mer 16 mag 2018 alle ore 06:09 Aki Tuomi 
> ha scritto:
>> You could probably automate this with sieve and e.g. GnuPG, which would
> mean that all your mails are encrypted without server having key to decrypt
> this.
> 
> Any guide or sample to look for ?
> 

Re: [SPAMMY]Re: Dovecot LMTP Proxy + STARTTLS?

[tobisworld]

Hi

thanks for the link. Read that page before but somehow missed the
comment about ssl+lmtp proxy :-)

Are there any plans to implement that to dovecot in future?

Regards

tobi

Am 23.11.2017 um 18:38 schrieb Carsten Rosenberg:
> NOTE: LMTP/doveadm proxying doesn't support SSL/TLS currently - any 
> ssl/starttls extra field is ignored
> 
> https://wiki2.dovecot.org/PasswordDatabase/ExtraFields/Proxy
> 
> Am 23. November 2017 09:31:41 MEZ schrieb Tobi :
>> Hi
>>
>> I got dovecot 2.2.26 on a Centos7 with latest updates. Dovecot is
>> configured to act as director and delivers to my two backend servers.
>> I enabled lmtp proxy on director to listen on port 24.
>>
>> Now I see in msg headers that the connection to the lmtp proxy uses
>> STARTTLS but the connection from proxy to backend seems to be
>> unencrypted. Is it possible to enforce the use of STARTTLS in the
>> connection from the director to the backend as well?
>>
>> Regards
>>
>> tobi