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

Brandon Long <blong@google.com> Thu, 16 February 2012 22:57 UTC

Return-Path: <blong@google.com>
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 7F19121F854E for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:57:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.977
X-Spam-Level:
X-Spam-Status: No, score=-102.977 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_LOW=-1, USER_IN_WHITELIST=-100]
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 B5AKv+o+g2gw for <imap5@ietfa.amsl.com>; Thu, 16 Feb 2012 14:57:55 -0800 (PST)
Received: from mail-qw0-f44.google.com (mail-qw0-f44.google.com [209.85.216.44]) by ietfa.amsl.com (Postfix) with ESMTP id E6A3D21F854C for <imap5@ietf.org>; Thu, 16 Feb 2012 14:57:54 -0800 (PST)
Received: by qafi29 with SMTP id i29so194199qaf.10 for <imap5@ietf.org>; Thu, 16 Feb 2012 14:57:54 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record; bh=PkhozYU1VyR2co+8MhhhbkvNYLjhRTM5zwRpMnm/hXw=; b=UpjEiyZZW2c2jS+I2aI+LbmjWOOd1tI/sxZv4fpMsQKRakICbXvzCebA0HxR8xp8MU K9EUbxikedsUleLvKt+qSmF84fVc3U69Oxbf8EJVU3YadY1kG590sNQrVo83jOmk9njF AZ1Iy9noXd0fz6CEIi+Vp9t9rRLXDXoNBPt+w=
Received: by 10.229.76.21 with SMTP id a21mr3214193qck.20.1329433074158; Thu, 16 Feb 2012 14:57:54 -0800 (PST)
MIME-Version: 1.0
Received: by 10.229.76.21 with SMTP id a21mr3214179qck.20.1329433073978; Thu, 16 Feb 2012 14:57:53 -0800 (PST)
Received: by 10.229.216.201 with HTTP; Thu, 16 Feb 2012 14:57:53 -0800 (PST)
In-Reply-To: <20120216224124.GC4578@dan.olp.net>
References: <3077.1329386263.642278@puncture> <4F3CD728.3010203@qbik.com> <3077.1329388899.383165@puncture> <4F3CE16B.3060603@qbik.com> <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>
Date: Thu, 16 Feb 2012 14:57:53 -0800
Message-ID: <CABa8R6uxeFVSDQzzSS6ziV8b2roYdw38GMpjEm+1DGkhD3MdVg@mail.gmail.com>
From: Brandon Long <blong@google.com>
To: Dan White <dwhite@olp.net>
Content-Type: text/plain; charset="ISO-8859-1"
X-System-Of-Record: true
X-Gm-Message-State: ALoCoQlu2QzNxA0a4YpEc0uQilvT1sARB8+HJQO4/dWq0fTbYQg3GvDwtOpajDrtn/Lpnnu4/YE1tdvdSSIh2cNuI4WeW5R69ARBbQTrQNzvxw8l8f9xWEERLCepZxqHJ+xOVsW5SkLs
Cc: "Discussion on drastically slimming-down IMAP." <imap5@ietf.org>, Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
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: Thu, 16 Feb 2012 22:57:55 -0000

On Thu, Feb 16, 2012 at 2:41 PM, Dan White <dwhite@olp.net> wrote:
> However, spam is a problem caused by a deficiency (or whatever you want to
> call it) within the smtp protocol. imap does not directly or indirectly lead
> to the generation of spam, unless you want to consider backscatter from a
> sieve notification to be spam.
>
> smtp (or submission) is one of those things that's actually easy to
> configure in an email client. I fear that if the two get combined on the
> same port that imap server IPs may start to get caught up in the cat
> and mouse game spam parsers play.

IMAP playing the game is no different than SMTP-MSA playing the game,
it still requires authentication.  I'm not sure how wide-spread it is,
but we certainly already have to deal with spam through spammy
accounts or hijacked accounts over SMTP-MSA.  I find it hard to
believe that IMAP doing mail submission is going to change any of
that, but perhaps you mean that you would have to have the same smarts
for protecting against bad logins in IMAP that you have in SMTP-MSA...
but I would expect anyone who's under attack for either already does
that as well (we certainly use the same auth backend for both.

Brandon