SMTP returner should use email library to compose RFC2822 returner messages.

[aphor]

Eventually there will be problems with encoding of data or the need to produce multipart MIME messages handling returner data. Instead of hand-crafting messages as strings, the SMTP returner should use the standard library email module to construct and control valid RFC2822 messages containing returner data.

returners/smtp_return.py

https://docs.python.org/3/library/email.html

[aphor]

Besides providing control over encoding (and ensuring the email headers properly identify the encoded text), using a library like the email module will enable custom rich text or HTML messages for human consumption with attachments containing machine readable formats like JSON data.

[techhat]

Since we still need to maintain Python 2 compatibility, here's a more appropriate link: https://docs.python.org/2/library/email.html

[sjorge]

Having it use the same backend as https://github.com/saltstack/salt/blob/develop/salt/states/smtp.py would be more consistent no?

Perhaps that backend could use some love too, i think it uses the smtp module

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.

[aphor]

I'm going to need this soon I think, and so I'd like to keep the ticket around to anchor work.

[stale]

Thank you for updating this issue. It is no longer marked as stale.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

If this issue is closed prematurely, please leave a comment and we will gladly reopen the issue.