Hello everybody!

Uit de FMAIL doc:

Two examples:

To send a file EXAMPLE.TXT as an echomail message in area
FMAIL_HELP, enter:

FTools Post EXAMPLE.TXT FMAIL_HELP -subj "This is an example"

To send a file EXAMPLE.TXT as a netmail message with the file
attached to node 2:283/619, enter

FTools Post EXAMPLE.TXT @netdir -to "Joe Sysop" -dest 2:283/619 /F

If I try this example 1 works as advertized.
Example 2 gives an error.
Bad or missing area tag
What is wrong with the area tag?


Chris


--- https://drschrisjacobs.nl/
* Origin: https://drschrisjacobs.nl (2:280/5555.11)

Hi Chris.

12 Jun 26 18:39:42, you wrote to All:

FTools Post EXAMPLE.TXT @netdir -to "Joe Sysop" -dest 2:283/619 /F

If I try this example 1 works as advertized.

Example 2 gives an error.
Bad or missing area tag
What is wrong with the area tag?

If you read the error, you get the reason. "-Subj <file name> is required for file attaches"

=== Cut ===
C:\bbs\fmail>FToolsW32.exe post test @netdir -to tommi -dest 2:221/0 /F FTools-W32-2.3.4.1-Beta20260520 - The Fast Message Base Utility
Copyright (C) 1991-2026 by FMail Developers - All rights reserved

-Subj <file name> is required for file attaches and file requests
Exiting with errorlevel 1

Post Active: 0.0030 sec.
=== Cut ===

'Tommi

--- FMail-W64 2.3.4.1-B20260521
* Origin: FPoint One (2:221/1.1)

Hello Chris,

On Friday June 12 2026 18:39, you wrote to All:

To send a file EXAMPLE.TXT as an echomail message in area
FMAIL_HELP, enter:

FTools Post EXAMPLE.TXT FMAIL_HELP -subj "This is an example"

To send a file EXAMPLE.TXT as a netmail message with the file
attached to node 2:283/619, enter

FTools Post EXAMPLE.TXT @netdir -to "Joe Sysop" -dest 2:283/619 /F

If I try this example 1 works as advertized.
Example 2 gives an error.
Bad or missing area tag
What is wrong with the area tag?

I vaguely recall that @netdir has been changed to #netdir for compatibility with Linux.

Other than that:

2:283/619 is no longer a valid Fodonet address.

/F does not work in a BSO environment, it only worked in a AMA environment.


You seem to have an old version of the DOC.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

On Fri, 12 Jun 2026 16:37:04 +0200 Michiel van der Vlist wrote:

MVDV> I vaguely recall that @netdir has been changed to #netdir for
MVDV> compatibility with Linux.

I think not true.

MVDV> /F does not work in a BSO environment, it only worked in a AMA
MVDV> environment.

But it creates a file attach message just fine. ;)

'Tommi

--- FMail-lnx64 2.3.4.1-B20260612
* Origin: news://news.fidonet.fi (2:221/360.0)

Hi Michiel,

On 2026-06-12 19:37:04, you wrote to Chris Jacobs:

MvdV> I vaguely recall that @netdir has been changed to #netdir for
MvdV> compatibility with Linux.

Probably the other way arround, because # starts a comment in linux. So you can't use # on the linux commandline...


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

Hello Tommi,

On Friday June 12 2026 21:15, you wrote to me:

On Fri, 12 Jun 2026 16:37:04 +0200 Michiel van der Vlist wrote:

MVDV>> I vaguely recall that @netdir has been changed to #netdir for
MVDV>> compatibility with Linux.

I think not true.

I gor it mixed up it was the other way around.

MVDV>> /F does not work in a BSO environment, it only worked in a AMA
MVDV>> environment.

But it creates a file attach message just fine. ;)

But does the "attached file" get delivered to the destination? (in a BSO environment)


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello Chris,

Friday June 12 2026 19:37, I wrote to you:

To send a file EXAMPLE.TXT as a netmail message with the file
attached to node 2:283/619, enter

FTools Post EXAMPLE.TXT @netdir -to "Joe Sysop" -dest 2:283/619 /F

If I try this example 1 works as advertized.
Example 2 gives an error.
Bad or missing area tag
What is wrong with the area tag?

I vaguely recall that @netdir has been changed to #netdir for compatibility with Linux.

I had it mixed up, it is the other way around.

So... did you correctly configure the netmail directory in fconfig?


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello Michiel!

13 Jun 26 10:54, you wrote to me:

So... did you correctly configure the netmail directory in fconfig?

Sending and receiving netmail works. So I guess yes.
My netmail directory is C:\fido\netmail\
I also have a hudson netmail board for my main aka.
Sending mail from that board works too.

Where can I find a more recent FMail doc than https://sourceforge.net/projects/fmail/ has?

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Chris


--- https://drschrisjacobs.nl/
* Origin: https://drschrisjacobs.nl (2:280/5555.11)

Hello Chris,

On Saturday June 13 2026 11:30, you wrote to me:

Sending and receiving netmail works. So I guess yes.
My netmail directory is C:\fido\netmail\
I also have a hudson netmail board for my main aka.
Sending mail from that board works too.

Where can I find a more recent FMail doc than https://sourceforge.net/projects/fmail/ has?

fmail.txt in your inbound...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Hello Chris!

13 Jun 26 11:30, I wrote to Michiel van der Vlist:

Where can I find a more recent FMail doc than https://sourceforge.net/projects/fmail/ has?

I received and compared the more recent doc. Thanks.
No difference in the part about @netdir.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Chris


--- Binkd, FMAIL, Golded+
* Origin: https://drschrisjacobs.nl (2:280/5555.11)

Hello Wilfred!

12 Jun 26 23:50, you wrote to Michiel van der Vlist:

Hi Michiel,

On 2026-06-12 19:37:04, you wrote to Chris Jacobs:

MvdV>> I vaguely recall that @netdir has been changed to #netdir for
MvdV>> compatibility with Linux.

Probably the other way arround, because # starts a comment in linux.
So you can't use # on the linux commandline...

And in a Windows 11 command line @ has a special meaning so it must be escaped. That was the problem.

Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

Chris


--- Binkd, FMail, Golded+
* Origin: https://drschrisjacobs.nl (2:280/5555.11)

Hello Michiel!

13 Jun 26 10:53, you wrote to Tommi Koivula:

But it creates a file attach message just fine. ;)

But does the "attached file" get delivered to the destination? (in a
BSO environment)

No, it is not found by FMail scan or FMail pack.

Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: http://www.vlist.eu (2:280/5555)

Chris


--- Binkd, FMail, Golded+
* Origin: https://drschrisjacobs.nl (2:280/5555.11)

Hi Michiel.

13 Jun 26 10:53:10, you wrote to me:

MVDV>>> /F does not work in a BSO environment, it only worked in a AMA
MVDV>>> environment.

But it creates a file attach message just fine. ;)

But does the "attached file" get delivered to the destination? (in a BSO environment)

Yes, after running "hpt pack". ;)

Well, an option to pack messages with file attaches seems to be missing.

'Tommi

--- FMail-W64 2.3.4.1-B20260521
* Origin: FPoint One (2:221/1.1)

Hi Chris,

On 2026-06-13 13:47:09, you wrote to me:

MvdV>>> I vaguely recall that @netdir has been changed to #netdir for
MvdV>>> compatibility with Linux.

Probably the other way arround, because # starts a comment in linux.
So you can't use # on the linux commandline...

And in a Windows 11 command line @ has a special meaning so it must be escaped. That was the problem.

I didn't know that, otherwise I probably thought of something else...

But is that powershell, or cmd, or both?


Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

Hello Wilfred!

13 Jun 26 15:48, you wrote to me:

Hi Chris,

On 2026-06-13 13:47:09, you wrote to me:

MvdV>>>> I vaguely recall that @netdir has been changed to #netdir for
MvdV>>>> compatibility with Linux.

Probably the other way arround, because # starts a comment in
linux. So you can't use # on the linux commandline...

And in a Windows 11 command line @ has a special meaning so it
must be escaped. That was the problem.

I didn't know that, otherwise I probably thought of something else...

But is that powershell, or cmd, or both?

That was in powershell. I did not try the other shells.

Bye, Wilfred.

--- FMail-lnx64 2.3.4.1-B20260520
* Origin: FMail development HQ (2:280/464)

Chris


--- Binkd, FMail, Golded+
* Origin: https://drschrisjacobs.nl (2:280/5555.11)