From: Richard Riley <rileyrg@googlemail.com>
To: ding@gnus.org
Subject: something changed in emacs 24 with gmail authentication?
Date: Tue, 01 Nov 2011 14:40:58 +0100 [thread overview]
Message-ID: <nzwrbk2c5x.fsf@news.eternal-september.org> (raw)
I just noticed that my emails from gnus are not sending. Nothing has
changed on my client other than a git pull recently for emacs 24.
,----
| 2011-11-01 14:37:09 1RLEWZ-0001UH-St plain authenticator failed H=gmail-smtp-msa.l.google.com [74.125.39.109] 535-5.7.1 Username and Password not accepted. Learn more at
| 535 5.7.1 http://mail.google.com/support/bin/answer.py?answer=14257 y17sm44891623faf.1
`----
Same entry in my .authinfo
server set up like this:-
,----
| (add-to-list 'gnus-secondary-select-methods
| '(nnimap "riley"
| (nnir-search-engine imap)
| (nnimap-address "imap.gmail.com")
| ))
`----
authinfo entry like this
,----
| machine riley login rileyrg password ******
`----
debian squeeze.
next reply other threads:[~2011-11-01 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-01 13:40 Richard Riley [this message]
2011-11-01 17:06 ` Ted Zlatanov
2011-11-02 14:35 ` Richard Riley
2011-11-02 14:45 ` Richard Riley
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=nzwrbk2c5x.fsf@news.eternal-september.org \
--to=rileyrg@googlemail.com \
--cc=ding@gnus.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).