Re: [dspam-users] 3.6 Scheduled for October 17

Dear Jonathan,

Fri, 30 Sep 2005 16:37:39 -0400, Jonathan Zdziarski ->
dspam-users@lists.nuclearelephant.com:

JZ> Please provide as much feedback as
JZ> possible with regards to any remaining bugs in 3.6 so we can squash
JZ> them and have a nice stable release :)

There is a spam message attached. It is base-64 encoded one-part message.
When dspam processes this kind of messages using --stdout switch, it does
not release stdout stream.

I mean, if i do something like
    $ cat bad_message.mbox |
dspam --client --stdout --process --deliver=innocent,spam --user korobkin

I will not get stdout closed. Dspam prints message to stdout and then sits
and waits. This is a problem because I use dspam in --stdout mode for mail
filtering.

Please take a look this patch, it helps me solve this problem.

=========diff decode.c==============
+++ dspam-3.6.rc3_patched/src/decode.c Thu Sep 29 08:31:44 2005
*** dspam-3.6.rc3/src/decode.c Sat Sep 24 21:49:48 2005

+++ 978,984 +++
      if (node_nt != NULL && node_nt->ptr != NULL)
        buffer_cat (out, "\n");
    }
+ buffer_cat (out, "\n");
    copyback = out->data;
    out->data = NULL;
    buffer_destroy (out);

*** 978,984 ***
      if (node_nt != NULL && node_nt->ptr != NULL)
        buffer_cat (out, "\n");
    }
!
    copyback = out->data;
    out->data = NULL;
    buffer_destroy (out);

=========diff decode.c================

--
With best regards, Alexei Korobkin.