Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP

Bron Gondwana <brong@fastmail.fm> Wed, 22 February 2012 19:36 UTC

Return-Path: <brong@fastmail.fm>
X-Original-To: imap5@ietfa.amsl.com
Delivered-To: imap5@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E31621F86E8 for <imap5@ietfa.amsl.com>; Wed, 22 Feb 2012 11:36:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.205
X-Spam-Level:
X-Spam-Status: No, score=-2.205 tagged_above=-999 required=5 tests=[AWL=-1.206, BAYES_50=0.001, RCVD_IN_DNSWL_LOW=-1]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BzZo6U8cqrt4 for <imap5@ietfa.amsl.com>; Wed, 22 Feb 2012 11:36:48 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by ietfa.amsl.com (Postfix) with ESMTP id 76B1421F86D1 for <imap5@ietf.org>; Wed, 22 Feb 2012 11:36:46 -0800 (PST)
Received: from compute2.internal (compute2.nyi.mail.srv.osa [10.202.2.42]) by gateway1.nyi.mail.srv.osa (Postfix) with ESMTP id E907621505 for <imap5@ietf.org>; Wed, 22 Feb 2012 14:36:45 -0500 (EST)
Received: from web3.nyi.mail.srv.osa ([10.202.2.213]) by compute2.internal (MEProxy); Wed, 22 Feb 2012 14:36:45 -0500
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=fastmail.fm; h= message-id:from:to:cc:mime-version:content-transfer-encoding :content-type:in-reply-to:references:subject:date; s=mesmtp; bh= /M0XGPQzBsq0K3WV8LK6dAmBOv4=; b=ixNUqi9iRVjEy96A0PKHcUv9fkxplT8m EBZnBAJpAYSIaNdSEL6QNmvc+TFpyhwq10F2Q1glui2FQ4NbIDj3NjSqmDWyJ7Zq j/6sbgIkyC+Xl4c1MmJeby7RHuBNanp8FJbeIlsThfbpD3SE8IARFj6vscy1q4VG WDIshTseSUc=
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d= messagingengine.com; h=message-id:from:to:cc:mime-version :content-transfer-encoding:content-type:in-reply-to:references :subject:date; s=smtpout; bh=/M0XGPQzBsq0K3WV8LK6dAmBOv4=; b=d0T iGHpZlWse+vo32dtzufUROU8J0fOS+NpiYZKvBJiv3t72D9a1bA8jXFzhdw0QOY/ A/bYT84b6+sqvAiJywLli0vguV/yj2q8xFJ6gzNtdTbgPFFC04ifwqGE7VM/Sz5o 7MwaHfEdyXTC3Xi5hKeQiMz4//ErfgsUXEFsAd5o=
Received: by web3.nyi.mail.srv.osa (Postfix, from userid 99) id 99084400EC; Wed, 22 Feb 2012 14:36:45 -0500 (EST)
Message-Id: <1329939405.3389.140661039979197@webmail.messagingengine.com>
X-Sasl-Enc: n/LEO4aH1nX9uwjWDs8zKZjgTfneJCXbGA71KxYziaIO 1329939405
From: Bron Gondwana <brong@fastmail.fm>
To: Brandon Long <blong@google.com>, Adrien de Croy <adrien@qbik.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
X-Mailer: MessagingEngine.com Webmail Interface
In-Reply-To: <CABa8R6ss=a5cXxO0TgF0df-E0irLT7HU5k9gXh0GXoShWcwbEA@mail.gmail.com>
References: <3077.1329391344.173214@puncture> <4F3CEB35.9080200@qbik.com><1329394296.953.140661037317197@webmail.messagingengine.com><4F3CFD35.10501@qbik.com><alpine.LSU.2.00.1202161626400.30682@hermes-2.csi.cam.ac.uk><4F3D6E57.8010301@qbik.com> <20120216224124.GC4578@dan.olp.net><CABa8R6uxeFVSDQzzSS6ziV8b2roYdw38GMpjEm+1DGkhD3MdVg@mail.gmail.com><20120216232954.GB5356@dan.olp.net> <4F3DA4A6.5020304@qbik.com><20120217171457.GB4503@dan.olp.net> <4F3F5234.2080406@qbik.com><4F3F56E7.3080004@panozzo.it> <4F3F784B.2000809@qbik.com> <CABa8R6ss=a5cXxO0TgF0df-E0irLT7HU5k9gXh0GXoShWcwbEA@mail.gmail.com>
Date: Wed, 22 Feb 2012 20:36:45 +0100
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>
Subject: Re: [imap5] Feature set? - was Re: Designing a new replacement protocol for IMAP
X-BeenThere: imap5@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion on drastically slimming-down IMAP." <imap5.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/imap5>, <mailto:imap5-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/imap5>
List-Post: <mailto:imap5@ietf.org>
List-Help: <mailto:imap5-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/imap5>, <mailto:imap5-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 22 Feb 2012 19:36:49 -0000

On Wed, Feb 22, 2012, at 11:24 AM, Brandon Long wrote:
> You seem to believe that all servers can always be entirely free from
> sending spam.  That's pretty funny.

Yeah, this.  We're a lot smaller than you, and we are more strict about
spam scanning what goes OUT than what comes in, but we still wind up
with all the usual reasons why we have outbound spam :(

> [...] They don't see how much effort we put into it, and
> they know nothing about it until their account gets hijacked or one of
> their friends does and they get a mugged in London message.  Or when
> some filter gets too aggressive and they don't get a message.  Or when
> some company still thinks the spam world is black & white and uses a
> blacklist against their server.

Or because someone's incoming rate limits are delaying their messages
(just saying ;) - one of my major causes of notifications is someone
who forwards all their email to gmail causing a massive outbound
backlog when their monitoring service goes crazy and your inbound limits
are stricter than our inbound limits...

> Any effort they would have to make to
> whitelist senders before they can send them mail is something they
> aren't likely to understand the need for.

There's some nice stuff you can do with semi-automatic whitelisting
(up-rate things which are a response to something they have already
sent, certainly up-rate addresses in their address book) - but we
found you can't go too far there (like whitelisting "from self"
because the spammers will exploit that.  Same with whitelisting stuff
from someone who has already spoken to them, because it just means
you get targetted spam supposedly from someone else on a public
mailing list.

> As for getting the Facebooks of the world to open up their social
> connection information to solve the spam problem for you, well, good
> luck with that.  If you're Yahoo or Microsoft you can pay enough money
> to get access to that, and maybe its in the ToS to use it that way.

The more I read (particularly from Bruce Schneier) about this, the
more I realise that spam isn't solveable.  Make it harder, and it
will be more valuable to be able to get through, because the scammer
is no longer competing against a ton of other scams.  The flavour
might change to more targetted, but unsolicited rubbish will always
exist.  The internet is not a special flower here.

Bron.
-- 
  Bron Gondwana
  brong@fastmail.fm