From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: problems with passwords containing characters with UTF-8 / ASCII codes >= 127
Date: Fri, 20 Nov 2015 11:05:39 -0500 [thread overview]
Message-ID: <87y4dsodv0.fsf@lifelogs.com> (raw)
In-Reply-To: <CALyZvKzPHH=AD+LXoMcmu+Bd-cXZ7YaYLc3fA459Gq0ZFRSDNQ@mail.gmail.com>
On Mon, 16 Nov 2015 16:17:02 +0000 Jason Vas Dias <jason.vas.dias@gmail.com> wrote:
JVD> Today I wasted alot of time after being forced to change my password,
...
JVD> just resulted in the message '(inhibited)' being written to the '*imap
JVD> log*' buffer .
JVD> Is there anyway to get gnus to be more verbose about the SSL encrypted
JVD> command / response traffic it is having with the server and precisely
JVD> why it fails ?
JVD> Maybe I should look at patching it to be more verbose when an IMAP error occurs.
That might be a good idea, but be careful about leaking the password to
a general buffer like *Messages*. It's OK for a quick run, but you
don't want to do it all the time.
In your case, `auth-source-debug' set to 'trivia or t or a custom
function might have helped.
Ted
prev parent reply other threads:[~2015-11-20 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 16:17 Jason Vas Dias
2015-11-20 16:05 ` Ted Zlatanov [this message]
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=87y4dsodv0.fsf@lifelogs.com \
--to=tzz@lifelogs.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).