Feature Request: Sender identities

[areynoua]

Short description:

• Allow users to have an arbitrary json data.
• Allow templates to access a user's data, considered the sender.

Motivation:
Alice (potential customer) has a discussion with Bob. Bob subscribes her to an opt-in list and clicks on the button to send a confirmation request. To improve customer contact, the email could be signed “Bob”.

Suggested implementation:
Either add an arbitrary json data to the users, or add a “Sender”. In the latter case, a user could choose which sender he send as by default.

• When sending a registration confirmation request, add sender data to the “dot” given to the template.
• (This makes less sense, but could be useful, perhaps?) When preparing a campaign, possibility to select the sender.

What do you think?

[knadh]

Hi @areynoua. Subscriber JSON attributes already exists - https://listmonk.app/docs/concepts/

[areynoua]

Thanks for the rely.

The idea was to have an equivalent of the Subscriber JSON attributes for the sender. But maybe it's not so common? Maybe it's more usual to register the contact person with each subscriber and sign emails in that person's name? I don't know, I'm figuring it all out by myself. But the idea was to be able to easily change who signs the emails. In my case, the “customer relationship” has to be as natural as possible.

Whether this is on the list of future features or not, thank you for the excellent application.

[knadh]

Ah, I see.

Per-campaign attributes are planned which may help here. The template could have logic to print different names/signatures etc. based on the campaign attributes, and the campaign attribute could have fields such as {"sender": "sender1"}

[areynoua]

Oh great, this corresponds almost perfectly to my use case (except for the signature in opt-in requests).