Hi,
 
 I've been lurking for some time, using qpsmtpd on a FreeBSD 5.1, with
SpamAssassin 2.60. 

 I'm using the http://gw.nsa.co.il/qpsmtpd/spamassassin spamassassin plugin
as it seems to work well with SA 2.60, although my comments below are true
with the standard SpamAssassin plugin;

 I like SpamAssassin's ability to re-write possible SPAM into an MIME
attachment so that the HTML links can't auto-verify your address when you
preview this "Possible Spam" in your browser. Right now qpsmtpd tags for
"Possible Spam" but it leaves the body alone, so the spam still
auto-executes in the preview window. 

 While I have this all configured for message re-writes, and my thresholds
are proper, the SA rewrites only appear in the logs, because I believe
qpsmtpd isn't setup to allow a new message to replace the older message that
is being scanned. 

 I believe this can be done by mucking about with the spamassassin plugin
(creating yet another variation) and using some sort of
$transaction->header->replace type of call.

 So my questions are:

 1) Has someone already done this (allowed SA's rewrite pass through), and
I'm just not seeing it as an option?
 2) Is there an easier way to do this? Possibly code something in the
spamassassin plugin to do the same thing, which is make a MIME attachment
when the "Possible Spam" threshold is crossed?
 3) If I take this on and code something up based on the existing
spamassassin plugin, how can we make it easier to keep one spamassassin
plugin current for everyone to use? It seems everyone and their dog has a
hack of the original that they are using - It's not the best for keeping
things clear. At the very least, we'd need a clearly defined variant (i.e.
spamassasinA, B, C, etc) if they have mutually exclusive features. 

 Thanks. Comments welcome. 

 

 

 


Reply via email to