Re: [Asrg] We don't need no stinkin IMAP or POP, was Adding a spam button to MUAs

Steve Atkins <> Sat, 06 February 2010 18:09 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id D11413A70E6 for <>; Sat, 6 Feb 2010 10:09:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -6.449
X-Spam-Status: No, score=-6.449 tagged_above=-999 required=5 tests=[AWL=-0.006, BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4, SUBJECT_FUZZY_TION=0.156]
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jxvfyP362saj for <>; Sat, 6 Feb 2010 10:09:39 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 2ACB03A70E5 for <>; Sat, 6 Feb 2010 10:09:39 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 4D5724F82C1 for <>; Sat, 6 Feb 2010 10:10:34 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Apple Message framework v1077)
From: Steve Atkins <>
In-Reply-To: <>
Date: Sat, 6 Feb 2010 10:10:34 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <>
To: Anti-Spam Research Group - IRTF <>
X-Mailer: Apple Mail (2.1077)
Subject: Re: [Asrg] We don't need no stinkin IMAP or POP, was Adding a spam button to MUAs
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: Anti-Spam Research Group - IRTF <>
List-Id: Anti-Spam Research Group - IRTF <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sat, 06 Feb 2010 18:09:39 -0000

On Feb 6, 2010, at 9:29 AM, Chris Lewis wrote:

> John Levine wrote:
>>> Make the ARF reporting address a configurable option, but default it to a role account at the email domain of the machine from which incoming mail is obtained.
>> Now it's not opt-in by the mailstore provider.
> We need to have it self-configuring if the mailstore provides the service.  Which either means a standard role account for it, or, some way for the mailstore to tell the UA what address to use.
> IOW: pure user configurable doesn't do that.
> In-stream configuration (via MDA or MTA) would work, but it requires the MDA/MTA be modified.  Which we're avoiding.

It requires the ability to add a header, for basic usage a constant header. That's a trivial configuration change, nothing more.

(And it avoids all the nasty heuristics people are discussing entirely, while providing way more flexibility).

> We've been talking about using DNS for some of the signalling.  You could specify a "_report.<mailstore hostname>" TXT record that specifies the address (which isn't necessarily in the mailstore's domain) to send it _and_ its very existence shows that the mailstore provider supports the functionality (and thus the TiS button gets enabled).
> Now, if the TXT record doesn't exist, we could suggest that the user could set their own abuse report destination.  But I'd rather not get into a situation where the user overrides the mailstore's explicit choice.