Enabling bounces

Kai Schaetzl maillists at conactive.com
Thu May 24 17:06:42 IST 2007


Julian Field wrote on Thu, 24 May 2007 16:06:03 +0100:

> Because it is necessary. If you want to bounce spam, you have to jump 
> through some hoops.

I'm not questioning the hoops, I'm wondering if I really understand it right that 
*two* rulesets are necessary.

For a given message, spam actions has to evaluate to 
> a result including "bounce", and enable spam bounce has to evaluate to 
> "yes". The ruleset is necessary because I say it is :-)

But I don't see how *two* rulesets are supposed to work or are necessary.
I think it's not clear what my confusion is about:

spam.actions.rules:
From:   IP  bounce
FromOrTo:   default     store notify header "X-Spam-Status: Yes"

*and*

bounce.rules;
From:   IP  yes
From: default no

is that really what I have to do if I wanted to bounce?

> MailScanner doesn't use the From: address in the headers at all, it only 
> uses the envelope sender address.

That's why I wanted to boost spamminess of the messages with Spamassassin which 
would then enable MailScanner to bounce the messages by detecting them as spam 
(for sure), but with high scoring spam excluded it's very unreliable as most 
messages would score high probably even without boosting them up.

I think I could also just forward all messages to a specific address, as the 
forward action is available for spam and non-spam. But the problem still is the 
detection. Can I create a rule that detects messages from <> *and* IP? I know 
that I can "and" rules, but can I detect an empty sender?

> > Any ideas how I can do it with MailScanner (as obviously what I had in mind 
> > won't work).
> >   
> You could do it with a Custom Function tied to "Enable Spam Bounce" 
> probably. I would need to think a bit about exactly what you would want 
> to do. You want to spot spam coming from postmaster at hisdomain (in the 
> From: header) and switch off its $message->{ishigh} flag so it gets 
> treated as normal scoring spam, at which point you can bounce it. It's 
> just a problem of working out which config option to attach the Custom 
> Function to.

Frankly, it's then probably easier to compile milter-regex as I think it can use 
header parts as well. I hoped I could do it somehow with MailScanner as I just 
need the blockage for this one thing.

Kai

-- 
Kai Schätzl, Berlin, Germany
Get your web at Conactive Internet Services: http://www.conactive.com





More information about the MailScanner mailing list