Re: Bug report: invalid \HasNoChildren in response when asterisk is used in the name

It appears to be fixed. From NEWS   - acl: When plugin was loaded \HasChildren and \HasNoChildren flags    were calculated incorrectly for mailboxes containing '*' and '%'    in their names.   Aki On 18/04/2024 16:15 EEST Merijn Schering via dovecot wrote:     Sorry, I

Re: Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Sorry, I only have access to a 2.3.19 dovecot because it's the debian bookworm included package. Has this bug recently been fixed? Best regards, Merijn Schering Intermesh https://www.group-office.com https://twitter.com/GroupOffice Op Maandag, 15-04-2024 om 20:39 schreef Aki Tuomi: Did

Re: Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Did you try with 2.3.21 which is the latest? Packages are available at https:// repo.dovecot.org/   Aki On 15/04/2024 14:36 EEST Merijn Schering via dovecot wrote:     Hi,     This problem still exists in v2.3.19.1 (9b53102964). I hope it can be fixed

Re: Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Hi, This problem still exists in v2.3.19.1 (9b53102964). I hope it can be fixed some day. Best regards, Merijn Schering Op Dinsdag, 10-11-2020 om 12:28 schreef Merijn Schering (Intermesh): Hi, I'm using dovecot 2.3.4.1 (f79e8e7e4). I have created a folder called "Test with *".  Now

Re: bug report: lmtp fails on root-squashed NFS filesystem

> On 25/11/2021 01:29 EET Anne Bennett wrote: > > > Hello Aki. > > >> I patched "src/lib-storage/index/mbox/mbox-storage.c" and > >> "src/lib-storage/index/maildir/maildir-storage.c" to replace > >> calls to "access()" with calls to "euidaccess()", and now mail > >> delivery (to mboxes) works

Re: bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

> On 24/05/2023 17:23 EEST Moritz Orbach via dovecot > wrote: > > > Hi Aki, > > I'm willing to spend some time on this. Is there something more I could > do to help find the cause? > > Best regards, > Moritz > > -- I would need some way to reproduce this, as the crash happens way too

Re: bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

Hi Aki, I'm willing to spend some time on this. Is there something more I could do to help find the cause? Best regards, Moritz -- [schlittermann – internet & unix support ] [supp...@schlittermann.de | https://schlittermann.de/ ] [Tel(Fax): +49 351 802998-1

Re: bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

Hi Aki, > Do you have `noreplicate` used anywhere? It seems this could > potentially cause the crash. Yes, noreplicate was set. But removing it (*) doesn't change anything. The stack trace is identical. *) - removed default_fields = noreplicate:protected=true in conf.d/auth-system.conf.ext -

Re: bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

> On 17/05/2023 09:56 EEST Moritz Orbach via dovecot > wrote: > > > Am Di, 16.05.2023 20:10 Uhr schrieb Aki Tuomi via dovecot: > > > On 16/05/2023 16:24 EEST Moritz Orbach via dovecot > > > wrote: > > > #6 0x7fd5ac89b08e in fd_set_nonblock (fd=-1, nonblock=true) at > > >

Re: bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

> On 16/05/2023 16:24 EEST Moritz Orbach via dovecot > wrote: > > > Hi all, > > Our Dovecot replication crashes because an assertion in > dovecot-core/src/lib/fd-util.c fails: > > #6 0x7fd5ac89b08e in fd_set_nonblock (fd=-1, nonblock=true) at > fd-util.c:102 > 102

bug report: fd-util.c: line 102 (fd_set_nonblock): assertion failed: (fd > -1)

Hi all, Our Dovecot replication crashes because an assertion in dovecot-core/src/lib/fd-util.c fails: #6 0x7fd5ac89b08e in fd_set_nonblock (fd=-1, nonblock=true) at fd-util.c:102 102 i_assert(fd > -1); This only happens if dovecot starts the replication by itself, i.e. not

Re: bug report: imap-login not killed

Hi, Does this happen with latest 2.3.20 too? You can find packages at https://repo.dovecot.org/ Yes it is, thanks \ò/ Sacha.

Re: bug report: imap-login not killed

  On 04/03/2023 17:10 EET Sacha wrote:     Hi, We have growing imap-login processes until we reach the max processes. This occurs when a particular user have a login error due to our LDAP misconfiguration: ---Mar  4

