commit | d6ceeee24cc81582f9596bc9ab0798d2a0e21e2d | [log] [tgz] |
---|---|---|
author | Dusan Kasan <me@dusankasan.com> | Sat Apr 29 00:22:21 2017 +0200 |
committer | Dusan Kasan <me@dusankasan.com> | Sat Apr 29 00:22:21 2017 +0200 |
tree | 9961dd9d5d68fc288c349130a0d45811a6d09647 | |
parent | b974c63f34a6a46ae21074ec0c6a7c9187ec99f0 [diff] |
Docs updated
This library allows for parsing an email message into a more convenient form than the net/mail
provides. Where the net/mail
just gives you a map of header fields and a io.Reader
of its body, Parsemail allows access to all the standard header fields set in RFC5322, html/text body as well as attachements/embedded content as binary streams with metadata.
You just parse a io.Reader that holds the email data. The returned Email struct contains all the standard email information/headers as public fields.
var reader io.Reader // this reads an email message email, err := parsemail.Parse(reader) // returns Email struct and error if err != nil { // handle error } fmt.Println(email.Subject) fmt.Println(email.From) fmt.Println(email.To) fmt.Println(email.HTMLBody)
Attachments are a easily accessible as Attachment
type, containing their mime type, filename and data stream.
var reader io.Reader email, err := parsemail.Parse(reader) if err != nil { // handle error } for _, a := range(email.Attachments) { fmt.Println(a.Filename) fmt.Println(a.ContentType) //and read a.Data }
You can access embedded files in the same way you can access attachments. THey contain the mime type, data stream and content id that is used to reference them through the email.
var reader io.Reader email, err := parsemail.Parse(reader) if err != nil { // handle error } for _, a := range(email.EmbeddedFiles) { fmt.Println(a.CID) fmt.Println(a.ContentType) //and read a.Data }