Manuel Lemos - 2012-09-15 04:31:06 - In reply to message 3 from Alan Fullmer
The class detects if the line break sequence of your OS is \n (for Linux/Unix) or \r\n (for Windows). I suspect that you are under Windows. Still the mail function should do the necessary conversions. Maybe it isn't the case.
Alan Fullmer - 2012-09-15 04:40:37 - In reply to message 4 from Manuel Lemos
Take a look at this. This is a view source to a Gmail message:
<p>Thank you and talk to you later</p>
Content-Type: multipart/related; boundary="94e8a694c944ec1e26111f51875b9443"
See how the --e8da39b5a054ed22e8f2f15d8140ecee-- is right up against the ending span tag? When I force it to \r\n the issue goes away.
I am still trying to determine where the issue lies.
Manuel Lemos - 2012-09-15 05:51:38 - In reply to message 5 from Alan Fullmer
As I mentioned, I suspect you are using Windows. In that case, there is a line break \n there which was not translated into \r\n which is required by SMTP to break lines. So I think that while you do not see the line break because Windows does not recognize it as such, it is there.
Alan Fullmer - 2012-09-15 06:00:41 - In reply to message 6 from Manuel Lemos
Well I'm not using Windows.
The server itself is a CentOS 6.x server running Zend's CE version of PHP.
Well either way, I will use the workaround for now. I just had to add an extra \n at the end of the body before I set it to the CreateQuotedPrintableHTMLPart function. That gave it the extra new line so the boundary doesn't get set on the same line.
Manuel Lemos - 2012-09-15 10:17:56 - In reply to message 7 from Alan Fullmer
Ah, since you said you added \r\n to the message, I thought it was a matter of line breaks.
Anyway, I just looked at the generated code and there was indeed a bug introduced in the last revision related with the need for line breaks between multipart message separators. The bug is fixed and a new version was uploaded. Just let me know if you find any other issues. Thank you for reporting.