8000 [Mailer] Incorrect Base64 encoded content of the attachment in Mailersend · Issue #51492 · symfony/symfony · GitHub
[go: up one dir, main page]

Skip to content

[Mailer] Incorrect Base64 encoded content of the attachment in Mailersend #51492

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

Closed
pavelwitassek opened this issue Aug 26, 2023 · 0 comments
Closed

Comments

@pavelwitassek
Copy link
Contributor

Symfony version(s) affected

6.3

Description

Currently is used method bodyToString of MIME attachment, which generates base64 string of body split into chunks by max-line-length for MIME. This is not correct behavior for Mailersend API which requires not-splitted base64 encoded string of body.

How to reproduce

Send email with attachment via Mailersend API integration. Error occurs if base64 encoded body string of attachment has more than 76 characters. Mailersend API response with: The value must be an Base64 encoded string.

Possible Solution

No response

Additional Context

No response

fabpot added a commit that referenced this issue Aug 26, 2023
…nsport (pavelwitassek)

This PR was merged into the 6.3 branch.

Discussion
----------

Fixed attachment base64 content string in MailerSendApiTransport

| Q             | A
| ------------- | ---
| Branch?       | 6.3
| Bug fix?      | yes
| New feature?  | no
| Deprecations? | no
| Tickets       | Fix #51492
| License       | MIT

- Fix base64 encoded body string of larger attachments in MailerSendApiTransport

Commits
-------

5580080 Fixed attachment base64 content string in MailerSendApiTransport
@fabpot fabpot closed this as completed Aug 26, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants
0