… gnu.org bug#27476 ; Package guix (Sat, 24 Jun 2017 16:33:01 GMT) Full text and rfc822 format available. Acknowledgement sent to Leo Famulari <leo <at> famulari.name> New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org (Sat, 24 Jun 2017 16:33:02 GMT) Full te…
… gnu.org bug#28144 ; Package guix (Sat, 19 Aug 2017 00:21:01 GMT) Full text and rfc822 format available. Acknowledgement sent to Christopher Baines <mail <at> cbaines.net> New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org (Sat, 19 Aug 2017 00:21:01 GMT) Fu…
…to the archive, but not yet accepted, can be seen here You can also look at the RFC822 version Packages uploaded and accepted, but not yet installed into the pool locations are to be found here until the dinstall cron run moves them into the pool. RSS feeds are available for pack…
…-822 ] standard, and as a consequence several fetch items in IMAP incorporate " RFC822 " in their name. With the exception of RFC822 .SIZE, there are more modern replacements; for example, the modern version of RFC822 .HEADER is BODY.PEEK[HEADER]. In all cases, " RFC822 " should …
…-822 ] standard, and as a consequence several fetch items in IMAP incorporate " RFC822 " in their name. With the exception of RFC822 .SIZE, there are more modern replacements; for example, the modern version of RFC822 .HEADER is BODY.PEEK[HEADER]. In all cases, " RFC822 " should …
…-822 ] standard, and as a consequence several fetch items in IMAP incorporate " RFC822 " in their name. With the exception of RFC822 .SIZE, there are more modern replacements; for example, the modern version of RFC822 .HEADER is BODY.PEEK[HEADER]. In all cases, " RFC822 " should …
…: bug#14388 ; Package coreutils . (Sat, 11 May 2013 17:53:03 GMT) Full text and rfc822 format available. Acknowledgement sent to vevek venkatesan <vevekvece <at> gmail.com> : New bug report received and forwarded. Copy sent to bug-coreutils <at> gnu.org . (Sat, 11 May 2013 17:53:…
… gnu.org bug#75157 ; Package guix (Sat, 28 Dec 2024 08:54:02 GMT) Full text and rfc822 format available. Acknowledgement sent to Dariqq <dariqq <at> posteo.net> New bug report received and forwarded. Copy sent to bug-guix <at> gnu.org (Sat, 28 Dec 2024 08:54:02 GMT) Full text and…
…made, the assertion often takes the form of a list of attributes and values. In RFC822 format messages, such as mail messages and HTTP messages, metadata is transferred where the attribute name is an RFC822 header name and the rest of the RFC822 line is the value of the attribute…
US
rfc3501
https://www.rfc-editor.org/rfc/inline-errata/rfc3501.html
…FC-822] standard, and as a consequence several fetch items in IMAP incorporate "RFC822" in their name. With the exception of RFC822.SIZE, there are more modern replacements; for example, the modern version of RFC822.HEADER is BODY.PEEK[HEADER]. In all cases, "RFC822" should be in…
…......... 28 5.2 Message Media Type .................................. 28 5.2.1 RFC822 Subtype .................................... 28 5.2.2 Partial Subtype ................................... 29 5.2.2.1 Message Fragmentation and Reassembly ............ 30 5.2.2.2 Fragmentation a…
US
rfc2046
https://www.rfc-editor.org/rfc/inline-errata/rfc2046.html
…......... 28 5.2 Message Media Type .................................. 28 5.2.1 RFC822 Subtype .................................... 28 5.2.2 Partial Subtype ................................... 29 5.2.2.1 Message Fragmentation and Reassembly ............ 30 5.2.2.2 Fragmentation a…
…FC-822] standard, and as a consequence several fetch items in IMAP incorporate "RFC822" in their name. With the exception of RFC822.SIZE, there are more modern replacements; for example, the modern version of RFC822.HEADER is BODY.PEEK[HEADER]. In all cases, "RFC822" should be in…
…......... 28 5.2 Message Media Type .................................. 28 5.2.1 RFC822 Subtype .................................... 28 5.2.2 Partial Subtype ................................... 29 5.2.2.1 Message Fragmentation and Reassembly ............ 30 5.2.2.2 Fragmentation a…
…......... 28 5.2 Message Media Type .................................. 28 5.2.1 RFC822 Subtype .................................... 28 5.2.2 Partial Subtype ................................... 29 5.2.2.1 Message Fragmentation and Reassembly ............ 30 5.2.2.2 Fragmentation a…
Page 1
Next →