On 24. sep. 2012 01:16, Brandon Penglase wrote: > I'm getting this same thing, and have seem a few posts about it, but > never a fix. The only time that it 'fixed itself' on me, was when I > moved the dspam DB from one system (Gentoo) to another (FreeBSD), > but forgot to move the filesystem part of it. After that, I've been > able to deliver correctly. > > However I still have it happening on a different system. > In both cases I am using dspam-web to retrain the emails. > > [...] > mail.log sample: > Sep 23 18:42:10 MailFilter postfix/smtpd[8429]: connect from > localhost[127.0.0.1] > Sep 23 18:42:10 MailFilter postfix/smtpd[8429]: D9590603B7: > client=localhost[127.0.0.1] > Sep 23 18:42:10 MailFilter postfix/cleanup[8421]: D9590603B7: > message-id=<0.0.21d.5cc.1cd9917beea6d72.3...@vz1197.businesswatchnetwork.com> > Sep 23 18:42:10 MailFilter postfix/qmgr[25855]: D9590603B7: from=<>, > size=16742, nrcpt=1 (queue active) > Sep 23 18:42:11 MailFilter postfix/smtpd[8429]: disconnect from > localhost[127.0.0.1] > Sep 23 18:42:11 MailFilter postfix/local[8596]: D9590603B7: > to=<?f???@mailfilter.domain.com>, orig_to=<?f???>, relay=local, delay=0.24, > delays=0.15/0.01/0/0.08, dsn=5.1.1, status=bounced (unknown user: "?f???") > Sep 23 18:42:11 MailFilter postfix/qmgr[25855]: D9590603B7: removed
After my first posting I got a fix from al...@rearden.com: > For some reason, the dspam list rejected my e-mail, but I sent this fix > to Stephan a few months ago, he said he'd include it in the next release. ... > Anyway, it's a simple fix to line 503, changing the assignment > to using strcpy() instead. The assignment results in the > trashing of the ATX->recipient on the subsequent call to > dspam_destroy (CTX) at the end of process_message(). > > Here's the fix in patch format: > > --- dspam-3.10.2/src/dspam.c 2012-04-11 18:48:33.000000000 +0000 > +++ dspam.c 2012-05-10 19:48:02.000000000 +0000 > @@ -500,7 +500,7 @@ > } > /* Change also the mail recipient */ > - ATX->recipient = CTX->username; > + strcpy(ATX->recipient, CTX->username); > > } > } > @@ -561,6 +561,7 @@ > do_notifications(CTX, ATX); > } > > + > /* Consult global group or classification network */ > result = ensure_confident_result(CTX, ATX, result); > if (result< 0) > > Hope this helps someone else. It was fun to track down! > > I am running with this patch applied, and the mangling is not happening any more. I have NOT verified that this patch is "correct" in any way, e.g. I do not know if this causes a memory leak. I figure I am reasonably safe as long as I run dspam (and not dspamc). ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Dspam-user mailing list Dspam-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspam-user
