From owner-freebsd-ports-bugs@freebsd.org Fri Apr 28 01:32:28 2017 Return-Path: Delivered-To: freebsd-ports-bugs@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 16128D53C46 for ; Fri, 28 Apr 2017 01:32:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0589C1459 for ; Fri, 28 Apr 2017 01:32:28 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v3S1WRex050905 for ; Fri, 28 Apr 2017 01:32:27 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218899] mail/mutt GSSAPI oddity Date: Fri, 28 Apr 2017 01:32:27 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Ports & Packages X-Bugzilla-Component: Individual Port(s) X-Bugzilla-Version: Latest X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Many People X-Bugzilla-Who: dereks@lifeofadishwasher.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-ports-bugs@FreeBSD.org X-Bugzilla-Flags: maintainer-feedback? X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Apr 2017 01:32:28 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D218899 --- Comment #1 from dereks@lifeofadishwasher.com --- Is this SMTP or IMAP auth that works once security/cyrus-sasl-gssapi is installed? If it's IMAP then maybe something is fishy however for SMTP it seems by design. GSSAPI options set GSS IMAP auth and SASL is for SMTP. SASL is enabled by default and security/cyrus-sasl is built without gss sup= port due gss being split off in 2013. Perhaps this has been "broken" in the mutt port since then or users followed UPDATING's directions (20131226) and installed security/cyrus-sasl-gssapi? I guess the port just doesn't know if the user needs GSS SASL auth. Do we n= eed another port option to control if security/cyrus-sasl-gssapi should be installed or can we assume if you want IMAP GSS auth it's safe to assume yo= u're going to need SMTP GSS auth as well? --=20 You are receiving this mail because: You are the assignee for the bug.=