KR> my mail last thursday was .th2, followed on friday by .th3. dunno
KR> what happenned to .th0 and .th1. i certainly didn't do any previous
KR> connects, and the .th2 was a normal size for a daily packet.

PE> Ok, what happened was that on the 19/5, your system rejected
PE> 0000fffa.th1, which I tried to send you.  This took it out of
PE> my .HLO file, but left the th1 file sitting there.  Indeed, the
PE> TH1 file is still sitting there doing nothing, and won't be sent
PE> to you because it's not in the HLO file, and whenever squish needs
PE> to create a new archive, it sees the TH1 sitting there and creates
PE> a TH2 and then adds the TH2 to the .HLO file.

KR> sounds a great theory paul, but what happened to .th0?

Presumably it had been successfully sent the day before the attempt
to send the .TH1 failed.

KR> exactly the same thing happened this thursday, and i was
KR> watching this time. nothing funny happened, just the receipt
KR> of .we1, then .th2. next day .th3 arrived as before.

Thats just the old refused .TH1 still there on Pauls causing that.

KR> unfortunately the bink log gets overwritten each day, but
KR> i will save it in future. i see no reason that, after 12 months
KR> with no changes, bink would suddenly start to refuse mail.

Sure, but then computings like that. When you do eventually find out
why it has suddenly started to do something different, you usually can
see why it did.

KR> the system here is being rebult from end to
KR> end to integrate the new 2.1 gig 7200rpm drive,

Funny that, and you are surprised it does something different
to what it has been doing for the last 12 months ?  Thats
absolutely classic, if things start to be seen to be different,
and you have just changed your system, very very likely indeed
its not a coincidence. Tho sometimes it is anyway.

KR> but the only thing that has happened to the point
KR> is to copy it to another partition, and then back
KR> to it's own, it is even on the same physical drive.

Heard it all before Keith. Time will tell what its due to, but I wont be
exactly shocked speechless if it does turn out to be due to your reconfig.

--- PQWK202