From: Francisco Solsona <flsc@hp.fciencias.unam.mx>
Subject: Re: sticking with multiple Mail Sources?
Date: 02 May 2000 20:06:01 -0500 [thread overview]
Message-ID: <m1snw0jvd2.fsf@biblio08.fciencias.unam.mx> (raw)
In-Reply-To: Jack Vinson's message of "01 May 2000 21:18:58 -0500"
Jack Vinson <JackVinson@yahoo.com> writes:
[...]
> Does Gnus have code to check for timeouts of multiple mail sources? It
> does check for at least one mail source. I've had it tell me that one of
> them had timed out.
I also have a pop mail source, and when there's a lot of
traffic, or the pop server is down, busy, etc. I had to C-g any attemp
to *-get-new-news. To mitigate this problem I advised `pop3-movemail'
which is what I use to get mail from my pop server, and the default
also, here's the code, from my .gnus:
,--------------------
| (defvar pop3-regular-delay 120
| "Time in seconds that takes to usually open a connection to your
| pop server.")
|
| (defadvice pop3-movemail (around pop3-movemail-timeout activate)
| "If connection to the pop server can be established relatively fast,
| then proceed, otherwise timeout and forget about this pop server, until next
| time anyway."
| (with-timeout (pop3-regular-delay
| (message "Pop connection timeout!")
| nil)
| ad-do-it))
`--------------------
...works for me. As is, tries to get your mail from each pop server
for 2 minutes (each) before being timeout.
It isn't perfect in a (big) number of ways, but you may use it as a
starting point and hack something more intelligent.
hth,
Francisco
--
Without facts, the decision cannot be made logically. You must rely on
your human intuition.
-- Spock, "Assignment: Earth", stardate unknown
prev parent reply other threads:[~2000-05-03 1:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-05-02 2:18 Jack Vinson
2000-05-02 18:44 ` Dan McGuirk
2000-05-03 1:06 ` Francisco Solsona [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=m1snw0jvd2.fsf@biblio08.fciencias.unam.mx \
--to=flsc@hp.fciencias.unam.mx \
/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).