-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
List-Unsubscribe header not in double opt-in confirmation #2224
Comments
@alt-romes if the toggle is enabled, then listmonk definitely includes the header. What SMTP server are you using? It may be possible that the SMTP server is stripping it? |
I'm using postfix. That's a good hypothesis. I'll troubleshoot that in particular, thanks for the quick reply |
I tried using a simple smtpd server to log the messages (
I also grepped a bit, and I found out that while I was setting up listmonk I did send out a few test e-mails that did contain the headers for a day or two, but they stopped showing up in all mails that came after. Is there any other test you'd like me to run? It can also be the configuration of the smtpd connection? Thanks again |
Right, so I've figured out the actual problem, which I misdiagnosed originally: The List-Unsubscribe headers are not added to the Double-opt-in confirmation message. They work as expected when campaigns are sent. |
Version:
Description of the bug and steps to reproduce:
It seems like the List-Unsubscribe feature is broken, or at least not properly configured by default (even when the option is toggled).
I'm using listmonk v4.1 and the emails sent by the campaign do not include the List-Unsubscribe header at all, and I have tried both with and without the option being toggled.
Screenshots:
I would upload a screenshot, but it would be hard to parse. The point is: with the option to include the list-unsubscribe header toggled on, and looking at the received email headers, the message does not have the list-unsubscribe header anywhere.
Any help would be very welcome.
The text was updated successfully, but these errors were encountered: