From: Matthias A. <mat...@gm...> - 2007-04-15 11:44:46
|
"Rob MacGregor" <rob...@gm...> writes: > On 4/13/07, Matthias Andree <mat...@gm...> wrote: >> Rob MacGregor schrieb: >> >> You're most welcome on this task - I haven't kept a close eye on what >> part of the information is outdated and what not, and I've so far only >> removed the most obvious stale stuff. > > Strange, nobody likes doing documentation :) At least not if it's documentation pertaining to code due to change anyways :) > Some form of diagnosis tool(s) wouldn't be a bad idea either, though > I've no idea what form that would take. Enough to confirm that the > basic networking part is functional and that fetchmail can (or cannot) > talk to the remote server. Python script perhaps, Python is widespread today. > Beyond that, if people won't/don't/can't do what they're asked to do > then there's not really much point in continuing to flog the > proverbial horse. In this case the OP did at least provide the > directly fetchmail related info, just nothing about his (unusual) > comms setup. I wouldn't even call it unusual comms setup without knowing the details, but that it gives him headaches while ADSL doesn't is reason for his concern. Anyways, the valid point is that just "socket error" isn't a very detailed report. -- Matthias Andree |