Downloads:
http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.1-Beta20240319.zip
http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.1-Beta20240319.zip http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.1-Beta20240319.zip
Downloads:
http://www.vlzn.nl/fmail/files/FMail-lnx32-2.3.0.1-Beta20240319.zip
http://www.vlzn.nl/fmail/files/FMail-lnx64-2.3.0.1-Beta20240319.zip
http://www.vlzn.nl/fmail/files/FMailW32-2.3.0.1-Beta20240319.zip
http://www.vlzn.nl/fmail/files/FMailW64-2.3.0.1-Beta20240319.zip
Wilfred... you should make OS/2 exes for those who don't have the capability...
But there is the OS/2 version by the original author from 2001:
http://www.vlzn.nl/fmail/files/fml2_160.zip
But there is the OS/2 version by the original author from 2001:
http://www.vlzn.nl/fmail/files/fml2_160.zip
I have FastEcho OS/2 ...
I just wanted the latest and greatest...
http://www.vlzn.nl/fmail/files/fml2_160.zip
I hope you don't have out of zone links, because FastEcho is known to strip seen-by's, when linking with out of zone links.
I just wanted the latest and greatest...
Who doesn't!? ;-)
http://www.vlzn.nl/fmail/files/fml2_160.zip
Does this need a key??
There is an update for the beta.
There is an update for the beta.
Compiled today..
fconfig seems to work fine so far.
First, is it just me or does the custom tearline only allow 24
characters?
Second, Am I not able to make JAM netmail areas? Or am I doing
something wrong?
Third, and last for now.. Is the backbone.na import format only for
file areas? I've made one with message areas with 168 lines of this format:
ECHOTAG <DESCRIPTION>
And I get "0 descriptions imported".
Sorry, I haven't used a GUI menu driven tosser configuration program
in quite some time. I don't even know what half of the options mean
yet. :)
Nice!
If I may ask, which linux distribution/version are you using? And which termimal?
Yes, that is the maximum, because that is the room for it that is reserved for it in the config file. I don't know why this is. I searched the ftsc docs, but it doesn't mention a length limit for tear lines.
They are not supported.
I have to look into this. But it isn't for file areas, because fmail doesn't do anything with file areas.
But there is always the description on the bottom line when you are on
an option. Or if you are desperate the doc file! ;-)
NB>> First, is it just me or does the custom tearline only allow 24
NB>> characters?
Yes, that is the maximum, because that is the room for it that is reserved for it in the config file. I don't know why this is. I searched the ftsc docs, but it doesn't mention a length limit for tear lines.
Is there an easy way to up that to 75? (this allows for the "--- ", so you could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I suppose?)
Tear lines (starting with "--- ") don't normally have FidoNet
addresses in them. Are you thinking of an origin line (starting with
" * Origin:") ?
If I may ask, which linux distribution/version are you using? And
which termimal?
Archlinux, 6.8.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 16 Mar 2024 17:15:35 +0000 x86_64 GNU/Linux
I use PuTTY from a Windows 11 machine to connect to the VM via SSH
(same as how I access Golded, if you remember that conversation). Full UTF-8. I did have to enable the "Enable VT100 line drawing even in
UTF-8 mode" option in Putty in order for it to display correctly. Otherwise I haven't found any issues compiling or using it, or even saving.. besides what I've mentioned below.
Yes, that is the maximum, because that is the room for it that is
reserved for it in the config file. I don't know why this is. I
searched the ftsc docs, but it doesn't mention a length limit for
tear lines.
Is there an easy way to up that to 75? (this allows for the "--- ",
so you could go less if you also need to allow for the " (XXX/XXX:XXX.XXX)" so it won't wrap to the next line. So around 55, I suppose?)
I don't even have it fully setup yet and I'm already requesting
features. :)
I have to look into this. But it isn't for file areas, because fmail
doesn't do anything with file areas.
Ok. Let me know if you find something, or if I'm doing something wrong.
Permissions don't seem to be the issue. I'm running everything as the
same user/group (the only user/group on that VM, actually) that I
compiled it with.
But there is always the description on the bottom line when you are
on an option. Or if you are desperate the doc file! ;-)
I've had to read most of them multiple times, and then sometimes look at the
doc file for a more detailed description. Even after that I'm still confused
on a few options that I've never used. Guessing leaving them default probably
won't hurt anything. :)
Third, and last for now.. Is the backbone.na import format only for
file areas? I've made one with message areas with 168 lines of this
format:
ECHOTAG <DESCRIPTION>
And I get "0 descriptions imported".
And the discussion to get my terminals right for golded, continued until yesterday! ;-)
But I now seem to have it as good as it can get.
Not so easy. There is reserve space in the binary config file, but not directly after the current field.
So you need code around it for compatibility to use the old or new
field. But I don't find this a very important new feature.
The tearline is mostly used for version info of the generating software, and fmail already handles that very well.
I've made one with message areas with 168 lines of this format:
ECHOTAG <DESCRIPTION>
And I get "0 descriptions imported".
I created a text file with nano. Echoarea descriptions imported fine
with fconfig.
I just tried creating a text file (also with nano) with a single line, test.na:
FMAIL_HELP FMAIL SUPPORT
It didn't import it. So I don't know what the problem is.
1) I've tried putting it in the same directory as fconfig and not using directories.
2) I've tried typing out the entire directory structure to the file.
3) I've tried renaming test.na to backbone.na, and backbone.NA, with no luck.
With all of these options it obviously finds the file, or it would have told me it couldn't.
Does your "Sysop Name" in fconfig need to match the user and/or
group you're running it with?
And the discussion to get my terminals right for golded, continued
until yesterday! ;-) But I now seem to have it as good as it can
get.
I've been keeping up. Glad you were able to get it all sorted!
You're still way luckier than most, if you have been able to use Golded for
all those years without having to use translation tables. I thought something
was weird when you told me that. :)
So you need code around it for compatibility to use the old or new
field. But I don't find this a very important new feature.
Not a new feature, really. Just fixing an old one.
The tearline is mostly used for version info of the generating
software, and fmail already handles that very well.
Some generating software uses much more space than FMail does when it comes to
the tearline. What if one wants to put FMail's information in the TID kludge,
instead, so the tearline can be used for the editor information?
I've made one with message areas with 168 lines of this format:
ECHOTAG <DESCRIPTION>
And I get "0 descriptions imported".
I created a text file with nano. Echoarea descriptions imported fine
with fconfig.
I just tried creating a text file (also with nano) with a single line, test.na:
FMAIL_HELP FMAIL SUPPORT
It didn't import it. So I don't know what the problem is.
1) I've tried putting it in the same directory as fconfig and not using directories.
2) I've tried typing out the entire directory structure to the file.
3) I've tried renaming test.na to backbone.na, and backbone.NA, with no luck.
With all of these options it obviously finds the file, or it would
have told me it couldn't.
Does your "Sysop Name" in fconfig need to match the user and/or group you're running it with?
Most text in fido messages is just ascii. So if you're not bothered by the occasional weird character, your fine! ;-)
Does something that has been working like this for 30 years, without complaints, really needs fixing?
FMail can be configured to just use the TID, so your editor can do what it wants with the tearline.
What I found out while testing, is that the area(s) you want to import the description for needs to already exist in the area configuration. It won't create new areas. Was this the case in your tests?
Most text in fido messages is just ascii. So if you're not bothered
by the occasional weird character, your fine! ;-)
I suppose. With all else that bothers you in regards to FTN messaging, I figured you would have been one of the pioneers on making it work correctly,
though. :)
What I found out while testing, is that the area(s) you want to
import the description for needs to already exist in the area
configuration. It won't create new areas. Was this the case in your
tests?
Yes!
I have 0 areas in my area configuration. That is kind of the whole point of
importing from backbone.na (or areas.bbs, or any other for that matter). To
create the areas and add their descriptions.
Is the original intent just meant to import the descriptions to said areas that were already entered manually?
If so, I digress. 30 years is a long time for nobody to complain about that one.
Am I? But indeed it takes effort to get your terminals, locale, and charset settings just right.
And there are limitations. You can't display utf correctly. And you have to choose a native charset. Any character not supported by the charset, can't be displayed correctly. I can probably not view Russian messages correctly for instance...
Is the original intent just meant to import the descriptions to said areas
that were already entered manually?
It says so in the bottom line description for the function:
"Import descriptions from Backbone.NA into fmail.ar"
But there are also import functions for a number of other config files
of other tossers.
And there are limitations. You can't display utf correctly. And you
have to choose a native charset. Any character not supported by the
charset, can't be displayed correctly. I can probably not view
Russian messages correctly for instance...
You might be able to view them, if your terminal is still UTF-8. But I think I
remember you changing your locale to CP850 now, so sure it's probably doubtful
you can view much of any UTF-8.
You can display utf-8 correctly if you terminals, locale, and charset settings are just right. The only issue I have is the CP437 line/box drawing characters when converted to UTF-8 just wrap early because
they are converted to multiple bytes. They do display correctly,
though.
Most of this was already covered in the GOLDED echo, and is probably
off topic here. I heard the moderator rules with an iron fist. ;)
It says so in the bottom line description for the function:
"Import descriptions from Backbone.NA into fmail.ar"
Ok. It is what it is, I guess.
So your suggestion would be to use two different config files to get your areas imported properly?
1) Import an AREAS.BBS first
2) Import the descriptions with backbone.NA?
1) Import an AREAS.BBS first
2) Import the descriptions with backbone.NA?
Yes, there is no other way.
1) Import an AREAS.BBS first
2) Import the descriptions with backbone.NA?
Yes, there is no other way.
I created areas.bbs from husky config and imported it to fmail. Worked fine.
| Sysop: | Nitro |
|---|---|
| Location: | Portland, OR |
| Users: | 3 |
| Nodes: | 10 (0 / 10) |
| Uptime: | 02:34:26 |
| Calls: | 136 |
| Files: | 751 |
| Messages: | 89,384 |