You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description of the bug and steps to reproduce:
I am using SMTP2GO and Listmonk, SMTP2GO will disconnect Listmonk from the server after about 2500 emails, it closes the pipe and Listmonk sees this as an error and pauses the running campaign. If I resume the paused campaign, Listmonk starts over from the beginning of the subscribers list. I was able to verify this by checking SMTP2Go's sent emails log. We sent about 12,000 emails, which was reflected in Listmonk however looking at the list of sends, 5 copies were sent out to our subscribers alphabetically until 'I' then 3 emails until 'J' then no more emails were sent because I assumed the list had reached the end based on the total emails sent vs subscribers. So around a third of our subscribers didn't receive any email and the other 2/3rds received 3 or more emails. Could this be investigated?
The text was updated successfully, but these errors were encountered:
Version:
Description of the bug and steps to reproduce:
I am using SMTP2GO and Listmonk, SMTP2GO will disconnect Listmonk from the server after about 2500 emails, it closes the pipe and Listmonk sees this as an error and pauses the running campaign. If I resume the paused campaign, Listmonk starts over from the beginning of the subscribers list. I was able to verify this by checking SMTP2Go's sent emails log. We sent about 12,000 emails, which was reflected in Listmonk however looking at the list of sends, 5 copies were sent out to our subscribers alphabetically until 'I' then 3 emails until 'J' then no more emails were sent because I assumed the list had reached the end based on the total emails sent vs subscribers. So around a third of our subscribers didn't receive any email and the other 2/3rds received 3 or more emails. Could this be investigated?
The text was updated successfully, but these errors were encountered: