From: Matthias Andree <ma@dt.e-technik.uni-dortmund.de>
Subject: Recent Gnus versions' failures (Emacs 21.3.1)
Date: Tue, 18 May 2004 12:37:48 +0200 [thread overview]
Message-ID: <m365aurpfn.fsf@merlin.emma.line.org> (raw)
Hi,
I have some troubles with the 2004-05-16 and later Gnus versions.
This is severe, with workaround:
1- On May 16th, sasl was enabled. It tried to log into my Dovecot
0.99.10.4 and failed. Upon investigation with tethereal, I figured
Gnus would send AUTHENTICATE "PLAIN" \0user\0password
when it should have base64-encoded the conversation like this:
< * OK dovecot ready.
> a001 CAPABILITY
< * CAPABILITY IMAP4rev1 SORT THREAD=REFERENCES MULTIAPPEND UNSELECT LITERAL+ IDLE CHILDREN LISTEXT LIST-SUBSCRIBED STARTTLS AUTH=PLAIN AUTH=DIGEST-MD5
< a001 OK Capability completed.
> a002 AUTHENTICATE "PLAIN"
< +
> AHVzZXIAc2VjcmV0
< a002 OK Logged in.
...
Workaround: (nnimap-authenticator login)
Obviously, the base64 encoded string is not my real password. Go figure.
:-P
This is a showstopper:
2- On May 18th (today), I tried upgrading to the recent version, which is
totally unusable for me on Emacs 21.3.1 for some part lacks to define
equalp. I'm back to 2004-05-15 now as I'm writing this.
Debugger entered--Lisp error: (void-function equalp)
equalp("merlin.emma.line.org" "merlin.emma.line.org")
message-idna-to-ascii-rhs-1("From")
message-idna-to-ascii-rhs()
message-generate-headers((From Date (optional . In-Reply-To) Message-ID (optional . User-Agent) (X-Draft-From lambda nil (gnus-inews-make-draft-meta-information "nnml+private:gnus" ...)) (optional . References) From))
message-setup-1(((To . "ding@gnus.org") (Subject . "")) nil nil)
message-setup(((To . "ding@gnus.org") (Subject . "")) nil nil)
message-mail("ding@gnus.org")
gnus-post-news(post "nnml+private:gnus")
gnus-summary-post-news(nil)
call-interactively(gnus-summary-post-news)
I cannot send the mail or save a draft.
The backtrace above was generated by pressing the "a" key in the Gnus
group summary, which is bound to gnus-summary-post-news (no surprise
here).
--
Matthias Andree
Encrypted mail welcome: my GnuPG key ID is 0x052E7D95
next reply other threads:[~2004-05-18 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 10:37 Matthias Andree [this message]
2004-05-18 14:00 ` Lars Magne Ingebrigtsen
2004-05-18 23:37 ` Matthias Andree
2004-05-18 23:57 ` Lars Magne Ingebrigtsen
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=m365aurpfn.fsf@merlin.emma.line.org \
--to=ma@dt.e-technik.uni-dortmund.de \
/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).