Allow storing attachment binary data within the clixml file #10
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
September 5, 2024 13:18
…chment's binary in the serialised mail object.
Author
|
Additional commit allow -To and -Attachments to accept arrays. Added Bcc and Priority (using an enum for tab completion) |
Member
|
Heya @jebbster88 , |
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Occasionally I have scripts that generate an attachment and send an email within a loop. The current MailDaemon approach of storing the path with the email object would result in the final attachment being used for all emails when sent.
These changes add a -PersistAttachments switch to Send-MDMail which serializes the attachment binary into the clixml file.