Netskin|Corin Langosch <[EMAIL PROTECTED]> wrote:
> hi,
>
> nobody can't help? :-(

Rather than forwarding the original message yet again thus creating a
new thread, you should have replied to it instead.

>
> corin
>
> Date: Wed, 09 Apr 2008 08:57:47 +0200
> From: Netskin|Corin Langosch <[EMAIL PROTECTED]>
> To: [email protected]
> Subject: SPAM: [dspam-users] reject at smtp time
> Reply-To: 
>
> Hi,
>
> I'm successfully running Exim4 with DSPAM. But currently infected
> messages are bounced to the sender, which is bad because the sender of
> most spam is forged.

Bouncing spam is about the worst you can do about it in my opinion (even
worse than not filtering at all).

>
> Before using DSPAM I ran Exim with SA which allowed me to reject the
> messages directly at smtp time using an ACL rule.
>
> I searched a lot but couldn't find a solution to setup Exim + DSPAM
> with spam reject at smtp time. Any hints / help would be really
> appreciated :)

There are a number of reasons why rejecting spam at smtp time is a
difficult subject as far as dspam is concerned. In fact, I can only
think of one situation in which this can actually be set up in a
consistent way: when dspam uses the same data for all recipients the
mail server accepts at smtp time, i.e., when you are using a global
group not just per domain, but per MX. Otherwise, dspam might classify
the incoming email differently for different recipients but you'd have
to accept the message anyway. Of course, you could also maintain a
grobal group or a merged group for that particular purpose and use the
classify option of dspam at smtp time. Either way, you'd probably have
to write your own local_scan function (see the exim manual). Trying to
integrate this with amavis may or may not be easier. Sorry that I don't
have the time to look into that myself.

Hope that helps,

Elias

Reply via email to