Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to FMAIL SUPPORT  <--  <--- Return to Home Page
   Networked Database  FMAIL SUPPORT   [422 / 801] RSS
 From   To   Subject   Date/Time 
Message   Paul Quinn    Wilfred van Velzen   Trialing FMail/lnx status check-in   September 4, 2017
 6:46 PM *  

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)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to FMAIL SUPPORT  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0754 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_0no6lsfudf8kl1iif8npusj115, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_0no6lsfudf8kl1iif8npusj115, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_0no6lsfudf8kl1iif8npusj115, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0