Greetings All!

I would have much prefered to use WinPoint to forward this message. Well actually, I could have but there's a *major* issue: WinPoint's "Forward" message template doesn't work :((

Anyway, I'm only forwarding the reply from Tommi as proof that the
Autosend feature actually works, not that anyone's doubting that it
doesn't :-)))

---------- Forwarded Message ----------
Subject: AutoSend test
Date: 12 Nov 21 11:22
From: Tommi Koivula@2:221/6
To: Martin Foster

Original Area: "FIDOTEST"
---------------------------------------

Hi Martin.

12 Nov 21 09:04, you wrote to All:

@MSGID: 2:310/31.7 f02fe683
@CHRS: IBMPC 2
@TZUTC: 0000
Greetings All!

Testing WinPoint's Autosend feature.

:)

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Autosend Process (2:310/31.7)
SEEN-BY: 19/36 80/1 103/705 124/5016 153/757 154/10 203/0 218/840 220/70 221/0
SEEN-BY: 226/17 240/5832 267/800 280/464 5003 5555 292/854 8125 301/1 310/31 SEEN-BY: 313/41 317/3 340/1000 341/234 396/45 423/120 460/58 633/280 712/848 SEEN-BY: 770/1 100 330 340 772/210 220 230 2452/250 221/6 218/700 840
@PATH: 310/31 280/464 770/1 218/840

'Tommi

-+- GoldED+/LNX 1.1.5-b20210627
+ Origin: nntps://news.fidonet.fi (2:221/6)
-------- End forwarded message --------

Regards,
Martin

--- OpenXP 5.0.50
* Origin: - o(0_0)o - (2:310/31.3)

//Hello Martin, //

*12.11.21* *11:05:00* in area *WINPOINT*
*All* Theme *"AutoSend test"*.

Greetings All!

I would have much prefered to use WinPoint to forward this message. Well actually, I could have but there's a *major* issue: WinPoint's "Forward" message template doesn't work :((

Anyway, I'm only forwarding the reply from Tommi as proof that the Autosend feature actually works, not that anyone's doubting that it doesn't :-)))

---------- Forwarded Message ---------- Subject: AutoSend test Date:
12 Nov 21 11:22 From: Tommi Koivula@2:221/6 To: Martin Foster Original Area: "FIDOTEST" ---------------------------------------
Hi Martin.
12 Nov 21 09:04, you wrote to All:

@MSGID: 2:310/31.7 f02fe683 @CHRS: IBMPC 2 @TZUTC: 0000 Greetings All!
Testing WinPoint's Autosend feature.
-+- WinPoint 373.0

Skip.

Is AutoSend not by-default?

--- WinPoint Beta 5 (359.1)
* Origin: "Novy jemchug" for :-D (1:153/757.1315)

//Hallo Martin, //

am *12.11.21* um *11:05:00* schriebst Du in der Area *WINPOINT*
an *All* eine Mail zum
Thema *"AutoSend test"*.

I would have much prefered to use WinPoint to forward this message. Well actually, I could have but there's a major issue: WinPoint's "Forward" message template doesn't work :((

I which respect ???

Anyway, I'm only forwarding the reply from Tommi as proof that the Autosend feature actually works, not that anyone's doubting that it doesn't :-)))

Nice

Bis denne ...
Tim Schattkowsky
--- WinPoint 373.0
* Origin: Original WinPoint Origin! (2:240/1120.29)

Hello Tim!

*** Friday 12.11.21 at 12:39:29, Tim Schattkowsky wrote to Martin Foster:

I would have much prefered to use WinPoint to forward this message. Well
actually, I could have but there's a major issue: WinPoint's "Forward"
message template doesn't work :((

I which respect ???

Ummmm, did you mean "*In* which respect" ? :)

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

Hello Denis!

*** Friday 12.11.21 at 12:46:22, Denis Mosko wrote to Martin Foster:

[snip]

Is AutoSend not by-default?

The Autosend feature is a "Tool" which can be configured to import the *contents* of a text file into a message and then post the message into an area on a specific day(s). A typical use for this would be for an echo moderator to automatically post the echo rules periodically.

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

//Hello Martin,//

om *13.11.21* at *9:21:17* You wrote in rea *WINPOINT*
to *Tim Schattkowsky*
about *"AutoSend test"*.

Hello Tim!

*** Friday 12.11.21 at 12:39:29, Tim Schattkowsky wrote to Martin Foster:

I would have much prefered to use WinPoint to forward this message.
Well actually, I could have but there's a major issue: WinPoint's
"Forward" message template doesn't work :((

I which respect ???

