Subj : Re: Fmail (2018 Questions)
To : Ozz Nixon
From : Wilfred van Velzen
Date : Thu Feb 14 2019 10:43 pm
Hi Ozz,
On 2019-02-14 10:09:08, you wrote to me:
ON>>> * Only major wishlist I did not see (may be there) -- a drop file
ON>>> from FMail to me ECHOLIST with new posts via TOSS.
WV>> You mean something like what is in the toss log file but in a more
WV>> machine readable form?
ON> For example, d'Bridge tosser would let me know
ON> FTSC_PUBLIC
ON> FMAIL_HELP
ON> FN_SYSOP
ON> Which my BBS used to circumvent a full scan of 1000+ echos when someone
ON> would log in, that was on before the most recent toss - I limited their
ON> "NEW SCAN" to those 3 echos listed above. I have a small DB of
userID,array
ON> of areas - so it only searched the array of areas from JLR forward. *MUCH*
ON> faster for a user on my systems... especially when I start pulling in
ON> newsgroups and any other FTN(etwork) I can get coming in.
There's already this option in the config:
Tossed Areas List
Writes a list of echomail areas in which mail has been
tossed to the specified file.
I don't use it myself, but it seems just what you want.
ON>>> And what is the best way for me to pass such from BBS/NNTP/etc to
ON>>> you for SCAN?
ON> Same going out, I could drop SCANTHIS.LST and simply drop in:
ON> AREA or AREA,MSG#
ON> To short-circuit scanning for timestamp or modcounter changes in JAM.
There is the "echomail.jam" that's read by fmail scan. Golded for instance
creates it.
Scan always
If set to "Yes", the messages base will always be
completely scanned for outgoing messages. If set to
"No", FMail relies on the files ECHOMAIL.BBS and
NETMAIL.BBS for Hudson and/or ECHOMAIL.JAM for JAM areas
to indicate new messages. If these files are found to be
pointing to a message that does not qualify for export,
a complete scan of the message base (or JAM base) will
be performed.
(I hate to quote the docs, but there you go ;)).
Bye, Wilfred.
--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)
