Re: [ietf-822] a detour into SPF, was Mailing lists - assumptions

Ned Freed <ned.freed@mrochek.com> Mon, 21 April 2014 05:23 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: ietf-822@ietfa.amsl.com
Delivered-To: ietf-822@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CB4E81A0043 for <ietf-822@ietfa.amsl.com>; Sun, 20 Apr 2014 22:23:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.274
X-Spam-Level:
X-Spam-Status: No, score=-2.274 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RP_MATCHES_RCVD=-0.272, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MMKnFMCEfhLA for <ietf-822@ietfa.amsl.com>; Sun, 20 Apr 2014 22:23:56 -0700 (PDT)
Received: from mauve.mrochek.com (mauve.mrochek.com [66.159.242.17]) by ietfa.amsl.com (Postfix) with ESMTP id 7C53E1A002D for <ietf-822@ietf.org>; Sun, 20 Apr 2014 22:23:56 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6VVPUA4BK006DLU@mauve.mrochek.com> for ietf-822@ietf.org; Sun, 20 Apr 2014 22:18:49 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=mrochek.com; s=mauve; t=1398057526; bh=F6bUb63LYtI5DaMgupRHOpBL9rsOIzM2RDrbTxyUbNo=; h=Cc:Date:From:Subject:In-reply-to:References:To; b=LUfQEc/Yi1bAYjerHb6qDB8nb4rDV1/yicybO/ITSkLdn/GyjCVC4u3yQG1OlU8Xq /cE2l2g/anC9C3nTdQ+KoEOvEiPSsaCgi1ddWJe9y9fPynIDjrhal2Fzh95w+yT4Og 2AdirW9tPIqLVdYDqZk8NAXJGpFHafe6pemP0dWQ=
MIME-version: 1.0
Content-type: TEXT/PLAIN; CHARSET="iso-8859-1"
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01P6SVAPGZY800004W@mauve.mrochek.com>; Sun, 20 Apr 2014 22:18:46 -0700 (PDT)
Message-id: <01P6VVPSHIX600004W@mauve.mrochek.com>
Date: Sun, 20 Apr 2014 22:17:08 -0700
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Sun, 20 Apr 2014 01:39:51 +0000" <20140420013951.56904.qmail@joyce.lan>
References: <01P6U784H7N400004W@mauve.mrochek.com> <20140420013951.56904.qmail@joyce.lan>
To: John Levine <johnl@taugh.com>
Archived-At: http://mailarchive.ietf.org/arch/msg/ietf-822/kGPsxGZraM8f3JZhTeZ6cCi0s7E
Cc: ietf-822@ietf.org, ned.freed@mrochek.com
Subject: Re: [ietf-822] a detour into SPF, was Mailing lists - assumptions
X-BeenThere: ietf-822@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "Discussion of issues related to Internet Message Format \[RFC 822, RFC 2822, RFC 5322\]" <ietf-822.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ietf-822/>
List-Post: <mailto:ietf-822@ietf.org>
List-Help: <mailto:ietf-822-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-822>, <mailto:ietf-822-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Apr 2014 05:23:58 -0000

> >Yes indeedy. Looks to me like bog-standard SRS. ...

> >At present draft-ietf-spfbis-4408bis has this to say about the issue:
> >
> > o  Mediators can solve the problem by rewriting the "MAIL FROM" to be
> >    in their own domain.  This means mail rejected from the external
> >    mailbox will have to be forwarded back to the original sender by
> >    the forwarding service.  Various schemes to do this exist though
> >    they vary widely in complexity and resource requirements on the
> >    part of the mediator.
> >
> >Does anyone seriously think this provides the necessary guidance to an
> >autoforwarder developer/administrator faced with wholesale rejection of their
> >forwarded mail due to SPF? Because I certainly don't.

> Nobody brought it up in SPFBIS that I can recall.  SRS has been around
> for a decade, and I only see it in a few academic mail forwarders and
> one web host's mail gateway.  The problem that SRS solves evidently
> isn't one that people care enough about very much.

Well, I don't claim to speak for the Internet, but there's been a fair bit
of interest in the SRS support we provide in our product... And that's
from my perspective; I only hear about what people are using when they
have a problem setting it up, find a bug, etc.

				Ned