| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | insecure messages |
PE> Presumably you had a TH1 sitting in your inbound mail directory on 19/5 PE> and your Binkley's zmodem told my Binkley's zmodem to skip the file. KR> definitely not, the mailer.bat has the line "del 0000fffa.*" in it RS> Now explain how his log shows your Bink refused the TH1 KR> i have no idea. There are atleast three possibilitys, that BAT didnt get used for that mail run for some reason. That bit of the BAT didnt actually achieve a complete removal of the 0000FFFA.* files for some reason, or the reason your system refused the TH1 wasnt because you had a TH1 on your system in that directory, but some other reason like lack of free space, or say some glitch in your drive subsystem which caused your Bink to get confused when checking your system for the presence of a TH1 and so it refused the the offered one. Without a proper log on your system its not possible to say. But you certainly aint entitled to proclaim that it cant have been your system. KR> how is mail refused? afaik all of the transfer is handled by the KR> two binkleys, mine hasn't been touched for 12 months, you seem to KR> be fudging yours on a fairly regular basis so where is the greatest KR> probability of the the problem being? (hint: at your end (: ) RS> Thats a tad economical with the truth when you also say RS> your system has been completely rebuilt 'end to end' too. KR> since paul has just revealed that the problem actually occurred on KR> may 19, somewhat before i got the new disk, it seems a bit unlikely KR> doesn't it? Dunno, it took you some time to even realise that the actual problem occurred on that date, not the date that you saw the unexpected TH2. Its still not clear if your system really had not been touched for 12 months prior to the 19-May. In fact I thought you have said that you had a loan of a 9GB drive or something in that period ? Thats a separate issue to the date of the full installation of the new drive. And you also said something about a power supply failure which might conceivably have resulted in some reconfig too. But you certainly cant just proclaim that your system was totally untouched for 12 months, so the problem cant be at your end. And when one possible reason for the refusal by your system of the offered TH1 could be anything from a hard drive subsystem glitch to something as simple as a lack of enough free space, its bogus. --- PQWK202* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 @PATH: 711/934 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.