For those you who are are Imail/Junkmail/Message Sniffer users: Scott Perry has modified a test version of Junkmail so that it logs like this:
02/22/2003 10:38:29 Q9973006e0464ef86 From: [EMAIL PROTECTED] To: [EMAIL PROTECTED] IP: 216.88.36.96 ID: 48D65EF927 ... where, in the case of IMGate, the ip is the one that sent the msg to IMGate, and the ID: is the postfix queue ID of that msg. So now we can easily harvest the JunkMail/Message Sniffer DELETE actions from the Junkmail logs and forward them into to IMGate where we can create new access rules. You're already DELETEing the msgs with Junkmail so what's the New Big Deal? By converting Junkmail content-scanning DELETEs into IMGate envelope rejects, you reduce the numerical traffic to IMail by a up to 10% (assuming 10% of spam gets through IMGate to Imail) and save on the bandwidth lost to spam by having IMGate rejecting at the envelope level (after RCPT TO: and before the DATA command). Say one ip or subnet is repeatedly sending you 1000's of msgs/week (maybe 100's of MB) that get through IMGate only to be DELETEd by Junkmail. By having Junkmail "tell" IMGate about those DELETEs, IMGate can block by ip (and perhaps @sender.domain), save the bandwidth on your WAN link and msg volumes through IMGate and Imail. Len
