search for: catenated

I'm pleased to see that dovecot-2.2 includes support for RFCs 4467 and 4469 (URLAUTH and CATENATE). I have begun testing these features (in dovecot-2.2.1) and comparing their functionality against Apple's implementation. So far I have discovered a few inconsistencies. I will report each of these, and any more that I may find, in separate threads. The first issue is that using CATENATE

Attached please find a perl script which tests the CATENATE support in dovecot. I used this to test my CATENATE implementation a few years ago and it runs fine against dovecot in OS X Server. When run against dovecot-2.2.4 though it always fails or hangs, which in some cases means we interpreted RFCs differently and in other cases means it's finding bugs; both conditions are worthy of

Dovecot-2.2.1 allows empty messages to be APPENDed when using CATENATE: b1 append inbox catenate (text {0+} ) b1 OK [APPENDUID 1366726248 12] Append completed. Contrast this with regular APPEND: b2 append inbox {0+} b2 NO Can't save a zero byte message. Note that zero-size literals are OK but zero-size messages are not. So while "b1" above should fail like "b2",

In the context in which I am actually working it is necessary for me to build parts of a text string to place on a plot in two separate stages. The following toy example illustrates what I am trying to do: L1 <- substitute(list(paste("Bias in ", gamma,", "))) L2 <- substitute(list(beta==b0),list(b0=300)) plot(1:10,main=L1) # Works fine. plot(1:10,main=L2) # Works fine.

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions

Dovecot-2.2.1 does not appear to support URLs specified via non-synchronizing literals (RFC 2088 LITERAL+), and also does not read and discard the literal+ input after reporting the error. This results in the literal+ input being interpreted as IMAP commands, which could alter the user's mail store in unexpected ways and/or lead to the abrupt disconnection of the client for exceeding the

Using 2.2.2, I see this: C: 6 APPEND "INBOX" (\seen) "16-May-2013 22:05:14 -0600" CATENATE (URL "/INBOX;UIDVALIDITY=1255685337/;UID=48812/;SECTION=HEADER" TEXT ~{40} S: 6 NO [UNKNOWN-CTE] Binary input allowed only when the first part is binary. Why is there this limitation? It seems to me that CATENATE is confusing the content-type encoding of the data/part

Dovecot-2.2.1 plus Timo's recent CATENATE and URLAUTH fixes mishandles literals after bad URLs. (As before remember that the "foobar" text below is really "foobarCRLF" hence the length of 8. Also, last time some MTA discarded an important single leading space character in the snippet I quoted so this time I'm prefixing all the lines to avoid that. In case it's

I was recently asked by one of new colleagues how to combine, or catentate, or concatentate two factors. If x and y are factors, doing c(x,y) appears to coerce x and y to numeric mode before catenating them. So what does one do if one wants the result to be a factor whose levels are the union of the levels of x and y? I vaguely recall seeing this discussed in r-help, but I can't find

Thanks Tomas. Do note that my original post also mentioned a bug or doc error in the PCRE docs for this regexp: > - perl = TRUE does *not* give the documented result on at least one > system (which is "123456789", because "{,5}" is documented to not be a > quantifier, so it should only match the literal string "{,5}"). Duncan On 2024-08-01 6:49 a.m.,

On 8/1/24 20:55, Duncan Murdoch wrote: > Thanks Tomas.? Do note that my original post also mentioned a bug or > doc error in the PCRE docs for this regexp: > >> ? - perl = TRUE does *not* give the documented result on at least one >> system (which is "123456789", because "{,5}" is documented to not be >> a quantifier, so it should only match the

On StackOverflow (here: https://stackoverflow.com/questions/78803652/why-does-gsub-in-r-match-one-character-too-many) there was a question about this result: > gsub("^([0-9]{,5}).*","\\1","123456789") [1] "123456" The OP expected "12345" as the result. Several points were raised: - The R docs don't mention the case of {,5} for the

I want to do something like produce a plot title of the form ``Sample size n = 42; critical value k_0 = 17.'' where the ``n'' is to be in a maths font and ``k_0'' indicates that the 0 is a subscript. (A la LaTeX.) But the values ``42'' and ``17'' are to be substituted in from the numeric values of R objects. After a bit of struggle I found that >

I''m building an app that needs i18n support across the entire database (i.e. localized attributes). In order to do this I''ve created a special HABTM join table that can be associated with _any_ other table: create table language_strings ( for_table varchar(255) not null, foreign_id int not null, language_id varchar(5) not null, attr_name varchar(255) not null, value text

I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ubuntu/ ) My configuration has worked nicely since 2009, but failed after a recent upgrade of dovecot (during basic upgrade from Ubuntu 18.04 to 18.10). The version of Alpine did not change.

Hi Aki, Thanks. I put that in the .conf file I mentioned, and it made no difference. Chris > Hi! > > In your case it's probably easiest to change > > service stats { > unix_listener stats-writer { > mode = 0666 > } > } > > Aki > > > On 31 December 2018 at 16:05 cpblpublic+dovecot at gmail.com wrote: > > > > > >

On 2015-12-30 09:58, Michael Felt wrote: > On 2015-12-29 11:02, Michael Felt wrote: >> This seems to be a problem that goes back a long time - and I hope >> someone who understands what tre is suppossed to be doing will look >> at this. >> >> A short history of other people who have reported on this on >> different versions of AIX. I shall only add that I

Ok, found the problem - on platforms that support it TRE uses wint_t (from wchar.h) as its type for characters (tre_cint_t) which on AIX is *signed* int. TRE uses liberally conversions between int and tre_cint_t apparently assuming that the latter is unsigned so conversions back to int are suitable for comparisons etc. On other platforms wint_t is unsigned so it works. Manually defining tre_cint_t

Hello Dovecot community, Below please find a patch that adds support to dovecot-1.2.11 for: - RFC 4467 - IMAP URLAUTH Extension - RFC 4468 - Submission BURL - RFC 4469 - IMAP CATENATE Extension URLAUTH URLAUTH is added as a plugin so it can be disabled to satisfy site security requirements. Each user's URLAUTH keys for all mailboxes are stored in a file named

Hi Aki, Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf # Pigeonhole version 0.5.2 () # OS: Linux 4.18.0-13-generic x86_64 Ubuntu 18.10 ext4 # Hostname: cpbl-t450s doveconf: Warning: please set