Skip to content

Allow listmaster to modify recipient on resend - #2071

Open
immae wants to merge 1 commit into
sympa-community:mainfrom
immae:allow_send_to
Open

Allow listmaster to modify recipient on resend#2071
immae wants to merge 1 commit into
sympa-community:mainfrom
immae:allow_send_to

Conversation

@immae

@immae immae commented Aug 18, 2026

Copy link
Copy Markdown

This commit is a change in the archive management, allowing the listmaster to chose a different e-mail as recipient when resending an e-mail.
The recipient is flexible (it doesn’t restrain to existing subscribers) on purpose: the use case that provoked this change was to submit a spam false positive to a remote mailer, which required sending the e-mail "exactly as is was sent initially"

This commit is a change in the archive management, allowing the
listmaster to chose a different e-mail as recipient when resending an
e-mail.
The recipient is flexible (it doesn’t restrain to existing subscribers)
on purpose: the use case that provoked this change was to submit a spam
false positive to a remote mailer, which required sending the e-mail
"exactly as is was sent initially"
@ikedas

ikedas commented Aug 22, 2026

Copy link
Copy Markdown
Member

Hi @immae ,
Listmasters can switch their identity to that of any user. Then they may resend the message to that recipient.

@immae

immae commented Aug 22, 2026

Copy link
Copy Markdown
Author

Hi @immae , Listmasters can switch their identity to that of any user. Then they may resend the message to that recipient.

Noted, but it doesn’t solve my usecase: I wanted to send the e-mail to an adress that didn’t subscribe to the mailing-list (in this case, some e-mail provider who wanted to analyse why the e-mail was considered as a spam by their system, they wanted the exact e-mail re-sent by the same system)

@ikedas

ikedas commented Aug 24, 2026

Copy link
Copy Markdown
Member

In your use case, you'd be better to retrieve (copy) the message in question from the server and to send it as data (an attachment) to the intended recipient. If you use a mechanism such as message forwarding, some parts of the message including header fields may be rewritten or deleted, thus accuracy would be compromised.

Please see also the description on the archive structure in the documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants