On Mon, Oct 26, 2009 at 09:41:14AM +0800, Yao Ziyuan wrote: > Passive Spam Revocation (PSR) > > Currently almost all mail systems (e.g. Hotmail and Gmail) use a spam > filter, which can drop good and important messages. > > I propose an optional feature for current mail systems. The main idea > is if a message is considered spam, this spam status can be tracked by
I have an idea. Receiver could SMTP REJECT the message and sender gets an error? Wait.. it can be implemented already. ;-) > the sender (but not sent to him directly, as the From field can be > faked). The message can be re-marked as "not spam" if the sender can > solve a CAPTCHA. > > STEP 1: A is going to send B a message. A's mail client generates a > random code and puts it in a custom field in the outgoing message's > header: > Code: <random code> > STEP 2: A's mail client sends the message, waits 30 seconds, and then visits: > https://spamstatus.<B's mail domain>/?msgid=<Message-ID>&code=<Code> > This page displays one of these possible "spam statuses": > * MESSAGE CONSIDERED SPAM. (A CAPTCHA is also presented below.) > * MESSAGE CONSIDERED NOT SPAM. > * PENDING. PLEASE TRY AGAIN LATER. > * All other responses mean B's mail system doesn't support this feature. > > In the first case, A's mail client will report the status and the > CAPTCHA to A. A can choose to solve the CAPTCHA to prove the message > is not spam. So my botnet will send a million spams with NON-RANDOM (your proposal lets the CLIENT choose it) Code: and Message-ID: and hammers the www service for each message. I'm sure ISPs with thousands of hosted domains are happy to implement this service. Sorry this is stupid and no one will implement it. If it doesn't seem like a good idea in the first minute, it's pointless to try to make it better. The real problem is bad filtering and spam/quarantine folders. I don't see how this has anything to do with SpamAssassin anyway, perhaps try SPAM-L or some other list next time.
