-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Thomas,

@12-Sep-2002, 22:28 +0700 (16:28 UK time) Thomas F. [TF] in
[EMAIL PROTECTED]">mid:[EMAIL PROTECTED] said:

MDP>>  I'll wager it's nothing to do with TB though.

TF> Let's see.

And now ZA peeps over the parapet yet again. If it were TB doing it,
more of us would be affected. I said never and I mean never. That's
not to say it doesn't happen. I accept that looking at a corrupted
message as stored in a TBB would reveal that it had happened to
someone, but that certainly doesn't mean TB did it! "There's many a
slip 'twixt cup and lip" - the message must pass through other ports
of call before TB gets it.

It is "interesting" that the problem can sometimes be cleared up by
forwarding the message. Hey - perhaps ZA re-corrupts the attachment
and renders it legible on the way back round :-).

- --
Cheers -- .\\arck D Pearlstone -- List moderator
TB! v1.62/Beta5 on Windows 2000 5.0.2195 Service Pack 2
'
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.1.91-nr1 (Windows 2000)

iD8DBQE9gLoOOeQkq5KdzaARAk/0AJ9glkyHMx7wByxIL+R0EQXyNQsfYQCgxyeZ
ewUZUlSdbEOjczfDtRQccVc=
=2yjI
-----END PGP SIGNATURE-----



________________________________________________
Current version is 1.61 | "Using TBUDL" information:
http://www.silverstones.com/thebat/TBUDLInfo.html

Reply via email to