Skip to content
This repository has been archived by the owner on Jan 30, 2020. It is now read-only.

Random spaces or broken characters in html mails with a lot of content #29

Open
stevleibelt opened this issue Jul 7, 2017 · 4 comments

Comments

@stevleibelt
Copy link

stevleibelt commented Jul 7, 2017

Hello,

we encountered an issue when sending multipart emails (html and text) with a lot of content.
There either random spaces inside the source code of the mail or broken characters because of invalid character entities.

Since things are working fine when we use the swiftmailer, we could get an idea where the error could be.

According to the RFC 2045 (search for "76"), you are doing a a hard line break instead of a soft line break after 76 characters (see Zend\Mime\Part and search for 76).
Swiftmailer is handling this 76 character limitation totally differently.
Since this is not an easy topic my thoughts are no having any kind of offense inside. My Intension is to put you into the right direction.

How can you reproduce this issue?
Send a multipart email with a lot of content in html and text.

Best regards,
Stev

[Update]
It would be cool if you could put the link to the RFC 2045 as close to the code as possible.
It took me a while to get the sense behind this "76" number when I had a look into the code.

What about this way?

    'line-length'      => 76, //@link** http://www.faqs.org/rfcs/rfc2045.html

Or put the "76" as constant on top and add the link as comment?

@jobleadsorder
Copy link

Is there a change of getting an update for this ticket?

@weierophinney
Copy link
Member

@stevleibelt Could you provide a sample email that demonstrates the issue? This will be easier for us to reproduce if we aren't having to first try and craft an email to trigger the issue.

Thanks!

@Noon2Dusk
Copy link

Noon2Dusk commented Mar 1, 2019

@weierophinney can I send you a sample of mail that breaks the swift mailer limit? I am having the same problem that I get random breaks in swiftmailer.

Or at least some general instructions on how I could fix that?

@weierophinney
Copy link
Member

This repository has been closed and moved to laminas/laminas-mime; a new issue has been opened at laminas/laminas-mime#3.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants