
	Where results make sense

Topic: RFC 2049

Related Topics

MMO

Horsham, Pennsylvania

Grand Theft Auto Advance

Universal translator

Taxodium

Tallit

Homa Hills, Wyoming

Masai

520s BCE

List of state leaders in 1585

In the News (Mon 28 Dec 09)

Northern Trust

Marvin Harrison

Peter Chernin

Gary Locke

Match Play

Penelope Cruz

Mickey Rourke

AR Rahman

Danny Boyle

Hugh Jackman

	RFC 2045 (rfc2045) - Multipurpose Internet Mail Extensions (MIME) Part One
		RFC 1049 used a simpler and less powerful syntax, but one that is largely compatible with the mechanism given here.
		RFC 2046 provides a mechanism for noting the addition of such padding in the case of the application/octet-stream media type, which has a "padding" parameter.
		RFC 2045: is it permitted to have two content-type: headers where the first replaces the...
	www.faqs.org /rfcs/rfc2045.html (8188 words)

	RFC 2047 (rfc2047) - MIME (Multipurpose Internet Mail Extensions) Part Thr
		Introduction RFC 2045 describes a mechanism for denoting textual body parts which are coded in various character sets, as well as methods for encoding such body parts as sequences of printable US-ASCII characters.
		The ABNF definition for 'phrase' from RFC 822 thus becomes: phrase = 1(encoded-word / word) In this case the set of characters that may be used in a "Q"-encoded 'encoded-word' is restricted to: ASCII letters, decimal digits, "!", "", "+", "-", "/", "=", and "_" (underscore, ASCII 95.)>.
		RFC 2047: There appears to be a conflict in the RFC between the ABNF for an "encoded-word"...
	www.faqs.org /rfcs/rfc2047.html (3616 words)

	RFC2049 (Site not responding. Last check: )
		RFC 2049 MIME Conformance November 1996 Message: -- Recognize and display at least the RFC822 message encapsulation (message/rfc822) in such a way as to preserve any recursive structure, that is, displaying or offering to display the encapsulated data in accordance with its media type.
		RFC 2049 MIME Conformance November 1996 The following guidelines may be useful to anyone devising a data format (media type) that is supposed to survive the widest range of networking technologies and known broken MTAs unscathed.
		RFC 2049 MIME Conformance November 1996 period (".") alone on a line is known to be corrupted by some (incorrect) SMTP implementations, and a line that starts with the five characters "From " (the fifth character is a SPACE) are commonly corrupted as well.
	rfc.net /rfc2049.html (5382 words)

	RFC 2045 - (rfc2045) - Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies
		RFC 1049 used a simpler and less powerful syntax, but one that is largely compatible with the mechanism given here.
		RFC 2046 provides a mechanism for noting the addition of such padding in the case of the application/octet-stream media type, which has a "padding" parameter.
		No restrictions imposed by either RFC 821 or RFC 822 are violated, and care has been taken to avoid problems caused by additional restrictions imposed by the characteristics of some Internet mail transport mechanisms (see RFC 2049).
	www.rfcsearch.org /rfcview/RFC/2045 (8226 words)

	rfc2049
		Freed and Borenstein Standards Track [Page 4] RFC 2049 MIME Conformance November 1996 Message: -- Recognize and display at least the RFC822 message encapsulation (message/rfc822) in such a way as to preserve any recursive structure, that is, displaying or offering to display the encapsulated data in accordance with its media type.
		Freed and Borenstein Standards Track [Page 6] RFC 2049 MIME Conformance November 1996 The following guidelines may be useful to anyone devising a data format (media type) that is supposed to survive the widest range of networking technologies and known broken MTAs unscathed.
		In particular, a Freed and Borenstein Standards Track [Page 8] RFC 2049 MIME Conformance November 1996 period (".") alone on a line is known to be corrupted by some (incorrect) SMTP implementations, and a line that starts with the five characters "From " (the fifth character is a SPACE) are commonly corrupted as well.
	ietfreport.isoc.org /idref/rfc2049 (5543 words)

	RFC 2046 (rfc2046) - Multipurpose Internet Mail Extensions (MIME) Part Two
		The "partial" subtype is defined for partial RFC 822 messages, to permit the fragmented transmission of bodies that are thought to be too large to be passed through transport facilities in one piece.
		RFC 1341 also defined the use of a "NAME" parameter which gave a suggested file name to be used if the data were to be written to a file.
		However, unlike top-level RFC 822 messages, the restriction that each "message/rfc822" body must include a "From", "Date", and at least one destination header is removed and replaced with the requirement that at least one of "From", "Subject", or "Date" must be present.
	www.faqs.org /rfcs/rfc2046.html (12520 words)

	RFC2047
		RFC 2047 Message Header Extensions November 1996 Instead, certain sequences of "ordinary" printable ASCII characters (known as "encoded-words") are reserved for use as encoded data.
		RFC 2047 Message Header Extensions November 1996 IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC 822 parser.
		RFC 2047 Message Header Extensions November 1996 (=?ISO-8859-1?Q?a_b?=) (a b) In order to cause a SPACE to be displayed within a portion of encoded text, the SPACE MUST be encoded as part of the 'encoded-word'.
	www.rfc.net /rfc2047.html (3643 words)

	(MIME) Part Three: Message Header Extensions for Non-ASCII Text
		RFC 2045, which specifies the various headers used to describe the structure of MIME messages.
		RFC 2049, which describes MIME conformance criteria and provides some illustrative examples of MIME message formats, acknowledgements, and the bibliography.
		RFC 2045 describes a mechanism for denoting textual body parts which are coded in various character sets, as well as methods for encoding such body parts as sequences of printable US-ASCII characters.
	www.mhonarc.org /~ehood/MIME/2047/rfc2047.html (3885 words)

	RFC 2045: Multipurpose Internet Mail Extensions (MIME) Part One
		A Content-Type header field, generalized from RFC 1049, which can be used to specify the media type and subtype of data in the body of a message and to fully specify the native representation (canonical form) of such data.
		Since RFC 822 was published in 1982, there has really been only one format standard for Internet messages, and there has been little perceived need to declare the format standard in use.
		Note that the definition of "tspecials" is the same as the RFC 822 definition of "specials" with the addition of the three characters "/", "?", and "=", and the removal of ".".
	www.hunnysoft.com /rfc/rfc2045.html (8107 words)

	RFC 2049 - Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
		RFC 821 MTAs are prohibited from altering the character of white space or wrapping long lines.
		For example, the local newline convention for text bodies might be carried through to the encoder itself along with knowledge of what that format is. (2) The output of the encoders may have to pass through one or more additional steps prior to being transmitted as a message.
		As such, the output of the encoder may not be conformant with the formats specified by RFC 822.
	tools.ietf.org /html/rfc2049 (5546 words)

	Roxen Community: RFC 2045 Multipurpose Internet Mail Extensions (MIME) Part One: Format of Internet Message Bodies ...
		The term "message", when not further qualified, means either a (complete or "top-level") RFC 822 message being transferred on a network, or a message encapsulated in a body of type "message/rfc822" or "message/partial".
		Since RFC 822 was published in 1982, there has really been only one format standard for Internet messages, and there has been little perceived need to declare the format standard in use.
		Note that the definition of "tspecials" is the same as the RFC 822 definition of "specials" with the addition of the three characters "/", "?", and "=", and the removal of ".".
	community.roxen.com /developers/idocs/rfc/rfc2045.html (8589 words)

	[No title]
		As media types are used in new environments, where the proliferation of media types is not a hindrance to interoperability, the original procedure was excessively restrictive and had to be generalized.
		However, the restrictions set forth in RFC 1602 on the use of patented technology in standards-track protocols must be respected when the specification of a media type is part of a standards-track protocol.
		RFC publication of vendor and personal media type proposals is encouraged but not required.
	www.ietf.org /rfc/rfc2048.txt (5283 words)

	Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
		The meaning of this phrase is that it is assumed to be "safe" to send virtually any kind of properly-marked data to users of such mail systems, because such systems will at least be able to treat the data as undifferentiated binary, and will not simply splash it onto the screen of unsuspecting users.
		The vital aspect of this discussion is that, in spite of any optimizations, collapsings of required steps, or insertion of additional processing, the resulting messages must be consistent with those produced by the model described here.
		These documents are a revision of RFC 1521, 1522, and 1590.
	xml.resource.org /public/rfc/html/rfc2049.html (4674 words)

	RFC2045 (Site not responding. Last check: )
		Default RFC 822 messages without a MIME Content-Type header are taken by this protocol to be plain text in the US-ASCII character set, which can be explicitly specified as: Content-type: text/plain; charset=us-ascii This default is assumed if no Content-Type header field is specified.
		RFC 2045 Internet Message Bodies November 1996 is already in a 7bit mail-ready representation.
		RFC 2045 Internet Message Bodies November 1996 respectively, but MUST NOT be so represented at the end of an encoded line.
	rfc.net /rfc2045.html (8102 words)

	RFC 2047 (rfc2047)
		Introduction RFC 2045 describes a mechanism for denoting textual body parts which are coded in various character sets, as well as methods for encoding such body parts as sequences of printable US-ASCII characters.
		Like the encoding techniques described in RFC 2045, the techniques outlined here were designed to allow the use of non-ASCII characters in message headers in a way which is unlikely to be disturbed by the quirks of existing Internet mail handling programs.
		Moore Standards Track [Page 12] RFC 2047 Message Header Extensions November 1996 (=?ISO-8859-1?Q?a_b?=) (a b) In order to cause a SPACE to be displayed within a portion of encoded text, the SPACE MUST be encoded as part of the 'encoded-word'.
	www.cse.ohio-state.edu /cgi-bin/rfc/rfc2047.html (3282 words)

	RFC 2049 (rfc2049) - Multipurpose Internet Mail Extensions (MIME) Part Fiv
		RFC 2049: Wow, design is much better from my last visit,my respect!
		RFC 2049: in the example given, --unique-boundary-2 Content-Type: audio/basic...
		RFC 2049: Can you guys get someone to volunteer and re-write your docs in layman's terms?...
	www.faqs.org /rfcs/rfc2049.html (5392 words)

	RFC 2047 - MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text. K. ...
		RFC 2047 Message Header Extensions November 1996 5.
		RFC 2047 Message Header Extensions November 1996 6.
		RFC 2047 Message Header Extensions November 1996 10.
	rfc.dotsrc.org /rfc/rfc2047.html (3719 words)

	[No title]
		Freed & Borenstein Standards Track [Page 28] RFC 2046 Media Types November 1996 It should be noted that, despite the use of the numbers "822", a "message/rfc822" entity isn't restricted to material in strict conformance to RFC822, nor are the semantics of "message/rfc822" objects restricted to the semantics defined in RFC822.
		Freed & Borenstein Standards Track [Page 29] RFC 2046 Media Types November 1996 Because some message transfer agents may choose to automatically fragment large messages, and because such agents may use very different fragmentation thresholds, it is possible that the pieces of a partial message, upon reassembly, may prove themselves to comprise a partial message.
		Freed & Borenstein Standards Track [Page 36] RFC 2046 Media Types November 1996 Because mail servers accept a variety of syntaxes, some of which is multiline, the full command to be sent to a mail server is not included as a parameter in the content-type header field.
	www.ietf.org /rfc/rfc2046.txt (12769 words)

	[No title]
		Moore Standards Track [Page 4] RFC 2047 Message Header Extensions November 1996 IMPORTANT: 'encoded-word's are designed to be recognized as 'atom's by an RFC 822 parser.
		The ABNF definition for 'phrase' from RFC 822 thus becomes: phrase = 1*(encoded-word / word) In this case the set of characters that may be used in a "Q"-encoded 'encoded-word' is restricted to:
		Moore Standards Track [Page 12] RFC 2047 Message Header Extensions November 1996 (=?ISO-8859-1?Q?a_b?=) (a b) In order to cause a SPACE to be displayed within a portion of encoded text, the SPACE MUST be encoded as part of the 'encoded-word'.
	www.rfc-editor.org /rfc/rfc2047.txt (3282 words)

	[No title]
		Up to the Yergeau Standards Track [Page 1] RFC 2279 UTF-8 January 1998 present time, changes in Unicode and amendments to ISO/IEC 10646 have tracked each other, so that the character repertoires and code point assignments have remained in sync.
		As long as a character set standard does not change incompatibly, version numbers serve no purpose, because one gains nothing by learning from the tag that newly assigned characters may be received that one doesn't know about.
		Yergeau Standards Track [Page 6] RFC 2279 UTF-8 January 1998 In practice, then, a version-independent label is warranted, provided the label is understood to refer to all versions after Amendment 5, and provided no incompatible change actually occurs.
	www.ietf.org /rfc/rfc2279.txt (2481 words)

	Internet mail: standards
		RFC 2822 defines the basic format of a mail message.
		RFC 2049 together describe the Multipurpose Internet Mail Extensions, better known as MIME.
		RFC 1855 contains Netiquette Guidelines, describing social issues using mail and other electronic communication media.
	www.lemis.com /email/email-rfc.html (407 words)

	(MIME) Part Five: Conformance Criteria and Examples
		Rose, M. and E. Stefferud, "Proposed Standard for Message Encapsulation", RFC 934, Delaware and NMA, January 1985.
		Postel, J., "Instructions to RFC Authors", RFC 1543, USC/Information Sciences Institute, October 1993.
		Resnick, P., and A. Walker, "The text/enriched MIME Content-type", RFC 1896, February, 1996.
	www.mhonarc.org /~ehood/MIME/2049/rfc2049.html (5247 words)

	MHonArc Reference -- Appendix: MIME Conformance
		MIME-conformance is defined in section 2 of RFC 2049: (MIME) Part Five: Conformance Criteria and Examples.
		It should be noted that the criteria listed in RFC 2049 is geared towards interactive MUAs; therefore, some criteria may not be applicable to MHonArc.
		Support for RFC 2369, The Use of URLs as Meta-Syntax for Core Mail List Commands and their Transport through Message Header Fields.
	hydra.nac.uci.edu /indiv/ehood/MHonArc/doc/app-mimeconf.html (1341 words)

	rfc2049 RFC 2049 Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples
		B. Changes from RFC 1521, 1522, and 1590.................
		RFC 821 MTAs are prohibited from altering the
		Encapsulation", RFC 934, Delaware and NMA, January 1985.
	www.robtex.com /rfc/rfc2049.html (3633 words)

	MIME (Multipurpose Internet Mail Extensions) Part Three: Message Header Extensions for Non-ASCII Text [RFC-Ref]
		These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049
		) said so little about message bodies, these documents are largely orthogonal to (rather than a revision of) RFC 822
		These documents are revisions of RFCs 1521(-> 2049
	www.rfc-ref.org /RFC-TEXTS/2047 (393 words)

	rfc2049
		Press here to go to the top of the rfc 'tree'.
		--unique-boundary-2-- --unique-boundary-1 Content-type: text/enriched This is <bold><italic>enriched.</italic></bold> <smaller>as defined in RFC 1896</smaller> Isn't it <bigger><bigger>cool?</bigger></bigger> --unique-boundary-1 Content-Type: message/rfc822 From: (mailbox in US-ASCII) To: (address in US-ASCII) Subject: (subject in US-ASCII) Content-Type: Text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: Quoted-printable...
		[RFC-1345] Simonsen, K., "Character Mnemonics & Character Sets", RFC 1345, Rationel Almen Planlaegning, June 1992.
	www.nalanda.nitc.ac.in /misc/rfc/html/rfc2049.html (5543 words)

	Multipurpose Internet Mail Extensions (MIME) Part Five: Conformance Criteria and Examples [RFC-Ref]
		These documents are based on earlier work documented in RFC 934, STD 11, and RFC 1049
		The initial document in this set, RFC 2045
		These documents are revisions of RFCs 1521(-> 2049
	rfc-ref.org /RFC-TEXTS/2049/index.html (354 words)

Try your search on: Qwika (all wikis)