Mailwizz - 1.4.8

Status
Not open for further replies.
@Baramon - I have replied to that github issue, we'll see if there's something i can help with, though as i said, i don't see how.

Regarding the hard-bounce (also refer to Github issue for more details: https://github.com/magicdude4eva/port25-bouncehandler/issues/17): Since we are now running into the busy season, I am unable to upgrade MailWizz from 1.4.3 or have much time to replicate this on a test environment.

The last release to the Port25 bounce-handler was done on 24th August - https://github.com/magicdude4eva/port25-bouncehandler/releases. This included handling for campaign bouncing. The end-points and changes where done by Twisted and those changes where supposed to be made available in 1.4.4 or later. Since I was running 1.4.3, I patched the installation as described here: https://github.com/magicdude4eva/port25-bouncehandler/releases/tag/1.3

So to eliminate a few aspects:
- If you have some bounce type issue and you have not installed https://github.com/magicdude4eva/port25-bouncehandler/releases/tag/1.3, then the issue might be with MailWizz (as the 1.1 release was from 2016)
- If you have installed Port25 handler 1.3, revert back to 1.2 and see if behaviour is back to old

Since I just patched my 1.4.3 installation with the changes, it could very well be that subsequent changes within MailWizz might have changed behaviour. The Port25 plugin does set a "hard-bounce" based on your configuration - please review that you have soft-bounce-categories set as per: https://github.com/magicdude4eva/port25-bouncehandler/blob/master/setup.php#L48 (any bounce-category not listed in that list will default to a hard-bounce).

FWIW: I also noticed a large number of people running old Port25 instances (some 3.5 or 3.6 and others 4.0). I can not support any queries from those and I urge people to move to a supported version (anything in the 4.5vxx tree).

FWIW2: My plugin is open-source / free and a side-project. I really get annoyed when people Skype/email me and demand that I fix something (only to figure out that they have not read documentation, run outdated software etc). Nothing stops someone to fork the Git project and make improvements or supply patches.
 
Status
Not open for further replies.
Back
Top