From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Robert Pluim Newsgroups: gmane.emacs.bugs Subject: bug#31990: 26.1; Stuck in loop trying to send bug report Date: Tue, 21 Aug 2018 12:22:19 +0200 Message-ID: <87va84uihw.fsf@gmail.com> References: <87zhxg8ja5.fsf@aol.com> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1534846869 28521 195.159.176.226 (21 Aug 2018 10:21:09 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Tue, 21 Aug 2018 10:21:09 +0000 (UTC) Cc: 31990@debbugs.gnu.org To: Live System User Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Aug 21 12:21:05 2018 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fs3mZ-0007En-8i for geb-bug-gnu-emacs@m.gmane.org; Tue, 21 Aug 2018 12:21:03 +0200 Original-Received: from localhost ([::1]:52139 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fs3oe-0002bO-3W for geb-bug-gnu-emacs@m.gmane.org; Tue, 21 Aug 2018 06:23:12 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59363) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1fs3oX-0002bJ-Tt for bug-gnu-emacs@gnu.org; Tue, 21 Aug 2018 06:23:06 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1fs3oU-0006LP-2Q for bug-gnu-emacs@gnu.org; Tue, 21 Aug 2018 06:23:05 -0400 Original-Received: from debbugs.gnu.org ([208.118.235.43]:51177) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1fs3oT-0006LJ-Uc for bug-gnu-emacs@gnu.org; Tue, 21 Aug 2018 06:23:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1fs3oT-0002T9-P2 for bug-gnu-emacs@gnu.org; Tue, 21 Aug 2018 06:23:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Robert Pluim Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 21 Aug 2018 10:23:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31990 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 31990-submit@debbugs.gnu.org id=B31990.15348469499450 (code B ref 31990); Tue, 21 Aug 2018 10:23:01 +0000 Original-Received: (at 31990) by debbugs.gnu.org; 21 Aug 2018 10:22:29 +0000 Original-Received: from localhost ([127.0.0.1]:56195 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fs3nx-0002SL-Ci for submit@debbugs.gnu.org; Tue, 21 Aug 2018 06:22:29 -0400 Original-Received: from mail-wm0-f44.google.com ([74.125.82.44]:37870) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1fs3nv-0002S9-Th for 31990@debbugs.gnu.org; Tue, 21 Aug 2018 06:22:28 -0400 Original-Received: by mail-wm0-f44.google.com with SMTP id n11-v6so2352932wmc.2 for <31990@debbugs.gnu.org>; Tue, 21 Aug 2018 03:22:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:references:mail-copies-to:gmane-reply-to-list :date:in-reply-to:message-id:mime-version:content-transfer-encoding; bh=Zy6ROsfv5pZ6Sumop+RhaTb6kUSR0B41Bvj+1UbYVVI=; b=hPDTsBXj7oBrdCw2gIMZMwVVWA1GAp1+4BtLwrFf7azuTH+tiZr8vS0PIPckmrMnSz 80oE3FtcRZZLjI4BwMjm3KLKu/yTxX7M28jGZqTw3ANZGxo1rWijnvT1kmTJxjsl3/sb A2CYG8sZYDBj72GdfKM0NToNstIkodUs0/m+pnzo0aOe+NV6pZ7RcRpRpfmnYT+SjU4/ jZ/Z/Ep/TlIYOe65FQUBb+lMdCTAe8XEkAJxApcCmLpYN4N51gS54e0tw4afVltXyCEu Ya3O39Qu0sw57tJFHd5LSuOEWuymKkMtHUfFnP8yShpntFMEKzPtJj1AJIxEkPsJZB0q Yxwg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:references:mail-copies-to :gmane-reply-to-list:date:in-reply-to:message-id:mime-version :content-transfer-encoding; bh=Zy6ROsfv5pZ6Sumop+RhaTb6kUSR0B41Bvj+1UbYVVI=; b=dfCjKX+1zAMNlgAQKL7OvCzaDtXyGzUdBFDMJHIwY0JPq8+qRdvQ29rKSTpXiXjZO7 Hq7EaFn5dsj51mnBUtw70geKjy2dqBpgaLq0nrWF8YDgr9T3ttUoW41FnioK4rLqp/tJ 5OcV9wHFxUEBY3mXnPtpzPZDgfrNFtyKjnPengnYIMbST5rw6HBjTbP2werMQGAWLxIM KeN9I4ci/uIhCUfCWaLyhvSG8rLZjIdvAMdi5OVPgnWnGaYCCmk2KxTph3pS6snzYyRT kJ5EbtRaXQvu4NDWMG3sH+z4PXfbkFkSHwmNooGb+VdwY3uqoF1QuVmXbw0qWc+pyUCR d0ZA== X-Gm-Message-State: AOUpUlEKM1h+2K8a4W+TvFfDoh0sNd3MEcPr4ipvUhWv3EfYyidxJaxk mJzAMXNf8/+IuIfWlqOCOr8Qw3RS X-Google-Smtp-Source: AA+uWPwivMUTZwfUPDcpgFOf46r4Psg/94ak68DCdfobfgIeR6rueHNDRtFMRRkz2IyUawS+NnNAaA== X-Received: by 2002:a1c:ae8d:: with SMTP id x135-v6mr28346725wme.20.1534846941834; Tue, 21 Aug 2018 03:22:21 -0700 (PDT) Original-Received: from rpluim-ubuntu ([149.5.228.1]) by smtp.gmail.com with ESMTPSA id v21-v6sm8755222wrd.4.2018.08.21.03.22.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Aug 2018 03:22:20 -0700 (PDT) Mail-Copies-To: never Gmane-Reply-To-List: yes In-Reply-To: <87zhxg8ja5.fsf@aol.com> (Live System User's message of "Mon, 20 Aug 2018 23:56:18 -0400") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:149638 Archived-At: Live System User writes: > Robert Pluim writes: > >> Live System User writes: >> >>>> Then how do you expect emacs to know that for those 2 particular >>>> servers it should prompt straight away? >>> >>> Because (I believe) that the protocol requires a "password" or >>> certificate. >> >> That=CA=BCs unfortunately not the way SMTP authentication works, > > I thought from my original message that you responded to that > you understood that the "protocol" I'm referring to (above) is > TLS (in conjunction with SMTP), not SMTP separately or in the > absense of a TLS connection. > > Perhaps we are miscommunicating? We are. I=CA=BCm only talking about SMTP authentication, not TLS. Without going back and rereading, my memory says that it turned out you were not having a TLS issue. > >> it=CA=BCs very >> much optional > > I believe that either a "password" or a certicate is needed > to establish a TLS conection and not optional. > You need a certificate on the server side for TLS. For SMTP auth you need a password. The two are completely separate protocols. >> (and some servers change their authentication >> requirements based on the recipient of the mail you=CA=BCre trying to >> send). > > Are we still talking about TLS connectons? >=20=20=20 > Unless there is NO authenication required, a changed authenication > requirement is still an authenication requiring a "password" or > certificate if it involves TLS, nonetheless. > > That valid "password" can even be blank, an email address or anything > (including the recipient) depending on the server's valid authenication > method. > > I'm saying that I believe the SSL/TLS or STARTTLS protocols require > a "password" or certficate. Are you saying that's incorrect or it's > not necessarily so? >> As noted above, I=CA=BCm only talking about SMTP authentication. Robert