Could it be changed to not return the attachment with the notification so that it will always be sent out? Maybe just name the attachment? Something like: "The attachment xyz.pdf attached to your message with subject 'abc' exceeds the allowed limit. The message was not sent to the list." Warm regards, Mary Ann -----Original Message----- From: Justin J [mailto:justin@PROTECTED] Sent: Sunday, November 13, 2011 1:01 PM To: Dada Mail Developers Subject: [dadadev] RE: Large Memory Leak found and Further Optim ...Continue Reading

Aha, so 2.10.16 is significantly faster for you, too.  I noticed the first slowdowns first with version 3.x.  I updated through most of the v3s and then back to v2 somewhere during that cycle.Glad so see you found some issues.The memory leak may have been around for a while.  When I was testing different versions, I would often have it stall and sometimes quit midstream.  I've even had problems with 2x if I leave open the sending monitor screen that automatically updates every ten s ...Continue Reading

Still not concerned with the backwards compatibility issue.  I get an email copy of all the subs and unsubs so I can manually correct the sql database.  And it wouldn't be a major calamity if the archive was missing a copy or two. 2.10.16 does have clickthough tracking. I don't know how accurate it is, but it serves as a guide so long as it shows the numbers are consistent from mailer to mailer.  Yes, I would like it to be 100% accurate, but if it's not, I guess, I can live with it.  ...Continue Reading

On Nov 13, 2011, at 10:45 AM, Alexander Judd wrote: > Redacted-Address: redacted > > So again we would need to modify Dada/Mystery Girl to spin through each attachment it finds, and look for it's own unsubscribe link in the body to parse. That's ridiculous. If the headers are intact, it shouldn't be too too hard. I've done a ton of work on the bounce handler: And I'll release it up with the rest of the changes soon, for something to play with. There's been a massive amount of work to untangle everythi ...Continue Reading

On Nov 13, 2011, at 10:25 AM, Mary Ann wrote: > These templating improvements won't affect sending straight HTML without templates, right? I send with my own message composed entirely outside of Dada (except for the appended signature that Dada adds). Actually, it'll affect everyone that sends an HTML mailing, no matter how you created it. It was pretty startling to look at memory usage to creep up and up and up when the mass mailing was going on. And startling again to see it *not* happen, when the bug was resolv ...Continue Reading

Hi JustinThanks for your reply and the link - agree that should be able to do most of the heavy liftingFrom reading around it looks like AOL sends the MTA back as: User-Agent: AOL SComp So we might be able to teach Mystery Girl to handle that, the problem remaining then is that AOL replies as the email address as 'redacted' Redacted-Address: redacted So again we would need to modify Dada/Mystery Girl to spin through each attachment it finds, and look for it's own unsubscribe link in the body to parse. I'll investigat ...Continue Reading

These templating improvements won't affect sending straight HTML without templates, right? I send with my own message composed entirely outside of Dada (except for the appended signature that Dada adds). I'm wondering if the memory leak is what was causing so many of my mailings to the non-profit's discussion list to get stuck, since the biggest problems seemed to be for mailings that had attachments. Which brings me to... If someone sends an attachment to the list that is too large, the message is simply not put thr ...Continue Reading

There's already a module for Perl called Email::Arf - http://search.cpan.org/~rjbs/Email-ARF-0.006/lib/Email/ARF/Report.pm That'll probably do most of the heavy work. ...Continue Reading

Hi everyoneNot quite sure if this is a developer or general 'hacks' forum discussion, but we are now receiving quite a large (50/60 per 1/2 million newsletter) amount of Abuse Reporting Format responses from AOL which are from people who flag the messages as spam (not true!) and we then manually unsubscribe them from our lists. I was about to sit down and roll some custom code to handle these automatically, as we have the unsubscribe link in the body of the email (ARF format doesn't include the reporter's email in the ...Continue Reading

During my optimization pass, I found a massive memory leak that happens during a mass mailing of an HTML message. The mass mailing process potentially starts eating up many hundreds of megs of memory, which could potentially start slowing things way, way down, or even get your sending process killed. This underlying problem could be the culprit of a lot of mysterious sending problems with Dada Mail. I've been able to remove the problem with the development stuff I've been doing and was also able to backport the bug, so ...Continue Reading