Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: info-gnus-english@gnu.org
Subject: Re: Imap problems after yrs of use with my config.
Date: Mon, 14 Aug 2017 16:39:46 -0700	[thread overview]
Message-ID: <874lt97m7x.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87bmni9dax.fsf@local.lan>

Harry Putnam <reader@newsguy.com> writes:

> My remote imap server is imap.fastmail.com.

[...]

> 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 doubt this is much to do with Gnus in particular. A quick scan of the
Fastmail documentation simply says that your "real" account password
will only work with Fastmail's own app/web client, so you should
definitely be using the "app password" you created for Gnus. Just to
make everything clean, I'd also delete the authinfo line, and give the
credentials manually when Gnus prompts you.

They also say not to use starttls, but it looks like nnimap will try ssl
first, anyway, so that shouldn't make any difference. If you're
a belt-and-suspenders kind of guy, you could try setting nnimap-stream
to `ssl' in your secondary methods setting.

In general, when stuff like this doesn't work out, it's usually best to
drop out of Emacs/Gnus and try via the command line. Depending on your
system, you can use something like gnutls-cli or openssl s_client to
manually log in from the command line, and sometimes that will show you
something interesting. At least it might rule out some problems.

Dunno what else to say...

Eric



  reply	other threads:[~2017-08-14 23:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-14 19:09 Harry Putnam
2017-08-14 23:39 ` Eric Abrahamsen [this message]
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=874lt97m7x.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).