We have been using Mailwizz for years...we are not novices. Usually it performs nicely. We send 250,000 emails each day. We moved our operation from AWS on Ubuntu 16.04 to Digital Ocean on Ubuntu 18.04 over a month ago. Twice it has stopped recording bounces. There is no apparent problem when I look at the bounce servers. They are always active in MW. But last week I found 64,000 unprocessed emails in the bounce address after MW stopped showing bounces.. I deleted those and Mailwizz started processing bounces again.
It was working well until 2 days ago when again no bounces for ANY deliver server. Nothing was changed in that time.
Now I see 31,000 unprocessed emails in the bounce server.
Have you ever seen anything like this before?
SO I followed instructions at https://forum.mailwizz.com/threads/...untu-bionic-18-04-3-lts-with-php-7-2-24.6396/
And now https://email.causeaction.com/phpinfo.php shows that PCNTL is enabled.
But still there are no bounces showing up in MW from today's sends.
They were showing up fine for several days, form the same Bounce mailbox...and then just stopped.
Our Return-Path in the header is richard@causeaction.com.
Today that mailbox has over 49,000 emails and Mailwizz is not processing them.
The Mailwizz server is Ubuntu 18.04 with Nginx and PHP 7.2. It has 6 vcpu and 16 GB of memory. The Monitor graphs show only moederate usage of CPU and Memory. There is 300 GB of free disk space.
And lastly, after 2 days, the bounces from June 1 finally showed up .Why the long delay? What is wrong with Mailwizz?
But they haven't been working since.
UPDATE: The bounces from June 2 just showed up....and today is June 4.
Also I noticed that in the email headers I see this: X-Wccc-Campaign-Uid: hk353fdsl6f82
When the online help says I should see this: X-Mw-Campaign-Uid: tf833t6s9z842
I do not rememeber customising the file apps/common/config/main-custom.php nor do I see any code for a custom header prefix like:
'email.custom.header.prefix' => 'X-Whatever-',
Before I go deleting the bounce emails from the bounce server again, do you have any suggestions for us?
Thank you
AND HERE ARE THE HEADER ENTRIES FOR THE BOUNCE EMAILS. Looks like everything is there.
Message-ID: <2c0963c16d77b04c41e4eb2678e0c33f@causeaction.com>
Date: Wed, 03 Jun 2020 07:38:56 +0000
Subject: Inform. Consider. Engage.
From: CauseACTION <rich@causeaction.com>
Reply-To: CauseACTION <rich@causeaction.com>
To: "chevy195@excite.com" <chevy195@excite.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="_=_swift_v4_1591169936_302f691edaed7f2d16b9dd906555213c_=_"
X-Wccc-Tracking-Did: 0
X-Wccc-Subscriber-Uid: mb45688p4o85e
X-Wccc-Mailer: SwiftMailer - 5.4.x
X-Wccc-EBS: https://email.causeaction.com/index.php/lists/block-address
X-Wccc-Delivery-Sid: 32
X-Wccc-Customer-Uid: oe776dlpxy494
X-Wccc-Customer-Gid: 1
X-Wccc-Campaign-Uid: hk353fdsl6f82
X-Sender: richard@causeaction.com
X-Report-Abuse: Please report abuse for this campaign here:
https://email.causeaction.com/index...6f82/report-abuse/vc7415rm1v947/mb45688p4o85e
X-Receiver: chevy195@excite.com
Precedence: bulk
List-Unsubscribe: <https://email.causeaction.com/index...direct?source=email-client-unsubscribe-button>,
<mailto:rich@causeaction.com?subject=Campaign-Uid:hk353fdsl6f82 /
Subscriber-Uid:mb45688p4o85e - Unsubscribe request&body=Please unsubscribe
me!>
It was working well until 2 days ago when again no bounces for ANY deliver server. Nothing was changed in that time.
Now I see 31,000 unprocessed emails in the bounce server.
Have you ever seen anything like this before?
SO I followed instructions at https://forum.mailwizz.com/threads/...untu-bionic-18-04-3-lts-with-php-7-2-24.6396/
And now https://email.causeaction.com/phpinfo.php shows that PCNTL is enabled.
But still there are no bounces showing up in MW from today's sends.
They were showing up fine for several days, form the same Bounce mailbox...and then just stopped.
Our Return-Path in the header is richard@causeaction.com.
Today that mailbox has over 49,000 emails and Mailwizz is not processing them.
The Mailwizz server is Ubuntu 18.04 with Nginx and PHP 7.2. It has 6 vcpu and 16 GB of memory. The Monitor graphs show only moederate usage of CPU and Memory. There is 300 GB of free disk space.
And lastly, after 2 days, the bounces from June 1 finally showed up .Why the long delay? What is wrong with Mailwizz?
But they haven't been working since.
UPDATE: The bounces from June 2 just showed up....and today is June 4.
Also I noticed that in the email headers I see this: X-Wccc-Campaign-Uid: hk353fdsl6f82
When the online help says I should see this: X-Mw-Campaign-Uid: tf833t6s9z842
I do not rememeber customising the file apps/common/config/main-custom.php nor do I see any code for a custom header prefix like:
'email.custom.header.prefix' => 'X-Whatever-',
Before I go deleting the bounce emails from the bounce server again, do you have any suggestions for us?
Thank you
AND HERE ARE THE HEADER ENTRIES FOR THE BOUNCE EMAILS. Looks like everything is there.
Message-ID: <2c0963c16d77b04c41e4eb2678e0c33f@causeaction.com>
Date: Wed, 03 Jun 2020 07:38:56 +0000
Subject: Inform. Consider. Engage.
From: CauseACTION <rich@causeaction.com>
Reply-To: CauseACTION <rich@causeaction.com>
To: "chevy195@excite.com" <chevy195@excite.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary="_=_swift_v4_1591169936_302f691edaed7f2d16b9dd906555213c_=_"
X-Wccc-Tracking-Did: 0
X-Wccc-Subscriber-Uid: mb45688p4o85e
X-Wccc-Mailer: SwiftMailer - 5.4.x
X-Wccc-EBS: https://email.causeaction.com/index.php/lists/block-address
X-Wccc-Delivery-Sid: 32
X-Wccc-Customer-Uid: oe776dlpxy494
X-Wccc-Customer-Gid: 1
X-Wccc-Campaign-Uid: hk353fdsl6f82
X-Sender: richard@causeaction.com
X-Report-Abuse: Please report abuse for this campaign here:
https://email.causeaction.com/index...6f82/report-abuse/vc7415rm1v947/mb45688p4o85e
X-Receiver: chevy195@excite.com
Precedence: bulk
List-Unsubscribe: <https://email.causeaction.com/index...direct?source=email-client-unsubscribe-button>,
<mailto:rich@causeaction.com?subject=Campaign-Uid:hk353fdsl6f82 /
Subscriber-Uid:mb45688p4o85e - Unsubscribe request&body=Please unsubscribe
me!>