Re: bounces going to list owner instead of bounce address

From: "Mary Ann Kelley maryann@PROTECTED [Dada Mail Developers]" <dadadev@PROTECTED>
Subject: Re: bounces going to list owner instead of bounce address
In-Reply-To: (no subject)
Date: August 26th 2019

>>I am monitoring the bounces emails by forwarding them to a different mailbox, and the emails I am getting at the list owner address are not going to the bounces email address where they can be parsed.<<

The bounces I emailed about today turned out to not be new—they were actually leftover behavior from the List Administrator email being incorrect for the last mailing when I installed the upgrade, not from a new mailing. I assume it coincided with the mail server trying again after 7 days or something. So the above was just me not having enough coffee while I was looking through them when I got up and saw them all.

Why would the bounce handler work correctly, and why wouldn't you be surprised to have sent all the bounced email messages to the list owner? 

It should work correctly (and per my note above that they ended up not being from a new mailing, it probably does). 

It was always set up as: list administrator address is the bounces address, and the server forwards all of the emails at the bounces address to a separate address just for that purpose, leaving the originals at the bounce handler email address without deleting them. 

Now that I fixed the list administrator problem that I caused when I had the wrong email in that field at upgrade, it is set up that way again and should be working. I’ll know when the next mailing goes out.

Set the bounce email address as just a POP3 account - don't try to monitor it. Set the list admin to that same address. That's all you have to do.

When I get thousands of bounces from an ISP for a mailing, I need be able to access the raw headers from the bounced emails so that I can solve the problem. Since Dada deletes the bounces, I can’t do that without monitoring them outside of the bounce handler email.

I have the server set to automatically forward the bounces via cPanel’s mail forwarding function from bounces@PROTECTED to a separate address set up just for that purpose (bouncedepot@PROTECTED)—the bounces are still going to the bounce handler, and they are not going to the list owner. They sit in a server mailbox so login via webmail and look at what is going on when the IP gets blocked, then once it’s resolved I delete them. 

If there is a way to access the raw headers of the bounced messages through Dada, I’m unaware of it. All I see is this:

Am I missing some way to access the raw headers of bounces through Dada?

Mary Ann

  • 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:


This mailing list is to discuss the nerdy programming development of Dada Mail -

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


To post to this list, send a message to:


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

Some on topic... topics include:

  • Positive Crits 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 internal 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 -

At the moment, there aren't many people with CVS access for Dada Mail - if you would like CVS access, please first talk about the changes you propose and how it will affect the program. If the idea is sound and agreed upon, the change will be comitted. A good track record of this will allow you to have CVS access. Some reasons that patches will not be accepted is if the patch breaks compatibility with a previous version of the program, the patch is too centric to your own problem or the patch simply isn't very good.

Please, please please familiarize yourself with the documentation at:


Since no one wants to answer the same question twice.

Another sneaky reason for this mailing list is to test out the discussion list capabilities of Dada Mail, since Dada Mail is used for the mailing list itself.

NOTE - because of this, there may be times that this list will be somewhat broken. Although we're not planning on breaking the program by using it, we're giving you the heads up that this may well happen anyways.

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.


Unsubscribe at Anytime | Privacy Policy

Dada Mail Project