Name Description Size
MimeEncoder.h 1548
MimeHeaderParser.h This is used to signal that the input header value has already been decoded according to RFC 2047 and is in UTF-16 form. 6567
moz.build 700
msgIStructuredHeaders.idl A collection of MIME headers that are stored in a rich, structured format. The structured forms defined in this method use the structured decoder and encoder functionality found in jsmime to interconvert between the raw string forms found in the actual message text and the structured forms supported by this interface. The alternative modes of access for specific headers are expected to only work for the headers for which that mode of access is the correct one. For example, retrieving the "To" header from getUnstructuredHeader would fail, since the To header is not an unstructured header but an addressing header. They are provided mostly as a convenience to C++ which is much less able to utilize a fully generic format. With the exception of mismatched headers, the methods do not throw an exception if the header is missing but rather return an appropriate default value as indicated in their documentation. 6656
nsIMimeContentTypeHandler.idl This interface is implemented by content type handlers that will be called upon by libmime to process various attachments types. The primary purpose of these handlers will be to represent the attached data in a viewable HTML format that is useful for the user Note: These will all register by their content type prefixed by the following: mimecth:text/vcard libmime will then use the XPCOM Component Manager to locate the appropriate Content Type handler 1265
nsIMimeConverter.idl Encode/decode mail headers (via libmime). 2979
nsIMimeEmitter.idl Write the HTML Headers for the current attachment. Note: Book case this with an EndHeader call. @param name The name of this attachment. 2945
nsIMimeHeaders.idl An interface that can extract individual headers from a body of headers. 1487
nsIMimeObjectClassAccess.h This interface is implemented by libmime. This interface is used by a Content-Type handler "Plug In" (i.e. vCard) for accessing various internal information about the object class system of libmime. When libmime progresses to a C++ object class, this would probably change. 2033
nsIMimeStreamConverter.idl This interface contains mailnews mime specific information for stream converters. Most of the code is just stuff that has been moved out of nsIStreamConverter.idl to make it more generic. 2942
nsIMsgHeaderParser.idl A structured representation of an address. This is meant to correspond to the address production from RFC 5322. As a result, an instance of this interface is either a single mailbox or a group of mailboxes. The difference between the two forms is in which attribute is undefined: mailboxes leave the members attribute undefined while groups leave the email attribute undefined. For example, an address like "John Doe <jdoe@machine.example>" will, when parsed, result in an instance with the name attribute set to "John Doe", the email attribute set to "jdoe@machine.example", and the members variable left undefined. A group like "undisclosed-recipients:;" will, when parsed, result in an instance with the name attribute set to "undisclosed-recipients", the email attribute left defined, and the members variable set to an empty array. In general, the attributes of this interface are always meant to be in a form suitable for display purposes, and not in a form usable for MIME emission. In particular, email addresses could be fully internationalized and non-ASCII, RFC 2047-encoded words may appear in names, and the name or email parameters are unquoted. 8990
nsIPgpMimeProxy.idl 815c4fbe-0e7c-45b6-8324-f7044c7252ac 2933
nsISimpleMimeConverter.idl nsISimpleMimeConverter provides an interface for rendering raw mime objects as HTML. It's used to provide converters for mime types not handled directly by the mime code. "text/calendar" - see calendar/base/src/CalMimeConverter.sys.mjs "text/vcard" - see mailnews/addrbook/modules/VCardUtils.sys.mjs 2043
nsMailHeaders.h This interface allows any module to access the encoder/decoder routines for RFC822 headers. This will allow any mail/news module to call on these routines. 3707