IMAP authentication changes
Robert Sparks <rjsparks@nostrum.com> Mon, 08 May 2023 20:59 UTC
Return-Path: <rjsparks@nostrum.com>
X-Original-To: ietf@ietfa.amsl.com
Delivered-To: ietf@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 948E8C16B5A6; Mon, 8 May 2023 13:59:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.277
X-Spam-Level:
X-Spam-Status: No, score=-1.277 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_INVALID=0.1, DKIM_SIGNED=0.1, KHOP_HELO_FCRDNS=0.399, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, T_SPF_HELO_PERMERROR=0.01, T_SPF_PERMERROR=0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=fail (1024-bit key) reason="fail (message has been altered)" header.d=nostrum.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 8QGEnAdQGFdG; Mon, 8 May 2023 13:59:21 -0700 (PDT)
Received: from nostrum.com (raven-v6.nostrum.com [IPv6:2001:470:d:1130::1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BF5E4C151982; Mon, 8 May 2023 13:59:21 -0700 (PDT)
Received: from [192.168.1.102] ([47.186.48.51]) (authenticated bits=0) by nostrum.com (8.17.1/8.17.1) with ESMTPSA id 348KxJOL064792 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Mon, 8 May 2023 15:59:19 -0500 (CDT) (envelope-from rjsparks@nostrum.com)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=nostrum.com; s=default; t=1683579560; bh=evTRRpR+WIeehnzkazlSqjTjY4VbO4J0kNC2pZB7wec=; h=Date:To:Reply-To:From:Subject; b=hA6vcnmbhyQ6kJPzbi/9CmFoHhzt3UDQIgjPnXOX/eNHSXYv89sAzpy5Z+G7OiPEi Is4mLTQnTP1bd/a2W2Nysu85IH7MfJau/R43pJLE9kS8pfT7c88XOnmR7KIoSLct2J ZEqJMW3mpt8306t0di0L4za3P9AFXU80VHH4bqfs=
X-Authentication-Warning: raven.nostrum.com: Host [47.186.48.51] claimed to be [192.168.1.102]
Message-ID: <cf80c2a9-8dd7-0af3-7471-8b8b51d4a663@nostrum.com>
Date: Mon, 08 May 2023 15:59:14 -0500
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.10.1
Content-Language: en-US
To: IETF discussion list <ietf@ietf.org>, tools-discuss <tools-discuss@ietf.org>, Working Chairs <wgchairs@ietf.org>
Reply-To: tools-discuss <tools-discuss@ietf.org>
From: Robert Sparks <rjsparks@nostrum.com>
Subject: IMAP authentication changes
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf/FhGJB6J0rfB7HbbdZS0MHEIsjag>
X-BeenThere: ietf@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF-Discussion. This is the most general IETF mailing list, intended for discussion of technical, procedural, operational, and other topics for which no dedicated mailing lists exist." <ietf.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf>, <mailto:ietf-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf/>
List-Post: <mailto:ietf@ietf.org>
List-Help: <mailto:ietf-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf>, <mailto:ietf-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 08 May 2023 20:59:25 -0000
All - We have changed the way the IETF IMAP service authenticates against the datatracker. In the process, we also discovered a bug that was allowing some people to authenticate with bad passwords that has been corrected. If you can't authenticate with the IMAP service now, but you have been able to in the past, please check that you are using the password that goes with the username you have provided. Note that the IMAP service does not (yet) let you login with any email address known to your Person the way the datatracker does. Your password will need to match your actual datatracker User username. This is something that we're working with Alexey to change in the future so that it behaves exactly as the datatracker does. If you try the above and are still not able to access IMAP, send email to support@ietf.org. RjS
- IMAP authentication changes Robert Sparks