We are using our own listmonk instance at https://newsletter.rekonas.com to mange our newsletters.
See the official documentation for detailed instructions.
TBD after Cloudron replies
Lists collect subscriber information. Every list can have settings related to the opt-in model and visibility.
Forms can be created from public lists to allow people to subscribe. They can either be embedded or hosted directly on the listmonk instance. A private list can only be edited by admins and does not allow people to sign up. This is useful for internally managed lists.
Subscribers are receivers that are part of one or more lists. They can unsubscribe themselves by clicking on a link at the bottom of the email or using the built-in unsubscribe function of many email clients.
Every email that gets send out to a list of subscribers is a campaign. A campaign makes use of a template.
Create a new campaign by cloning an existing one or starting from scratch. Select a template to use and one or more subscriber lists to send it to. The content of a campaign can be edited with the rich-text editor or even as raw HTML. After the campaign has been send it cannot be changed any more.
Listmonk has a built-in analytics solution. It can track views and clicks. To track clicks on certain links inside a newsletter, make sure to use the “tracked link” feature of the editor.
We are sending the messages via AWS SES. Listmonk receives automated feedback from AWS SES and takes actions accordingly to preserve our sender reputation. If a messages can not be delivered or a user marked our message as SPAM, this user will be put on a block list and we will not send messages to them in the future. This ensures we are not marked as SPAM by other providers.
In addition to campaigns, listmonk can also be used to send transactional messages via API.
A template can be created from an existing one by cloning it or by starting from scratch.
It consists of a raw HTML file with embedded CSS styles. Media needs to be uploaded via the Media manager first and references with their absolute URL. Inside templates, variables such as \{\{ template “content” . \}\} can be used. These will be replaced with the relevant content before the messages are send out.