search for: abnf

I need to write some documentation: I'm looking for a standard, consistent way of referring to the components and attributes of R data structures. Googling and Stackoverflow yield a variety of github sites that do not seem to be particularly authoritative. I was hoping to find a BNF/ABNF grammar for R. I've looked at the output of bison -v ./R-3.6.2/src/main/gram.y but it does not appear helpful. I appreciate any suggestions for where to look or what to do. Thanks, Steve -- Ever tried, Ever failed, No Matter: Try again, Fail again, Fail Better. Samuel Beckett *Worstward...

I'm using Evolution and Dovecot (on the localhost) and receiving these errors trying to move a message into the IMAP folder: C00095 APPEND INBOX (\Answered \Seen NotJunk "Junk" "NotJunk" "receipt-handled") {1022} C00095 BAD Error in IMAP command APPEND: Flags list contains non-atoms. Is this a Dovecot or Evolution bug? Thanks, Richard $ dovecot -n # 1.1.11:

...;m looking for a standard, consistent way of referring to the > components > > and attributes of R data structures. Googling and Stackoverflow yield a > > variety of github sites that do not seem to be particularly > authoritative. > > > > I was hoping to find a BNF/ABNF grammar for R. > > > > I've looked at the output of bison -v ./R-3.6.2/src/main/gram.y but it > does > > not appear helpful. > > > > I appreciate any suggestions for where to look or what to do. > > > > Thanks, Steve > > > > -- > >...

Hi there, Quoting RFC 3501 sec. 7.4.2 ?FETCH Response? (data item BODYSTRUCTURE): ?A body type of type MESSAGE and subtype RFC822 contains, immediately after the basic fields, the envelope structure, body structure, and size in text lines of the encapsulated message.? According the ABNF (RFC 3501 sec. 9) the envelope structure is that of the ENVELOPE FETCH data item, and the env-{from,sender,reply-to,to,cc, bcc} fields are non-space-separated address lists: body-type-msg = media-message SP body-fields SP envelope SP body SP body-fld-lines envelope = "(" env...

I was porting some email from one imap server location to another and ran into a feature of something. One of them writes message-id as 'Message-Id' and the other writes it as 'Message-ID'. Because of this, all the messages are forever different. All mail is delivered from postfix and will be in the future. But I'm asking which of these syntaxes is correct or if there is

I created a client library to send emails for a webapp. After connecting to the SMTP server with credential setup in CPANEL, and then do NOT add Message-Id header, the DKIM signature 'h' record created by dovecot/WHM is wrong, and a Message-ID (with a capital D) header is added, invalidating the generated DKIM signature value. This causes outlook, yahoo, gmail and other email

I'm looking at what would be involved in converting from MeetMe to ConfBridge and there seems to be a lot of missing administrative things, but I hope I'm just missing it. We all know about the missing realtime linkage. That's a major nuisance, but can be worked around. More serious is that the CLI command to display users in a ConfBridge don't show the caller ID information, so

...documentation: > > I'm looking for a standard, consistent way of referring to the components > and attributes of R data structures. Googling and Stackoverflow yield a > variety of github sites that do not seem to be particularly authoritative. > > I was hoping to find a BNF/ABNF grammar for R. > > I've looked at the output of bison -v ./R-3.6.2/src/main/gram.y but it does > not appear helpful. > > I appreciate any suggestions for where to look or what to do. > > Thanks, Steve > > -- > > Ever tried, Ever failed, No Matter: > > Try...

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello Stephan, GETSCRIPT does not return a literal, there is the + character missing before }: diff -r bcebda39c0ed src/managesieve/cmd-getscript.c - --- a/src/managesieve/cmd-getscript.c Mon Feb 18 14:13:12 2008 +0100 +++ b/src/managesieve/cmd-getscript.c Fri Feb 29 11:52:00 2008 +0100 @@ -112,7 +112,7 @@ return

Hi- I'm developing an IMAP client library in lua and tried using a literal form of the STATUS command. Dovecot rejected the command. I was successfully able to use a literal form of the LOGIN command, so I have some confidence in my code working properly. Is this correct and, if so, is there a list of IMAP commands that don't support the literal form? I searched hi and lo

...that incorrect FETCH parameters must return a BAD. I can verify that the above commands fail on Cyrus. I don't disagree that the way Dovecot handles this is correct - or at least is the way that I wish the RFCs were written. Since this seems a bit redundant, but is necessary under the ABNF: 1 UID FETCH 1:* UID (CHANGEDSINCE 1) -or- 1 UID FETCH 1:* (UID) (CHANGEDSINCE 1) michael

...e () a2 BAD Invalid arguments. According to RFC 4469 section 3 CATENATE requires "one or more message parts." This is formalized in section 5: append-data =/ "CATENATE" SP "(" cat-part *(SP cat-part) ")" and in RFC 3501 section 9 which states that "[ABNF] rules MUST be followed strictly." I believe that permitting zero cat-parts is contrary to the RFC, although I can understand permitting it under the general doctrine of "servers should be liberal in what they accept, and clients strict in what they send." Is accepting zero cat-par...

Hi Timo, >> * LIST (\HasNoChildren) "/" "folder1" >> * LIST (\HasNoChildren) "/" "folder2" >> * LIST (\HasNoChildren) "/" {9} >> six"wafer >> . OK List completed. >> >> Note the {9} length of the following real folder name. Is this normal >> handling of special folder names ? >Yes. Well,