home bbs files messages ]

Just a sample of the Echomail archive

Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.

   ASIAN_LINK      Not the kind that loves you long time      8,456 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 6,442 of 8,456   
   mark lewis to Ozz Nixon   
   May see some *errors*....   
   22 Mar 19 10:03:00   
   
   REPLY: 1:275/362.0 5c930588   
   MSGID: 1:3634/12.73 5c94ec91   
   PID: GED+LNX 1.1.5-b20180707   
   CHRS: CP437 2   
   TZUTC: -0400   
   TID: hpt/lnx 1.9.0-cur 07-09-15   
    On 2019 Mar 20 22:31:24, you wrote to All:   
      
    ON> PSPS. Also with the topic of TZUTC, if my engine auto calculates UTC as   
    ON> timestamp, is TZUTC: Z valid or just 0000?   
      
   only four digits with maybe leading "+" or "-"...   
      
     http://ftsc.org/docs/fts-4008.002   
      
   ----- snip -----   
   4. Control paragraph specification   
   -----------------------------   
      
     Messages which conform to this specification must add the following   
     control paragraph:   
      
       ^aTZUTC:    
      
     Where ^a is ASCII 1, 01h.   
      
     The offset has the format <[-]hhmm>, where hhmm is the number of   
     hours and minutes, zero-padded to two digits each, that local time   
     is offset from UTC.  If local time is WEST of UTC, then the offset   
     is NEGATIVE.  See the table below for typical offsets.   
      
     Note that the hh in a time zone offset is not limited to a maximum   
     of 12.  This is because the International Date Line does not run   
     exactly along the boundary between zone -1200 and +1200.  The   
     minutes part is 00 for most time zones.   
      
     All four digits must be present.  If the offset is negative, there   
     must be a minus ('-', ASCII 45, 2Dh) in front of the offset.   
      
     Implementations must NOT put a plus ('+', ASCII 43, 2Bh) in front of   
     the offset for positive numbers, but robust implementations should   
     be prepared to find (and ignore) a plus if it exists.   
      
     If local time changes as a result of, for example, daylight savings   
     time, then the offset in the TZUTC control paragraph should change   
     to reflect this.   
   ----- snip -----   
      
    ON> (And any reason I should not adjust from local to UTC?)   
      
   you can set any time as long as the TZUTC is correct to reflect the actual   
   local time of the post... i think i said that right...   
      
   )\/(ark   
      
   Always Mount a Scratch Monkey   
   Do you manage your own servers? If you are not running an IDS/IPS yer doin' it   
   wrong...   
   ... RTFM: Read The Fine Manual.   
   ---   
    * Origin:  (1:3634/12.73)   
   SEEN-BY: 15/2 18/200 57/0 123/1970 153/250 154/10 203/0 221/0 226/17   
   SEEN-BY: 229/107 426 452 1014 240/5832 249/206 317 400 267/800 280/464   
   SEEN-BY: 280/5003 310/31 317/2 3 322/757 342/200 393/68 396/45 423/120   
   SEEN-BY: 633/280 712/848 770/0 1 10 100 330 340 772/0 1 210 500   
   PATH: 3634/12 153/7715 250 770/1 280/464 229/426   
      

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca