[imp] Imp and Spamassassin

[Jon Lewis]

I'm curious if anyone has done any patches for integration of spamassassin 
(to be used for checking mail as it's sent) with Imp?

i.e. For ISP's customers having their customers' usernames/passwords 
stolen or phished seems to be an ongoing problem.  Spammers then use 
webmail to send their junk.  The problem is, the spammers frequently also 
change the From: address to be an address at some other site (usually one 
of the common free mail providers).  If we do spamassassin scanning on the 
SMTP server after IMP has sent the mail, and the message is scored as 
spam, then we have 2 choices.  Bounce mail to a likely forged From: 
address.  Eat the message.

I'm a firm believer in "mail should never disappear", but I really don't 
like the idea of spam messages bouncing to sites from which they didn't 
actually originate, in part because it's likely to set off the same sort 
of problems the spam filtering is meant to stop.  So, it seems that 
ideally, if the message is scored as spam, imp should fail to or refuse to 
send it, and give the sender an error saying their message could not be 
sent.

It looks like imp/lib/Compose.php could be hacked to pipe $msg to spamc -c 
and check the result...or am I better off just using 
$conf['mailer']['type'] = 'smtp'; and an SMTP server that can do content 
scanning during the SMTP dialog?

----------------------------------------------------------------------
  Jon Lewis                   |  I route
  Senior Network Engineer     |  therefore you are
  Atlantic Net                |
_________ http://www.lewis.org/~jlewis/pgp for PGP public key_________