Search results

In case someone finds this useful: The DS1 server, which was assigned to Campaigns but was also sending for List, was associated with a Customer. When the customer was removed, it became a system server and stopped sending to the List

That was my assumption, so it seems that's how it works. To prevent it from sending to "old" ones after unpausing, we should simply create the welcome campaign again. Could this possibly be related to the fact that we are not using the latest version of MailWizz, using 1.9.48?

Sorry for the offtop but got into the campaign_delivery_log. Noticed that welcome emails set to "after subscription" and "including current subscribers - no" are sent not only to new subscribers, but also to old subscribers. As i said these campaigns have been on pause for a while and yesterday...

Didn't notice that at campaign_delivery_log there is information on servers (facepalm). Thank you, we'll wait for your test results!

@twisted1919 Currently, we are sending out the following types of emails: Subscription confirmation emails (these should go through DS2, as it's configured for "All"). Welcome emails, sent immediately after confirmation (we have a choice between DS1 and DS2, and DS2 is set for these...

Hello! Trying to solve issue... We have two delivery servers. Both assigned for one customer. One is the old DS1, which was previously used for all types of mailings. Recently, we added another one, DS2, to separate different types of emails. The idea is that DS2 should be used for confirmation...