SpamMePlease PleasePlease wrote:
I am in the very same situation. In past days I have asked on amavisd
lists how to force it or dspam to leave the headers but with no reply.
Maybe here someone will know the answer?
Can you explain your problem with more details?
And by the way, why there is
so much silence on both sides when talkins about amavisd+dspam - is
there any "war" or bad will among the projects? Both of them have
*nothing* about connecting those two together in their respective
docs...
I don't think there is a 'war' or something. It's just that amavisd-new works
much better with SpamAssassin than it works with DSPAM. For example using DSPAM
in amavisd-new you loose:
- the ability to use the DSPAM web frontend
- no body modifications for easy retraining
- the ability to have multiple DSPAM user profiles
- no ability to disable SpamAssassin
Therefore I suspect that most amavisd-new users use SpamAssassin (which seem to
be good enough for most) and don't care about DSPAM (including amavisd-new's
maintainer Mark Martinec who described the DSPAM support as experimental). On
the other hand most DSPAM users don't like to loose the features named above so
they don't use amavisd-new or at least not DSPAM in amavisd-new.
I wrote a patch which I'm using for some months on production servers which
makes DSPAM (sort of) a first class citizen in amavisd-new (e.g. you can use
DSPAM without SpamAssassin in amavisd-new, you get modified bodies and you can
have multiple DSPAM profiles). But it has some disadvantages so I didn't publish
it widely.
fs
