Hi Flavio,

On 2022-04-21 10:19:52, you wrote to All:

@MSGID: 4:801/195 626159f6
@PID: JamNNTPd/Linux 1
@TID: Mystic BBS 1.12 A48
@REPLYADDR fcbessa@gmail.com
@CHRS: IBMPC 2
@TZUTC: -0300

Testing Jamnntpd...

--- NewsTap/5.5 (iPhone/iPod Touch)
* Origin: Andromeda - Epimetheus NNTP Gateway (4:801/195)
SEEN-BY: 19/36 80/1 103/705 124/5016 153/757 154/10 203/0 218/840 220/70 SEEN-BY: 221/0 226/17 240/5832 267/800 280/464 5003 5555 292/854 8125 SEEN-BY: 301/1 310/31 317/3 341/66 234 396/45 423/120 460/58 633/280 SEEN-BY: 712/848 770/1 100 330 340 772/210 220 230 801/161 188 189 194 SEEN-BY: 801/195 197 202 2452/250
@PATH: 801/195 80/1 770/1 280/464

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello fcbessa,

On Thursday April 21 2022 10:19, Flavio Bessa wrote to All:

@CHRS: IBMPC 2

The identifier "IBMPC" is obsolete. See FTS-5003:

Level 2 obsolete character set identifiers (see note)

IBMPC IBM PC character sets for European
+7_FIDO IBM codepage 866, use CP866 instead
MAC Macintosh character set, use CPxxxxx instead

[..]

5. Obsolete indentifiers
------------------------

These indentifiers must not be used when creating new messages.
The following only applies to processing messages that were
created using old software.

Since the "IBMPC" identifier, initially used to indicate IBM
codepage 437, eventually evolved into identifying "any IBM
codepage", there exists in some implementations an additional
control line, "CODEPAGE", identifying the messages codepage:

"^ACODEPAGE: xxx

This use is deprecated in favour of the "CPxxx" identifiers
defined above. If found in incoming messages, however, it should
be used as an override of the "CHRS: IBMPC" identifier.


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Flavio!

21 Apr 2022 10:19, from Flavio Bessa -> All:

@TID: Mystic BBS 1.12 A48
@MSGID: 4:801/195 626159f6
@REPLYADDR fcbessa@gmail.com
@PID: JamNNTPd/Linux 1
@CHRS: IBMPC 2
@TZUTC: -0300

Testing Jamnntpd...

SEEN-BY: 19/36 80/1 103/705 124/5016 153/757 154/10 203/0 218/840
220/70
SEEN-BY: 221/0 226/17 240/5832 267/800 280/464 5003 5555 292/854 8125 SEEN-BY: 301/1 310/31 317/3 341/66 234 396/45 423/120 460/58 633/280 SEEN-BY: 712/848 770/1 100 330 340 772/210 220 230 801/161 188 189 194 SEEN-BY: 801/195 197 202 2452/250
@PATH: 801/195 80/1 770/1 280/464

CU, Ricsi

... If everything's coming your way, you're in the wrong lane.
--- GoldED+/LNX
* Origin: Bad Band Name #753: Toxic Popsicle (2:310/31)

Flavio,

Testing Jamnntpd...

It made it to Arkansas.

Daryl

... Why does the Psychic Hotline have to ask for your name??
=== MultiMail/Win v0.52
--- SBBSecho 3.15-Win32
* Origin: The Thunderbolt BBS - Little Rock, Arkansas (1:2320/33)

21 Apr 2022 16:24, you wrote to fcbessa@gmail.com:

Hello fcbessa,

[...]

Your reply to Flavio took the recipient name from the REPLYADDR kludge. :-?

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyb point (2:341/234.1)

Hello Carlos,

On Friday April 22 2022 13:46, you wrote to me:

Hello fcbessa,

[...]

Your reply to Flavio took the recipient name from the REPLYADDR
kludge. :-?

So it seems. I wonder if this is a quirk in Golded...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Michiel,

On 2022-04-22 14:44:46, you wrote to Carlos Navarro:

Hello fcbessa,

[...]

Your reply to Flavio took the recipient name from the REPLYADDR
kludge. :-?

MvdV> So it seems. I wonder if this is a quirk in Golded...

Mine doesn't do this. But it could have to do with your INTERNET* golded settings. INTERNETREPLY for instance...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Friday April 22 2022 15:15, you wrote to me:

Your reply to Flavio took the recipient name from the REPLYADDR
kludge. :-?

MvdV>> So it seems. I wonder if this is a quirk in Golded...

Mine doesn't do this. But it could have to do with your INTERNET*
golded settings. INTERNETREPLY for instance...

