Remove use of our custom patched Symfony mailer #5299

New Issue

OVERLORD · 2026-02-05T09:56:02+03:00

OVERLORD commented

2026-02-05 09:56:02 +03:00

Originally created by @ssddanbrown on GitHub (May 31, 2025).

Description

Should now be able to use Symfony 7.3 mailer now that my changes have been included.

Originally created by @ssddanbrown on GitHub (May 31, 2025). ### Description Should now be able to use Symfony 7.3 mailer now that my changes have been included.

OVERLORD added the 🔧 Maintenance 🏭 Back-End labels 2026-02-05 09:56:02 +03:00

OVERLORD closed this issue

2026-02-05 09:56:03 +03:00

OVERLORD commented

2026-02-05 09:56:04 +03:00

@BIGWALDOR commented on GitHub (Jul 2, 2025):

Hey @ssddanbrown, is it possible to get a bit more context on this?

@BIGWALDOR commented on GitHub (Jul 2, 2025): Hey @ssddanbrown, is it possible to get a bit more context on this?

OVERLORD commented

2026-02-05 09:56:06 +03:00

@ssddanbrown commented on GitHub (Jul 2, 2025):

Hi @BIGWALDOR,
The context is that I was maintaining some custom changes to enforce some level of TLS usage, for backwards compatibility with older versions of BookStack which used a different mailer lib.
I since provided these changes upstream: https://github.com/symfony/symfony/pull/59479
Therefore we don't need to use a customized branch and can instead switch to the original version of the mailer library.

@ssddanbrown commented on GitHub (Jul 2, 2025): Hi @BIGWALDOR, The context is that I was maintaining some custom changes to enforce some level of TLS usage, for backwards compatibility with older versions of BookStack which used a different mailer lib. I since provided these changes upstream: https://github.com/symfony/symfony/pull/59479 Therefore we don't need to use a customized branch and can instead switch to the original version of the mailer library.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/BookStack#5299