From: Harry Putnam <reader@newsguy.com>
To: info-gnus-english@gnu.org
Subject: Imap problems after yrs of use with my config.
Date: Mon, 14 Aug 2017 15:09:26 -0400 [thread overview]
Message-ID: <87bmni9dax.fsf@local.lan> (raw)
My remote imap server is imap.fastmail.com.
I've been able to access that server for literally a couple of yrs with the
following code.
(add-to-list 'gnus-secondary-select-methods
'(nnimap "hput3fm"
(nnimap-address "imap.fastmail.com")))
And the credential in ~/.authinfo
machine hput3fm login hput3@fastmail.fm password MY-PASSWD port imap force yes
------- ------- ---=--- ------- -------
On advice from fastmail I added:
(add-to-list 'gnus-secondary-select-methods
'(nnimap "hput3fm"
(nnimap-address "imap.fastmail.com")
(nnimap-server-port 993)))
They can't get past the notion that this is not being done on
some nifty windows application and so I added the port they insisted
on just in case it might help.
It did not help.
The uid and passwd has always been my login on their website.
I recently had to change my passwd at the web login
But in the course of this I found a new policy was put in place a
while ago where to use fastmail servers, you need to get something
they call an App passwd .. I guess they geared up to handle
phones/tablets and whatever.
So, I end up with 2 new passwds... one to access my fastmail acc and
this new policy ... app passwd for .. apparently for smtp server or
imap server.
OK, so I got account passwd changed about a week ago, and got the `app
passwd' on friday I think.
I've been unable to access imap.fastmail.com ever since.
I did try with both new passwds, making sure.
I've been in touch with fastmail via a trouble ticket but so far their
usefulness has been right up there with teats on a boar hog.
They've told me to use the `App passwd' now. Of course I replied
letting them know it was not working and waiting now to hear back.
So any suggestions as to what I can do to learn more about why it is
rejected?
I don't see much in \*Messages\*
I open another emacs window and go to \*Messages\* buffer, then
in the other window, enter the server buffer, then at the `denied'
flag on the fastmail server I do a Close followed by an open
(C, then O) then a few moments, the `denied' flag reappears.
But all that appears in the \*Messages\* buffer is:
Opening connection to imap.fastmail.com via tls...
That's it.
next reply other threads:[~2017-08-14 19:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-14 19:09 Harry Putnam [this message]
2017-08-14 23:39 ` Eric Abrahamsen
2017-08-15 13:35 ` Harry Putnam
2017-08-15 13:16 ` Byung-Hee HWANG (황병희, 黃炳熙)
2017-08-17 14:42 ` Harry Putnam
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=87bmni9dax.fsf@local.lan \
--to=reader@newsguy.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).