Hi All,

We just discovered something between Mystic and Synchronet, in reference to netmail.

When netmail is written on a Synchronet system, routed through a Synchronet hub, and sent to my Mystic system, there is a problem with the reply-to address. In this othernet, zone 24, I was sent a netmail from 24:100/1. This was routed through 24:24/1, which is the hub. The message got to me just
fine, but when I try to reply to it, it shows 24:24/1 for the address instead of the 24:100/1 address.

When I view the kludge lines, I see this:

@INTL 24:150/1 24:100/1
@INTL 24:150/1 24:100/1
@PID: Synchronet 3.17a-Win32 Nov 25 2017 MSC
@INTL 24:150/1 24:100/1
@TZUTC: -0500
@Via: 24:100/1 @20171128.013935.UTC SBBSecho 3
@Via: 24:24/1 @20171128.014945.UTC SBBSecho 3.

Each time I reply, I need to change the address to 24:100/1. I'm not sure if this is a problem with Synchronet or Mystic. (I do know that Rob Swindell is looking into this as well)

It was also mentioned that there should only be one @INTL line in the
message, but I believe that is being added by Synchronet.

There is some testing being done from the Synchronet system, to see if
similar issues arise from other Mystic systems, as well as non-Mystic/Synchronet systems.

Has anyone else noticed anything like this?


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A36 2017/11/27 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)

There is some testing being done from the Synchronet system, to see if similar issues arise from other Mystic systems, as well as non-Mystic/Synchronet systems.

I can't say for sure because I haven't looked at it yet, but its probably an issue with Mystic. I just recently changed the way all of that works because of the way BBBS processes mail with its "security" option, and it breaks the way Mystic got the reply netmail address.

I don't think its a Synchronet issue, so you can probably pass what I said back to Rob so he's not wasting his time chasing a non-existant issue in Synchronet. If for some reason I am wrong I can follow back up with you or him.

Its on my TODO list to look at. Hopefully this weekend.

--- Mystic BBS v1.12 A36 2017/11/27 (Windows/64)
* Origin: Sector 7 [Mystic BBS WHQ] (21:1/108)

On 11/28/17, g00r00 said the following...

There is some testing being done from the Synchronet system, to see i similar issues arise from other Mystic systems, as well as non-Mystic/Synchronet systems.

I don't think its a Synchronet issue, so you can probably pass what I
said back to Rob so he's not wasting his time chasing a non-existant
issue in Synchronet. If for some reason I am wrong I can follow back up with you or him.

I forwarded this message his direction.

Thanks for the quick reply.


---

Black Panther
a.k.a. Dan Richter
Sysop - Castle Rock BBS (RCS)
The sparrows are flying again....

--- Mystic BBS v1.12 A36 2017/11/27 (Linux/64)
* Origin: Castle Rock BBS - castlerockbbs.com (21:1/186)