That seems to have done the trick, thanks. What exactly happened and how did this fix it? Warm regards, Mary Ann On Apr 3, 2012, at 6:59 PM, Mary Ann Kelley wrote: > I restored the schedules and am hoping that will help. ...Continue Reading

I started getting this yesterday but upgraded thinking that might help. I just realized that I haven't gotten this error since I upgraded to 5.01 today; now I'm only getting the other one. I restored the schedules and am hoping that will help. Warm regards, Mary Ann On Apr 3, 2012, at 6:06 PM, Justin J wrote: > That would be strange if you're getting this error, as it was one of the bugs fixed for 5.0.1 - > > https://github.com/justingit/dada-mail/issues/262 > > If you are running v5.0.1, see if ...Continue Reading

On Apr 3, 2012, at 3:53 PM, Mary Ann Kelley wrote: > > And I'm getting this for the bridge plugin on the same install. > > Any idea what is going on? That would be strange if you're getting this error, as it was one of the bugs fixed for 5.0.1 - https://github.com/justingit/dada-mail/issues/262 If you are running v5.0.1, see if just removing the, dada/DADA/perllib/Params directory (or renaming it) does the trick, ...Continue Reading

> I'm getting the following error for Dada 5.01 from the scheduled mailer cron job. Server maintenance was done just prior to this error message being generated with each run of the cron job, but I wouldn't even begin to know how to talk to support about it. Help would be appreciated. Try simply restoring your lists: http://example.com/cgi-bin/dada/mail.cgi?f=restore_lists you'll need only to restore your schedules. ...Continue Reading

And I'm getting this for the bridge plugin on the same install. Any idea what is going on? Warm regards, Mary Ann Begin forwarded message: > Status: 500 > Content-type: text/html > > Software error: > Undefined subroutine &Params::Validate::validate called at ..//DADA/App/Guts.pm line 635. > > > For help, please send mail to the webmaster, giving this error message > and the time and date of the error. > > ...Continue Reading

I'm getting the following error for Dada 5.01 from the scheduled mailer cron job. Server maintenance was done just prior to this error message being generated with each run of the cron job, but I wouldn't even begin to know how to talk to support about it. Help would be appreciated. _______________ Status: 500 Content-type: text/html Software error: Byte order is not compatible at /usr/local/lib/perl5/5.8.8/x86_64-linux/Storable.pm line 416, <CONFIG> line 1, at ../DADA/perllib/MLDBM/Serializer/Storable.pm line ...Continue Reading

Re: Exim bounces (or any bounces, really) - Here's how to make the bounce handler work better: The bounce handler works by parsing and filtering bounced messages - the more bounce messages I have to work with, the better the bounces can get. Right now for Exim, there's only one? in the corpus: https://github.com/justingit/dada-mail/blob/master/dada/t/corpus/email_messages/bounce-exim-something.eml Sadly, it doesn't look like Exim follows any sort of agreed-upon format for bounced messages - or even non-agreed-u ...Continue Reading

Generally the bounce handler has been very helpful to me even if it isn't parsing as well as I'd like, but it would be nice if it didn't substitute user_unknown when that's not the exact reason. Prior to Dada I was handling bounces manually which would be impossible at the size my list is now. Even if it has errors distinguishing between hard and soft bounces, at least it is handling them. Warm regards, Mary Ann On Apr 2, 2012, at 10:21 PM, Moshe Katz wrote: > When we first started using Dada Mail, (around 2.x), ...Continue Reading

When we first started using Dada Mail, (around 2.x), we tried to use the bounce handler.  However, as you have seen, Exim's Delivery Failure notifications are not parsed very well by Dada Mail (at least as of last week) and we gave up pretty quickly because we weren't really getting useful information  Every single bounce that we received came in as user_unknown.  If you are using Exim (or whatever other server generated the message is using Exim), I am not surprised that you got these results. Moshe-- ...Continue Reading

Here are 2 of them, stripped of identifiers: Date: Mon Apr 2 15:40:37 2012 List Name: XXX Newsletter Email: XXX@PROTECTED Action Taken: add_to_score softbounce_score Diagnostics of the Bounced Message: Simplified-Message-Id : 20120402153918 Bounce_To : XXX@PROTECTED reason : Bounce_From : Mail Delivery System std_reason : user_unknown Message-Id : Diagnostic-Code : This message was created automatically by mail delivery software. A message that you sent could not be delivered to one ...Continue Reading