Kailash Nadh

Multiple lists on a campaign don't result in duplicate emails for overlapping subscribers. Subscribers are picked uniquely across all lists on a campaign.

I haven't had a chance to look at this yet. Will try to see if I can before the next release. Hoping to get a PR from someone in the...

Hi @toabctl. If `SOURCE_DATE_EPOCH` is set, it should be used as the Unix timestamp offset and the `date` should be derived from that, otherwise, the system time. Here, if it's...

This isn't fundamentally possible with the way listmonk batches messages for sending (which is sequential, ascending order of IDs). I am afraid there are no plans to implement batching based...

> listmonk_app | 2024/09/18 23:41:53 pipe.go:122: messages exceeded (1) for the window (1m0s since 18 Sep 24 23:41 +0200). Sleeping for 1m0s. The error says that listmonk has been set...

`Broken pipe` is a network error. listmonk's TCP connection to the SMTP server outside is breaking for reasons outside of listmonk controls.

PRs for this are welcome if anyone is interested in picking up this task. I wouldn't have time to work on this personally.

@vividvilla you may be interested in picking this up. A simple `tags[]` field in the `media` table with tagging on the UI can solve this UX problem. listmonk already has...

Hi @arbialexandri. Will consider this for the next release. It's easy to implement.

The `Timestamps` column in the campaigns header already sorts the table by the `created_at` date, although the column has created, started, ended timestamps. The [Buefy UI lib](https://buefy.org/documentation/table) that listmonk uses...