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.
I encountered some encoding problem when send email attachment with non-ascii filename, as these 2 posts described:
Sending MIME-encoded email attachments with utf-8 filenames
How to encode the filename parameter of Content-Disposition header in HTTP?
so I create a patch to add non-ascii attach filename support.
Example :
sendEmail -u 华夏 -m 华夏 -o message-charset=utf8 -f [email protected] -t [email protected] -a 华夏.txt