How to retry or view transactional mails

[2m5g]

Hello,

I was wondering how to retry or view transactional mails.

Yesterday I had some connection issues (timeouts) related to SES and my hoster. Because of that, a lot of transactional mails failed with the generic error message: "2025/03/27 error sending message 'my subject': dial tcp 0.000.000.00:465: i/o timeout" (masked subject and ip).

If my understanding is correct, the listmonk API for tx is just responding with ok because of the underlying queuing logic and has no database tables setup. So I am in a situation where I am unable to validate which of the transactional mails were successfully sent or not.

Hope someone is able to help me or advice!

Thanks in advance!

[knadh]

Hi @rocknrolla801. Unfortunately, there's no mechanism that records the states of transactional e-mails. This is indeed a limitation and is a consideration for a future version.

[2m5g]

@knadh Thanks a lot for your response and taking the time! Please let me know if I can support or if I may add this as enhancement/feature request. Even just adding the mail address (recipient) to enhance the logs in case of an error would already be a huge improvement.

[MaximilianKohler]

Even just adding the mail address (recipient) to enhance the logs in case of an error would already be a huge improvement.

Here's some relevant info for how to use the log data to resend: https://github.com/knadh/listmonk/issues/1629#issuecomment-1858762315

[2m5g]

Here's some relevant info for how to use the log data to resend: #1629 (comment)

Hi @MaximilianKohler , maybe I am missing something but my logs for transactional mails do not include any link to subscriber lists like the comment you shared where the id is present. Do I have to set a higher log level somewhere?

My log for the failed tx looks like: 2025/03/27 14:55:55.012333 manager.go:517: error sending message 'my subject': dial tcp 111.111.111.111:465: i/o timeout

Thanks

[github-actions[bot]]

This issue has been marked 'stale' after 90 days of inactivity. If there is no further activity, it will be closed in 7 days.