Re: Avoiding mass unsubscribes due to bouncing

 
From: "Eef Weenink h.e.weenink@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
In-Reply-To: (no subject)
Date: March 2nd 2016
Sure, that would help, but I would rather have it much sooner. 
I run an mailing of 400.000+.
If there is a spam issue after 10.000 or so. I would have to fix 390.000 afterwards :-( 
So something with a treshold (after x bounces) I get an message AND/OR at the end? 

Regards, Eef

Van: <dadadev@PROTECTED> namens "Mary Ann Kelley maryann@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
Beantwoorden - Aan: Dada Mail Developers <dadadev@PROTECTED>
Datum: woensdag 2 maart 2016 15:40
Aan: Eef Weenink <h.e.weenink@PROTECTED>
Onderwerp: [dadadev] Re: Avoiding mass unsubscribes due to bouncing

Thanks, Eef. I have adjusted the thresholds so I do have more mailings before an unsubscribe happens, but I do want to process the bounces regularly. I thought an email summary after each mailing would be helpful to alert me when the IP is blocked.

Warm regards,

Mary Ann




On Feb 29, 2016, at 9:51 AM, Eef Weenink h.e.weenink@PROTECTED [Dada Mail Developers] <dadadev@PROTECTED> wrote:

Hello Mary Ann, 

I recognize the problem. I am running a 400.000 (and even plus) mailing. And sometimes the IP gets blocked. 
This is how I workaround it: 
1. Set the bounce treshold much higher. Hard bounce is 4, so I have 3-4 mailings before a mailaddress is unsubscribed
2. To set unsubscribed addresses back I interfere directly with the mysql database (the addresses are double there, so you only have to delete the address listed as unsubscribed)
Play al little bit around there and you see what I mean. 
3. I have an outgoing spamchecker on my mailserver. I train this server to accept the mail which was bounced
4 Empty list in bounced addresses. 
And you are back to normal situation. 

Regards, Eef

  • This mailing list is a public mailing list - anyone may join or leave, at any time.
  • This mailing list is a group discussion list (unmoderated)
  • Start a new thread, email: dadadev@dadamailproject.com

This is the developer discussion mailing list for Dada Mail.

If you are just looking for support Dada Mail, consult the message boards at:

https://forum.dadamailproject.com

Documentation for Dada Mail:

https://dadamailproject.com/d

Specifically, see the Error FAQ:

https://dadamailproject.com/d/FAQ-errors.pod.html

To post to this list, send a message to:

mailto:dadadev@dadamailproject.com

All subscribers of this list may post to the list itself.

Topics that are welcome:

  • Constructive critiques on the program (I like, "x", but, "y" needs some work - here's an idea on how to make this better...)
  • Bug/Error reports
  • Bug fixes
  • Request For Comments on any changes to the program
  • Help customizing Dada Mail for your own needs
  • Patches
  • Language Translations
  • Support Documentation/Doc editing, FAQ's, etc.
  • Discussion of any changes that you would like to be committed to the next version of Dada Mail -

Dada Mail is on Github:

https://github.com/justingit/dada-mail/

If you would like to fork, branch, send over PRs, open up issues, etc.

Privacy Policy:

This Privacy Policy is for this mailing list, and this mailing list only.

Email addresses collection through this mailing list are used explicitly to work within this email discussion list.

We only collect email addresses through our Closed-Loop Opt-In system.

We don't use your email address for any other purpose.

We won't be sharing your email address with any other entity.

Unsubscription can be done at any time. Please contact us at: justin@dadamailproject.com for any help regarding your subscription, including removal from the mailing list.

All mailing list messages sent from us will include a subscription removal link, which will allow you to remove yourself from this mailing list automatically, and permanently.

All consent to use your email address for any other purpose stated at the time of the mailing list subscription will also be revoked upon mailing list removal.