bug report: imap-login not killed

Hi, We have growing imap-login processes until we reach the max processes. This occurs when a particular user have a login error due to our LDAP misconfiguration: --- Mar  4 14:59:33 hera dovecot[2226963]: auth: Error: plain(john.doe,XX.XX.XX.XX,<13C0eBP2354lqXpO>): user not found from any

Re: Bug report: TLS SNI for LDAP userdb/passdb

ble) here, and the changelog does not > offer > any hope of salvation, so a bug report it is. > > The LDAP connections for userdb/passdb do not support SNI via TLS. > > Simple construct to reproduce this: > > 0.) Have a.pem with SAN `foo.example.com`, b.pem with > `bar.example.c

Re: Bug report: TLS SNI for LDAP userdb/passdb

4.1 (Debian stable) here, and the changelog does not >> > offer >> > any hope of salvation, so a bug report it is. >> > >> > The LDAP connections for userdb/passdb do not support SNI via TLS. >> > >> > Simple construct to reproduce this: >> >

Re: Bug report: TLS SNI for LDAP userdb/passdb

Cheers, On Thu, 2022-09-15 at 07:18 +0300, Aki Tuomi wrote: > On September 14, 2022 5:29:46 PM GMT+03:00, Tobias Wolter > wrote: > > Cheers, > > > > Dovecot 2.3.4.1 (Debian stable) here, and the changelog does not > > offer > > any hope of salvation, so a

Re: Bug report: TLS SNI for LDAP userdb/passdb

On September 14, 2022 5:29:46 PM GMT+03:00, Tobias Wolter wrote: >Cheers, > >Dovecot 2.3.4.1 (Debian stable) here, and the changelog does not offer >any hope of salvation, so a bug report it is. > >The LDAP connections for userdb/passdb do not support SNI via TLS. &

Bug report: TLS SNI for LDAP userdb/passdb

Cheers, Dovecot 2.3.4.1 (Debian stable) here, and the changelog does not offer any hope of salvation, so a bug report it is. The LDAP connections for userdb/passdb do not support SNI via TLS. Simple construct to reproduce this: 0.) Have a.pem with SAN `foo.example.com`, b.pem

Re: Replicator bug report

Yeah. As I said it's a bug, it should never allocate that much data stack memory. I don't know any workarond immediately for this. Maybe try setting `service_count=1` for the replicator service, it might or not help. Aki > On 12/12/2021 14:31 Jörg Faudin Schulz wrote: > > > No ... it just

Re: Replicator bug report

No ... it just crashes a bit later: Dec 12 13:28:26 replicator: Panic: data stack: Out of memory when allocating 68719476776 bytes Am 12.12.21 um 08:23 schrieb Daniel Miller: It appears when I set vsz_limit=0 it works without crashing. So the problem appears when setting an explicit

Re[9]: Replicator bug report

It appears when I set vsz_limit=0 it works without crashing. So the problem appears when setting an explicit maximum. -- Daniel On 12/7/2021 9:57:29 PM, "Aki Tuomi" wrote: On 7 December 2021 23.10.50 UTC, Daniel Miller wrote: On 12/7/2021 12:29:49 PM, "Daniel Miller" wrote: service

Re: Re[7]: Replicator bug report

On 7 December 2021 23.10.50 UTC, Daniel Miller wrote: >On 12/7/2021 12:29:49 PM, "Daniel Miller" wrote: > >>>service replicator { >>>vsz_limit = 2G >>>} >>> >>>Aki >>> >>Tried that - got another one. > > >I just tried setting >service replicator { > vcsz_limit = 5G >} >and I still get:

Re[7]: Replicator bug report

On 12/7/2021 12:29:49 PM, "Daniel Miller" wrote: service replicator { vsz_limit = 2G } Aki Tried that - got another one. I just tried setting service replicator { vcsz_limit = 5G } and I still get: Dec 7 15:08:25 bubba dovecot: replicator: Panic: data stack: Out of memory when

Re[6]: Replicator bug report

service replicator { vsz_limit = 2G } Aki Tried that - got another one. [New LWP 14072] Core was generated by `dovecot/replicator'. Program terminated with signal SIGABRT, Aborted. ---Type to continue, or q to quit--- #0 __GI_raise (sig=sig@entry=6) at

Re: Re[4]: Replicator bug report

On 7 December 2021 19.27.20 UTC, Daniel Miller - CLOUD wrote: >>Use >> >>gdb /path/to/replicator /path/to/core >>bt full >> >>Aki >> service replicator { vsz_limit = 2G } Aki

Re[4]: Replicator bug report

Use gdb /path/to/replicator /path/to/core bt full Aki root@bubba:/var/core# gdb /usr/lib/dovecot/replicator /var/core/11199.replicator GNU gdb (Ubuntu 8.1.1-0ubuntu1) 8.1.1 Copyright (C) 2018 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later

Re: Re[2]: Replicator bug report

On 7 December 2021 19.11.18 UTC, Daniel Miller wrote: >-- Original Message -- >> >>Hi! >> >>Can you instead submit gdb bt full output and doveconf -n? >> >>Aki >> > >Certainly - but I need to know how. The problem is during TCP >replication. > > >-- >Daniel > > Use gdb

Re[2]: Replicator bug report

-- Original Message -- Hi! Can you instead submit gdb bt full output and doveconf -n? Aki Certainly - but I need to know how. The problem is during TCP replication. Here is dovecot -n: # 2.3.17.1 (476cd46418): /etc/dovecot/dovecot.conf # Pigeonhole version 0.5.17.1 (a1a0b892) #

Re: Replicator bug report

On 7 December 2021 18.55.40 UTC, Daniel Miller wrote: >I've run dovecot-sysreport -o and generated a file - but it's a >few gigs in size. Am I generating the core dump incorrectly? Should I do >something different? > >-- >Daniel Hi! Can you instead submit gdb bt full output and doveconf

Replicator bug report

I've run dovecot-sysreport -o and generated a file - but it's a few gigs in size. Am I generating the core dump incorrectly? Should I do something different? -- Daniel

Re: bug report: lmtp fails on root-squashed NFS filesystem

