From: Shenghuo ZHU <zsh@cs.rochester.edu>
Cc: Gnus Mailing List <ding@gnus.org>
Subject: Re: webmail/yahoo problems
Date: 01 Dec 1999 22:46:30 -0500 [thread overview]
Message-ID: <2nbt8a57jd.fsf@tiger.jia.vnet> (raw)
In-Reply-To: David Aspinwall's message of "01 Dec 1999 18:01:15 -0800"
>>>>> "David" == David Aspinwall <aspinwall@timesten.com> writes:
David> Hi. I tried accessing my yahoo mail using webmail, and had some
David> problems. I did this:
David> (push '(webmail :subtype yahoo :user "aspin") mail-sources)
David> then tried to get new mail. These came out in the *Messages* buffer:
David> nnml: Reading incoming mail from webmail...
David> Password for aspin at yahoo:
David> Password for aspin at yahoo: .
David> Password for aspin at yahoo: ..
David> Password for aspin at yahoo: ...
David> Password for aspin at yahoo: .........
David> Contacting mail.yahoo.com:80
David> Reading [text/plain]... 393 bytes
David> Retrieval complete. [2 times]
David> Mark set
David> Retrieval complete. [8 times]
David> Contacting edit.yahoo.com:80
David> Retrieval complete. [6 times]
David> But then a *W3-WARNINGS* buffer appeared, with this:
David> (url/error) The URL http://login.yahoo.com/config/login?749hhtagc98rc tried to issue a redirect to http://login.yahoo.com/config/verify?.done=http%3a//edit.yahoo.com/config/mail%3f.intl= using a method other than
David> GET, which can open up various security holes. Please see the
David> HTTP/1.0 specification for more details.
David> And this in the minibuf:
David> Mail source error ((error Variable binding depth exceeds max-specpdl-size)).
David> I set debug-on-error to t, but there wasn't any trace.
David> The environment is Windows NT with:
David> emacs-version "20.4.1"
David> gnus-version "Pterodactyl Gnus v0.99"
David> w3-version "WWW 4.0pre.46 1999/10/01 20:22:11"
David> Do you have any idea what might be going wrong?
David> Thanks for all your work on gnus.
To use webmail, you need patch w3, since Yahoo only accept one line
cookie. I've sent the patch to the ding list when I announced the
function.
Don't worry about the *W3-WARNINGS* buffer. It is OK. It is because
the status code returned from web server is not so standard, and w3
think it is not secure.
--
Shenghuo
prev parent reply other threads:[~1999-12-02 3:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-11-19 7:07 agent and mail-source Shenghuo ZHU
1999-12-01 18:36 ` Lars Magne Ingebrigtsen
1999-12-01 22:50 ` Shenghuo ZHU
[not found] ` <ur9h614pg.fsf_-_@TimesTen.com>
1999-12-02 3:46 ` Shenghuo ZHU [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=2nbt8a57jd.fsf@tiger.jia.vnet \
--to=zsh@cs.rochester.edu \
--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).