Quoting from Michael Abbott's mail on Tue, Dec 16, 2003 at 09:29:27AM +0000:
Here's an interesting fetchmail problem that blocked my fetchmail
processing for several days. Alas, once again fetchmail is stuck on a
dodgy incoming mail.
For what it's worth, I include the output of `fetchmail -v -v`, but I
think I know where it is failing.
After reading one (clearly spam) message from
undxf703rz(_at_)microbitnet(_dot_)com,
fetchmail tries to hand this on to my local sendmail. Attempting (and
failing) to resolve microbitnet.com takes one minute, by which time it
seems my ISP has become bored. At least, that's how I interpret these
lines:
Try reducing the value of timeout. The default of 300 is too high for
you. Something like:
poll server
timeout 55
... # other usual options
or
fetchmail -t 55 ... # other usual options
You will have to experiment with the option to get the ideal timeout.
If you set it high, you will still have the same problem. If you set
it low, there will be disconnections from your side! On using the
ideal timeout, fetchmail will get bored just before your ISP!
--
Sunil Shetye.