You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ability to have more flexible attachments (other than just specifying path) would be useful.
The easiest way to do this is to change the $AttachmentParameter to [object[]] type and rely on MimeKit.AttachmentCollection.Add() which supports both Strings and MimeEntity
Although this doesn't really help with LinkedResources for things like changing changing attachment meta-data, such as Content-Disposition and Content-Id which is required for inline images in HTML emails in some emails. Perhaps LinkedResources can be exposed as a parameter too? Could be a number of ways to implement this as a more polished easy-to-use solution, maybe a separate -InlineAttachments Parameter that handles both?
The ability to have more flexible attachments (other than just specifying path) would be useful.
The easiest way to do this is to change the
$Attachment
Parameter to[object[]]
type and rely on MimeKit.AttachmentCollection.Add() which supports both Strings andMimeEntity
Although this doesn't really help with LinkedResources for things like changing changing attachment meta-data, such as
Content-Disposition
andContent-Id
which is required for inline images in HTML emails in some emails. Perhaps LinkedResources can be exposed as a parameter too? Could be a number of ways to implement this as a more polished easy-to-use solution, maybe a separate-InlineAttachments
Parameter that handles both?https://www.mimekit.net/docs/html/Creating-Messages.htm#UsingBodyBuilder
The text was updated successfully, but these errors were encountered: