On May 30, 2007, at 4:28 AM, Bruce Scherzinger wrote: ...Continue Reading

Hmmm...I am wondering if the bounce handler is smart enough to look at the score and decide at some point to put addresses that bounce regularly into an 'off_list', keeping the addresses in the list but making them inactive. That would be a great thing. Regarding Test::Files, based on the write-up it seems to be little more than a file/directory comparison program. I mean, that's probably a good thing for a distro that has lots of files. But for a small application like the typical Joomla extension, it's probably not ...Continue Reading

On May 29, 2007, at 9:13 PM, Bruce Scherzinger wrote: > I haven't had much luck (and haven't really tried either) at > getting the bounce handler to do anything for me. So i don't really > know what it's capabilities are in terms of managing bouncing > addresses. Is it possible that it sets (or could set) this > list_type DB field such that it stops trying to send messages to > addresses that bounce? Or does it just send the bounce messages to > a special email address? Bounced messag ...Continue Reading

Hey Justin, I haven't had much luck (and haven't really tried either) at getting the bounce handler to do anything for me. So i don't really know what it's capabilities are in terms of managing bouncing addresses. Is it possible that it sets (or could set) this list_type DB field such that it stops trying to send messages to addresses that bounce? Or does it just send the bounce messages to a special email address? I believe you told me that 'black_list' is one obvious alternative the normal 'list' value in the ...Continue Reading

Heya everyone, I've made some changes to the bounce handler. Along with the other changes I've mentioned, I've made the score cards list-specific, instead of global. In fact, all the rules are now (again) list- specific and the good thing is, you still have to only set up one bounce handler address for the entire installation. Right now, the score card is saved in a DB file - I may have the option to also have the scorecard us an SQL backend, since the SQL backends seem to be easier for people from other ...Continue Reading

Hey everyone, I've been playing around with how to speed up the, "Add Subscribers" screen in Dada Mail. At the moment, it's glacial. I was under the impression that it's this way simply because the validation process is resource intensive and if you do something like the validation process for, say, 10,000 subscribers, it's just gonna take some time. Well, there is some room for improvement and have some fun and try this out: In the dada/DADA/MailingList/Subscribers.pm file, find these lines: [ ...Continue Reading

On May 20, 2007, at 7:36 AM, Bruce Scherzinger wrote: > On the remove-after-bounce thing...why not just add an attribute > that disables the address instead of removing it? This attribute > could also indicate WHY the address was removed. Mailman has a > feature like this. It shows whether bouncing, user, or admin action > was the cause. I found that feature extremely useful. That's fine and I like the idea, but, Dada Mail only supports an email address in its subscription list. When it suppo ...Continue Reading

Justin, On the remove-after-bounce thing...why not just add an attribute that disables the address instead of removing it? This attribute could also indicate WHY the address was removed. Mailman has a feature like this. It shows whether bouncing, user, or admin action was the cause. I found that feature extremely useful. The rest of this stuff sounds very great. Thanks for your continued and relentless pursuit of Dada Mail perfection! Bruce ______________________________________________ Bruce Scherzinger * joomland ...Continue Reading

Hello all, Been working on the bounce handler, Some improvements: First off, like dada_bridge.pl, you can now set the cronjob to just use a URL, instead of having to use the command line interface. What's that good for? Well, firstly, you don't have to explicitly set the site-wide and dada-specific Perl Libraries in the plugin, every time you want to install and upgrade the plugin. It's also easier to make sure the cronjob *works*, since it'll run in the cronjob in the same environment as if you visit in ...Continue Reading

The last development cycle, there were two distinct branches, * One for bug fixes - this became the 2.10.14 release * One for features - this became the 2.11 Alpha 5 release I've merged both of these branches into the main trunk, so I may be able to release a distro with the features of 2.11 a5 and the bugfixes of 2.10.14. Huh. I've also created a new branch for 2.10.15 - this will again be purely for bug fixes. I probably won't make a new branch for new features - instead just work on the new features in t ...Continue Reading