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.

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

Open
alt-romes opened this issue Dec 27, 2024 · 4 comments
Open

List-Unsubscribe header not in double opt-in confirmation #2224

alt-romes opened this issue Dec 27, 2024 · 4 comments
Labels
needs-investigation Potential bug. Needs investigation

Comments

@alt-romes
Copy link

Version:

  • listmonk: v4.1.0
  • OS: NixOS

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.

@alt-romes alt-romes added the bug Something isn't working label Dec 27, 2024
@alt-romes alt-romes changed the title List-Unsubscribe header not in newsletter headers despite toggled on List-Unsubscribe header not in headers despite toggled on Dec 27, 2024
@knadh knadh added needs-investigation Potential bug. Needs investigation and removed bug Something isn't working labels Dec 27, 2024
@knadh
Copy link
Owner

knadh commented Dec 27, 2024

@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?

@alt-romes
Copy link
Author

alt-romes commented Dec 27, 2024

@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

@alt-romes
Copy link
Author

alt-romes commented Dec 27, 2024

I tried using a simple smtpd server to log the messages (python3 -u -m smtpd -n -c DebuggingServer 127.0.0.1:1025), and it seemingly confirms the mail sent from Listmonk doesn't have a List-Unsubscribe header:

---------- MESSAGE FOLLOWS ----------
mail options: ['BODY=8BITMIME']
b'Mime-Version: 1.0'
b'Content-Type: text/html; charset=UTF-8'
b'Content-Transfer-Encoding: quoted-printable'
b'To: <[email protected]>'
b'Subject: Confirm subscription'
b'Message-Id: <1735314136278694511.1085.2907996738875964026@kanjideck>'
b'From: "Kanjideck Newsletter" <[email protected] >'
b'Date: Fri, 27 Dec 2024 15:42:16 +0000'
b'X-Peer: 127.0.0.1'
b''
b''
b''
b'<!doctype html>'
b'<html>'
b'    <head>'
....
------------ END MESSAGE ------------

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

Configuration of main server:
Screenshot 2024-12-27 at 15 47 52

Configuration of dummy debug server:
Screenshot 2024-12-27 at 15 48 34

@alt-romes
Copy link
Author

alt-romes commented Dec 28, 2024

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.

@alt-romes alt-romes changed the title List-Unsubscribe header not in headers despite toggled on List-Unsubscribe header not in double opt-in confirmation Dec 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs-investigation Potential bug. Needs investigation
Projects
None yet
Development

No branches or pull requests

2 participants