similar to: pigeonhole tests crashing in deleteheader.svtest

> On 28 March 2019 19:40 Michal Hlavinka via dovecot <dovecot at dovecot.org> wrote: > > > Hi, > > when trying to build dovecot 2.3.5.1 pigeonhole testsuite crashes in > Which version of pigeonhole are you using? Aki

On 3/28/19 6:41 PM, Aki Tuomi via dovecot wrote: > >> On 28 March 2019 19:40 Michal Hlavinka via dovecot <dovecot at dovecot.org> wrote: >> >> >> Hi, >> >> when trying to build dovecot 2.3.5.1 pigeonhole testsuite crashes in >> > > Which version of pigeonhole are you using? latest available - 0.5.5

On 29/03/2019 10:23, Michal Hlavinka via dovecot wrote: > On 3/28/19 6:41 PM, Aki Tuomi via dovecot wrote: >> >>> On 28 March 2019 19:40 Michal Hlavinka via dovecot >>> <dovecot at dovecot.org> wrote: >>> >>> ? Hi, >>> >>> when trying to build dovecot 2.3.5.1 pigeonhole testsuite crashes in >>> >> >> Which

On 4/12/19 12:48 AM, Stephan Bosch wrote: > > > On 29/03/2019 10:23, Michal Hlavinka via dovecot wrote: >> On 3/28/19 6:41 PM, Aki Tuomi via dovecot wrote: >>> >>>> On 28 March 2019 19:40 Michal Hlavinka via dovecot >>>> <dovecot at dovecot.org> wrote: >>>> >>>> ? Hi, >>>> >>>> when trying to

Hi, We're using Dovecot 2.1.16 with Pigeonhole 0.3.4. Mail is delivered by exim4 to the dovecot LDA. Sometimes users are unable to delete headers. I've narrowed the problem down to preceding the deleteheader command with a query against the body. A simple example: """ require ["body", "editheader", "fileinto"]; if body :contains

On 03/09/2020 23:25, Alec Moskvin wrote: > Hi Stephan, > > On Wednesday 02 September 2020 19:59:57, Stephan Bosch wrote: >> >> On 29/08/2020 21:04, Alec Moskvin wrote: >>> Hello, >>> >>> I have a rule to always delete a header. If the message gets fileinto'd, >>> the header is gone, but if it's delivered into the INBOX through

On 29/08/2020 21:04, Alec Moskvin wrote: > Hello, > > I have a rule to always delete a header. If the message gets fileinto'd, > the header is gone, but if it's delivered into the INBOX through > implicit keep, the header does not get deleted. > > Interestingly, if I remove the "if duplicate" filter, the header does > get deleted as expected. > >

Hello, I have a rule to always delete a header. If the message gets fileinto'd, the header is gone, but if it's delivered into the INBOX through implicit keep, the header does not get deleted. Interestingly, if I remove the "if duplicate" filter, the header does get deleted as expected. I'm using the latest Dovecot 2.3.11.3 / Pigeonhole 0.5.11. Any idea why this is

Hi Stephan, On Wednesday 02 September 2020 19:59:57, Stephan Bosch wrote: > > > On 29/08/2020 21:04, Alec Moskvin wrote: > > Hello, > > > > I have a rule to always delete a header. If the message gets fileinto'd, > > the header is gone, but if it's delivered into the INBOX through > > implicit keep, the header does not get deleted. > > >

Dear Juan, I don't see what is the problem from your report. Please try to create a minimal but complete reproducible example that does not use the renv package. Perhaps you could use the R debugger (e.g. via options(error=recover)) to find out what is the argument that file.exists() has been called with. And then you could try just to call file.exists() directly with that argument to

Hi Yihui, list.files() returns file names converted to native encoding by Windows, so one needs to use only characters representable in current native encoding for file names. If one wants to be safe, it makes sense to be much stricter than that (only ASCII, and only a subset of it, there is a number of recommendations that can be found online). Using more than that is asking for trouble.

Hi Juan, For bug reports to R, you should attempt to create a minimally-reproducible example, using only R's builtin facilities and not any other addon packages. Given your report, it's not clear whether the issue lies within renv or truly is caused by a change in R 4.0.0. Also note that you have not supplied a minimally reproducible example. If at all possible, you should be able to

Dear R Developers, I am having an issue with the renv package and R 4.0.1, which I suspect is related to base R and not the renv package itself, as with R 3.6.3 such an "error" does not appear. The error is raised by a file.exists() path, and path "C:\Users\J-tel\Documents", which in R 3.6.3 is read correctly, but in R 4.0.1 fails (Probably because of the "-"

Hi Tomas, I received a report about R 4.0.0 in the knitr package (https://github.com/yihui/knitr/issues/1840), and I think it is related to the issue here. I created a minimal reproducible example below: owd = setwd(tempdir()) z = 'K\u00e4sch.txt' file.create(z) list.files() file.exists(list.files()) setwd(owd) Output: > owd = setwd(tempdir()) > z = 'K\u00e4sch.txt' >

Hi Tomas, Sorry for the false alarm! I did some further testing, and you were right. There was no regression. I suspected it was a regression because the user who reported the issue said his code worked in R 3.6 but not 4.0. I should have tested it more carefully by myself. After I tested it again with the German locale and Chinese locale, respectively, I found that the code worked for both

Hola, La otra solución es actualizar R a una versión más reciente (con la 3.6 es posible que esto te llegue a pasar con más paquetes, la versión actual es 4.3.2). Si por tus requerimientos tienes que seguir usando la 3.6, entonces como dice Eric debes controlar también las versiones de los paquetes, y mejor aún si lo haces con renv (https://rstudio.github.io/renv/articles/renv.html) Emilio

Dear WizaRds, I wrote a small function in R and would like to create a package. The necessary documentation is done, Rtools etc. are installed and I am still unable to complete the process under Windows. I did extensive research in the archives and read the Murdoch-Sutherland website on the Rtools and MikTeX hints. I realize that I understand only half or less of what is said there

I?ve bene looking for examples on how to do this, but so far am coming up short. I want to check certain messages for a reply-ro header and if it is present, rewrite it to X-Reply-To: and then add my own reply-to header. I don?t see anything in the various sieve examples I?ve found on altering the actual message. There is the editheader extension, but I failed to find documentation or examples

I have an active sieve file for my list account that alters the headers for this list (sets the reply-to address to the list instead of the poster) which is suddenly failing. require [ "regex", "variables", "fileinto", "envelope", "mailbox", "imap4flags", "editheader" ]; /* other stuff */ elsif header :contains

Hello, i do some tests with sieve editheader extensions. deleteheader and addheader are working, but i noticed that new headerlines are always prepended to current header. So new lines can be found always on top. I am looking for a possibility to edit a headerline in place, without moving the new line to top of stack(replaceheader?). It is not looking good if a Subject-Line suddenly moves to