NewAttachmentOptions Enumeration
Defines the available flags affecting how a new Attachment object will be created by Add(String, String, String, String, HeaderCollection, NewAttachmentOptions, MailTransferEncoding) method and its overloads which accept options parameter.

Namespace: MailBee.Mime
Assembly: MailBee.NET (in MailBee.NET.dll) Version: 11.2.0 build 590 for .NET 4.5
Syntax
[FlagsAttribute]
public enum NewAttachmentOptions
Members
  Member nameValueDescription
None0 No additional options.
ReplaceIfExists1 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.
Inline2 Forcibly add the attachment as inline object. This causes MailBee to insert "Content-Disposition: inline" instead of "Content-Disposition: attachment" in the header section.
NoDefaultHeaders4 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.
PathIsUri8 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.
NoContentDispositionForInline16 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