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.

Sign up for GitHub

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

Jump to bottom

Message->setBody: Clear headers when adding multi-part body #268

Open
wants to merge 1 commit into
base: 2.26.x
Choose a base branch
from
Open

Message->setBody: Clear headers when adding multi-part body #268

wants to merge 1 commit into from

Conversation

vlk-charles
Copy link

It is undesirable for the Content-Type and Content-Transfer-Encoding headers to remain from a previous single-part call. Solves #265

@vlk-charles
Message->setBody: Clear headers when adding multi-part body
6b2c5a7 
It is undesirable for these headers to remain from a previous single-part call. Solves laminas#265

Signed-off-by: Karel Vlk <[email protected]>
@arhimede
Copy link

arhimede commented Sep 3, 2024

This library is discontinued.
You should switch to some other libraries in order to handle emails.

@vlk-charles
Copy link
Author

Thank you for the information. Is there an official statement available somewhere? I can't find any deprecation notice here or anywhere else.

Unfortunately I encountered this bug becasue a third-party project (iTop) recently switched to this library.

@arhimede
Copy link

arhimede commented Sep 3, 2024

Thank you for the information. Is there an official statement available somewhere? I can't find any deprecation notice here or anywhere else.

Unfortunately I encountered this bug becasue a third-party project (iTop) recently switched to this library.

See below the status of all packages and libraries
https://getlaminas.org/packages-maintenance-status/

@froschdesign
Copy link
Member

@Slamdunk
It is your decision to accept or close the pull request.

@vlk-charles
Copy link
Author

Sorry about breaking the one Psalm test. I did some non-essential refactoring for (my) readability. I can fix it if necessary for acceptance of the pull request. But no point in committing new code if it won't be accepted for EOL reasons anyway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@Slamdunk Slamdunk

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@vlk-charles @arhimede @froschdesign @Slamdunk