Ummmm, did you mean "*In* which respect" ? :)

Have to save some letters from time to time ;)

Regards,
Tim
--- WinPoint 374.1
* Origin: Original WinPoint Origin! (2:240/1120.29)

Hello Tim!

*** Saturday 13.11.21 at 11:22:40, Tim Schattkowsky wrote to Martin Foster:

I would have much prefered to use WinPoint to forward this message.
Well actually, I could have but there's a major issue: WinPoint's
"Forward" message template doesn't work :((

I which respect ???

Ummmm, did you mean "*In* which respect" ? :)

Have to save some letters from time to time ;)

Yes, absolutely :-))

The issue is that neither the "Forwards (Header)" nor the "Forwards (Footer)" templates are imported into a forwarded message.

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

Hello Martin Foster!

** On Sunday 14.11.21 - 09:05, Martin Foster wrote to Tim Schattkowsky:

The issue is that neither the "Forwards (Header)" nor the "Forwards (Footer)" templates are imported into a forwarded message.

That was the same problem in the last public release:

[WinPoint v359.1 Beta 5] CONS


[o] internal editor: ^Y deletes UNDER the current line.

[o] limited to no extended-ascii support

[o] external editor option: no

[o] no highlighting on a search match

[o] does not support incoming areafix lists that are in lowercase [*3]

[o] sometimes areafix is created for "0:8/15" address.

[o] received nodelists need manual intervention to \WinpointNL directory

[o] if you don't specify a domain, WinPoint adds "@" to the end of your AKA [*4]

[o] when forwarding a post to another echo/area, the Extra/Options/ Templates for the defined header/footer do not get inserted into the new message.

[o] when replying to a message (echo or netmail) templates (headers/footers) do not get applied.

[o] editor on reply removes <CR>'s on a line by line basis; therefore ordered lists/lines/columnar text in incoming messages become reflowed paragraphs.

[o] cannot place unfinalized reply on hold.

[o] some parts of WinPoint remain in German.

[o] reply window opens up full screen [*5]

[o] http:// links not clickable

[o] when message sort order is last "set" by Received date or Sent date and newest to oldest, the program will always resort by oldest to newest the next time the program is run.

[o] when message sort order is last "set" by Bytes and largest to smallest, the program will always resort by smallest to largest the next time the program is run.


[*3] can use manually re-edited areafix list to uppercase, or
create content of WinPoint\MsgBase\z.nt.nd.0.EchoAreas
manually.

[*4] WinPoint is incapable of transmitting valid 4D addresses
to the remote system(s), which can cause problems with some
(but not all) remote systems. It is therefore strongly
advisable to use 5D addresses.

[*5] hack = use Window's Alt-<space> to bring up the System
menu and use "R" to restore the window to a smaller default.
--
../|ug

--- OpenXP 5.0.50
* Origin: My Westcoast Point (1:153/757.21)

//Hello August,//

om *14.11.21* at *19:26:00* You wrote in rea *WINPOINT*
to *Martin Foster* about *"AutoSend test"*.

The issue is that neither the "Forwards (Header)" nor the "Forwards
(Footer)" templates are imported into a forwarded message.

That was the same problem in the last public release:
[WinPoint v359.1 Beta 5] CONS

As far as I can tell everythings works as intended und did so already in 359.1.

What are you actually doing (step by step), what are your expectations and what is the actual result on your system?

Regards,
Tim
--- WinPoint 374.1
* Origin: Original WinPoint Origin! (2:240/1120.29)

//Hello August,//

om *14.11.21* at *19:26:00* You wrote in rea *WINPOINT*
to *Martin Foster*
about *"AutoSend test"*.

[WinPoint v359.1 Beta 5] CONS

As far as I remember the following issues have been *already adressed*:

[o] internal editor: ^Y deletes UNDER the current line.
[o] limited to no extended-ascii support
[o] does not support incoming areafix lists that are in lowercase
[o] if you don't specify a domain, WinPoint adds "@" to the end of your AKA
[o] editor on reply removes <CR>'s on a line by line basis; therefore ordered lists/lines/columnar text in incoming messages become reflowed paragraphs.
[o] when message sort order is last "set" by Received date or Sent date and newest to oldest, the program will always resort by oldest to newest the next time the program is run.
[o] when message sort order is last "set" by Bytes and largest to smallest, the program will always resort by smallest to largest the next time the program is run.

These issues are *on my list*:

[o] some parts of WinPoint remain in German.
[o] no highlighting on a search match
[o] cannot place unfinalized reply on hold.
[o] reply window opens up full screen [*5]
[o] http:// links not clickable

