Hello, Dmitry!

Hoe about adding PING functionality?

FTS-4010.001

Cheers, Michiel

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 15 Sep 26 11:09, Michiel wrote to Dmitry:

MvdV> Hoe about adding PING functionality?

MvdV> FTS-4010.001

But you can just send netmail with PING?


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

Hello, Dmitry!

Dmitry Protasoff wrote:

MvdV>> Hoe about adding PING functionality?

MvdV>> FTS-4010.001

But you can just send netmail with PING?

Yes, of course I can send a ping request to any system in Fidonet. That is not what I meant. What I meant was FidoMail /responding/ to a ping request sent /to/ it.

Cheers, Michiel

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 15 Sep 26 22:38, Michiel wrote to Dmitry:

But you can just send netmail with PING?

MvdV> Yes, of course I can send a ping request to any system in
MvdV> Fidonet. That is not what I meant. What I meant was FidoMail
MvdV> /responding/ to a ping request sent /to/ it.

Hm, yes, I can see that some points have PING flag..
And you are one of such persons ;)
How do you use it? Automatically answering?

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

Hello, Dmitry!

Dmitry Protasoff wrote:

Hm, yes, I can see that some points have PING flag..
And you are one of such persons ;)
How do you use it? Automatically answering?

It is build into Fmail. All I have to do is enable it in the configuration and after that incoming messages to "ping" are answered automatically. Try it with my point 11. He polls multiple times a day.

Cheers, Michiel

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 16 Sep 26 07:55, Michiel wrote to Dmitry:

MvdV> It is build into Fmail. All I have to do is enable it in the
MvdV> configuration and after that incoming messages to "ping" are
MvdV> answered automatically. Try it with my point 11. He polls
MvdV> multiple times a day.

Ok, I'll add an option for that!

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

Hello, Dmitry!

Dmitry Protasoff wrote:

Ok, I'll add an option for that!

Great!
I wait patiently. ...

Cheers, Michiel

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 16 Sep 26 17:32, Michiel wrote to Dmitry:

MvdV> Great!
MvdV> I wait patiently. ...

0.1.7+88 is waiting for Apple's review, probably tomorrow will be available for upgrade.



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

Michiel van der Vlist wrote:

Dmitry Protasoff wrote:

Ok, I'll add an option for that!

Great!
I wait patiently. ...

Keep waiting. Meanwhile, it works. Try me. ;)

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

'Tommi

--- FidoMailMobile/0.1.7+88 (Android)
* Origin: FidoMailMobile (2:221/360.1)

Hello, Tommi!

Tommi Koivula wrote:

Keep waiting. Meanwhile, it works. Try me. ;)

It works!

Cheers, Michiel

--- FidoMailMobile/0.1.6+87 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello, Tommi!

Michiel van der Vlist wrote:

Keep waiting. Meanwhile, it works. Try me. ;)

It works!

In the meantime the iOS version 1.7 is available in the App Store. Apple was quick again. So ping to 2:280/5555.6 now works too. Feel free to test it.

Cheers, Michiel

--- FidoMailMobile/0.1.7+88 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hi Dmitry,

On 2026-09-16 16:19:35, you wrote to Michiel van der Vlist:

0.1.7+88 is waiting for Apple's review, probably tomorrow will be available for upgrade.

I did a test, and got this back:

----------------------------------------------------------------------------- It travelled via:
@Via 2:280/464 @20260916.221102.074.UTC FMail-lnx64(Pack) 2.3.4.1-B20260520
@Via 2:280/5555 @20260916.221118.295.UTC FMail-W32(Toss) 2.3.0.1-B20240319
@Via 2:280/5555 @20260916.221118.413.UTC FMail-W32(Pack) 2.3.0.1-B20240319

Quoted message text:

Hi PING,

Bye, Wilfred.

This reply was generated automatically (FTS-4010 PING).

--- FidoMailMobile/0.1.7+88 (iOS)
@Via 2:280/5555 @20260916.222248.514.UTC FMail-W32(Toss) 2.3.0.1-B20240319
@Via 2:280/5555 @20260916.222248.577.UTC FMail-W32(Pack) 2.3.0.1-B20240319
@Via 2:280/464 @20260916.222247.829.UTC FMail-lnx64(Toss) 2.3.4.1-B20260520 -----------------------------------------------------------------------------

It would be nice if it added 1 or 2 Via lines itself! (On receipt of the netmail, and when sending the new netmail as reply).


Bye, Wilfred.

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

Hello, Dmitry!

Wilfred van Velzen wrote:

It would be nice if it added 1 or 2 Via lines itself! (On receipt
of the netmail, and when sending the new netmail as reply).

Seconded!

Cheers, Michiel

--- FidoMailMobile/0.1.7+88 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Dmitry,

First of all, I congratulate you on introducing this fine product. Frankly I am amazed at the speed you handle feature request. Often less than a day and without any major bugs. Chapeaux!

OK, regarding ping.

1) Would it be possible to (optinally? retain a copy of the response to a ping in the sent group? At the moment it is difficult to se if there was a response to the ping other than a short notice in the log. I'd like to see what actually went out.

2) From the 1.6 announcement:

=== start quote ===

Charsets:

- A message whose text is pure 7-bit is now labelled "ASCII 1", as
FTS-5003 says, instead of the server's 8-bit charset. AreaFix
requests always are. An echo or netmail explicitly set to UTF-8
keeps its UTF-8 label.

=== end quote ===

The ping responder seems to act different. The response to a message addressed to ping that only has ASCII text is labelled "CHRS: ASCII 1" despite the fact that the messages that is responded to has "CHRS: UTF-8 4" and the system is set to UTF-8. If the original message contains non ASCII, he response is set to "CHRS: UTF-8"


Cheers, Michiel

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

Hello Wilfred!

In a message of 17 Sep 26 09:43, Wilfred wrote to Dmitry:

It would be nice if it added 1 or 2 Via lines itself! (On receipt
of the netmail, and when sending the new netmail as reply).

Yeah, good idea. Fixed.

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

Hello Michiel!

In a message of 17 Sep 26 11:00, Michiel wrote to Dmitry:

MvdV> First of all, I congratulate you on introducing this fine
MvdV> product. Frankly I am amazed at the speed you handle feature
MvdV> request. Often less than a day and without any major bugs.
MvdV> Chapeaux!

Thank you! :)

It's gonna be less speedy, eventually :) Right now the effort is to make the product usable and get the most-used features inside.

In fact, it was never planned as full-scale Fidonet software. It was just a test tool to test my server-side FidoMail (that's why it's called FidoMail Mobile :)

MvdV> 1) Would it be possible to (optinally? retain a copy of the
MvdV> response to a ping in the sent group? At the moment it is
MvdV> difficult to se if there was a response to the ping other than a

Yeah, it should be kept. It's bug and will be fixed in next release.

MvdV> - A message whose text is pure 7-bit is now labelled "ASCII 1",
MvdV> as FTS-5003 says, instead of the server's 8-bit charset. AreaFix
MvdV> requests always are. An echo or netmail explicitly set to UTF-8
MvdV> keeps its UTF-8 label.

MvdV> === end quote ===

MvdV> The ping responder seems to act different. The response to a
MvdV> message addressed to ping that only has ASCII text is labelled
MvdV> "CHRS: ASCII 1" despite the fact that the messages that is
MvdV> responded to has "CHRS: UTF-8 4" and the system is set to UTF-8.
MvdV> If the original message contains non ASCII, he response is set to
MvdV> "CHRS: UTF-8"

Not actually a bug-bug, just my thoughts on how charset behaviour changed at some point but wasn't cleanly implemented ;) Previously I was trying to "downgrade" the charset where possible, but it looks like more and more editors and BBS systems are getting UTF-8 support, so we should be moving toward UTF-8 faster.

Now answers to UTF-8 requests will always be sent in UTF-8, before that I was always trying to answer with "ASCII-1" if possible.

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

Hello Dmitry,

On 17 Sep 26 16:24, you wrote to me:

MvdV>> First of all, I congratulate you on introducing this fine
MvdV>> product. Frankly I am amazed at the speed you handle feature
MvdV>> request. Often less than a day and without any major bugs.
MvdV>> Chapeaux!

Thank you! :)

You'r welcome...

It's gonna be less speedy, eventually :) Right now the effort is to
make the product usable and get the most-used features inside.

Of course. Once the introduction phase is over, things will slow down. That's why I am submittimg a new request now: ;-)

In Fidonet it has been custom for decades to seldom having to enter a full address (zone:net/node.point). From left to right address parts can be ommited if they are within ome's own address space. They are filled in automatically. To address my own point 6 just entering ".6" will do.

Fidomail always wants the full 4D address. Can you make it accept abriviated addresses? Please...

In fact, it was never planned as full-scale Fidonet software. It was
just a test tool to test my server-side FidoMail (that's why it's
called FidoMail Mobile :)

Yeah, sometimes things get a life of their own. ;-)


Cheers, Michiel

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

17 Sep 26 16:24, Dmitry Protasoff -> Michiel van der Vlist:

In fact, it was never planned as full-scale Fidonet software. It
was just a test tool to test my server-side FidoMail (that's why
it's called FidoMail Mobile :)

You could rename FidoMail to FidoMail Server (or something like that) and FidoMailMobile to FidoMail, since the latter is no longer limited to mobile devices...

Carlos

--- FidoMailMobile/0.1.8+89 (Android)
* Origin: cyberiada (2:341/234.5001)

Hello, Carlos!

Carlos Navarro wrote:

You could rename FidoMail to FidoMail Server (or something like
that) and FidoMailMobile to FidoMail, since the latter is no longer limited to mobile devices...

Won't that screw up Apple's protocol for submitting updates to the App Store?

Cheers, Michiel

--- FidoMailMobile/0.1.8+89 (iOS)
* Origin: Michiel's iPhone (2:280/5555.6)

Hello Michiel!

In a message of 18 Sep 26 10:24, Michiel wrote to Dmitry:

MvdV> Fidomail always wants the full 4D address. Can you make it accept
MvdV> abriviated addresses? Please...

Done! Will be available in next release (tomorrow).

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

Hello Dmitry,

On 18 Sep 26 19:45, you wrote to me:

MvdV>> Fidomail always wants the full 4D address. Can you make it
MvdV>> accept abriviated addresses? Please...

Done! Will be available in next release (tomorrow).

Great!


Cheers, Michiel

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

Hello Carlos!

In a message of 18 Sep 26 17:53, Carlos wrote to Dmitry:

You could rename FidoMail to FidoMail Server (or something like
that) and FidoMailMobile to FidoMail, since the latter is no longer limited to mobile devices...

Too much agony to change names in Google/Apple Stores..

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