Hello Aki. >> I patched "src/lib-storage/index/mbox/mbox-storage.c" and >> "src/lib-storage/index/maildir/maildir-storage.c" to replace >> calls to "access()" with calls to "euidaccess()", and now mail >> delivery (to mboxes) works for me. (I can't test maildir yet.) >> >> Could this be

Re: bug report: lmtp fails on root-squashed NFS filesystem

> On 23/11/2021 23:47 Anne Bennett wrote: > > > Following up to my own post: > > > I'm trying to set up Postfix with dovecot LTMP delivery > > on a host where the user files (/var/spool/mail as well as > > home directories) are on NFS filesystems, which are exported > > root-squashed to the

Re: bug report: lmtp fails on root-squashed NFS filesystem

Following up to my own post: > I'm trying to set up Postfix with dovecot LTMP delivery > on a host where the user files (/var/spool/mail as well as > home directories) are on NFS filesystems, which are exported > root-squashed to the mail server. [LMTP delivery fails with "save failed to

bug report: lmtp fails on root-squashed NFS filesystem

Hi, all. I'm trying to set up Postfix with dovecot LTMP delivery on a host where the user files (/var/spool/mail as well as home directories) are on NFS filesystems, which are exported root-squashed to the mail server. I definitely don't want to give the mail server root permissions on the user

Re: BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

ean365 wrote: Hi, Aki: Just resending below bug report. I notice that it has not been fixed, yet. Am I correct that this is a bug, albeit a small one? Best Regards, Eric On 12/27/2020 11:02 AM, Aki Tuomi wrote: On 26/12/2020 10:41 ean365 wrote: Aki: I have identified a bug

Re: BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

> > > Hi, Aki: > > Just resending below bug report. I notice that it has not been fixed, yet. > > Am I correct that this is a bug, albeit a small one? > > Best Regards, > > Eric > > > > > > On 12/27/2020 11:02 AM, Aki Tuo

Re: BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

Yes, it's a bug. It's being tracked by us. Aki > On 28/07/2021 07:56 ean365 wrote: > > > Hi, Aki: > Just resending below bug report. I notice that it has not been fixed, yet. > Am I correct that this is a bug, albeit a small one? > Best Regards, > Eric > >

Re: BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

Hi, Aki: Just resending below bug report.  I notice that it has not been fixed, yet.  Am I correct that this is a bug, albeit a small one? Best Regards, Eric On 12/27/2020 11:02 AM, Aki Tuomi wrote: On 26/12/2020 10:41 ean365 wrote: Aki: I have identified a bug in the "-O&qu

BUG report

Hello! I've compiled Dovecot without any error, but couldn't run it. - The error is: - Feb 09 19:22:50 master: Panic: kevent(EV_ADD, READ, 21) failed: Invalid argument Feb 09 19:22:50 master: Error: Raw backtrace: 0 libdovecot.0.dylib 0x00216d58 askpass + 136 -> 1

Re: BUG report

On 21 Feb 2021, at 06:19, Oleg Pyzin wrote: > I've compiled Dovecot on a macmini G4 PPC from ports, What OS version are you running on it? -- "Are you pondering what I'm pondering?" "I think so, Brain. But does 'Chunk o' Cheesy's' deliver packing material?"

BUG report

Hello! I've compiled Dovecot on a macmini G4 PPC from ports, but couldn't launch it. When Dovecot is trying to launch it's stop launching because got an error. - The error is: Feb 09 19:22:50 master: Panic: kevent(EV_ADD, READ, 21) failed: Invalid argument Feb 09 19:22:50 master:

Re: BUG report: dbox movealt doesn't move reverse (to default location)

On 09.07.20 14:12, Vitalii wrote: However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u v...@vito.pp.ua -r all That seems behave like the original command ignoring '-r'. Same problem here with Dovecot 2.3.13, "doveadm altmove -r" is not moving anything

Re: [BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing

Hello John, Sorry for a bit delayed reply. For some reason some of dovecot mail list messages are not reaching my inbox :( Indeed, I can confirm that your patch works as expected: meaning strips out just the message body. So yes, in my report I supposed to say: message bodies of affected

Re: [BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing

rkaround: there is a useful patch by John Fawcett  > <https://www.mail-archive.com/dovecot@dovecot.org/msg82296.html> that > allows to set the FTS indexing message body maximum size. It works > perfectly, but affected messages are getting completely ignored by FTS. > > This bu

[BUG REPORT] In some cases dovecot sends (huge) binary data to solr for indexing

the FTS indexing message body maximum size. It works perfectly, but affected messages are getting completely ignored by FTS. This bug report is a summarised result of this discussion <https://www.mail-archive.com/dovecot@dovecot.org/msg82599.html>.

Re: BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

> On 26/12/2020 10:41 ean365 wrote: > > > Aki: > > I have identified a bug in the "-O" option of "doveadm mailbox cryptokey > password" plugin command -- it is expecting an argument, but it is supposed > to be a boolean option. I have also identified the (simple) fix to the source > on

BUG REPORT: MAIL-CRYPT plugin: doveadm mailbox cryptokey -O option

Aki: I have identified a bug in the "*-O*" option of "*doveadm mailbox cryptokey password*" plugin command -- it is expecting an argument, but it is supposed to be a boolean option.  I have also identified the (simple) fix to the source on github... /I am a dovecot community noob, so please

Re: Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Does this happen with A3 LIST "" "*" RETURN (CHILDREN STATUS (MESSAGES UNSEEN)) as well? Also, can you try this with 2.3.11.3 from repo.dovecot.org? Aki > On 01/12/2020 15:12 Merijn Schering wrote: > > > Hi, > > I'm using dovecot 2.3.4.1 (f79e8e7e4). > > I have created a folder called

Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Hi, I'm using dovecot 2.3.4.1 (f79e8e7e4). I have created a folder called "Test with *". Now when I do a command: A3 LIST "" "%" RETURN (CHILDREN STATUS (MESSAGES UNSEEN)) It responds: * STATUS Test with * ( MESSAGES 0 UNSEEN 0 ) * LIST ( \HasNoChildren \UnMarked ) / Spam But it

Bug report: invalid \HasNoChildren in response when asterisk is used in the name

Hi, I'm using dovecot 2.3.4.1 (f79e8e7e4). I have created a folder called "Test with *".  Now when I do a command: A3 LIST "" "%" RETURN (CHILDREN STATUS (MESSAGES UNSEEN)) It responds:   * STATUS Test with * ( MESSAGES 0 UNSEEN 0 ) * LIST ( \HasNoChildren \UnMarked ) / Spam But it

Re: BUG report: dbox movealt doesn't move reverse (to default location)

On Thu, 9 Jul 2020 13:12:46 +0100 Vitalii wrote: > Hi, > > Here is the problem that occured: > #sudo doveadm -D altmove -u v...@vito.pp.ua all > works properly and moves all storage to alt dir. > However, to move it back to default storage I add '-r' by manual: > #sudo doveadm -D altmove -u

Re: BUG report: dbox movealt doesn't move reverse (to default location)

> On 9. Jul 2020, at 15.12, Vitalii wrote: > > Hi, > > Here is the problem that occured: > #sudo doveadm -D altmove -u v...@vito.pp.ua all > works properly and moves all storage to alt dir. > However, to move it back to default storage I add '-r' by manual: > #sudo doveadm -D altmove -u

BUG report: dbox movealt doesn't move reverse (to default location)

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u v...@vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u v...@vito.pp.ua -r all That seems behave like the original command

BUG report: dbox movealt doesn't move reverse (to default location)

Hi, Here is the problem that occured: #sudo doveadm -D altmove -u v...@vito.pp.ua all works properly and moves all storage to alt dir. However, to move it back to default storage I add '-r' by manual: #sudo doveadm -D altmove -u v...@vito.pp.ua -r all That seems behave like the original command

Bug[?]report: duplicate response

hi, i'm not sure if i've discovered a bug or if i'm not following the IMAP specs correctly. observations: { echo -en "a1 login foo bar\r\na2 notify set (subscribed (FlagChange SubscriptionChange MessageNew MessageExpunge))\r\n"; cat - } | openssl s_client -connect [my_dovecot_server]:993

Re: Bug report

Peter Nabbefeld via dovecot skrev den 2019-11-01 23:30: ~/.getmail/log = 2019-11-01 21:44:20 Delivery error (command deliver 42245 error (127, exec of command deliver failed (change UID/GID to vmail/vmail failed ([Errno 1] Operation not permitted maybe provide getmail debug logs

Re: Bug report

On 01 Nov 2019, at 16:30, Peter Nabbefeld wrote: > ~/.getmail/log > = > 2019-11-01 21:44:20 Delivery error (command deliver 42245 error (127, exec of > command deliver failed (change UID/GID to vmail/vmail failed ([Errno 1] > Operation not permitted Seems pretty clear, get mail is

Bug report

Hello, I've got a problem fetching my emails using getmail. First question is, of course, what's causing the problems. I'm going to think that getmail get's an error code from dovecot when trying to connect and just signals the most common error, so it seems to be a problem with dovecot.

[BUG REPORT] Case sensitivity in :addresses in sieve vacation scripts

gt; > > > Unfortunately adding the :comparator statement to vacation results in an error while compiling the script: managesieve: line 5: error: unknown tagged argument ':comparator' for the vacation command (reported only once at first occurrence). Since https://www.dovecot.org/bugr

Re: dovecot-2.2.33 bug report

On 11.10.2017 09:53, David Binderman wrote: > Hello there, > > dovecot-2.2.33/src/lib/str-find.c:86]: (warning) Calling 'sizeof' on 'sizeof' > > Source code is > > ctx = p_malloc(pool, MALLOC_ADD(sizeof(struct str_find_context), > MALLOC_MULTIPLY(sizeof(ctx->goodtab[0]), key_len)));

dovecot-2.2.33 bug report

Hello there, dovecot-2.2.33/src/lib/str-find.c:86]: (warning) Calling 'sizeof' on 'sizeof' Source code is ctx = p_malloc(pool, MALLOC_ADD(sizeof(struct str_find_context), MALLOC_MULTIPLY(sizeof(ctx->goodtab[0]), key_len))); Regards David Binderman

Re: Potential bug report: Cannot use ":args" option via Pigeonhole Sieve pipe plugin

Op 7-6-2016 om 12:16 schreef Zeeshan Muhammad: It looks like pipe addon specification at http://hg.rename-it.nl/pigeonhole-0.2-sieve-pipe/raw-file/tip/doc/rfc/spec-bosch-sieve-pipe.txt notes ":args" usage is possible but the implementation source at

Re: Potential bug report: Cannot use ":args" option via Pigeonhole Sieve pipe plugin

It looks like pipe addon specification at http://hg.rename-it.nl/pigeonhole-0.2-sieve-pipe/raw-file/tip/doc/rfc/spec-bosch-sieve-pipe.txt notes ":args" usage is possible but the implementation source at https://github.com/dovecot/pigeonhole/blob/master/src/plugins/sieve-extprograms/cmd-pipe.c

Potential bug report: Cannot use ":args" option via Pigeonhole Sieve pipe plugin

Hi all, Following the instructions noted at http://wiki2.dovecot.org/Pigeonhole/Sieve/Plugins/Pipe , I am trying to make use of the Pigeonhole sieve pipe plugin to execute an application with custom arguments via my test sieve script: require ["vnd.dovecot.pipe"]; if address :is "to"

Re: Bug Report - Crash on imap with core dump - Alternate storage related

Ah, sorry, missed it =) Aki On 12.05.2016 12:53, Daniel van Ham Colchete wrote: > Hi Aki! > > It was already there: http://pastebin.com/2xA2xuRw > > Best, > Daniel Colchete > > On Thu, May 12, 2016 at 3:03 AM, Aki Tuomi wrote: > >> >> On 11.05.2016 22:45, Daniel van Ham

Re: Bug Report - Crash on imap with core dump - Alternate storage related

Hi Aki! It was already there: http://pastebin.com/2xA2xuRw Best, Daniel Colchete On Thu, May 12, 2016 at 3:03 AM, Aki Tuomi wrote: > > > On 11.05.2016 22:45, Daniel van Ham Colchete wrote: > > I can confirm that this bug also happens on the latest version available: > >

Re: Bug Report - Crash on imap with core dump - Alternate storage related

On 11.05.2016 22:45, Daniel van Ham Colchete wrote: > I can confirm that this bug also happens on the latest version available: > > root@dovecot:/# dovecot --version > 2.2.devel (ebf2e93) > root@dovecot:/# dpkg -l|grep dovecot > ii dovecot-core 2:2.2.24-1~auto+23amd64 >

Re: Bug Report - Crash on imap with core dump - Alternate storage related

I can confirm that this bug also happens on the latest version available: root@dovecot:/# dovecot --version 2.2.devel (ebf2e93) root@dovecot:/# dpkg -l|grep dovecot ii dovecot-core 2:2.2.24-1~auto+23amd64 secure POP3/IMAP server - core files ii dovecot-dbg

Bug Report - Crash on imap with core dump - Alternate storage related

I would like to report a bug we are seeing on an new deployment here: Linux: Debian Jessie, inside a Docker container Dovecot version: 2.2.23 (806d709) / 2.2.23-1~bpo8+1 doveconf -n: http://pastebin.com/2xA2xuRw Filesystem: CephFS - Jewel After migrating our users from our old server to our new

Re: Bug Report: %% variables not expanded properly with shared namespace using . as separator

On 19/02/2016 8:09 PM, Steffen Kaiser wrote: > On Fri, 19 Feb 2016, Hugh Bragg wrote: > > > Subject: Bug Report: %% variables not expanded properly with shared > namespace > > using . as separator > > > I think this is a bug. > > I'd expect that location

Re: Bug Report: %% variables not expanded properly with shared namespace using . as separator

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Fri, 19 Feb 2016, Hugh Bragg wrote: Subject: Bug Report: %% variables not expanded properly with shared namespace using . as separator I think this is a bug. I'd expect that location %% variables are translated the same way % variables

Bug Report: %% variables not expanded properly with shared namespace using . as separator

I think this is a bug. I'd expect that location %% variables are translated the same way % variables are interpreted, but apparently this isn't the case. virtual folders work fine, but my shared folders fail because of the . in the domain name. What I get is the following: # doveadm acl debug -u

Re: bug report: dovecot-imapd core dump

On 10 Oct 2015, at 20:34, Tamas Papp wrote: > > Hi, > > Since I did not get any specific suggestions about this bug, I am > attaching another backtrace. Any suggestions for workarounds etc would > be appreciated -- should I regenerate the index? Or install a dovecot > from the

Re: bug report: dovecot-imapd core dump

Hi, Since I did not get any specific suggestions about this bug, I am attaching another backtrace. Any suggestions for workarounds etc would be appreciated -- should I regenerate the index? Or install a dovecot from the repo where this might be fixed? Is this a known bug? Best, Tamas

bug report: dovecot-imapd core dump

Typical log message: Oct 7 11:39:36 hostname dovecot: imap(username): Fatal: master: service(imap): child 14864 killed with signal 11 (core dumped) What triggers the problem: User moving multiple messages to a subfolder via IMAP (from another account, on another server, client: Thunderbird).

Re: bug report: dovecot-imapd core dump

Hi, could not find it -- back to the list, maybe someone can suggest a fix/workaround. Best, Tamas On Wed, Oct 07 2015, Dominik Breu wrote: > Hello, > > yeah this one looks familiar to me can you search the list back in > september there was a somewhat similar bug with thunderbird imho timo >

Re: doveadm backup/sync are badly documented (SOLVED AND BUG REPORT!)

On 09/29/2014 12:15 AM, Jesus Cea wrote: … $ doveadm backup -h backup: invalid option -- 'h' doveadm backup [-u user|-A] [-S socket_path] [-dfR] [-l secs] [-r rawlog path] [-m mailbox] [-n namespace | -N] [-x exclude] [-s state] dest I can't find any explanation at all about the different

Re: doveadm backup/sync are badly documented (SOLVED AND BUG REPORT!)

On 28/09/14 23:52, Jesus Cea wrote: [..] This will backup this mailing list mailbox to /tmp/aa. Good. Lets try thru SSH: $ doveadm backup -u jcea -m proveedores/dovecot ssh 127.0.0.1 dsync -u jcea mdbox:/tmp/aa/ jcea@127.0.0.1's password: Fatal: Invalid parameter: mdbox:/tmp/aa/

Bug report: Error: posix_fadvise on FreeBSD

dovecot2-2.2.13_3 FreeBSD 9.3 CPU: Intel(R) Celeron(R) CPUE1400 @ 2.00GHz (1995.04-MHz 686-class CPU) Origin = GenuineIntel Id = 0x6fd Family = 6 Model = f Stepping = 13

Re: [Dovecot] Bug Report

huh? You are logging a bug for antique version, if you grab latest source, build and install it, and problem remains with current version, THEN it is a bug, most devs would ignore you for such sillyness otherwise On 2/20/14, Jon Thompson jthomp...@dmevolve.com wrote: Since I'm obviously using

Re: [Dovecot] Bug Report

Since I’m obviously using version 2.2.5, which is apparently a supported version by dovecot, I’d still maintain that it should be submitted as a bug. I’ve also submitted the bug to Apple as well. Regardless, has anyone compiled a drop-in update that supports Apple Push Notifications, Sieve,

[Dovecot] Bug report

I'm using release 2.2.12, during a copy operation i get segfault on imap process. I have full bt of the issue: (gdb) bt #0 0x7fcc521029cd in mail_cache_header_fields_read (cache=0x15c7210) at mail-cache-fields.c:369 #1 0x7fcc52100664 in mail_cache_open_and_verify (cache=0x15c7210)

[Dovecot] Bug Report

So when I try and create a sub mailbox in shared-folders, I get this error… imap(pid 56143 user -): Fatal: master: service(imap): child 56143 killed with signal 11 (core dumps disabled) I’ve not been able to figure out how to get dovecot in OS X to core dump, so I haven’t included that.

Re: [Dovecot] Bug Report

since you are obviously using the binary shipped with Mac OSX and packaged by Apple Inc. which is heavily outdated while current dovecot is version 2.2.12 you may complain to Apple Inc. Am 18.02.2014 00:19, schrieb Jon Thompson: So when I try and create a sub mailbox in shared-folders, I get

Re: [Dovecot] BUG report: doveadm HEADER field pattern when concatenating with another Search key

Hey Joseph! Thanks for testing. I couldn't recreate this with 2.1.16. Also, my version of doveadm search does not accept missing header patterns. Is this corroborated by dumping out the header with this same search query? doveadm fetch -u exampleuser hdr SUBJECT Silvester \

Re: [Dovecot] BUG report: doveadm HEADER field pattern when concatenating with another Search key

So E.g. When doing doveadm fetch -u exampleuser hdr SUBJECT Silvester HEADER Return-Path someu...@example.com it initially outputs 13 headers (same as when using with SUBJECT Silvester only) , when piping it to grep -i 'Return-Path' it even found only 3 out of 13 headers containing a

[Dovecot] BUG report: doveadm HEADER field pattern when concatenating with another Search key

Hey there, I'm pretty sure I've found a bug with doveadm when concatenating with another search key. While doveadm HEADER field pattern works fine when not using additional search keys, it doesn't work properly when concatenating with other serarch keys - it then simply seems to ignore the

Re: [Dovecot] BUG report: doveadm HEADER field pattern when concatenating with another Search key

On Wed, 8 Jan 2014, dovecot-requ...@dovecot.org wrote: doveadm search -u exampleuser SUBJECT Silvester (outputs correctly 10 matches) ... doveadm search -u exampleuser SUBJECT Silvester HEADER Return-Path someu...@example.com (gives exactly the same output - but this is WRONG, as the given

Re: [Dovecot] bug report: doveadm assertion failure mail_index_map_lookup_seq_range

Since reporting this (from the wrong account, sorry), I've tried to investigate whether the problem exists in 2.2.9. While building 2.2.9 was no problem, I balked at actually installing it for fear of causing trouble with future system updates. (Or current operation, for that matter.) Could

Re: [Dovecot] bug report: doveadm assertion failure mail_index_map_lookup_seq_range

On 6.12.2013, at 15.33, email-from-bobby email-from-bo...@vishniac.com wrote: A negated subject search on an empty folder causes an assertion failure in doveadm. To reproduce: bash-3.2# doveadm mailbox create -u ephraim Freshly Empty bash-3.2# doveadm search -u ephraim mailbox Freshly

[Dovecot] bug report: doveadm assertion failure mail_index_map_lookup_seq_range

A negated subject search on an empty folder causes an assertion failure in doveadm. To reproduce: bash-3.2# doveadm mailbox create -u ephraim Freshly Empty bash-3.2# doveadm search -u ephraim mailbox Freshly Empty NOT subject '***JUNK MAIL***' doveadm(ephraim): Panic: file mail-index-map.c:

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

If doveadm says it's invalid UTF-8, it's invalid UTF-8. I guess your terminal isn't actually using UTF-8 then, but something else. (locale output should say something about UTF-8.) I guess doveadm could also automatically translate parameters to UTF-8, but that's a bit annoying to

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

Hi there Timo, first of all thank you for taking your time for support! Forget about mUTF-7 with Dovecot. It's an IMAP-protocol relic, and Dovecot is trying to get rid of it in as many places as possible. Although by default the filesystem users mUTF-7, but that can also be changed with a

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

On 23.9.2013, at 16.52, mego...@inboxalias.com wrote: I suspect your shell is breaking the 8bit chars into invalid UTF-8. I just tried and it works fine with me. Sorry, we got confusion here... apparently my (lousy) freemail provider which I use to post on this mailinglist doesn't send

[Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

Hello there, I'm pretty sure I found a bug in latest Dovecot 2.2.5.5 (EE) when playing with the doveadm command. Naturally renaming a users mail folder should be done via doveadm es consistent. So when using doveadm rename trying to rename a folder with special characters e.g. german umlauts

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

Sorry, it seems like some part of the sh*tty freenet webmailer omitted half of my second sentence of the message I just posted before... . ..so please replace the weird sentence: Naturally renaming a users mail folder should be done via doveadm es consistent. with: Naturally renaming a users

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

correction posts). Seems like a have to write another bug report to freenet admins... (sigh) Sorry again, Megodin --- Alle Postfächer an einem Ort. Jetzt wechseln und E-Mail-Adresse mitnehmen! http://email.freenet.de/basic/Informationen

Re: [Dovecot] Bug report: doveadm rename encodes special characters wrongly in mUTF-7 (in fs)

On 20.9.2013, at 17.42, mego...@inboxalias.com wrote: So when using doveadm rename trying to rename a folder with special characters e.g. german umlauts like ä it seems to create the folder wrongly in the filesystem. Example: When I want to rename a users folder 'geschaftliches' to

Re: [Dovecot] bug report: auth via dict

On Fri, 2013-01-11 at 00:08 -0800, ForestYang wrote: I was testing dovecot server , auth via redis. first I follow http://master.wiki2.dovecot.org/AuthDatabase/Dict but auth always fail, last , I found value { uid: 123, gid: 123, home: /home/username } was wrong, the uid and gid must as

  1   2   >