After some tests I've found that HotdogEd does not import (or show up) netmails that have the TOPT kludge before the INTL kludge.

My node's tosser, Fmail, puts TOPT before INTL, so I don't receive (or see) any netmails in my HotdogEd points. Nodes using other tossers like hpt or SBBSecho do not seem to have this issue because @INTL is the first line in the body.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

04 Dec 21 09:30, Carlos Navarro wrote to All:

After some tests I've found that HotdogEd does not import (or show up) netmails that have the
TOPT kludge before the INTL kludge.

Oh, bad! :( But now I know. Thanks! ;)

My node's tosser, Fmail, puts TOPT before INTL,

That's what my netmail tracker O/T-Track also does. And netmails via O/T won't show up in Hotdoged if they contain INTL. Messages without INTL are fine.

One more reason to use NNTP in Hotdoged.

'Tommi

---
* Origin: rbb.fidonet.fi (2:221/1)

04 Dec 2021 15:35, you wrote to me:

After some tests I've found that HotdogEd does not import (or
show up) netmails that have the TOPT kludge before the INTL
kludge.

Oh, bad! :( But now I know. Thanks! ;)

I have made and am using a script that moves up the INTL kludge in packets for my HotdogEd points. Now I can receive netmail in HotdogEd.

My node's tosser, Fmail, puts TOPT before INTL,

That's what my netmail tracker O/T-Track also does. And netmails via
O/T won't show up in Hotdoged if they contain INTL. Messages without
INTL are fine.

True. I had also found that in my tests, but forgot to report. (Anyway I see that most netmails have INTL even if they are not inter-zone.)

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

08 Dec 2021 21:53, I wrote to Tommi Koivula:

After some tests I've found that HotdogEd does not import (or
show up) netmails that have the TOPT kludge before the INTL
kludge.

Oh, bad! :( But now I know. Thanks! ;)

I have made and am using a script that moves up the INTL kludge in
packets for my HotdogEd points. Now I can receive netmail in HotdogEd.

While testing my script, Tommi found that there are also issues with netmails from other points if the FMPT kludge is present before the INTL kludge: FMPT is discarded, thus they show up as if they came from the point's bossnode.

So I have updated the script to reorder the kludges like:

MSGID
INTL
FMTP
TOPT

This way HotdogEd seems to receive all netmails properly (as long as they have MSGID, but that's another issue...)

The script still needs some polishing and optimisation, but if anyone needs (or wants to test) it, let me know.

Carlos

--- GoldED+/W32-MSVC 1.1.5-b20180707
* Origin: Costa Blanca, Spain (2:341/234)

Hello, Carlos Navarro.
On 05/03/2022 11.14 you wrote:

08 Dec 2021 21:53, I wrote to Tommi Koivula:

After some tests I've found that HotdogEd does not import (or
show up) netmails that have the TOPT kludge before the INTL
kludge.

Oh, bad! :( But now I know. Thanks! ;)

I have made and am using a script that moves up the INTL kludge in
packets for my HotdogEd points. Now I can receive netmail in HotdogEd.

While testing my script, Tommi found that there are also issues with netmails from other points if the FMPT kludge is present before the INTL kludge: FMPT is discarded, thus they show up as if they came from the point's bossnode.
So I have updated the script to reorder the kludges like:
MSGID
INTL
FMTP
TOPT
This way HotdogEd seems to receive all netmails properly (as long as they have MSGID, but that's another issue...)
The script still needs some polishing and optimisation, but if anyone needs (or wants to test) it, let me know.

Yeah, I run the script for pkts to this point. Netmail works fine. :)

--- Hotdoged/2.13.5/Android
* Origin: ----. .---- .---- (2:221/1.911)

Hello, Tommi Koivula.
On 5/3/22 10:38 p. m. you wrote:

Yeah, I run the script for pkts to this point. Netmail works fine.
:)

I reported this to Sergey. He says he hopes he'll be able to fix it some day...

Carlos
--- Hotdoged/2.13.5/Android
* Origin: Costa Blanca, Spain (2:341/234.12)