I even tried the /s that you suggested but that was not recognized.
See below:
C:\FMail>fmailw32 /s
FMail-W32-2.2.0.0 - The Fast Echomail Processor
Copyright (C) 1991-2023 by FMail Developers - All rights reserved
Usage:
FMail <command> [parameters]
Commands:
About Show some information about the program
Scan Scan the message base for outgoing messages
Toss Toss and forward incoming mailbundles
Import Import netmail messages into the message base
Pack Pack and compress outgoing netmail found in the netmail directory
Mgr Only process AreaMgr requests
Enter 'FMail <command> ?' for more information about [parameters]
I love that FMail is current but am having an issue with the scan
(export) of echomail as I mentioned earlier to Chad Adams.
I even tried the /s that you suggested but that was not recognized.
Hi Jason,Wilfred,
On 2023-07-17 11:32:43, you wrote to me:
I love that FMail is current but am having an issue with the scan (export) of echomail as I mentioned earlier to Chad Adams.
I even tried the /s that you suggested but that was not recognized.
C:\FMail>> fmailw32 /s
The /S is used in combination with the SCAN function. It's in the doc:
4.1 Scan
...
The Scan option can be used in combination with six switches:
...
/S Scan the entire message base (ignore
ECHOMAIL.BBS/JAM and NETMAIL.BBS/JAM)
Without the /S, scan checks the above files for which areas it needs to check for new mail. If these files don't exist or are empty it does nothing. These files should be created by your editor or bbs software when a new message is entered into a message base...
Bye, Wilfred.
--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)
On 17.07.2023 13:32, Jason Bock wrote:Tommi,
I even tried the /s that you suggested but that was not recognized.
See below:
Sometimes it helps if you read the 'Usage:' ;)
C:\FMail>fmailw32 /s
FMail-W32-2.2.0.0 - The Fast Echomail Processor
Copyright (C) 1991-2023 by FMail Developers - All rights reserved
Usage:
FMail <command> [parameters]
Commands:
About Show some information about the programdirectory
Scan Scan the message base for outgoing messages
Toss Toss and forward incoming mailbundles
Import Import netmail messages into the message base
Pack Pack and compress outgoing netmail found in the netmail
Mgr Only process AreaMgr requests
Enter 'FMail <command> ?' for more information about [parameters]
'Tommi
--- FMail-lnx64 2.2.0.0
* Origin: nntp://news.fidonet.fi (2:221/6.0)
Hi Jason,Wilfred,
On 2023-07-17 11:32:43, you wrote to me:
I love that FMail is current but am having an issue with the scan (export) of echomail as I mentioned earlier to Chad Adams.
I even tried the /s that you suggested but that was not recognized.
C:\FMail>> fmailw32 /s
The /S is used in combination with the SCAN function. It's in the doc:
4.1 Scan
...
The Scan option can be used in combination with six switches:
...
/S Scan the entire message base (ignore
ECHOMAIL.BBS/JAM and NETMAIL.BBS/JAM)
Without the /S, scan checks the above files for which areas it needs to check for new mail. If these files don't exist or are empty it does nothing. These files should be created by your editor or bbs software when a new message is entered into a message base...
Bye, Wilfred.
--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)
I just tried it and still does not find any new messages but FE does.
See below:
FMail-W32-2.2.0.0 - The Fast Echomail Processor
Copyright (C) 1991-2023 by FMail Developers - All rights reserved
Scanning netmail directory...
Scanning JAM message bases for outgoing messages...
Rescanning all JAM areas
Scanning JAM area 0: AGN_ADS
Scanning JAM area 1: AGN_ART
Scanning JAM area 2: AGN_BBS
...
Scanning JAM area 230: Z1_ROUTING
Scanning JAM area 231: Z1_SYSOP
Scanning JAM area 232: Z39_AMY
Scanning JAM area 233: ZEC
Scanning JAM area 234: ZEUS_AMY
No new outgoing messages
Scanning Hudson message base for outgoing messages...
No new outgoing messages
Netmail: 0, Personal: 0, Hudson: 0, JAMbase: 0
Msgbase net: 0, echo: 0, dup: 0, bad: 0
Scan Active: 47.520 sec.
It just worked!
I will keep testing! ;)
Hi Jason,
On 2023-07-18 08:37:10, you wrote to me:
I just tried it and still does not find any new messages but FEdoes.
See below:
C:\FMail>> fmailw32 scan /S
FMail-W32-2.2.0.0 - The Fast Echomail Processor
Copyright (C) 1991-2023 by FMail Developers - All rights reserved
Scanning netmail directory...
Wilfred,Scanning JAM message bases for outgoing messages...
Rescanning all JAM areas
Scanning JAM area 0: AGN_ADS
Scanning JAM area 1: AGN_ART
Scanning JAM area 2: AGN_BBS
...
Scanning JAM area 230: Z1_ROUTING
Scanning JAM area 231: Z1_SYSOP
Scanning JAM area 232: Z39_AMY
Scanning JAM area 233: ZEC
Scanning JAM area 234: ZEUS_AMY
No new outgoing messages
Scanning Hudson message base for outgoing messages...
No new outgoing messages
Netmail: 0, Personal: 0, Hudson: 0, JAMbase: 0
Msgbase net: 0, echo: 0, dup: 0, bad: 0
Scan Active: 47.520 sec.
So it seems to scan all your areas, in which one of those should it find a new message? And can you show the message (The flags should be interesting), in for instance golded?
Bye, Wilfred.
--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)
I use ProBoard v2.30-A1u4 (Alpha), Internet Rex and now FMail. ;)
My next step is to get netmail to import, but I believe currently it
only supports Hudon, right? If so, is there any timeframe for JAM support?
Since FMail is tossing/scanning well, I have a couple questions.
Is there any possibility that FMail will support Squish or *.MSG formats coming to/from packets?
If I sent you ProBoard file structures, could there be tighter integration with ProBoard?
Hi Jason,I used to use binkd, too plain, lol. It ran smoothly though. Is there anything you recommend?
On 2023-07-18 12:35:49, you wrote to me:
I use ProBoard v2.30-A1u4 (Alpha), Internet Rex and now FMail. ;)
Internet Rex is not the best choice if you just use it for binkp connectivity. It's abandon-ware...
It would be nice to have as I really do not want to use Hudson. But Hudson works. I guess for netmail it would not matter. ;)My next step is to get netmail to import, but I believe currently it only supports Hudon, right? If so, is there any timeframe for JAM support?
There is no time frame for that. Do you really need it? Or is it just nice to have?
I guess **.msg is not needed as most would use it for netmail anyway. Squish would only be nice for people that use it with ProBoard, but everyone so far uses Hudson or JAM.Since FMail is tossing/scanning well, I have a couple questions.
Is there any possibility that FMail will support Squish or *.MSGformats
coming to/from packets?
There probably will not be Squish support. FMail already uses *.msg format for netmails to and from .pkt's, but not for echomail. Is that what you are asking for?
I'll test it out very soon. ;) I need to see if it replaces only changes or everything.If I sent you ProBoard file structures, could there be tighterintegration
with ProBoard?
There already is the auto export function that supports ProBoard in FMail/FConfig. I haven't checked what exactly that does. But what more would you need?
Bye, Wilfred.Thank you,
--- FMail-lnx64 2.2.0.0
* Origin: FMail development HQ (2:280/464)
I use ProBoard v2.30-A1u4 (Alpha), Internet Rex and now FMail.
Internet Rex is not the best choice if you just use it for binkp
connectivity. It's abandon-ware...
I used to use binkd, too plain, lol. It ran smoothly though. Is
there anything you recommend?
There probably will not be Squish support. FMail already uses *.msg
format for netmails to and from .pkt's, but not for echomail. Is
that what you are asking for?
I guess **.msg is not needed as most would use it for netmail anyway. Squish would only be nice for people that use it with ProBoard, but everyone so far uses Hudson or JAM.
There already is the auto export function that supports ProBoard in
FMail/FConfig. I haven't checked what exactly that does. But what
more would you need?
I'll test it out very soon. ;) I need to see if it replaces only
changes or everything.
Sysop: | digital man |
---|---|
Location: | Riverside County, California |
Users: | 1,042 |
Nodes: | 15 (0 / 15) |
Uptime: | 190:39:12 |
Calls: | 500,282 |
Files: | 95,203 |
D/L today: |
349 files (36,172K bytes) |
Messages: | 465,055 |