Mail_Mbox::_process (Previous) (Next) Mail_Mime::Mail_Mime()

View this page in Last updated: Mon, 02 Jul 2007
English | Dutch | French | German | Hungarian | Japanese | Polish | Russian | Spanish | Plain HTML

Mail_Mime

Spis treści
Mail_Mime::Mail_Mime() -- creates a new instance
Mail_Mime::addAttachment() -- add attachment
Mail_Mime::addHTMLImage() -- add image to message
Mail_Mime::get() -- build the message
Mail_Mime::headers() -- build the header lines
Mail_Mime::setHTMLBody() -- set HTML part
Mail_Mime::setTxtBody() -- set plain text part
Mail_Mime - Example -- generation and sending of a MIME mail
Mail_mimePart::Mail_mimePart() -- constructor
Mail_mimePart::addsubpart() -- add sub part to a MIME part
Mail_mimePart::encode() -- encode a mail
Mail_mimeDecode::Mail_mimeDecode() -- constructor
Mail_mimeDecode::decode() -- perform decoding
Mail_mimeDecode::uudecode() -- decode of UU-coded data
Mail_mimeDecode::getXML() -- create XML representation of MIME parts
Mail_mimeDecode - Example -- decode an email

Pakiet pozwalający łatwo tworzyć skomplikowane emaile (multipart). Jeżeli poszukujesz prostego API do tworzenia takich emaili, to klasa Mail_Mime prawdopodobnie wystarczy. Jeżeli nie wystarczy, to klasa Mail_mimePare oferuje większą kontrolę nad tworzeniem MIME.

Mail_mimeDecode udostępnia API dla dekodowania danych MIME.

Mail_Mbox::_process (Previous) (Next) Mail_Mime::Mail_Mime()

Download Documentation Last updated: Mon, 02 Jul 2007
Do you think that something on this page is wrong? Please file a bug report or add a note.
User Notes:
Note by: PixEye
If you want to use a special charset encoding (UTF-8 for example) and/or use base64 instead of quoted-printable, you should use the optional array parameter of function get(). See the API documentation for list of options supported. HTH.
Note by: zarthras
I'd like to point out, that there are quite a few more methods to the mime object than listed here. Among them such important helpers like

setSubject()
setFrom()
adBcc()

and so on. I'm not sure why they weren't put in the documentation, but you will find all of them in the api docs.