Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
weierophinney opened this issue Dec 31, 2019 · 6 comments

Comments

@weierophinney
Copy link
Member

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?


Originally posted by @stevleibelt at zendframework/zend-mime#29

@weierophinney
Copy link
Member Author

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


Originally posted by @jobleadsorder at zendframework/zend-mime#29 (comment)

@weierophinney
Copy link
Member Author

@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!


Originally posted by @weierophinney at zendframework/zend-mime#29 (comment)

@weierophinney
Copy link
Member Author

@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?


Originally posted by @Noon2Dusk at zendframework/zend-mime#29 (comment)

@stevleibelt
Copy link

@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!

Originally posted by @weierophinney at zendframework/zend-mime#29 (comment)

Maybe @tworzenieweb (https://github.com/tworzenieweb) can do this.
It is not part of my job business anymore.

@sma27
Copy link

sma27 commented Nov 13, 2020

We have been experiencing this bug as well using Laminas Mail. Emails with long paragraphs end up with one or more spaces inserted into the content (middle of words, etc.). If we break the paragraph up, the issue goes away. Seems like some hard breaks are being inserted into the message. The messages are stored and then sent from our MySQL database. We've confirmed there are no formatting issues or strange characters in the messages when sent.

@weierophinney
Copy link
Member Author

This package is considered feature-complete, and is now in security-only maintenance mode, following a decision by the Technical Steering Committee.
If you have a security issue, please follow our security reporting guidelines.
If you wish to take on the role of maintainer, please nominate yourself

If you are looking for an actively maintained package alternative, we recommend:

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

No branches or pull requests

3 participants