rechecking blacklisted emails after adding new dnsbl

[Mike Oltmans]

I got stuck on SORBs and was told that I have one of their honey pot emails on my list so I added SORBS DNSBL. My question is will the system recheck the emails that are already blacklisted if I reenable them, or do I need to remove them from my list and add them via the bulk tool to have them get checked against DNSBL.

 

[twisted1919]

@Mike Oltmans - mailwizz doesn't check against DNSBLs anymore since it's too time consuming.
If you're using an extension like this then each email address is checked right before sending.

 

[Mike Oltmans]

Ahh so just curious why do you still have the dnsbl section on the site? What is its purpose?

 

[Mike Oltmans]

Also thanks for the link I'll be adding it to the site!

 

[twisted1919]

Ahh so just curious why do you still have the dnsbl section on the site? What is its purpose?

It there in the hope that sometimes in future i'll be able to provide a proper service for these checks. A decent fast service.

 

[Mike Oltmans]

ahhh ive played project choosy picky as well it is indeed a diabolical game.

 

[Mike Oltmans]

we send emails for different clients and sometimes one of them gets caught as being spammy by someone however your system then blacklists that email. Can I make it so it reports those as soft bounces because maybe the next one I send out will get through correctly.

 

[twisted1919]

From backend > settings > cron, in the last panel you can loose those checks.

 

[Mike Oltmans]

What i am trying to do is for instance the below 3 codes are spam detected. I want to make it so these codes are recognized as a soft bounce.

550 5.7.1
554 5.7.1
571 5.0.0

 

[twisted1919]

@Mike Oltmans - I see. unzip attached file and put resulted file in apps/common/vendors/BounceHandler/ to override existing rule file.

 

[Mike Oltmans]

You rock! I am a php programmer so I may edit it further

 

[Superyo]

Hi,

This file will be overwritten in a future realease or it will be mantained?. Is there a way to overwrite the rules of de BounceHandler?.

Thanks.

 

[twisted1919]

@Superyo / @Mike Oltmans - just place a file named rules-custom.php in the same folder with your own rules and mailwizz will load that one too. This way is safe for future updates.

 

[frm.mwz]

@Superyo / @Mike Oltmans - just place a file named rules-custom.php in the same folder with your own rules and mailwizz will load that one too. This way is safe for future updates.

If both, the mwz internal and the custom rules are loaded,
will it automatically use the custom ones overriding the built-in?

 

[twisted1919]

@frm.mwz - it will merge both, custom ones over the existing ones.

 

[Mike Oltmans]

Like this?

<?php if ( ! class_exists('BounceHandler', false)) exit('No direct script access allowed');

return array(
    BounceHandler::DIAGNOSTIC_CODE_RULES => array(),
    BounceHandler::DSN_MESSAGE_RULES     => array(),
    BounceHandler::BODY_RULES            => array(),
    BounceHandler::COMMON_RULES          => array(
        array(
            'bounceType' => BounceHandler::BOUNCE_SOFT,
            'regex'      => array(
                '/553/i',
                '/554/i',
                '/571/i',
                '/551/i',
                '/550/i',
                '/557/i',
                '/spam/i',
                '/blocked/i',
                '/dnsbl/i',
                '/BOUNCED BACK/i',
            ),
        ),
        array(
            'bounceType' => BounceHandler::BOUNCE_HARD,
            'regex' => array(
            ),
        ),
    ),
);

 

[twisted1919]

@Mike Oltmans - That looks good.

 

[Superyo]

Can we replace the rules?, not add new ones, just replace all with our custom rules in a way can survive an update, I mean. Not editing rules.php

 

[twisted1919]

@Superyo - From next version placing a file called "rules-custom-override.php" will override all the rules with yours.

 

[Superyo]

Perfect!.. Thanks. For this version I will replace rules.php