Hmmm... I can find nothing to that effect in my Golded config... :(

But setting "INTERNETREPLY NO" seems to fix it...


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Michiel,

On 2022-04-22 18:07:42, you wrote to me:

Your reply to Flavio took the recipient name from the REPLYADDR
kludge. :-?

MvdV>>> So it seems. I wonder if this is a quirk in Golded...

Mine doesn't do this. But it could have to do with your INTERNET*
golded settings. INTERNETREPLY for instance...

MvdV> Hmmm... I can find nothing to that effect in my Golded config... :(

MvdV> But setting "INTERNETREPLY NO" seems to fix it...

Maybe the default for my linux version is different, because I don't have that setting in my config either. Yet it seems to work as if the setting is 'NO'.

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

22 Apr 2022 18:07, you wrote to Wilfred van Velzen:

Mine doesn't do this. But it could have to do with your INTERNET*
golded settings. INTERNETREPLY for instance...

Hmmm... I can find nothing to that effect in my Golded config... :(

But setting "INTERNETREPLY NO" seems to fix it...

I have no INTERNETREPLY setting in my cfg and I don't have this issue...

--- GoldED+/W32-MSVC 1.1.5-b20170303

...but we use different Golded+ versions (see tearline)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Carlos,

On 2022-04-22 20:51:17, you wrote to Michiel van der Vlist:

Mine doesn't do this. But it could have to do with your INTERNET*
golded settings. INTERNETREPLY for instance...

Hmmm... I can find nothing to that effect in my Golded config... :(

But setting "INTERNETREPLY NO" seems to fix it...

I have no INTERNETREPLY setting in my cfg and I don't have this issue...

--- GoldED+/W32-MSVC 1.1.5-b20170303

...but we use different Golded+ versions (see tearline)

--- GoldED+/W32-MSVC 1.1.5-b20180707

I could only find this commit:

commit 1c2e81064eedded769ec7c7b2f583af28497aba0
Author: asa <asa>
Date: Sun Jan 12 12:11:29 2003 +0000

InternetReply should only affect netmail areas. Fixed.

It's way older then either of your versions...

But I know Michiel sometimes (as I do sometimes) uses "reply to" a temporary netmail directory, to be able to finish the reply at a later time. When I do that here, I get the same effect with the default INTERNETREPLY setting...

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

//Hello Flavio,//

on *21.04.22* at *13:19:52* You wrote in area *FIDOTEST*
to *All* about *"Testing JAMNNTPD"*.

AREA:FIDOTEST
@TID: Mystic BBS 1.12 A48
@MSGID: 4:801/195 626159f6
@REPLYADDR fcbessa@gmail.com
@PID: JamNNTPd/Linux 1
@CHRS: IBMPC 2
@TZUTC: -0300
Testing Jamnntpd...

--- NewsTap/5.5 (iPhone/iPod Touch)
* Origin: Andromeda - Epimetheus NNTP Gateway (4:801/195)
SEEN-BY: 19/36 30/0 80/1 103/705 124/5016 153/757 154/10 203/0 218/840 220/70 SEEN-BY: 221/0 1 6 360 226/17 240/1120 1634 1895 5832 8002 8005 267/800 SEEN-BY: 280/464 5003 5555 291/111 292/854 8125 301/1 310/31 313/41 317/3 SEEN-BY: 335/364 341/66 234 371/0 52 380/5 382/147 396/45 423/81 120 460/58 SEEN-BY: 633/280 712/848 770/1 100 330 340 772/210 220 230 801/161 188 189 SEEN-BY: 801/194 195 197 202 2452/250 3634/12
@PATH: 801/195 80/1 770/1 280/464 221/1 240/1120 371/0 52

Regards,
Daniel PATH
--- WinPoint 400.2
* Origin: Roon's Point (2:371/52.1)

22 Apr 2022 21:44, you wrote to me:

But I know Michiel sometimes (as I do sometimes) uses "reply to" a temporary netmail directory, to be able to finish the reply at a later time. When I do that here, I get the same effect with the default INTERNETREPLY setting...

Me too (I just tested).

A workaround could be using a local echomail area/directory for those draft messages.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: cyberiada (2:341/234)

Hi Carlos,

On 2022-04-23 09:50:11, you wrote to me:

But I know Michiel sometimes (as I do sometimes) uses "reply to" a
temporary netmail directory, to be able to finish the reply at a
later time. When I do that here, I get the same effect with the
default INTERNETREPLY setting...

Me too (I just tested).

A workaround could be using a local echomail area/directory for those draft
messages.

Yeah, but setting INTERNETREPLY to NO also works as Michiel found out, which is more simple... ;)

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)

Hello Wilfred,

On Saturday April 23 2022 10:34, you wrote to Carlos Navarro:

A workaround could be using a local echomail area/directory for
those draft messages.

Does not work, the problem also appears in echomail. :-(

Yeah, but setting INTERNETREPLY to NO also works as Michiel found out, which is more simple... ;)

Except that I have to take it back. It seems to work at first, but then if you continue with editing the reply message, it starts using the REPLYADDR anyway. :-(

I was too quick in reporting that "INTERNETREPLY NO" fixes it. :(


Cheers, Michiel

--- GoldED+/W32-MSVC 1.1.5-b20170303
* Origin: ZC1 certified techno-dick (2:280/5555)

Hi Michiel,

On 2022-04-23 14:43:09, you wrote to me:

A workaround could be using a local echomail area/directory for
those draft messages.

MvdV> Does not work, the problem also appears in echomail. :-(

Yeah, but setting INTERNETREPLY to NO also works as Michiel found out,
which is more simple... ;)

MvdV> Except that I have to take it back. It seems to work at first, but then if
MvdV> you continue with editing the reply message, it starts using the REPLYADDR
MvdV> anyway. :-(

MvdV> I was too quick in reporting that "INTERNETREPLY NO" fixes it. :(

Strange!

Bye, Wilfred.

--- FMail-lnx64 2.1.0.18-B20170815
* Origin: FMail development HQ (2:280/464)