| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Editor. |
CA>>> If FIDO BBS were not mis-configured to repair dates older CA>>> than ml>> it is not misconfiguration... in the case of those mail ml>> movers using PKTDATE, it is specific and desired... CA> There was a time when this was NOT the philosophy at all. the goal, in this y2k case, is to not loose valid mail... there have been huge arguments about the volunteer mail movers manipulating the mail and this was one way to prevent the "filtering" argument... CA>>> 3 years and were dumping them as they are supposed to CA>>> Jean's 'solution' would be no solution at all. ml>> and he'd likely (many have and did) drop out due to ml>> frustration and lack of reply or comment since no one would ml>> be able to read his pleas for help... CA> There was ample warning to either update or replace non Y2K CA> OLRs. You are overstating their difficulty. The problem was CA> just self-interest and stubbornness IMO. there's a system in Net105, portland, or. that is still sending out y2k flawed messages... he never upgraded his software and doesn't appear to even be interested in this stuff any more... if forced, the system would be shut down... so, what do we, as fidonet, do? loose another system and what users there are using it or ??? ml>> the main goal of PKTDATE is to repair the dates in the PKTs ml>> that fidonet messages are carried within... there are ml>> several checks in place so that it is not a blind "fix the ml>> year" fix... CA> I will have to take your word for this. CA> Personally I found a Y2K OLR. :-) hehehe, i'm glad to have moved far beyond OLRs > )\/(ark* Origin: (1:3634/12) SEEN-BY: 633/267 270 @PATH: 3634/12 106/2000 633/267 |
|
| 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™.