Re: Crash in dovecot snippet when using imapc
Sorry, the provided patch link was wrong, it's already in 2.3.21, my bad. Anyways, it is still fixed in main, since it does not happen there. Aki > On 19/01/2024 09:13 EET Aki Tuomi via dovecot wrote: > > > Hi! > > I was able to reproduce this issue with 2.3.21, but it seems to have been > fixed in main. I think > https://github.com/dovecot/core/commit/1c1b77dbf9a548aac788efb76973ce2d0fa6c732.patch > will fix this. > > Aki > > > On 18/01/2024 22:51 EET John van der Kamp via dovecot > > wrote: > > > > > > Hello, > > > > > > I've found a crash in a very specific setup. A dovecot server with imapc > > connection needs to receive an email with no body contents for the intent > > of generating a preview/snippet. It crashes somewhere deep in the jungle of > > istream and snapshots. I've included a script which sets up the systems to > > reproduce the crash. > > > > > > I've tested this with several versions. 2.3.16 doesn't seem to be affected, > > but 2.3.20 and 2.3.21 are affect. > > > > > > For me it produces a traceback like this, using the ubuntu version from > > here: https://packages.ubuntu.com/noble/dovecot-core > > > > > > (gdb) bt > > #0 __pthread_kill_implementation (no_tid=0, signo=6, > > threadid=140530132887360) at ./nptl/pthread_kill.c:44 > > #1 __pthread_kill_internal (signo=6, threadid=140530132887360) at > > ./nptl/pthread_kill.c:78 > > #2 __GI___pthread_kill (threadid=140530132887360, signo=signo@entry=6) at > > ./nptl/pthread_kill.c:89 > > #3 0x7fcfb8842476 in __GI_raise (sig=sig@entry=6) at > > ../sysdeps/posix/raise.c:26 > > #4 0x7fcfb88287f3 in __GI_abort () at ./stdlib/abort.c:79 > > #5 0x7fcfb8b37fe5 in default_fatal_finish (status=0, > > type=LOG_TYPE_PANIC) at ../lib/failures.c:465 > > #6 fatal_handler_real (ctx=, format=, > > args=) at ../lib/failures.c:477 > > #7 0x7fcfb8be50d7 in i_internal_fatal_handler (ctx=, > > format=, args=) at ../lib/failures.c:879 > > #8 0x7fcfb8b37eea in i_panic (format=0x7fcfb8c29020 "file %s: line %d > > (%s): assertion failed: (%s)") at ../lib/failures.c:530 > > #9 0x7fcfb8b3387b in i_stream_header_filter_snapshot_free > > (_snapshot=) at ../lib-mail/istream-header-filter.c:663 > > #10 i_stream_header_filter_snapshot_free (_snapshot=0x55dabe297a60) at > > ../lib-mail/istream-header-filter.c:655 > > #11 0x7fcfb8bf25ac in i_stream_snapshot_free > > (_snapshot=_snapshot@entry=0x55dabe29b0d0) at ../lib/istream.c:253 > > #12 0x7fcfb8bf2654 in i_stream_unref (stream=0x7ffc16cc7fa0) at > > ../lib/istream.c:66 > > #13 0x7fcfb8d96baa in index_mail_write_body_snippet > > (mail=0x55dabe292058) at index/index-mail.c:1151 > > #14 0x7fcfb8d97e48 in index_mail_parse_bodystructure > > (mail=0x55dabe292058, field=MAIL_CACHE_BODY_SNIPPET) at > > index/index-mail.c:1551 > > #15 0x7fcfb8d97fe2 in index_mail_fetch_body_snippet > > (value_r=0x7ffc16cc8050, mail=0x55dabe292058) at index/index-mail.c:1602 > > #16 index_mail_get_special (_mail=0x55dabe292058, field=, > > value_r=0x7ffc16cc8050) at index/index-mail.c:1730 > > #17 0x7fcfb8d16ffe in mail_get_special (mail=mail@entry=0x55dabe292058, > > field=field@entry=MAIL_FETCH_BODY_SNIPPET, > > value_r=value_r@entry=0x7ffc16cc8050) > > at > > /home/ubuntu/dovecot/new/dovecot-2.3.21+dfsg1/src/lib-storage/mail.c:418 > > #18 0x55dabc52645c in fetch_snippet (ctx=0x55dabe26e050, > > mail=0x55dabe292058, preview=0x55dabe28f1f8) at > > ./src/imap/imap-fetch-body.c:615 > > #19 0x55dabc52b5cc in imap_fetch_more_int (ctx=0x55dabe26e050, > > cancel=false) at ./src/imap/imap-fetch.c:562 > > #20 0x55dabc52b8ad in imap_fetch_more (ctx=0x55dabe26e050, > > cmd=0x55dabe26de98) at ./src/imap/imap-fetch.c:617 > > #21 0x55dabc51fd07 in cmd_fetch (cmd=0x55dabe26de98) at > > ./src/imap/cmd-fetch.c:382 > > #22 0x55dabc528af4 in command_exec (cmd=0x55dabe26de98) at > > ./src/imap/imap-commands.c:201 > > #23 0x55dabc52e9e2 in client_command_input (cmd=) at > > ./src/imap/imap-client.c:1237 > > #24 0x55dabc52ea96 in client_command_input (cmd=) at > > ./src/imap/imap-client.c:1307 > > #25 0x55dabc52eeed in client_handle_next_command > > (remove_io_r=, client=0x55dabe26d2c8) at > > ./src/imap/imap-client.c:1349 > > #26 client_handle_input (client=0x55dabe26d2c8) at > > ./src/imap/imap-client.c:1363 > > #27 0x55dabc52f2c4 in client_input (client=0x55dabe26d2c8) at > > ./src/imap/imap-client.c:1407 > > #28 0x7fcfb8bfe27d in io_loop_call_io (io=0x55dabe26e660) at > > ../lib/ioloop.c:737 > > #29 0x7fcfb8bff81a in io_loop_handler_run_internal > > (ioloop=0x55dabe243fd0) at ../lib/ioloop-epoll.c:222 > > #30 0x7fcfb8bff8d4 in io_loop_handler_run (ioloop=0x55dabe243fd0) at > > ../lib/ioloop.c:789 > > #31 0x7fcfb8bffa90 in io_loop_run (ioloop=0x55dabe243fd0) at > > ../lib/ioloop.c:762 > > #32 0x7fcfb8b6ce57 in master_service_run (service=0x55dabe243e20, > >
Re: Crash in dovecot snippet when using imapc
Hi! I was able to reproduce this issue with 2.3.21, but it seems to have been fixed in main. I think https://github.com/dovecot/core/commit/1c1b77dbf9a548aac788efb76973ce2d0fa6c732.patch will fix this. Aki > On 18/01/2024 22:51 EET John van der Kamp via dovecot > wrote: > > > Hello, > > > I've found a crash in a very specific setup. A dovecot server with imapc > connection needs to receive an email with no body contents for the intent of > generating a preview/snippet. It crashes somewhere deep in the jungle of > istream and snapshots. I've included a script which sets up the systems to > reproduce the crash. > > > I've tested this with several versions. 2.3.16 doesn't seem to be affected, > but 2.3.20 and 2.3.21 are affect. > > > For me it produces a traceback like this, using the ubuntu version from here: > https://packages.ubuntu.com/noble/dovecot-core > > > (gdb) bt > #0 __pthread_kill_implementation (no_tid=0, signo=6, > threadid=140530132887360) at ./nptl/pthread_kill.c:44 > #1 __pthread_kill_internal (signo=6, threadid=140530132887360) at > ./nptl/pthread_kill.c:78 > #2 __GI___pthread_kill (threadid=140530132887360, signo=signo@entry=6) at > ./nptl/pthread_kill.c:89 > #3 0x7fcfb8842476 in __GI_raise (sig=sig@entry=6) at > ../sysdeps/posix/raise.c:26 > #4 0x7fcfb88287f3 in __GI_abort () at ./stdlib/abort.c:79 > #5 0x7fcfb8b37fe5 in default_fatal_finish (status=0, > type=LOG_TYPE_PANIC) at ../lib/failures.c:465 > #6 fatal_handler_real (ctx=, format=, > args=) at ../lib/failures.c:477 > #7 0x7fcfb8be50d7 in i_internal_fatal_handler (ctx=, > format=, args=) at ../lib/failures.c:879 > #8 0x7fcfb8b37eea in i_panic (format=0x7fcfb8c29020 "file %s: line %d > (%s): assertion failed: (%s)") at ../lib/failures.c:530 > #9 0x7fcfb8b3387b in i_stream_header_filter_snapshot_free > (_snapshot=) at ../lib-mail/istream-header-filter.c:663 > #10 i_stream_header_filter_snapshot_free (_snapshot=0x55dabe297a60) at > ../lib-mail/istream-header-filter.c:655 > #11 0x7fcfb8bf25ac in i_stream_snapshot_free > (_snapshot=_snapshot@entry=0x55dabe29b0d0) at ../lib/istream.c:253 > #12 0x7fcfb8bf2654 in i_stream_unref (stream=0x7ffc16cc7fa0) at > ../lib/istream.c:66 > #13 0x7fcfb8d96baa in index_mail_write_body_snippet (mail=0x55dabe292058) > at index/index-mail.c:1151 > #14 0x7fcfb8d97e48 in index_mail_parse_bodystructure > (mail=0x55dabe292058, field=MAIL_CACHE_BODY_SNIPPET) at > index/index-mail.c:1551 > #15 0x7fcfb8d97fe2 in index_mail_fetch_body_snippet > (value_r=0x7ffc16cc8050, mail=0x55dabe292058) at index/index-mail.c:1602 > #16 index_mail_get_special (_mail=0x55dabe292058, field=, > value_r=0x7ffc16cc8050) at index/index-mail.c:1730 > #17 0x7fcfb8d16ffe in mail_get_special (mail=mail@entry=0x55dabe292058, > field=field@entry=MAIL_FETCH_BODY_SNIPPET, > value_r=value_r@entry=0x7ffc16cc8050) > at > /home/ubuntu/dovecot/new/dovecot-2.3.21+dfsg1/src/lib-storage/mail.c:418 > #18 0x55dabc52645c in fetch_snippet (ctx=0x55dabe26e050, > mail=0x55dabe292058, preview=0x55dabe28f1f8) at > ./src/imap/imap-fetch-body.c:615 > #19 0x55dabc52b5cc in imap_fetch_more_int (ctx=0x55dabe26e050, > cancel=false) at ./src/imap/imap-fetch.c:562 > #20 0x55dabc52b8ad in imap_fetch_more (ctx=0x55dabe26e050, > cmd=0x55dabe26de98) at ./src/imap/imap-fetch.c:617 > #21 0x55dabc51fd07 in cmd_fetch (cmd=0x55dabe26de98) at > ./src/imap/cmd-fetch.c:382 > #22 0x55dabc528af4 in command_exec (cmd=0x55dabe26de98) at > ./src/imap/imap-commands.c:201 > #23 0x55dabc52e9e2 in client_command_input (cmd=) at > ./src/imap/imap-client.c:1237 > #24 0x55dabc52ea96 in client_command_input (cmd=) at > ./src/imap/imap-client.c:1307 > #25 0x55dabc52eeed in client_handle_next_command (remove_io_r= pointer>, client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1349 > #26 client_handle_input (client=0x55dabe26d2c8) at > ./src/imap/imap-client.c:1363 > #27 0x55dabc52f2c4 in client_input (client=0x55dabe26d2c8) at > ./src/imap/imap-client.c:1407 > #28 0x7fcfb8bfe27d in io_loop_call_io (io=0x55dabe26e660) at > ../lib/ioloop.c:737 > #29 0x7fcfb8bff81a in io_loop_handler_run_internal > (ioloop=0x55dabe243fd0) at ../lib/ioloop-epoll.c:222 > #30 0x7fcfb8bff8d4 in io_loop_handler_run (ioloop=0x55dabe243fd0) at > ../lib/ioloop.c:789 > #31 0x7fcfb8bffa90 in io_loop_run (ioloop=0x55dabe243fd0) at > ../lib/ioloop.c:762 > #32 0x7fcfb8b6ce57 in master_service_run (service=0x55dabe243e20, > callback=callback@entry=0x55dabc533210 ) at > ../lib-master/master-service.c:878 > #33 0x55dabc51ad37 in main (argc=, argv=) > at ./src/imap/main.c:575 > > > John > > > > Hello, > > I've found a crash in a very specific setup. A dovecot server with imapc > connection needs to receive an email with no body contents for the intent of > generating a preview/snippet. It crashes somewhere deep in the jungle of > istream
Re: Documentation flaw: man-page link.
> On 18/01/2024 15:34 EET Ralph Corderoy wrote: > > > Hi, > > https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/ ends with > > The man-pages also contain good descriptions of doveadm commands. > Man-pages can be accessed online at e.g. > https://wiki.dovecot.org/Tools/Doveadm > > That wiki page says > > Our primary documentation is now at https://doc.dovecot.org, please > update your links. > > But I was at https://doc.dovecot.org to start with and there is no > obvious mention of man pages there. > > This needs tidying up to avoid the loop and ideally provide man pages. > > -- > Cheers, Ralph. Hi! Thanks for pointing this out, we are working on fixing the links. Aki ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Crash in dovecot snippet when using imapc
Hello, I've found a crash in a very specific setup. A dovecot server with imapc connection needs to receive an email with no body contents for the intent of generating a preview/snippet. It crashes somewhere deep in the jungle of istream and snapshots. I've included a script which sets up the systems to reproduce the crash. I've tested this with several versions. 2.3.16 doesn't seem to be affected, but 2.3.20 and 2.3.21 are affect. For me it produces a traceback like this, using the ubuntu version from here: https://packages.ubuntu.com/noble/dovecot-core (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140530132887360) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140530132887360) at ./nptl/ pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140530132887360, signo=signo@entry=6) at ./ nptl/pthread_kill.c:89 #3 0x7fcfb8842476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/ raise.c:26 #4 0x7fcfb88287f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x7fcfb8b37fe5 in default_fatal_finish (status=0, type=LOG_TYPE_PANIC) at ../lib/failures.c:465 #6 fatal_handler_real (ctx=, format=, args=) at ../lib/failures.c:477 #7 0x7fcfb8be50d7 in i_internal_fatal_handler (ctx=, format=, args=) at ../lib/failures.c:879 #8 0x7fcfb8b37eea in i_panic (format=0x7fcfb8c29020 "file %s: line %d (%s): assertion failed: (%s)") at ../lib/failures.c:530 #9 0x7fcfb8b3387b in i_stream_header_filter_snapshot_free (_snapshot=) at ../lib-mail/istream-header-filter.c:663 #10 i_stream_header_filter_snapshot_free (_snapshot=0x55dabe297a60) at ../lib- mail/istream-header-filter.c:655 #11 0x7fcfb8bf25ac in i_stream_snapshot_free (_snapshot=_snapshot@entry=0x55dabe29b0d0) at ../lib/istream.c:253 #12 0x7fcfb8bf2654 in i_stream_unref (stream=0x7ffc16cc7fa0) at ../lib/ istream.c:66 #13 0x7fcfb8d96baa in index_mail_write_body_snippet (mail=0x55dabe292058) at index/index-mail.c:1151 #14 0x7fcfb8d97e48 in index_mail_parse_bodystructure (mail=0x55dabe292058, field=MAIL_CACHE_BODY_SNIPPET) at index/index-mail.c:1551 #15 0x7fcfb8d97fe2 in index_mail_fetch_body_snippet (value_r=0x7ffc16cc8050, mail=0x55dabe292058) at index/index-mail.c:1602 #16 index_mail_get_special (_mail=0x55dabe292058, field=, value_r=0x7ffc16cc8050) at index/index-mail.c:1730 #17 0x7fcfb8d16ffe in mail_get_special (mail=mail@entry=0x55dabe292058, field=field@entry=MAIL_FETCH_BODY_SNIPPET, value_r=value_r@entry=0x7ffc16cc8050) at /home/ubuntu/dovecot/new/dovecot-2.3.21+dfsg1/src/lib-storage/mail.c:418 #18 0x55dabc52645c in fetch_snippet (ctx=0x55dabe26e050, mail=0x55dabe292058, preview=0x55dabe28f1f8) at ./src/imap/imap-fetch-body.c: 615 #19 0x55dabc52b5cc in imap_fetch_more_int (ctx=0x55dabe26e050, cancel=false) at ./src/imap/imap-fetch.c:562 #20 0x55dabc52b8ad in imap_fetch_more (ctx=0x55dabe26e050, cmd=0x55dabe26de98) at ./src/imap/imap-fetch.c:617 #21 0x55dabc51fd07 in cmd_fetch (cmd=0x55dabe26de98) at ./src/imap/cmd- fetch.c:382 #22 0x55dabc528af4 in command_exec (cmd=0x55dabe26de98) at ./src/imap/imap- commands.c:201 #23 0x55dabc52e9e2 in client_command_input (cmd=) at ./src/ imap/imap-client.c:1237 #24 0x55dabc52ea96 in client_command_input (cmd=) at ./src/ imap/imap-client.c:1307 #25 0x55dabc52eeed in client_handle_next_command (remove_io_r=, client=0x55dabe26d2c8) at ./src/imap/imap-client.c:1349 #26 client_handle_input (client=0x55dabe26d2c8) at ./src/imap/imap-client.c: 1363 #27 0x55dabc52f2c4 in client_input (client=0x55dabe26d2c8) at ./src/imap/ imap-client.c:1407 #28 0x7fcfb8bfe27d in io_loop_call_io (io=0x55dabe26e660) at ../lib/ ioloop.c:737 #29 0x7fcfb8bff81a in io_loop_handler_run_internal (ioloop=0x55dabe243fd0) at ../lib/ioloop-epoll.c:222 #30 0x7fcfb8bff8d4 in io_loop_handler_run (ioloop=0x55dabe243fd0) at ../ lib/ioloop.c:789 #31 0x7fcfb8bffa90 in io_loop_run (ioloop=0x55dabe243fd0) at ../lib/ ioloop.c:762 #32 0x7fcfb8b6ce57 in master_service_run (service=0x55dabe243e20, callback=callback@entry=0x55dabc533210 ) at ../lib-master/ master-service.c:878 #33 0x55dabc51ad37 in main (argc=, argv=) at ./src/imap/main.c:575 John imapc-snippet-crash.sh Description: application/shellscript ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Documentation flaw: man-page link.
Hi, https://doc.dovecot.org/admin_manual/doveadm_mailbox_commands/ ends with The man-pages also contain good descriptions of doveadm commands. Man-pages can be accessed online at e.g. https://wiki.dovecot.org/Tools/Doveadm That wiki page says Our primary documentation is now at https://doc.dovecot.org, please update your links. But I was at https://doc.dovecot.org to start with and there is no obvious mention of man pages there. This needs tidying up to avoid the loop and ideally provide man pages. -- Cheers, Ralph. ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: post-login scripting
I also wanted to ask if it's possible to add the local server name so I can
use one database for all systems?
I suppose there's a chance there could be issues with namespace conflicts,
but this would make it much easier for me.
Not sure how you are tracking your users, in my setup each user is the full
email address with domain. (u...@example.com) This way when it saves the time
stamp it's associated with the username/email which is unique. My dictionary
looks like this...
connect = host=/var/lib/mysql/mysql.sock dbname=mailservice
map {
pattern = shared/last-login/$user
table = lastEmailCheck
value_field = last
value_type = uint
fields {
email = $user
}
}
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Re: What is the difference between BEFORE, SENTBEFORE, and SAVEDBEFORE?
On Thu, Jan 18, 2024 at 6:42 PM Joseph Tam wrote: > If you dump the above values e.g. > > doveadm fetch -ftab -A 'mailbox date.received' mailbox Trash BEFORE 90d Correction: if what I suspect is true, this won't show you anything as all your messages will be younger than 90d. Instead, remove the "BEFORE 90d" condition and dump all values. Joseph Tam ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: What is the difference between BEFORE, SENTBEFORE, and SAVEDBEFORE?
From: Paul Pace > BEFORE date specification > Matches messages with an internal date before date > specification. > > SENTBEFORE date specification > Matches messages with a Date: header before date specification. > > SAVEDBEFORE date specification > Matches messages, which were saved before date specification. > > I am creating a cron job to purge old messages in Trash or Spam folders, > but I discovered using doveadm search queries using savedbefore that > somehow no message in any of the folders shows up with queries starting > at 5d, even though there are much older messages. I don't know exactly the answer to your query, but the semantics of each term may not be the problem. I had this exact problem a decade ago with my own trash purging script. If you dump the above values e.g. doveadm fetch -ftab -A 'mailbox date.received' mailbox Trash BEFORE 90d you may find that many of them have the same value, and what's more, the time coincides with the first time you queried for that value (i.e. when you ran the above doveadm fetch). I think these fields may not have cached values before you ask for it, then it gets instantiated the current timestamp when you do. If you do a fetch every day, you'll eventually reach 90d, and it will work forever more (+/- 1 day). Perhaps adding those fields into these settings is a more direct and better solution: https://doc.dovecot.org/configuration_manual/mail_cache_settings/ Joseph Tam ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Here it is. On Thu, Jan 18, 2024 at 8:21 PM Joe Acquisto wrote: Sure. Thanks. I can post mine here, I suppose in a bit joe a. On 1/18/24 20:29, Larry Rosenman wrote: I could send your a dovecot -n of my setup, which works with RoundCube, if you want. On Thu, Jan 18, 2024 at 6:46 PM Joe Acquisto wrote: They look fine to me, questions remails if many of the items commented out in the default config need to be enabled and if those might prevent the managesieve server from "grabbing" the port. Surely there should be errors logged somewhere? On 1/18/24 19:11, Larry Rosenman wrote: You may wish to double-check that file (all of it) and 90-sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20- managesieve.conf? > notably the below top of that file. > ❯ more 20-managesieve.conf > ## > ## ManageSieve specific settings > ## > > # Uncomment to enable managesieve protocol: > protocols = $protocols sieve > > # Service definitions > > > On Thu, Jan 18, 2024 at 5: 30 PM Joe Acquisto > wrote: > Trying to connect to managesieve server configured to port 4190. No > go. > > Roundcube is configured (thunderbird apparently having nothing > current), > but selecting "Add Filter" (new since re- configured for managesieve) > produces "unable to connect to server". > > Port 4190 does not seem to answer or be "bound" to anything. Telnet > to > 4190 produces "connection refused". > > A "one box" solution. > > If I had to guess, I would guess, operator error. Otherwise, > things > are looking up. But, I remember a movie that said never to do that . > . . > > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org > > > -- > Larry Rosenman http://www.lerctr.org/ ~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > > ___ > dovecot mailing list - - dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list - - dovecot@dovecot.org To unsubscribe send an email
Re: managesieve server not answering?
Sure. Thanks. I can post mine here, I suppose in a bit joe a. On 1/18/24 20:29, Larry Rosenman wrote: I could send your a dovecot -n of my setup, which works with RoundCube, if you want. On Thu, Jan 18, 2024 at 6:46 PM Joe Acquisto wrote: They look fine to me, questions remails if many of the items commented out in the default config need to be enabled and if those might prevent the managesieve server from "grabbing" the port. Surely there should be errors logged somewhere? On 1/18/24 19:11, Larry Rosenman wrote: You may wish to double-check that file (all of it) and 90- sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20-managesieve.conf? > notably the below top of that file. > ❯ more 20-managesieve.conf > ## > ## ManageSieve specific settings > ## > > # Uncomment to enable managesieve protocol: > protocols = $protocols sieve > > # Service definitions > > > On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto > wrote: > Trying to connect to managesieve server configured to port 4190. No > go. > > Roundcube is configured (thunderbird apparently having nothing > current), > but selecting "Add Filter" (new since re- configured for managesieve) > produces "unable to connect to server". > > Port 4190 does not seem to answer or be "bound" to anything. Telnet > to > 4190 produces "connection refused". > > A "one box" solution. > > If I had to guess, I would guess, operator error. Otherwise, > things > are looking up. But, I remember a movie that said never to do that . > . . > > > ___ > dovecot mailing list - - dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org > > > -- > Larry Rosenman http:// www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665- 2106 > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot- le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/ ~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
I could send your a dovecot -n of my setup, which works with RoundCube, if you want. On Thu, Jan 18, 2024 at 6:46 PM Joe Acquisto wrote: They look fine to me, questions remails if many of the items commented out in the default config need to be enabled and if those might prevent the managesieve server from "grabbing" the port. Surely there should be errors logged somewhere? On 1/18/24 19:11, Larry Rosenman wrote: You may wish to double-check that file (all of it) and 90- sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20-managesieve.conf? > notably the below top of that file. > ❯ more 20-managesieve.conf > ## > ## ManageSieve specific settings > ## > > # Uncomment to enable managesieve protocol: > protocols = $protocols sieve > > # Service definitions > > > On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto > wrote: > Trying to connect to managesieve server configured to port 4190. No > go. > > Roundcube is configured (thunderbird apparently having nothing > current), > but selecting "Add Filter" (new since re- configured for managesieve) > produces "unable to connect to server". > > Port 4190 does not seem to answer or be "bound" to anything. Telnet > to > 4190 produces "connection refused". > > A "one box" solution. > > If I had to guess, I would guess, operator error. Otherwise, > things > are looking up. But, I remember a movie that said never to do that . > . . > > > ___ > dovecot mailing list - - dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org > > > -- > Larry Rosenman http:// www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665- 2106 > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot- le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot- le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/ ~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
What is the difference between BEFORE, SENTBEFORE, and SAVEDBEFORE?
In doveadm-search-query(7), it states: BEFORE date specification Matches messages with an internal date before date specification. SENTBEFORE date specification Matches messages with a Date: header before date specification. SAVEDBEFORE date specification Matches messages, which were saved before date specification. I am creating a cron job to purge old messages in Trash or Spam folders, but I discovered using doveadm search queries using savedbefore that somehow no message in any of the folders shows up with queries starting at 5d, even though there are much older messages. doveadm search mailbox Trash before 90d -A | wc -l 277 doveadm search mailbox Trash sentbefore 90d -A | wc -l 277 doveadm search mailbox Trash savedbefore 90d -A | wc -l 0 For my purpose, I'm not clear on the differences between the different queries and am wondering what will be the better option. Thank you, Paul ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
They look fine to me, questions remails if many of the items commented out in the default config need to be enabled and if those might prevent the managesieve server from "grabbing" the port. Surely there should be errors logged somewhere? On 1/18/24 19:11, Larry Rosenman wrote: You may wish to double-check that file (all of it) and 90-sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20-managesieve.conf? > notably the below top of that file. > ❯ more 20-managesieve.conf > ## > ## ManageSieve specific settings > ## > > # Uncomment to enable managesieve protocol: > protocols = $protocols sieve > > # Service definitions > > > On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto > wrote: > Trying to connect to managesieve server configured to port 4190. No > go. > > Roundcube is configured (thunderbird apparently having nothing > current), > but selecting "Add Filter" (new since re-configured for managesieve) > produces "unable to connect to server". > > Port 4190 does not seem to answer or be "bound" to anything. Telnet > to > 4190 produces "connection refused". > > A "one box" solution. > > If I had to guess, I would guess, operator error. Otherwise, > things > are looking up. But, I remember a movie that said never to do that . > . . > > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: post-login scripting
Hi, > I'm trying to determine the last login time for my IMAP users. There is already a built in plugin that does this without needing to use scripting. You can use it to save a timestamp to a database. https://doc.dovecot.org/settings/plugin/last-login- plugin/ https://doc.dovecot.org/configuration_manual/ lastlogin_plugin/ That's very helpful, thanks. The only trouble I had was that my password had a pound sign in it and apparently it was parsed as a comment: Jan 18 18:53:28 xavier dovecot[3549186]: dict(3552926): Warning: Configuration file /etc/dovecot/dovecot-dict-sql.conf.ext line 1: Ambiguous '#' character in line, treating it as comment. Add a space before it to remove this warning. I also wanted to ask if it's possible to add the local server name so I can use one database for all systems? I suppose there's a chance there could be issues with namespace conflicts, but this would make it much easier for me. Thanks so much. ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: post-login scripting
Hi,
When I put the following in my dovecot.conf instead of conf.d/
10-
auth.conf, it
core dumps. I thought local changes should be made in
dovecot.conf?
service imap-login {
executable = imap imap-postlogin
inet_listener imap {
port = 0
}
inet_listener imaps {
port = 993
}
process_min_avail = 6
service_count = 0
vsz_limit = 512 M
}
service imap-postlogin {
executable = script-login /usr/local/bin/postlogin.sh
user = $default_internal_user
}
service pop3-login {
inet_listener pop3 {
port = 0
}
inet_listener pop3s {
port = 995
}
}
Hi Alex
I notice you didn't define the listner socket. You're missing this
inside your
imap-postlogin service definition:
unix_listener imap-postlogin {
}
Okay, thanks. Although I have it working with the last_login plugin now, I'm
still interested in figuring out what went wrong with postlogin and how I can
use it for other things as well.
It no longer core dumps, but it also doesn't touch the ~/.last_login file in
the user's home directory either.
How can I troubleshoot this further? I thought I would see a postlogin socket
after adding the listener line, but I don't see anything with lsof.
Other ideas greatly appreciated.
___
dovecot mailing list -- dovecot@dovecot.org
To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
You may wish to double-check that file (all of it) and 90-sieve.conf as well On Thu, Jan 18, 2024 at 6:08 PM Joe Acquisto wrote: Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: > Did you look at conf.d/20-managesieve.conf? > notably the below top of that file. > ❯ more 20-managesieve.conf > ## > ## ManageSieve specific settings > ## > > # Uncomment to enable managesieve protocol: > protocols = $protocols sieve > > # Service definitions > > > On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto > wrote: > Trying to connect to managesieve server configured to port 4190. No > go. > > Roundcube is configured (thunderbird apparently having nothing > current), > but selecting "Add Filter" (new since re-configured for managesieve) > produces "unable to connect to server". > > Port 4190 does not seem to answer or be "bound" to anything. Telnet > to > 4190 produces "connection refused". > > A "one box" solution. > > If I had to guess, I would guess, operator error. Otherwise, > things > are looking up. But, I remember a movie that said never to do that . > . . > > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org > > > -- > Larry Rosenman http://www.lerctr.org/~ler > Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com > US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 > > ___ > dovecot mailing list -- dovecot@dovecot.org > To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Most of the items below that, number of connections, process limit, etc, are commented out. I presumed there would be defaults used if not specified. Is that correct, or must I un-comment them. No examples showed such un commenting. joe a On 1/18/24 18:33, Larry Rosenman wrote: Did you look at conf.d/20-managesieve.conf? notably the below top of that file. ❯ more 20-managesieve.conf ## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Yes. It is uncommented as shown there below. Service was restarted. joe a On 1/18/24 18:33, Larry Rosenman wrote: Did you look at conf.d/20-managesieve.conf? notably the below top of that file. ❯ more 20-managesieve.conf ## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: post-login scripting
> I'm trying to determine the last login time for my IMAP users. There is already a built in plugin that does this without needing to use scripting. You can use it to save a timestamp to a database. https://doc.dovecot.org/settings/plugin/last-login-plugin/ https://doc.dovecot.org/configuration_manual/lastlogin_plugin/ That's very helpful, thanks. The only trouble I had was that my password had a pound sign in it and apparently it was parsed as a comment: Jan 18 18:53:28 xavier dovecot[3549186]: dict(3552926): Warning: Configuration file /etc/dovecot/dovecot-dict-sql.conf.ext line 1: Ambiguous '#' character in line, treating it as comment. Add a space before it to remove this warning. Thanks so much. ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: managesieve server not answering?
Did you look at conf.d/20-managesieve.conf? notably the below top of that file. ❯ more 20-managesieve.conf ## ## ManageSieve specific settings ## # Uncomment to enable managesieve protocol: protocols = $protocols sieve # Service definitions On Thu, Jan 18, 2024 at 5:30 PM Joe Acquisto wrote: Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org -- Larry Rosenman http://www.lerctr.org/~ler Phone: +1 214-642-9640 (c) E-Mail: larry...@gmail.com US Mail: 5708 Sabbia Dr, Round Rock, TX 78665-2106 ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
managesieve server not answering?
Trying to connect to managesieve server configured to port 4190. No go. Roundcube is configured (thunderbird apparently having nothing current), but selecting "Add Filter" (new since re-configured for managesieve) produces "unable to connect to server". Port 4190 does not seem to answer or be "bound" to anything. Telnet to 4190 produces "connection refused". A "one box" solution. If I had to guess, I would guess, operator error. Otherwise, things are looking up. But, I remember a movie that said never to do that . . . ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
CRe: testing sieve/pigeonhole, auth errors
On 1/18/24 15:34, Joe Acquisto wrote: On 1/15/24 15:13, Joe Acquisto wrote: A small SOHO system, of installed perhaps a year. Seems to be working and wished to add pigeonhole/sieve. Back to attempting to configure this. No doubt simple for one more familiar with dovecot and sundry stuff. One thing I find unclear is how to set the sieve script location. Appears to depend on other choices made earlier. In this snippet of proposed /etc/dovecot/conf.d/90-sieve.conf, gleaned from various places on the web, seems appropriate for my setup. But, the %d (domain) and %d (user name) leave me uncertain. The mail locations chosen earlier contain "u...@somedomain.com" in the path. Don't see how the propose string accounts for that. Also unclear is how the user script storage locations get created. A manual administrator task, or created "on the fly" by the system, once properly configured? And, is it required to have a "default" script and location even if none is desired? # sieve = file:~/sieve;active=~/.dovecot.sieve sieve=file:/home/vmail/%d/%n/sieve/scripts;active=/home/vmail/%d/%n/ sieve/.dovecot.sieve sieve_user_log=file:/home/vmail/%d/%n/sieve/scripts;active=/home/vmail/%d/%n/ sieve/sieve_error.log Appears that %u should replace /%d/%n in my case? ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: testing sieve/pigeonhole, auth errors
On 1/15/24 15:13, Joe Acquisto wrote: A small SOHO system, of installed perhaps a year. Seems to be working and wished to add pigeonhole/sieve. Back to attempting to configure this. No doubt simple for one more familiar with dovecot and sundry stuff. One thing I find unclear is how to set the sieve script location. Appears to depend on other choices made earlier. In this snippet of proposed /etc/dovecot/conf.d/90-sieve.conf, gleaned from various places on the web, seems appropriate for my setup. But, the %d (domain) and %d (user name) leave me uncertain. The mail locations chosen earlier contain "u...@somedomain.com" in the path. Don't see how the propose string accounts for that. Also unclear is how the user script storage locations get created. A manual administrator task, or created "on the fly" by the system, once properly configured? And, is it required to have a "default" script and location even if none is desired? # sieve = file:~/sieve;active=~/.dovecot.sieve sieve=file:/home/vmail/%d/%n/sieve/scripts;active=/home/vmail/%d/%n/ sieve/.dovecot.sieve sieve_user_log=file:/home/vmail/%d/%n/sieve/scripts;active=/home/vmail/%d/%n/ sieve/sieve_error.log ___ dovecot mailing list -- dovecot@dovecot.org To unsubscribe send an email to dovecot-le...@dovecot.org
Re: [EXT] Re: Dovecot imap-hibernate errors in 2.3.21
Can you send `doveconf -n`? I think it might be related to the separete user accounts somehow. Aki > On 18/01/2024 09:45 EET Lucas Rolff wrote: > > > SELinux runs in permissive mode on the system (so doesn't take action, and no > violations are logged either), the OS specifically is Oracle Linux 8.9, the > only main thing that differs from RHEL or eg rocky/almalinux is I use the > newer oracle kernel they release, but shouldn't have any effect > > > The only "special" thing being that mail users are isolated on their own > Linux user (a domain will result in a local Linux user being created), but > that's about it. > There's nothing with eg virtualized file systems or anything like that, that > would result in per user mount points as well > > > Sent from Outlook for iOS (https://aka.ms/o0ukef) > -- > From: Aki Tuomi > Sent: Thursday, January 18, 2024 8:37:07 AM > To: Lucas Rolff ; dovecot@dovecot.org > > Subject: Re: Dovecot imap-hibernate errors in 2.3.21 > Did you check if maybe selinux is interfering here? I tested the 2.3.21-CE in > a RHEL7 VM and hibernation seems to work there. > > Aki > > > On 17/01/2024 22:51 EET lu...@lucasrolff.com wrote: > > > > > > Thanks for your reply Aki! > > > > It doesn't seem to contain much more information sadly that points towards > anything related to hibernate itself. > > "Debug: open(/proc/self/io) failed: Permission denied" being the main > "thing" that seems a bit odd, but that also happens under 2.3.20 as well by > the looks of it: > > > > ``` > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: imap-login: Login: > user=, method=PLAIN, rip=193.36.xx.xx, > lip=176.9.151.xxx, mpid=3631534, TLS, session= > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Loading modules > from directory: /usr/lib64/dovecot > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib10_quota_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib11_imap_quota_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib20_fts_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib20_quota_clone_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib20_zlib_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Module loaded: > /usr/lib64/dovecot/lib21_fts_solr_plugin.so > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Added userdb > setting: mail=mdbox:~/mail/example.com/customer/ > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Added userdb > setting: plugin/quota_rule=*:bytes=10240M > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Effective > uid=1098, gid=1098, home=/home/username/ > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Quota root: > name=User quota backend=count args= > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Quota rule: > root=User quota mailbox=* bytes=10737418240 messages=0 > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Quota grace: > root=User quota bytes=1073741824 (10%) > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: dict(proxy): > dict created (uri=proxy::sqlquota, base_dir=/run/dovecot) > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: > open(/proc/self/io) failed: Permission denied > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Namespace > inbox: type=private, prefix=, sep=, inbox=yes, hidden=no, list=yes, > subscriptions=yes location=mdbox:~/mail/example.com/customer/ > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: fs: > root=/home/username//mail/example.com/customer, index=, indexpvt=, control=, > inbox=, alt= > > Jan 17 20:42:16 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: quota: > quota_over_flag check: quota_over_script unset - skipping > > Jan 17 20:42:17 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Mailbox INBOX: > Mailbox opened > > Jan 17 20:42:17 de-mail01 dovecot[3631433]: > imap(custo...@example.com)<3631534>: Debug: Mailbox INBOX: > Mailbox opened > > Jan 17 20:42:49 de-mail01 dovecot[3631433]:
