Hello Dmitry,

FidoMail (iOS) presents itself as "FidoMailM" in he via line.

@Via 2:280/5555.6 @20260918.174727.UTC FidoMailM 0.1.8+89

Is that intentional or an artefact?

Everywhere else it is "FidoMailMobile".


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

Hello Michiel!

In a message of 18 Sep 26 21:53, Michiel wrote to Dmitry:


MvdV> @Via 2:280/5555.6 @20260918.174727.UTC FidoMailM 0.1.8+89

MvdV> Is that intentional or an artefact?

MvdV> Everywhere else it is "FidoMailMobile".

FTS-4009:
---

Program Name
------------

This field is a mandatory string field of up to ten (10) characters
naming the product inserting the Via line.


---

FidoMailM
123456789


Sad, but can't fit the full name there.

The examples in FTS-4009 have "Gleipner/Java" as a valid program name, but it's against the rules of FTS-4009 itself.

See you,
dp.
--- FidoMail v0.1.4-117-g0bf6376
* Origin: livin' on the edge (2:5001/100)

Hello Dmitry,

On 18 Sep 26 21:07, you wrote to me:

FTS-4009:
---

Program Name
------------

This field is a mandatory string field of up to ten (10) characters
naming the product inserting the Via line.

Ah, there you got me! Since I am no longer active in the FTSC many of the details have evaporated from my active memory. This is one of those details.

Sad, but can't fit the full name there.

Not according to FTS-4009... ...

The examples in FTS-4009 have "Gleipner/Java" as a valid program name,
but it's against the rules of FTS-4009 itself.

Indeed. But there is not just that. "Gleipner/Java" is not (any more?) in active use. Fmail is in use and in active development. Fmail also violates the ten character limit:

=== quote===

@Via 2:280/464 @20260918.092144.282.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
@Via 2:280/5003.0 @20260918.092402.UTC FIDOGATE/ftntoss 4.4.14
@Via 2:280/2060 @20260918.092601.UTC hpt/lnx 1.9.0-cur 2020-04-15

=== end quote ===

As you can see, Fmail is not the only one. Same for FIDOGATE. My guess is that if you analyse the via lines in your PING tests, you will find many more examples. It does not seem to harm anyone. So we can ask if the FTS-4009 ten character limit on the program name is still "current practise".

"Current practise" is not static. It evolves...

In this particular case it is up to you. Strictly follow 23 year old FTS-4009 or follow the pioneers that ignore the ten character limit and set new "currect practise". ...


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

In a message of 19 Sep 26 10:35, Michiel wrote to Dmitry:

MvdV> @Via 2:280/2060 @20260918.092601.UTC hpt/lnx 1.9.0-cur 2020-04-15
------- --------- ----------

All these fields are ok.


== cut ==============================================================

Program Name
------------

This field is a mandatory string field of up to ten (10) characters
naming the product inserting the Via line.

Version
-------

This field is a mandatory string field of up to ten (10) characters
specifying the version of the product inserting the Via line,
including any alpha, beta or gamma status.

Serial Number
-------------

This field is an optional string field of up to ten (10) characters
identifying the specific copy of the product inserting the Via line.

== cut ==============================================================

'Tommi


--- FidoMail v0.1.4
* Origin: fidomail @ mxt.fidonet.fi (2:221/1.22)

Hello Tommi,

On 19 Sep 26 12:17, you wrote to me:


MvdV>> @Via 2:280/2060 @20260918.092601.UTC hpt/lnx 1.9.0-cur
MvdV>> 2020-04-15

------- ---------
----------

All these fields are ok.

Yes. My point being that two out of the three via lines from that particular message are in violation of the 10 character limit.


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

Hello Michiel!

In a message of 19 Sep 26 10:35, Michiel wrote to Dmitry:

MvdV> Indeed. But there is not just that. "Gleipner/Java" is not (any
MvdV> more?) in active use. Fmail is in use and in active development.
MvdV> Fmail also violates the ten character limit:

