is there any way to keep the bounce server active but ignore it by bounce processing cronjobs which connects via IMAP?

[pradeep sharma]

Hi @twisted1919

i have around 600 bounce servers for my customers. but we are using PMTA as an incoming mail Server to receive bounces , where we can forward the bounce emails received to a particular mailbox i.e all-domain-bounces@domain.com , its a single mailbox that receives all forwarded emails for all bounces servers.

We do this just to create a unified system to process bounces but here are a few challenges.

1. We need to create a login mailbox fo each bounce server where bounce mails are expected but we are using forward method so all email are funneled to a single mailbox. and these mailboxes serve no email for a bounce.
2. even if we create mailboxes logins we cant prevent them from picking up by the cronjob, because its just waist of resources.


i am looking for any solution where

1. we can keep the bounce server active but ignore them from corn processing, can we get some status-based system in the bounce processor like ACTIVE-CRON-DISABLED!! where cron will not pick up the server but it can still be used as a bounce server.


I have another query regarding the processing bounces.

2. Does a bounce server process bounce per sending server basis or unified for all bounces matched in mailwizz systems? for example if mailwizz query a particular mailbox for bounces email, does it check and mark bounces to email sent from the delivery server where this bounce server is used or it can process bounces to other email sent from another delivery server. this question is important as we intended to keep just 1 bounce server which will server bounces for many domains and customers are expected to point MX record to our bounce server.

So if mailwizz process bounces irrespective of the delivery server used then its a very good idea. and we should keep it up..

 

[twisted1919]

1. we can keep the bounce server active but ignore them from corn processing, can we get some status-based system in the bounce processor like ACTIVE-CRON-DISABLED!! where cron will not pick up the server but it can still be used as a bounce server.

Don't run the cron job for bounce-handler.

We do this just to create a unified system to process bounces but here are a few challenges.

pmta can post the bounces to a url. MailWizz has a bounce handler for this, If you add a delivery server of type smtp-pmta, you'll see the url where to send this information and mailwizz will process it just fine.

2. Does a bounce server process bounce per sending server basis or unified for all bounces matched in mailwizz systems? for example if mailwizz query a particular mailbox for bounces email, does it check and mark bounces to email sent from the delivery server where this bounce server is used or it can process bounces to other email sent from another delivery server. this question is important as we intended to keep just 1 bounce server which will server bounces for many domains and customers are expected to point MX record to our bounce server.

MailWizz pulls the emails and checks their message-id header then matches them with the campaign_delivery_log table to see the campaign and subscriber. It does not care how those emails ended up in that email box.

 

[pradeep sharma]

Don't run the cron job for bounce-handler.

We want to process 1 bounces server which is a unified mailbox for bounces. any solution for this!!