From owner-freebsd-ports-bugs@FreeBSD.ORG  Fri Mar 14 03:48:38 2014
Return-Path: <owner-freebsd-ports-bugs@FreeBSD.ORG>
Delivered-To: freebsd-ports-bugs@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 936B95C6
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 14 Mar 2014 03:48:38 +0000 (UTC)
Received: from mail.soaustin.net (pancho.soaustin.net [76.74.250.40])
 by mx1.freebsd.org (Postfix) with ESMTP id 76995801
 for <freebsd-ports-bugs@FreeBSD.org>; Fri, 14 Mar 2014 03:48:38 +0000 (UTC)
Received: by mail.soaustin.net (Postfix, from userid 502)
 id D27D35607C; Thu, 13 Mar 2014 22:48:37 -0500 (CDT)
Date: Thu, 13 Mar 2014 22:48:37 -0500
From: Mark Linimon <linimon@lonesome.com>
To: Matthew Luckie <mjl@luckie.org.nz>
Subject: Re: ports/187539: maintainer-update of mail mutt
Message-ID: <20140314034837.GB5484@lonesome.com>
References: <201403132020.s2DKK27B046498@freefall.freebsd.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <201403132020.s2DKK27B046498@freefall.freebsd.org>
User-Agent: Mutt/1.5.21 (2010-09-15)
Cc: freebsd-ports-bugs@FreeBSD.org
X-BeenThere: freebsd-ports-bugs@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: Ports bug reports <freebsd-ports-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports-bugs/>
List-Post: <mailto:freebsd-ports-bugs@freebsd.org>
List-Help: <mailto:freebsd-ports-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports-bugs>, 
 <mailto:freebsd-ports-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 14 Mar 2014 03:48:38 -0000

On Thu, Mar 13, 2014 at 08:20:02PM +0000, Matthew Luckie wrote:
>  Can we update the severity of this PR so there might be more priority
>  to committing this fix?  There's a CVE associated.

The severity field is almost meaningless these days.

For security problems, it is best to email secteam@FreeBSD.org.

mcl