Just a sample of the Echomail archive
Cooperative anarchy at its finest, still active today. Darkrealms is the Zone 1 Hub.
|    FMAIL_HELP    |    Fmail support    |    2,396 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 968 of 2,396    |
|    Paul Quinn to Wilfred van Velzen    |
|    Trialing FMail/lnx status check-in    |
|    04 Sep 17 18:46:02    |
      Hi! Wilfred,              FMail/lnx is wonderful, Wilfred. Thank you for letting me try it out.              What was what I call 'Phase 1' testing ceased for me at about midday on       Saturday. Test packets originated from -this- node as received from my       current peer linked Fidonet systems. They were shoved otherwise-untouched to       my test system via binkD, and ingested by FMail.              With FMail, I have enjoyed seeing _full_ inter-zone SEENBY & PATH data in       messages. These items form the singular function that's caused me to try       FMail.              FMail was under rigorous supervision for about three weeks of 24/7 operation.        I think there's about three Mb of logfiles with nary a glitch reported, IIRC.              It did turn up that weirdness with message sorting that I was later to find       was subject to what Uncle Google & Wikipedia tells me is the 'Observer       effect'. After I reworked the data originating from FastEcho, whose packet       size limits dated from the POTS days, all was well.              Interestingly, a couple of AreaMgr requests were replied to but the responses       were not sent. I guess that could be the case with potential PING responses       as well. Is that normal? (On my main node [~/384] I would have a BATch file       check for any *.Msg files in the netmail path, since the primary netmail area       is usually empty, and would attempt a PACK if any such mails existed.) How do       you recommend they be completed by FMail if it is the only configured netmail       area?              The 'Phase 2' test occurred later on Saturday and lasted for about 10 seconds       or less. :) It's premise was simply continuing function with a pre-existing       messagebase, from that morning's backup from this node. I did allow the       *.Msg, HMB areas & dupe ID database to remain as they were. FMail cruised       through the test without even a grunt.              On Sunday I was surprised and pleased by the 'badmail' capability to detect       old mails... it found one! (It was a phurphy from region 18 IIRC, and was a       re-badged old mail from NZ.) Did yours? ;-)              Now 'Phase 3'. I'm thinking of doing some sort of export SCANning of outbound       mails. I think I need something further from you? Do you have something of a       32-bit flavour, please? :)              Cheers,       Paul.              --- Mozilla/5.0 (X11; Linux i686; rv:31.0) Gecko/20100101 Thunderbird/31.4.0        * Origin: Quinn's Rock vBox - sunny side up on the bookcase (3:640/1384)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca