Is your feature request related to a problem?
Campaign/newsletter emails often need specific email headers to identify them as bulk mail, support modern unsubscribe behavior, and reduce automatic replies such as out-of-office responses.
Currently, Plunk campaign emails sent through the web interface include a List-Unsubscribe header, but do not appear to include or expose configuration for other common bulk/newsletter headers, for example:
Precedence: bulk
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
This can lead to practical issues, such as out-of-office replies being sent back to the sender/reply-to mailbox after a campaign is sent.
Describe the solution you'd like
It would be useful if Plunk campaigns supported common bulk/newsletter headers.
A reasonable default for campaign/newsletter sends could be:
Precedence: bulk
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Additional optional headers that may make sense depending on the campaign type:
Auto-Submitted: auto-generated
X-Auto-Response-Suppress: All
Ideally, Plunk would either:
- Add sensible default headers automatically for campaign/newsletter sends.
- Allow custom headers to be configured per campaign.
- Allow default campaign headers to be configured at workspace/project level.
A settings-based approach would be especially useful because some headers are broadly useful defaults, while others may depend on the sender’s use case or infrastructure.
Alternatives or workarounds
One possible workaround would be to send emails through the transactional API if custom headers are required there. However, this is not ideal for campaigns because it bypasses the normal campaign workflow in the web interface.
Another workaround would be to handle autoresponder replies in the receiving mailbox with filters, but that only hides the symptom and does not improve the actual email headers sent by Plunk.
Additional context
Some relevant headers and their purpose:
A widely used de facto header for bulk/list/newsletter email. Many autoresponders use it as a signal to avoid sending vacation or out-of-office replies.
List-Unsubscribe-Post: List-Unsubscribe=One-Click
Used together with List-Unsubscribe to support one-click unsubscribe behavior for modern bulk email.
Auto-Submitted: auto-generated
A standards-based header that marks a message as automatically generated. It may help some systems avoid automatic reply loops or unnecessary autoresponses.
X-Auto-Response-Suppress: All
A non-standard but commonly useful header for Microsoft/Exchange environments to suppress automatic responses.
This feature should probably apply to campaign/newsletter emails, not necessarily to all transactional emails.
Is your feature request related to a problem?
Campaign/newsletter emails often need specific email headers to identify them as bulk mail, support modern unsubscribe behavior, and reduce automatic replies such as out-of-office responses.
Currently, Plunk campaign emails sent through the web interface include a
List-Unsubscribeheader, but do not appear to include or expose configuration for other common bulk/newsletter headers, for example:This can lead to practical issues, such as out-of-office replies being sent back to the sender/reply-to mailbox after a campaign is sent.
Describe the solution you'd like
It would be useful if Plunk campaigns supported common bulk/newsletter headers.
A reasonable default for campaign/newsletter sends could be:
Additional optional headers that may make sense depending on the campaign type:
Ideally, Plunk would either:
A settings-based approach would be especially useful because some headers are broadly useful defaults, while others may depend on the sender’s use case or infrastructure.
Alternatives or workarounds
One possible workaround would be to send emails through the transactional API if custom headers are required there. However, this is not ideal for campaigns because it bypasses the normal campaign workflow in the web interface.
Another workaround would be to handle autoresponder replies in the receiving mailbox with filters, but that only hides the symptom and does not improve the actual email headers sent by Plunk.
Additional context
Some relevant headers and their purpose:
A widely used de facto header for bulk/list/newsletter email. Many autoresponders use it as a signal to avoid sending vacation or out-of-office replies.
Used together with
List-Unsubscribeto support one-click unsubscribe behavior for modern bulk email.A standards-based header that marks a message as automatically generated. It may help some systems avoid automatic reply loops or unnecessary autoresponses.
A non-standard but commonly useful header for Microsoft/Exchange environments to suppress automatic responses.
This feature should probably apply to campaign/newsletter emails, not necessarily to all transactional emails.