Line 125 in includes/destinations.email.inc is:

125 $multipart = "Content-Type: multipart/mixed; boundary = $boundary\n\nThis is a MIME encoded message.\n\n--$boundary";

Sec 5.1 of RFC2045 ( http://www.ietf.org/rfc/rfc2045.txt ) doesn't allow for space between parameters or the '=' character. This causes problems with MIME part parsing in the MTA that my employer sells because we're being RFC-strict. We can build in some leniency ( once we define what the limit of that leniency is ) but the email generated by the backup_migrate was specifically called out by our customer who is currently experiencing the issue.

Comments

ronan’s picture

Status: Active » Needs work

I don't use the email destination at all, but if you can post a patch that you have confirmed works with your client's system I'll commit it for you.

couturier’s picture

Status: Needs work » Closed (outdated)