On Jun 7, 2006, at 12:15 AM, Andreas Grau wrote:

These type of people will almost certainly get unsubscribed by the elephant-memory bounce handler strategy Which is why I am trying to come up with something different I'll leave my thinking cap on for
this

Please do - I'd love to hear your thoughts

In the meantime, what about giving a bonus to the bounce score with every message sent to the address This way, an earlier single bounce will be "forgiven" after some time

Possibly - right now, to keep things simple, I want to just have the,
"Score Card" updated, just for bounces - although there is a
workaround -

At the moment, the threshold you have to hit is currently at, "10"

Hard Bounces count for, "4"

Soft Bounces count for, "1"

So, you'd have to get 10 soft bounces to have the bounce handler
chuck you off - it'll take 3 hard bounces

(plus, if you want, you can set any rule to anything you want)

So, we can set the threshold to, "50", keep soft bounces to, "1" and
hard bounces up to, say, "12" and get a similar effect, but be
incredibly lenient on soft bounces This still solves the problem of
having a list owner receive a deluge of bounces they may or may not
want to go through, individually over coffee and still does remove
non-existent email addresses without any real work by the list owner
- it just sort of works

I'm open to changing these defaults - in fact, we can change soft
bounces to just, "0", if we wanted to, but I'd like to have them
still have some sort of weight to them, as some rules that count the
bounces as soft are a little well, less than verbose as why
they're bouncing - the email address could possibly be non-existant,
but still registering as a soft bounce

I do like having an easy way to remove the score card - I think,
although a big huge hammer to solve a delicate problem, it would help
to a large degree to make this problem a little less And it would be
like 10 more lines to write :) Set this as another cron job task to
run every day/week/month/year and we're pretty good in making sure
the less-than-stellar performance of an email address in one month,
doesn't hurt it in the next :)

If you're interested, the changes are in CVS now:

<http://mojomail
cvs
sourceforge
net/mojomail/dada_mail_stable/dada/ 

extensions/dada_bounce_handler pl? view=log&pathrev=dada_mail_2_10_9_maintenance-branch>

What I was pleased to realize that implementing this wasn't too hard
- I just had to set up a new action, and, erm, make that action
happen The whole way the scores are kept is the same as what the
default list archives and settings are currently based on, so no real
heavy lifting there Which, was a pleasant surprise