These items are *by design* and will not be adressed:

[o] external editor option: no

I *cannot reproduce* (or simply dont understand) these issues:

[o] when forwarding a post to another echo/area, the Extra/Options/ Templates for the defined header/footer do not get inserted into the new message.
[o] when replying to a message (echo or netmail) templates (headers/footers) do not get applied.

And then there are *those issues* ... where after (for some of the code) 25 years my memory is getting in the way:

[o] received nodelists need manual intervention to \WinpointNL directory

Actually, WP95 was able to do fully automatic processing of incoming nodelist, nodediffs etc. I know it because me and everbody I know was using it for at least a decade. However, nowadays, it seems like the step the decompresses the incoming files into the proper directory is missing. I think I recall that for this, earlier WP versions where having a feature called "automatic unpack jobs" that could be employed to decompress incoming files from file areas to the nodelist directories (where the presence of the files triggered the actual processing). However, it seems to be gone and I have to figure out why.

Another disturbing thing is that Winpoint still has the option to do automated postings to a mailing list (i.e., a list of users). However, the GUI for managing these lists seems to be gone. Will investigate that later.


Regards,
Tim
--- WinPoint 374.1
* Origin: Original WinPoint Origin! (2:240/1120.29)

//Hallo August,//

am *14.11.21* um *19:49:49* schrieb *Tim Schattkowsky*
in der Area *WINPOINT* eine Mail an Dich
zum Thema *"Re: AutoSend test"*.

Hello August,

om 14.11.21 at 19:26:00 You wrote in rea WINPOINT to Martin Foster about "AutoSend test".

The issue is that neither the "Forwards (Header)" nor the "Forwards
(Footer)" templates are imported into a forwarded message.

That was the same problem in the last public release: [WinPoint v359.1
Beta 5] CONS

As far as I can tell everythings works as intended und did so already in 359.1.

Ok, I checked this and this is what I think:

WinPoint always applies the templates from the text group assign to the destination (!) area of the new message. The reasoning behind this is obvious. However, that is not necessarily where the message will end up as the destination area can be changed in the editor.

I think, you are expecting the text group of the source area to be applied. However, the default area for forwarded messages is NETMAIL, so the headers are taken from the text group assigned to NETMAIL (if any). My guess is you have no text group assigned there and end up with no headers.

Bis denne ...
Tim Schattkowsky
--- WinPoint 374.1
* Origin: Original WinPoint Origin! (2:240/1120.29)

Hello Tim!

*** Sunday 14.11.21 at 20:24:15, Tim Schattkowsky wrote to August Abolins:

The issue is that neither the "Forwards (Header)" nor the "Forwards
(Footer)" templates are imported into a forwarded message.

That was the same problem in the last public release: [WinPoint v359.1
Beta 5] CONS

As far as I can tell everythings works as intended und did so already in
359.1.

Ok, I checked this and this is what I think:

WinPoint always applies the templates from the text group assign to the destination (!) area of the new message. The reasoning behind this is obvious. However, that is not necessarily where the message will end up
as the destination area can be changed in the editor.

I think, you are expecting the text group of the source area to be applied. However, the default area for forwarded messages is NETMAIL, so the headers are taken from the text group assigned to NETMAIL (if any).
My guess is you have no text group assigned there and end up with no headers.

Ah, Aha! :-))

Your guess is absolutely spot on and the reason for this is that in a *new clean* install of WinPoint, there aren't any text groups and therefore, a text group cannot be assigned to the *existing* NETMAIL area. The message templates have to be enabled by going into Extras -> Options -> Signatures and clicking the "Add" button and then giving the new text group a name but the new text group is NOT assigned to the *existing* NETMAIL area(I hadn't realised that until now).

In addition, a text group cannot be assigned to the Prototype Area(Extras -> Options -> General) in a *new clean* install for the same reason as above.

Also :))
This would explain why I thought that some of the templates weren't working in NETMAIL but now that I've placed the NETMAIL area in my default text group, they are now working, as well as the forward templates. Super! =8-)

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

Hello August!

*** Sunday 14.11.21 at 19:26:00, August Abolins wrote to Martin Foster:

The issue is that neither the "Forwards (Header)" nor the "Forwards
(Footer)" templates are imported into a forwarded message.

That was the same problem in the last public release:

Yes it was and now we know why :)

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

Hello Tim!

*** Sunday 14.11.21 at 20:07:16, Tim Schattkowsky wrote to August Abolins:

As far as I remember the following issues have been already adressed:

[snip]

[o] does not support incoming areafix lists that are in lowercase

