Hi David,
On Fri, 18 Oct 2002 17:04:17 +0200
David Cantatore <[EMAIL PROTECTED]> wrote:
>> A few questions. Is everyone of them using TB? And if so, do all
>> copies of TB show the same behaviour? In the latter case you could
>> try to ask the ISP about changes in the server.
> They all use TB and the ISP maintains the problem isn't on their side
> (which I believe).
Why do you belive that?
The reason why I'm asking is: the 'leave messages on server and do not
download them a second time' is such a simple function there can't be
mayn things wrong. I'll try to explain it in short words:
1.) TB! connects to the Mail server and asks for a list of so called
'UID's. The POP3-command for this purpose is 'UIDL' (Unique ID
List).
2.) Assuming TB! hasn't downloaded any message before it now fetches all
messages and writes the UIDs of messages fetched to a local file.
3.) Next time TB! connects it fetches the UIDs again, compares them with
the local list and fetches only the messages not in the local
UID-list.
The UID is calculated and generated by the mail server, TB! has in no
way any influence on this UID generation process. Therefore if such a
scenario, as you describe, _suddenly_ happens _AND_ the The Bat! version
has _not_ changed there are two possibilities:
1.) TB! suddenly is not capable to handle the UID file correctly. Have a
look at the account dir for a file called: 'ACCOUNT.M_R'. This file
contains the UIDs. Is it empty? Seems TB! is the culprit. Not? What's
it's last modification time? Long ago? Maybe TB! is the culprit. It was
just modified lately? Chances are high the server does something
unusual.
2.) The server has changed, maybe a minor upgrade of POP3 daemon and now
calculates the UIDs on a basis that does not provide the same
result on every run. Maybe the UID generator uses file modification
time of mbox file / maildir and that time might change as the mail
box is touched every time you fetch your mail.
This can proven _only_ by doing some low level stuff, namely: doing
multiple telnet sessions and sending POP3 commands manually to
compare the results the server gives on one picky message.
I for myselft wouldn't trust the ISP this fast only because he tells the
problem ain't on their side ... Hey, THIS is the fastest way for him to
get rid of that problem: telling it's you and let the work be done by
you or live with the problem.
If _nothing_ changed on TB! side why should it 'out of a sudden' start
behaving incorrectly? On _four independent_ machines, everywhere with
the same symptoms. You'd have to misconfigure _all four system_ the
_same way_ ... quite hard to believe :-)
--
Pit
________________________________________________
Current version is 1.61 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html
