String, Buffer or a Stream contents for the attachmentent
optional content disposition type for the attachment, defaults to ‘attachment’
optional transfer encoding for the attachment, if not set it will be derived from the contentType property. Example values: quoted-printable, base64. If it is unset then base64 encoding is used for the attachment. If it is set to false then previous default applies (base64 for most, 7bit for text).
optional content type for the attachment, if not set will be derived from the filename property
If set and content is string, then encodes the content to a Buffer using the specified encoding. Example values: base64, hex, binary etc. Useful if you want to use binary attachments in a JSON formatted e-mail object
filename to be reported as the name of the attached file, use of unicode is allowed. If you do not want to use a filename, set this value as false, otherwise a filename is generated automatically
is an object of additional headers
path to a file or an URL (data uris are allowed as well) if you want to stream the file instead of including it (better for larger attachments)
an optional value that overrides entire node content in the mime message. If used then all other options set for this node are ignored.
Generated using TypeDoc
optional content id for using inline images in HTML message source. Using cid sets the default contentDisposition to 'inline' and moves the attachment into a multipart/related mime node, so use it only if you actually want to use this attachment as an embedded image