Very sad news, indeed!

MvdV> === quote===

MvdV> @Via 2:280/464 @20260918.092144.282.UTC FMail-lnx64(Pack)
MvdV> 2.3.4.1-B20260520 @Via 2:280/5003.0 @20260918.092402.UTC
MvdV> FIDOGATE/ftntoss 4.4.14 @Via 2:280/2060 @20260918.092601.UTC
MvdV> hpt/lnx 1.9.0-cur 2020-04-15

MvdV> === end quote ===

MvdV> As you can see, Fmail is not the only one. Same for FIDOGATE. My

And more! JustTosser/W32, InterSquish, SpaceToss/LINUX, SoupGate-Linux, LxTrack/LNX, txt2pkt/lnx (from HPT), Phfito/1.3.6/cvs, hpt-nsf/linux, hpt/w32-mvcdll

Synchronet breaks 10 characters for serial number rule: master/40daa513e, and 10 characters version rule: 3.28-FreeBSD.
RNtrack is wrong for version length: 2.2.2/Lnx/Perl

Also some weird examples, like "perl packPKT by Stas Mishchenkov"

No one was reading FTS-4009 sober? :)

MvdV> In this particular case it is up to you. Strictly follow 23 year
MvdV> old FTS-4009 or follow the pioneers that ignore the ten character
MvdV> limit and set new "currect practise". ...

FTS-4009 needs to be aligned with reality!

Ok, I'll fix the Program Name to FidoMailMobile, but it's my duty now to push FTS-4009 changes.

See you,
dp.
--- FidoMail v0.1.4-122-g97f43bf5
* Origin: livin' on the edge (2:5001/100)

Hello Dmitry,

On 19 Sep 26 13:20, you wrote to me:

No one was reading FTS-4009 sober? :)

So it seems...

MvdV>> In this particular case it is up to you. Strictly follow 23
MvdV>> year old FTS-4009 or follow the pioneers that ignore the ten
MvdV>> character limit and set new "currect practise". ...

FTS-4009 needs to be aligned with reality!

Not going to happen.

Ok, I'll fix the Program Name to FidoMailMobile,

Good! "Current practise" evolves. :-)

but it's my duty now to push FTS-4009 changes.

The reality is that the FTSC is dead for all intents and purposes. How that came to happen is another story. Forget the FTSC, it is flogging a dead horse. Direct your time and energy to making Fidomail better. Live with the new reality.


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)

Hello Michiel!

In a message of 19 Sep 26 15:31, Michiel wrote to Dmitry:

FTS-4009 needs to be aligned with reality!

MvdV> Not going to happen.

Why so?

MvdV> The reality is that the FTSC is dead for all intents and
MvdV> purposes. How that came to happen is another story. Forget the
MvdV> FTSC, it is flogging a dead horse. Direct your time and energy to
MvdV> making Fidomail better. Live with the new reality.

But FTSC team could be re-elected, probably?

I want to live in a new reality, but still following the standards ;)

See you,
dp.
--- FidoMail v0.1.4-122-g97f43bf5
* Origin: livin' on the edge (2:5001/100)

Hello Dmitry,

On 19 Sep 26 14:03, you wrote to me:

FTS-4009 needs to be aligned with reality!

MvdV>> Not going to happen.

Why so?

Because, as I wrote the FTSC had stopped documenting current practise. FTS-4010 (written by me) is the last technical document published.

MvdV>> The reality is that the FTSC is dead for all intents and
MvdV>> purposes. How that came to happen is another story. Forget the
MvdV>> FTSC, it is flogging a dead horse. Direct your time and energy
MvdV>> to making Fidomail better. Live with the new reality.

But FTSC team could be re-elected, probably?

That has been tried. Members were elected, but it did not lead to any activity other than updating the membership list.

Forget it, it is a waste of time.


Cheers, Michiel

--- GoldED+/W32-MINGW 2.0.0-b20260917
* Origin: Nieuw Schoord (2:280/5555)