Christian Loitsch
Christian Loitsch
Mention inline images in README. (content-id should contain an `@` !) mailer should add the `` to the content-id. kind of a duplicate of #85
instead of ending DATA with '\r\n.\r\n' many smtp server support CHUNKING rfc3030. As a client we don't really care about encoding '\r\n.\r\n' but CHUNKING is a requirement for BINARYMIME which...
rfc6531 allows utf8 encoded mail addresses for both the local and domain part. A server supporting this extension returns SMTPUTF8 in the EHLO response.
RFC 5890 provides support for encoding non-ASCII domain names in the Domain Name System This encoding should only be used if the server does not support SMTPUTF8 (separate issue.)
[ '1', 3 ] should result in '"1",3' Currently 1 is not quoted.
Far too many documents use the system eol encoding. It shouldn't be a problem to accept both.
this branch tries to make the arduino platform optional, so that the library may be used on other platforms. Is this something you would even consider merging? Note that I...
replace String with const char* replace copies with const references. RFC: would you consider merging this? Is there anything, you would like me to change? This code compiles, but I...