Re: modernizing dovecot.conf
On 12/29/2021 9:53 PM, Benny Pedersen wrote: On 2021-12-30 05:40, Laura Steynes wrote: Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only so you are just a gmail victim ? :=) I have no experience on this with gmail. I haven't subscribed to any mailing lists with my gmail account. Thunderbird changed a while back so it ignores a Reply-To header sent by a mailing list and replies to the sender of the email... so if you just press Ctrl-R you will not be sending to the mailing list. It is possible to get the old behavior back by disabling the "mail.override_list_reply_to" setting in the Thunderbird config editor. I can't remember which version made this change. I'll await someone more knowledgeable to answer my original questions I think knowledge ? would imap protocol work on gmail ?, can roundcube use gmail imap protocol ?, would it break leggs or bones ? Yes, roundcube can access gmail. This is the config I needed to put in roundcube's config file: $config['default_host'] = 'imaps://imap.gmail.com'; $config['default_port'] = 993; My mail server cannot connect to imap.gmail.com on port 143, so I had to change it to 993. I tested this by making a copy of my roundcube install on another URL and reconfiguring the copy. Thanks, Shawn
Re: modernizing dovecot.conf
On 2021-12-30 05:40, Laura Steynes wrote: Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only so you are just a gmail victim ? :=) I'll await someone more knowledgeable to answer my original questions I think knowledge ? would imap protocol work on gmail ?, can roundcube use gmail imap protocol ?, would it break leggs or bones ? if you waiting, start with a question with imho you still have not asked
Re: modernizing dovecot.conf
Because gmail is dumb. good mail client interfaces see reply-all with a mailing list as reply to list only I'll await someone more knowledgeable to answer my original questions I think On Thu, Dec 30, 2021 at 2:27 PM Benny Pedersen wrote: > On 2021-12-30 04:58, Laura Steynes wrote: > > That prints out what I have now, inside protcol sections, which > > differs from the config examples, so is of no use to my questions, > > thank you for trying anyway > > this is maillists, why did you reply privately aswell ?, more info ? > > HPNY all >
spf helo pass
would be nice to see added :=) talvi.dovecot.org txt "spfv1 a -all"
Re: modernizing dovecot.conf
On 2021-12-30 04:58, Laura Steynes wrote: That prints out what I have now, inside protcol sections, which differs from the config examples, so is of no use to my questions, thank you for trying anyway this is maillists, why did you reply privately aswell ?, more info ? HPNY all
Re: modernizing dovecot.conf
That prints out what I have now, inside protcol sections, which differs from the config examples, so is of no use to my questions, thank you for trying anyway On Thu, Dec 30, 2021 at 1:13 PM Benny Pedersen wrote: > On 2021-12-30 03:34, Laura Steynes wrote: > > easier to find options in one file, rather > > than trying to sift through 40 included files like I am looking at now > > :-) > > you dont have spare times > > doveconf -n > > no need to read more > > if something should change to the better, it would be better default > config, that could lead to less questions on why and how to get xxx to > work, currect is not that much helpfull for setup new things with unless > we all are developpers sadly, and now that dovecot is not enterprise > anymore there is less support there aswell :( >
Re: modernizing dovecot.conf
On 2021-12-30 03:34, Laura Steynes wrote: easier to find options in one file, rather than trying to sift through 40 included files like I am looking at now :-) you dont have spare times doveconf -n no need to read more if something should change to the better, it would be better default config, that could lead to less questions on why and how to get xxx to work, currect is not that much helpfull for setup new things with unless we all are developpers sadly, and now that dovecot is not enterprise anymore there is less support there aswell :(
modernizing dovecot.conf
Happy Holidays,
And if you like me are working throughout so more senior engineers get
their holidays, my condolences hah
Taking the time to bring our dovecot.conf into the 2021/22 era .since its
quiet time of year,
Do I read it right that where we have things like
service imap {
process_limit = 1024
executable = imap imap-postlogin
are not needed now ?
and process limit is a global option?
things like pop3/imap_client_workarounds = fooy
are now global options, not to be in protocol { } sections ?
I am reading the example conf files and see these outside the protocol
sections where they have in the past lived, this is what makes me think
they are now global and not needed in sub sections. but I may be missing
some linking going from file to file , we have forever updated our single
config file, just fixing whatever breaks when major versions break
something, easier to find options in one file, rather than trying to sift
through 40 included files like I am looking at now :-)
Re: Permission denied
On 2021-12-29 17:51, Ken Wright wrote: On Wed, 2021-12-29 at 18:34 +0200, Aki Tuomi wrote: > On 29/12/2021 18:09 Ken Wright wrote: > > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > Any further information available upon request! > > > > Maybe systemd is blocking it? > > > > If systemd unit has ProtectSystem=strict or ProtectSystem=full, > > try adding override.conf with > > > > [Service] > > ReadWritePaths=/var/mail > > I checked /etc/systemd but I can't find anything with ProtectSystem > uncommented. Am I looking in the wrong place? Try systemctl show dovecot | grep Protect Okay, I did this, and ProtectSystem=full was there. So I created override.conf in /etc/systemd as per the above and restarted Dovecot. The override.conf goes to /etc/systemd/system/dovecot.service.d/ to be included. Issue systemctl daemon-reload before restarting dovecot. systemctl cat dovecot.service shows you the content of the involved conf files No joy. Evolution is still begging for a password and Dovecot is still rejecting it. And yes, I've verified I'm using the correct password. -- Christian Kivalo
cumulative resource limit exceeded
Hi I’m running dovecot-2.3.15 and dovecot-pigeonhole-0.5.15 on FreeBSD 13 To day i suddenly get errors in my personal logfile (.dovecot.sieve.log) sieve: info: started log at Dec 29 20:26:42. .dovecot: error: cumulative resource usage limit exceeded. Is there anything I can do about this error? /mm signature.asc Description: Message signed with OpenPGP
Re: Permission denied
On Wed, 2021-12-29 at 18:34 +0200, Aki Tuomi wrote: > > > On 29/12/2021 18:09 Ken Wright wrote: > > > > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > > > Any further information available upon request! > > > > > > Maybe systemd is blocking it? > > > > > > If systemd unit has ProtectSystem=strict or ProtectSystem=full, > > > try adding override.conf with > > > > > > [Service] > > > ReadWritePaths=/var/mail > > > > I checked /etc/systemd but I can't find anything with ProtectSystem > > uncommented. Am I looking in the wrong place? > > Try > > systemctl show dovecot | grep Protect Okay, I did this, and ProtectSystem=full was there. So I created override.conf in /etc/systemd as per the above and restarted Dovecot. No joy. Evolution is still begging for a password and Dovecot is still rejecting it. And yes, I've verified I'm using the correct password.
Re: Permission denied
> On 29/12/2021 18:09 Ken Wright wrote: > > > On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > > > Any further information available upon request! > > > > Maybe systemd is blocking it? > > > > If systemd unit has ProtectSystem=strict or ProtectSystem=full, try > > adding override.conf with > > > > [Service] > > ReadWritePaths=/var/mail > > I checked /etc/systemd but I can't find anything with ProtectSystem > uncommented. Am I looking in the wrong place? Try systemctl show dovecot | grep Protect Aki
Re: Permission denied
On Wed, 2021-12-29 at 09:51 +0200, Aki Tuomi wrote: > > > On 29/12/2021 05:22 Ken Wright wrote: > > > > Any further information available upon request! > > Maybe systemd is blocking it? > > If systemd unit has ProtectSystem=strict or ProtectSystem=full, try > adding override.conf with > > [Service] > ReadWritePaths=/var/mail I checked /etc/systemd but I can't find anything with ProtectSystem uncommented. Am I looking in the wrong place?
Re: Panic: file mail-index-transaction-finish.c: line 185
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
> 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
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
Re: Panic: file mail-index-transaction-finish.c: line 185
> On 29/12/2021 11:20 tobiswo...@gmail.com wrote: > > > 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 Do you have multiple backends with concurrent access via e.g. nfs? Aki
Panic: file mail-index-transaction-finish.c: line 185
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
