| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Compliance |
PE> P.S. You will see that all the hair-splitting over "serious" in PE> "serious network problems" has now been said as "network problems" RS> Now try explaining why the date 'out of spec' persists. Have fun. PE> You try explaining how that fact remotely helps your case. Have fun. Some loon called Paul Edwards was proclaiming that if it causes a problem for him alone, he can demand that those messages be fixed, particularly in this case where 'the spec' DOES rigidly specify that field and those messages clearly are 'out of spec'. Unfortunately for him, the real world is more complicated than that. PE> even when it was emphasised that there was only ONE node affected. RS> He hasnt even agreed with you that that *IS* an example of even RS> 'network problem' Paul. His message is heavily larded with *IF*s PE> Poor old Rod. Gets a message supporting what I said all along, Soorree, it did nothing of the sort. @EOT: ---* Origin: afswlw rjfilepwq (3:711/934.2) SEEN-BY: 711/934 712/610 @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™.