Oh, I wasn't aware that you'd fixed this, must test it out.

Later .....
Yep, imported my BossNode's areas list(lowercase echo tags) without problems. Thank you very much :)

Regards,
Martin

--- WinPoint 373.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

//Hello Martin,//

om *15.11.21* at *11:35:49* You wrote in rea *WINPOINT*
to *Tim Schattkowsky* about *"AutoSend test"*.

Hello Tim!

*** Sunday 14.11.21 at 20:07:16, Tim Schattkowsky wrote to August
Abolins:

As far as I remember the following issues have been already adressed:

[snip]

[o] does not support incoming areafix lists that are in lowercase

Oh, I wasn't aware that you'd fixed this, must test it out.

Later .....
Yep, imported my BossNode's areas list(lowercase echo tags) without problems. Thank you very much :)

Change a little more around this, so WP375 enforces on its side uppercase now. We will see if this works ..

Regards,
Tim
--- WinPoint 375.0
* Origin: Original WinPoint Origin! (2:240/1120.29)

//Hello Martin,//

om *15.11.21* at *11:14:18* You wrote in rea *WINPOINT*
to *Tim Schattkowsky* about *"AutoSend test"*.

WinPoint always applies the templates from the text group assign to the
destination (!) area of the new message. The reasoning behind this is
obvious. However, that is not necessarily where the message will end up
as the destination area can be changed in the editor.

I think, you are expecting the text group of the source area to be
applied. However, the default area for forwarded messages is NETMAIL, so
the headers are taken from the text group assigned to NETMAIL (if any).
My guess is you have no text group assigned there and end up with no
headers.

Ah, Aha! :-))

Your guess is absolutely spot on and the reason for this is that in a new clean install of WinPoint, there aren't any text groups and therefore, a text group cannot be assigned to the existing NETMAIL area. The message templates have to be enabled by going into Extras -> Options ->
Signatures and clicking the "Add" button and then giving the new text group a name but the new text group is NOT assigned to the existing NETMAIL area(I hadn't realised that until now).

In addition, a text group cannot be assigned to the Prototype Area(Extras

Options -> General) in a new clean install for the same reason as

above.

Probably creating and assigning the default text group at first start would make sense. This is less trivial than one may expect because it requires some collaboration between the setup program and the application binary, but I put it on the list.

Regards,
Tim
--- WinPoint 375.0
* Origin: Original WinPoint Origin! (2:240/1120.29)

Hello Tim!

*** Monday 15.11.21 at 22:59:06, Tim Schattkowsky wrote to Martin Foster:

As far as I remember the following issues have been already adressed:

[snip]

[o] does not support incoming areafix lists that are in lowercase

Oh, I wasn't aware that you'd fixed this, must test it out.

Later .....
Yep, imported my BossNode's areas list(lowercase echo tags) without
problems. Thank you very much :)

Change a little more around this, so WP375 enforces on its side uppercase now. We will see if this works ..

I re-imported the areas list and it worked but none of the existing lowercase area tags had been deleted in the EchoArea Manager. It was a simple matter of manually deleting all the lowercase area tags etc. from the "2.310.31.0.EchoAreas" file in the "MsgBase" directory and I now have a list of area tags in UPPERCASE in the EchoArea Manager.

Regards,
Martin

--- WinPoint 375.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)

Hello Tim!

*** Monday 15.11.21 at 23:12:54, Tim Schattkowsky wrote to Martin Foster:

WinPoint always applies the templates from the text group assign to the
destination (!) area of the new message. The reasoning behind this is
obvious. However, that is not necessarily where the message will end up
as the destination area can be changed in the editor.

I think, you are expecting the text group of the source area to be
applied. However, the default area for forwarded messages is NETMAIL,
so the headers are taken from the text group assigned to NETMAIL (if
any). My guess is you have no text group assigned there and end up with
no headers.

Ah, Aha! :-))

Your guess is absolutely spot on and the reason for this is that in a
new clean install of WinPoint, there aren't any text groups and
therefore, a text group cannot be assigned to the existing NETMAIL area.
The message templates have to be enabled by going into Extras -> Options

Signatures and clicking the "Add" button and then giving the new text

group a name but the new text group is NOT assigned to the existing
NETMAIL area(I hadn't realised that until now).

In addition, a text group cannot be assigned to the Prototype
Area(Extras

Options -> General) in a new clean install for the same reason as

above.

Probably creating and assigning the default text group at first start would make sense.

Yes, it would make perfect sense :-)

Regards,
Martin

--- WinPoint 375.0
* Origin: WinPoint Test Rig - UK - (2:310/31.7)