On Sep 5, 2013, at 7:08 AM, Gerald Fox foxation@PROTECTED wrote:

Having just upgraded to Dada Mail 6 6 0, I was wondering if a problem I have been having with “Return-path: <>” that apparently causes Bounce Handler to prematurely delete bounce notifications had disappeared Unfortunately, not

Is this a problem you've reported before? If not, it's not the worst guess that I won't know about it ;) I release dev releases of the app, so that people can try out things, and make sure it's working for them, in their specific environment I don't get as much feedback as I'd like, though ;)

Here's the place to add bug reports:

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

But I don't think there's a problem with a "blank" Return-Path header Sometimes (usually?) bounce messages will have a blank Return-Path by design, to stop infinite loops from happening I'm sure the entire Internet went down one time, when a bounce message was delivered to an address that doesn't exist, so it bounced back - and so on and so forth!

The result of all this is that when I run the Bounce Handler against bounces@sender com, I get this message from Dada Mail:

Guessed_MTA: Exim Bounce_Subject: Mail delivery failed: returning message to sender

• Using Rule: permanent_error Bounced Message is from an email address that isn't subscribed to: newsletter Ignorning Forwarding bounces message to the List Owner (newsletter@sender com) deleting message #: 1

But, what was the email address that was found, by the Bounce Handler? There's tricky stuff going on, in the original report, in the bounce message:

A message that you sent could not be delivered to one or more of its recipients This is a permanent error The following address(es) failed: bounce@my_service_provider com (generated from moreinfo@recipient com) There is no one at this address

So, did the Bounce Handler find, "bounce@my_service_provider com" as the address, or, "moreinfo@recipient com" My guess is that it found, "bounce@my_service_provider com", looked to see if it was a subscriber, saw it wasn't, and went, "meh"

If you'd like, open up an issue, and attach the entire bounced message that's giving you problems, and I'll see what I can do, in an attempt to make things parse better

If you'd like to play around with this some more, you can go to the Bounce Handler's somewhat secret debugging screen,

http://example/cgi-bin/dada/plugins/bounce_handler
cgi?flavor=manually_enter_bounces

and paste in the source of bounced messages, to see how it parses them