You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 6, 2023. It is now read-only.
I implemented the functionality of embedding images into emails, instead of having them linked to external servers. Of course this blows up email size, but displays images right away in today's email programs and navigates around several problems with password protected sites.
To achieve this, in addition to hook into the SendBatchEvent event, I had to override\Civi\FlexMailer\Listener\DefaultSender::onSend for just one single line of injection, because the available hooks did not give me access to the full MIME message. This is needed because the whole MIME message structure is changed at this step.
I read and understood the thoughts about what interface to the message contents is used in the hooks, but for the final stage just before sending I think giving the whole MIME content and/or the powerful message object would be better. This could also implement a S/MIME or similar encryption plugin.
The text was updated successfully, but these errors were encountered:
I implemented the functionality of embedding images into emails, instead of having them linked to external servers. Of course this blows up email size, but displays images right away in today's email programs and navigates around several problems with password protected sites.
To achieve this, in addition to hook into the
SendBatchEvent
event, I had to override\Civi\FlexMailer\Listener\DefaultSender::onSend
for just one single line of injection, because the available hooks did not give me access to the full MIME message. This is needed because the whole MIME message structure is changed at this step.I read and understood the thoughts about what interface to the message contents is used in the hooks, but for the final stage just before sending I think giving the whole MIME content and/or the powerful message object would be better. This could also implement a S/MIME or similar encryption plugin.
The text was updated successfully, but these errors were encountered: