-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Labels
needs-investigationPotential bug. Needs investigationPotential bug. Needs investigation
Description
Version:
- listmonk: 4.1.0
- OS: linux/amd64
Description of the bug and steps to reproduce:
When the List-Unsubscribe
header is enabled in the configuration (m.cfg.UnsubHeader
), sending messages results in the following error:
subscriber 3: 450 Invalid literal value, expected ""
Steps to Reproduce
- Enable the
List-Unsubscribe
header in the configuration. - Send a message using the current setup.
- Observe the error message.
Expected Behavior
Messages should be sent successfully without any errors when the List-Unsubscribe
header is enabled.
Actual Behavior
An error occurs when the List-Unsubscribe
header is enabled, preventing the message from being sent.
Possible Cause
The issue might be related to the format or value of the List-Unsubscribe
header. Specifically, the header value might not be correctly formatted or might contain invalid characters. The header is set as follows:
h.Set("List-Unsubscribe-Post", "List-Unsubscribe=One-Click")
h.Set("List-Unsubscribe", `<`+msg.unsubURL+`>`)
Screenshots:
If applicable, add screenshots to help explain your problem.
Metadata
Metadata
Assignees
Labels
needs-investigationPotential bug. Needs investigationPotential bug. Needs investigation
Projects
Milestone
Relationships
Development
Select code repository
Activity
knadh commentedon Jan 1, 2025
This is strange. This is the first report of such an issue and the header is enabled by default on all installations.
What SMTP server are you using?
CaoMeiYouRen commentedon Jan 1, 2025
Host: smtp.resend.com
Port: 587
https://resend.com/
knadh commentedon Jan 5, 2025
Any updates on this? This definitely seems SMTP-specific. You might want to write to Resend and confirm.
CaoMeiYouRen commentedon Jan 5, 2025
I tried it today and couldn't reproduce the problem. I think we can close this issue now