Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Richmond <dnomhcir@gmx.com>
To: "Adam Sjøgren via info-gnus-english" <info-gnus-english@gnu.org>
Subject: Re: gmail
Date: Sun, 05 Apr 2020 20:50:57 +0100	[thread overview]
Message-ID: <86blo5k8ym.fsf@gmx.com> (raw)
In-Reply-To: <87v9mdhiyw.fsf@tullinup.koldfront.dk> ("Adam =?utf-8?Q?Sj?= =?utf-8?Q?=C3=B8gren?= via info-gnus-english"'s message of "Sun, 05 Apr 2020 20:43:03 +0200")

Adam Sjøgren via info-gnus-english <info-gnus-english@gnu.org> writes:

> Richmond writes:
>
>> "This setting is not available for accounts with 2-Step Verification
>> enabled. Such accounts require an application-specific password for less
>> secure apps access. Learn more"
>
> Ah, I don't have 2-step verification enabled in Gmail. I guess you need
> to get an application-specific password then?
>
>> So I don't understand. I am able to use seamonkey and claws-mail with an
>> app password, and it used to work with gnus. I am using ssl on port 993.
>
> Maybe Gmail has changed?
>
> Does it work if you try with the app-specific password and specifying
> "port imap" in .authinfo.gpg (that's what used)?
>
>
>   Best regards,
>
>     Adam

Here is what I have in .gnus

(setq gnus-select-method '(nnimap "gmail"
 8                                  (nnimap-address "imap.gmail.com")
 9                                  (nnimap-server-port 993)
10                                  (nnimap-stream ssl)
11                                  (nnimap-logout-timeout 60.0)))

And in .authinfo

machine imap.gmail.com login "xxxxxxxxxxx@gmail.com" password xxxxxxxxxxxx port 993

I set the gnutls-log-level to 2 and see these. Maybe they have changed
tls requirements? :

gnutls.c: [2] Advertizing version 3.4
 76
 77gnutls.c: [2] Advertizing version 3.3
 78
 79gnutls.c: [2] Advertizing version 3.2
 80
 81gnutls.c: [2] Advertizing version 3.1
 82
 83gnutls.c: [2] HSK[0x2745000]: sent server name: 'imap.gmail.com'
 84
 85gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [336 times]
 86gnutls.c: [2] EXT[0x2745000]: client generated X25519 shared key
 87
 88gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [2 times]
 89gnutls.c: [2] (Emacs) Deallocating x509 credentials
 90Unable to open server nnimap+gmail due to: Process *nnimap* not running

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2020-04-05 19:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 17:59 gmail Richmond
2020-04-05 18:16 ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 18:35   ` gmail Richmond
2020-04-05 18:43     ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 19:50       ` Richmond [this message]
2020-04-05 20:02         ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 20:38           ` gmail Richmond
2020-04-05 20:47             ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 20:48               ` gmail Richmond
2020-04-05 20:55                 ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 21:00                   ` gmail Adam Sjøgren via info-gnus-english
2020-04-05 21:25     ` gmail Bob Newell
2020-04-05 21:51       ` gmail Richmond

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86blo5k8ym.fsf@gmx.com \
    --to=dnomhcir@gmx.com \
    --cc=info-gnus-english@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).