Search results

@twisted1919 : Could you please expand on this. We are currently running 1.4.3. Does the above mean that any license other than 1.5.0 will stop working? If so, this is highly problematic as this will force users to upgrade literally over xmas.

@twisted1919: Is there not an option to customise the unsubscribe form (i.e. the one which is displayed by list or does this only apply to the current list - i.e. https://MAILWIZZ.DOMAIN/customer/lists/LISTID/forms). I think it would be a valuable addition to have a "[UNSUBSCRIBE_ALL_URL]".

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...

We can burst to about 150K/p.h. and Port25 could very well push out about 3m mails per day. Port25 and the scripts would not have an issue with the automation. In a setup of 10M+/day you will just need to cluster Port25. Our longest uptime on Port25 was 130days without any interference (we then...

We have automated all the bounce-handling and reporting. Port25 requires no 24/7 support as it is stable as rock once properly configured. The SysOps team does the regular maintenance/upgrades. Monitoring (Zabbix / Pagerduty) does the rest.

We tried hosted services but the USD exchange rate and volatility of our local currency presented an issue with regards to TCO. We also found that most hosted solutions would incur a cost of about $1-2k/pm for our volume of about 15-20m mails per month. We bought a Port25 enterprise license...

Pre-release available here: https://github.com/magicdude4eva/port25-bouncehandler/releases/tag/1.2 ---- MAKE SURE YOU READ DOCS.

I covered this here as a reply: https://github.com/magicdude4eva/port25-bouncehandler/issues/12#issuecomment-324093860 With my port25-bouncehandler I unsubscribe a bounced email from ALL lists. This would mean that an email is unsubscribed from currently running campaigns as well as scheduled...

I am not sure why there is relevance to the number of IPs. It really depends on the MTA. In our case we use Port25 and can push out about 260-400K messages per hour. This is on a 8-core, 10GB linux box (no SSD) etc (we use 4 IPs for marketing mails and the below are our marketing stats)...

I use the following (which deletes Mutex files older than a day) via a once a day cronjob (I run it at 1am where we do nothing) find /[PATH_TO_MAILWIZZ]/apps/common/runtime/mutex/ -type f -mtime +1 -name '*.lock' -execdir rm -- {} + Although the app is idle, I do not find that it cleans up...

BTW: error is in Line 249 in apps/frontend/controllers/CampaignsController.php: $url = CampaignUrl::model()->findByAttributes(array( 'campaign_id' => $campaign->campaign_id, 'hash' => $hash, )); if (empty($url)) {...

Same here. When I copied the campaign and sent to a smaller test group it works. But I do notice a lot of 404s in application log: 2017/05/04 07:05:37 [error] [exception.CHttpException.404] [105.255.216.232] exception 'CHttpException' with message 'The requested page does not exist.' in...

@twisted1919 : Has anything changed in the APIs? We have been using them and always provided the signature and HMACed it but after the upgrade I noticed that the API fails with error "Invalid API request signature. Please refer to the documentation.". I then had to set "Disable signature check"...

Graylog / Kibana / Logstash will sort out most reporting aspects. We have not looked at a log-file since then and normally work off a few dashboards which are displayed in realtime - drill-down is instant: Marketing guys would look at Kibana as it is not as "technical". All of it is using OSS...

On our side this is proprietary, but we use a combination of Logstash, Graylog and Kibana. I can offer the Logstash configuration for free though: https://gist.github.com/magicdude4eva/5001d3b52743062f6fb28e3a92b7fce4

The one part I do not get (this is based on the number of queries I receive about my Github PMTA bouncehandler) is that there are many users of Port25 out there who manage an really expensive mail infrastructure but somehow have not bothered to even read the PowerMTA userguide in it's entirety...

Great job - thank you - works perfectly fine.

Thank you. I have given up running it with 4 subscribers against 300 campaigns - ten minutes in it was still not complete. I don't see this work well if I were to run it against a list of 300K subs.

Question regarding "delete-inactive-subscribers": I have a list with 4 email addresses and 300 campaigns. When I run the command " delete-inactive-subscribers --list_uid="LISTID" --time="-6 months" --limit=1000" the delete command seems to iterate / run a query per campaign. Isn't there a more...

@twisted1919 - Is there an option to unsubscribe inactive users (this would help in an re-engagement campaign).