Some of these problems might be from the mail server, not the fetchmail client. I know mail servers can do things like making a complete copy of your spool file before + after processing. So there can be quite a delay for them to get going.
On Wed, Oct 18, 2000 at 01:40:20PM +0100, Anthony Campbell wrote: > On 18 Oct 2000, Rino Mardo wrote: > > it means either the name was not resolving at the exact time and date OR > > that it timedout while checking for mails. > > > > sounds crazy i know but that's my experience with fetchmail having used it > > for > > over two years now. anyway, i'm open to more reasonable explanation. > > > > -- > > Who's watching the watchmen? > > I still get problems intermittently with fetchmail pausing for a long > time while getting the first messsage. I thought I'd fixed it by editing > /etc/hosts but it still happens sometimes. At other times it works > perfectly. > > Anthing else worth checking? > > > -- > Anthony Campbell - running Linux Debian 2.2 (Windows-free zone) > Over 100 book reviews: http://www.cix.co.uk/~acampbell/bookreviews/ > Skeptical articles: http://www.cix.co.uk/~acampbell/freethinker/ > > "Palo y tente tieso." (Spanish proverb) > Free translation: "Holdfast is your only dog." > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null >
