NewAttachmentOptions Enumeration |
Namespace: MailBee.MimeAssembly: MailBee.NET (in MailBee.NET.dll) Version: 12.5.0 build 687 for .NET 4.5
Syntax [FlagsAttribute]
public enum NewAttachmentOptions
<FlagsAttribute>
Public Enumeration NewAttachmentOptions
Members
| Member name | Value | Description |
---|
| None | 0 |
No additional options.
|
| ReplaceIfExists | 1 |
If the attachment with such name already exists in collection, it will be replaced with the newly created one.
Otherwise, the newly created attachment will be appended to collection.
|
| Inline | 2 |
Forcibly add the attachment as inline object. This causes MailBee to insert "Content-Disposition: inline" instead of "Content-Disposition: attachment" in the header section.
|
| NoDefaultHeaders | 4 |
Add only custom headers (specified by customHeaders parameter of
Add(String, String, String, String, HeaderCollection, NewAttachmentOptions, MailTransferEncoding))
method) and do not produce any default headers.
|
| PathIsUri | 8 |
The path to the attachment is a URI (URL) rather than filesystem path. Example is http://www.domain.com/picture.gif.
If this flag is not set, filesystem path will be assumed (e.g. C:\Inetpub\wwwroot\picture.gif).
This flag has no effect for those overloads of Add(String, String, String, String, HeaderCollection, NewAttachmentOptions, MailTransferEncoding)
method which add the attachment from memory rather than from a file.
|
| NoContentDispositionForInline | 16 |
If Inline flag is set, NoContentDispositionForInline flag will cause the header section not contain Content-Disposition header at all.
Because "inline" is the default value of Content-Disposition parameter in MIME, it's usually safe to omit it completely for inline attachments. Note that not including
Content-Disposition header will also cause its "filename" parameter not being set.
|
See Also