Hi g00r00

One for when you return and read your mail.

Below a copy of some correspondence and testing I did recently re MUTIL and a suspected problem with the way it handles messages being tossed to other echonodes..

Best, Paul

[snip]

From: Paul Hayton
To: Allen Prunty
Subj: Re: Check your settings pls!
Date: 10/29/16 16:59
Base: Fidonet (FN_SYSOP)

On 10/28/16, ALLEN PRUNTY pondered and said...

Paul, I am not 100% sure it's mystic although some are. What is
happening is that messages are looping back with the message headers altered. The time and dates are changed which causes from my honeypot systems Gecho, Platinum Express, and PCBoard to flag the messages as "Duplicates" because it's like a new message once the time/date has been altered.

Hi Allen.

I've undertaken some hours of testing this Saturday afternoon (my time).

To do this I set up a test Mystic 1.12 A31 Windows system using an address of 3:770/500 and had this accepting traffic from my (same specs) Agency BBS
Mystic system 3:770/100 ..

This test HUB was also set up to export to the Agency HUB 3:770/1 (running Fastecho) but I never actually sent the packets on to that system, rather looked at them to spot differences between packets coming in from 3:770/100
and what was being tossed via /500 to /1

On the basis running a few posts from /100 via /500 to /1 I can also confirm
I am seeing a behavior in my /500 test system that appears to reset the
seconds in the message being tossed to other nodes using MUTIL 1.12 A31

Examples follow (exported from .PKT format to .TXT format using InspectA)

Original post ex /100

[snip]

------------------------------------------------------------------------------ Date: 29 Oct 16 15:47:10
From: Paul Hayton
To: All
Subj: Test 3.47pm
Stat: Locl ------------------------------------------------------------------------------ AREA:NZ_TEST
@TID: Mystic BBS 1.12 A31
@MSGID: 3:770/100 00edd821
@TZUTC: 1300
Test

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)
@PATH: 770/100

[snip]

..and tossed post to /1 via /500

[snip]

------------------------------------------------------------------------------ Date: 29 Oct 16 15:47:00
From: Paul Hayton
To: All
Subj: Test 3.47pm ------------------------------------------------------------------------------ AREA:NZ_TEST
@TID: Mystic BBS 1.12 A31
@MSGID: 3:770/100 00edd821
@TZUTC: 1300
Test

--- Mystic BBS v1.12 A31 (Windows)
* Origin: Agency BBS | telnet://agency.bbs.geek.nz (3:770/100)
@PATH: 770/100 500

[snip]

Note the seconds field in the posted time changes from 15:47:10 to 15:47:00
so those seconds are being altered to 00

Next I wanted to see if the behavior was the same for a source packet posted later within a given minute, closer to a new minute... would Mystic still
when tossing the source packet set the seconds to 00 or round up to the following minute?

Original post ex /10