Re: [Asrg] Generally workable ways of adding a spam button to MUAs

Ian Eiloart <iane@sussex.ac.uk> Tue, 09 February 2010 12:20 UTC

Return-Path: <iane@sussex.ac.uk>
X-Original-To: asrg@core3.amsl.com
Delivered-To: asrg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 4CE1F3A755E for <asrg@core3.amsl.com>; Tue, 9 Feb 2010 04:20:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.506
X-Spam-Level:
X-Spam-Status: No, score=-2.506 tagged_above=-999 required=5 tests=[AWL=-0.063, BAYES_00=-2.599, SUBJECT_FUZZY_TION=0.156]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id NXN+zCT5OTRQ for <asrg@core3.amsl.com>; Tue, 9 Feb 2010 04:20:29 -0800 (PST)
Received: from sivits.uscs.susx.ac.uk (sivits.uscs.susx.ac.uk [139.184.14.88]) by core3.amsl.com (Postfix) with ESMTP id ECF7628C1EA for <asrg@irtf.org>; Tue, 9 Feb 2010 04:20:19 -0800 (PST)
Received: from lewes.staff.uscs.susx.ac.uk ([139.184.135.133]:51250) by sivits.uscs.susx.ac.uk with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.64) (envelope-from <iane@sussex.ac.uk>) id KXKQCB-000322-L1 for asrg@irtf.org; Tue, 09 Feb 2010 12:21:47 +0000
Date: Tue, 09 Feb 2010 12:21:12 +0000
From: Ian Eiloart <iane@sussex.ac.uk>
Sender: iane@sussex.ac.uk
To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
Message-ID: <50A41CF939734E960F23B3AD@lewes.staff.uscs.susx.ac.uk>
In-Reply-To: <4B704FCF.7030406@nortel.com>
References: <20100205152046.87683.qmail@simone.iecc.com> <A57020F253FEFC9A8ED39F50@lewes.staff.uscs.susx.ac.uk> <4B704FCF.7030406@nortel.com>
Originator-Info: login-token=Mulberry:01weWsGCpGGn0CUgB6LQs0Wh+LJ13NciQLNlA=; token_authority=support@its.sussex.ac.uk
X-Mailer: Mulberry/4.0.8 (Mac OS X)
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
X-Sussex: true
X-Sussex-transport: remote_smtp
Subject: Re: [Asrg] Generally workable ways of adding a spam button to MUAs
X-BeenThere: asrg@irtf.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <asrg@irtf.org>
List-Id: Anti-Spam Research Group - IRTF <asrg.irtf.org>
List-Unsubscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/asrg>
List-Post: <mailto:asrg@irtf.org>
List-Help: <mailto:asrg-request@irtf.org?subject=help>
List-Subscribe: <http://www.irtf.org/mailman/listinfo/asrg>, <mailto:asrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 09 Feb 2010 12:20:30 -0000

--On 8 February 2010 12:54:23 -0500 Chris Lewis <clewis@nortel.com> wrote:

> By insisting on MDA-specific methods, it forces the same result as making
> the assumption that all the world is IMAP (+ POP or whatever other
> protocol we deign to notice).  It isn't.
>
>> I'm simply claiming that the problem isn't
>> a single problem (1. "how to report junk messages"). It's two problems:
>> "2.  how to report junk messages to an IMAP mailstore operator" and "3.
>> how to  report junk messages to a POP mailstore operator".
>
> Four: SMTP

You use SMTP to retrieve messages from a mailstore? No, I guess you mean 
that you want to be able to send a report to the operator who forwarded 
spam to your primary mail account. I provide a forwarding service, but if 
the message isn't stored on my system, then I'm not going to trust the 
report. One thing that I know about email that I've forwarded is that it 
doesn't look like the message that I saw originally.

This is already a different problem.

> Five: Webmail

We have a webmail service. It's an IMAP mail client. If yours isn't, then 
the question is "can it flag messages" in the same way that an IMAP client 
can? If it can, then an IMAP flag-like solution could be implemented in the 
client.

> Six: Microsoft RPC

You mean Exchange clients? They also have different problem. For example, 
they haven't preserved the RFC5322 headers properly.



-- 
Ian Eiloart
IT Services, University of Sussex
01273-873148 x3148
For new support requests, see http://www.sussex.ac.uk/its/help/