Hello Wilfred,

On 22 Nov 16 10:32, Wilfred van Velzen wrote to Richard Menedetter:

 WV> Linux first, JAM netmail later... ;)

 WV> Why do you need/want that anyway? You're using GoldED!

That's what I was thinking. Unless using some sort of BBS package that
/only/ handles JAM message bases would I see that any kind of problem.

 RM>> Especially if there is a text config

 WV> There won't be at first...

I thought you were saying that's what you may have to do at first seeing as
though the current config program wasn't playing nice with the recompiles?

 RM>> and a more intuitive rescan. (telling me that I am already
 RM>> subscribed instead of doing a rescan on that area)

 WV> What's not intuitive about:

 WV>   FMAIL_HELP /R      Connect area FMAIL_HELP and rescan all messages
 WV>                      in the message base
 WV>   FMAIL_HELP /R=50   Connect area FMAIL_HELP and rescan at most 50
 WV> messages =FMAIL_HELP        Rescan the connected area FMAIL_HELP
 WV> without having
 WV>                      to disconnect it first

 WV>   %RESCAN            Request a rescan of all new areas
 WV>   %RESCAN=50         Request a rescan of at most 50 messages per area
 WV> for
 WV>                      all new areas

 WV> That's how a lot of Tossers AreaFix functions do it...

What I would like to know (and I was wondering the same about HPT), is if
say I were to do a rescan from another system, and I was using either FMail
or HPT, if my system would then spit that entire rescan out to my other
links?

I avoided doing any kind of rescan to this new hub because I was worried
about that, and didn't want to do a rescan before adding all my links to
the config. Is there some sort of identifier in the message header or body
that would tell FMail or HPT it was a rescanned message and not to process
it to other links?

Regards,
Nick

... "Не знаю. Я здесь только работаю."
--- GoldED+/LNX 1.1.5-b20160827