Hi,
We've been having a number of issues with our mw lately. One campaign keeps sending even after we paused a delivery server and then also paused the campaign itself. It is still sending and seems like it will continue to everything is sent. the issue is that all the sendouts end up as Giveup. So we're just wasting memory now and don't know how to stop it.
The following is the type of an error we are seeing in the campaign logs:
++ Starting Swift_SmtpTransport << 220 sub.zimbradomain.com ESMTP Postfix >> EHLO sub.mailwizzdomain.com << sub.zimbradomain.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN >> STARTTLS << 220 2.0.0 Ready to start TLS >> EHLO sub.mailwizzdomain.com << 250-sub.zimbradomain.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-AUTH LOGIN PLAIN 250-AUTH=LOGIN PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN >> AUTH LOGIN << 334 VXsevNlcm5hbWU6 >> Y29udGFjddirEB6bTIuYXUtbmV3djoec2xldHRlci5jb20= << 334 UGFzc3dvcmQ6 >> bDJGc3FmdVI4Z25ZRmZacWJLTFJJd1pXTeweGk2ZXB5S0FIZ1hjcDdYM3ZtMnIzSnAxVGVWeEo0elR2ZkMz << 235 2.7.0 Authentication successful ++ Swift_SmtpTransport started >> MAIL FROM:<bounce@sub.zimbradomain.com> << 250 2.1.0 Ok >> RCPT TO:<contact@contactdomain.com> << 451 4.3.0 <bounce@sub.zimbradomain.com>: Temporary lookup failure !! Expected response code 250/251/252 but got code "451", with message "451 4.3.0 <bounce@sub.zimbradomain.com>: Temporary lookup failure " (code: 451) >> RSET << 250 2.0.0 Ok
When we wanted to start a different campaign with a new list, we found that the list count showed 0 in spite of the fact that we already added subscribers. It's been hours now and it's still showing 0.
We've been having a number of issues with our mw lately. One campaign keeps sending even after we paused a delivery server and then also paused the campaign itself. It is still sending and seems like it will continue to everything is sent. the issue is that all the sendouts end up as Giveup. So we're just wasting memory now and don't know how to stop it.
The following is the type of an error we are seeing in the campaign logs:
++ Starting Swift_SmtpTransport << 220 sub.zimbradomain.com ESMTP Postfix >> EHLO sub.mailwizzdomain.com << sub.zimbradomain.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-STARTTLS 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN >> STARTTLS << 220 2.0.0 Ready to start TLS >> EHLO sub.mailwizzdomain.com << 250-sub.zimbradomain.com 250-PIPELINING 250-SIZE 10240000 250-VRFY 250-ETRN 250-AUTH LOGIN PLAIN 250-AUTH=LOGIN PLAIN 250-ENHANCEDSTATUSCODES 250-8BITMIME 250 DSN >> AUTH LOGIN << 334 VXsevNlcm5hbWU6 >> Y29udGFjddirEB6bTIuYXUtbmV3djoec2xldHRlci5jb20= << 334 UGFzc3dvcmQ6 >> bDJGc3FmdVI4Z25ZRmZacWJLTFJJd1pXTeweGk2ZXB5S0FIZ1hjcDdYM3ZtMnIzSnAxVGVWeEo0elR2ZkMz << 235 2.7.0 Authentication successful ++ Swift_SmtpTransport started >> MAIL FROM:<bounce@sub.zimbradomain.com> << 250 2.1.0 Ok >> RCPT TO:<contact@contactdomain.com> << 451 4.3.0 <bounce@sub.zimbradomain.com>: Temporary lookup failure !! Expected response code 250/251/252 but got code "451", with message "451 4.3.0 <bounce@sub.zimbradomain.com>: Temporary lookup failure " (code: 451) >> RSET << 250 2.0.0 Ok
When we wanted to start a different campaign with a new list, we found that the list count showed 0 in spite of the fact that we already added subscribers. It's been hours now and it's still showing 0.