At 8:28 PM +1200 8/17/00, Alan Brown wrote:
> On Wed, 16 Aug 2000, Randall Gellens wrote:
>
>> Which clients are they using? There have been reports of problems
>> with Outlook. You might try Eudora and see if the problem still
>> occurs. (You can get Eudora for free at <http://www.eudora.com>).
>
> Eudora has the same 60 second timeout by default.
>
> You would save a _lot_ of tech support handholding problems if Eudora
> looked at the size of a message to see if it's still growing, rather
> thgan taking the dain bramaged approach that a messge which takes
> longer than 'n' seconds is indicative of a stall_timeout
>
> Especially in these days of multi-Mb attachments over 56k (or
> slower) modems. Even on a 10Mb/s LAN there can be problems, as I
> discovered yesterday.
>
>> You can adjust the server timeout by using the '-T' option, for
>> example, '-T 600' to use a 10-minute timeout.
>
> QPopper thankfully uses some intelligence and looks at throughput, not
> per message download time.
What makes you say that Eudora's timeout is per transaction instead
of for network inactivity? I checked with both the Mac and Windows
Eudora client team, and was told that Eudora's timeout, while five
minutes by default, is how long it waits after receiving network data
for it to receive any more.
