* Forwarded (from: NET) by Marc Lewis using timEd/2 1.10.y2k+.
* Originally from Marc Lewis (1:396/45) to Lance Vavricka (1:106/987).
* Original dated: Tue Dec 08, 10:44

Hello Lance.

<On 08Dec2020 09:35 Lance Vavricka (1:106/987) wrote a message to Marc Lewis regarding Send me a test NetMail >

@TZUTC: -0600
@MSGID: 819@1:106/987 2434d671
@REPLY: 1:396/45.0 fcefaef0
@PID: Synchronet 3.18c-Linux Dec 5 2020 GCC 4.8.5
@CHRS: ASCII 1
@NOTE: SlyEdit 1.73 (2020-03-31) (DCT style)
Hello Marc,

Let's see how this msg arrives.


___ SBBSecho 3.11-Linux
@ia 1:106/987 @20201208.153538.UTC SBBSecho 3.11-Linux r3.179

It arrived perfect. NO problem!!! Apparently the simple change over to Squish format for the NetMail area from the normal .MSG type storage APPEARS TO have solved the problem. Send a message to SEAL Echo here to see if it responds properly - I believe it will. Send the command %HELP.

I still cannot completely comprehend the reason why Squish cannot properly interpret NetMail messages in .MSG format that have the added characters in the
@MSGID line... Would that I were a programmer; I'd straighten that crap out "chop-chop." For the present time, it looks like I'll be in the clear.

If this continues to work properly, I'll be happier than a pig in a mud puddle.

Best regards,
Marc
___ timEd/2 1.10.y2k+

To top it off - NetMgr continues to work properly - apparently. I didn't think it was able to read the Squish format - but apparently it can as its log shows no irregularity. I'm thrilled to say the least.

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Marc wrote:

It arrived perfect. NO problem!!! Apparently the simple change over to

Squish format for the NetMail area from the normal .MSG type storage APPEARS TO
have solved the problem. Send a message to SEAL Echo here to see if it responds properly - I believe it will. Send the command %HELP.

I still cannot completely comprehend the reason why Squish cannot properly

interpret NetMail messages in .MSG format that have the added characters in the
@MSGID line... Would that I were a programmer; I'd straighten that crap out "chop-chop." For the present time, it looks like I'll be in the clear.

If this continues to work properly, I'll be happier than a pig in a mud

puddle.

I sent a %LINKED request at 12:08PM CST. Nothing back as yet but I think it takes your system a while to process. Let me know if you see the message and
if it gets stuck.

Thanks,
Nigel

---
■ Synchronet ■ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Nelgin wrote:

Marc wrote:

It arrived perfect. NO problem!!! Apparently the simple change over to Squish format for the NetMail area from the normal .MSG type storage APPEARS TO

have solved the problem. Send a message to SEAL Echo here to see if it responds properly - I believe it will. Send the command %HELP.

I still cannot completely comprehend the reason why Squish cannot properly interpret NetMail messages in .MSG format that have the added characters in the

@MSGID line... Would that I were a programmer; I'd straighten that crap out "chop-chop." For the present time, it looks like I'll be in the clear.

If this continues to work properly, I'll be happier than a pig in a mud puddle.

I sent a %LINKED request at 12:08PM CST. Nothing back as yet but I think it takes your system a while to process. Let me know if you see the message and if it gets stuck.

There it is...

2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported
2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported
2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported

---
■ Synchronet ■ End Of The Line BBS - endofthelinebbs.com
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Re: FWD: RE: Send me a test NetMail
By: Marc Lewis to Rob Swindell on Tue Dec 08 2020 11:10 am

I still cannot completely comprehend the reason why Squish cannot properly interpret NetMail messages in .MSG format that have the added characters in the @MSGID line... Would that I were a programmer; I'd straighten that crap out "chop-chop." For the present time, it looks like I'll be in the clear.

Are you sure it wasn't NetMgr that has the issue (and not Squish)?
--
digital man

Synchronet/BBS Terminology Definition #63:
SAUCE = Standard Architecture for Universal Comment Extensions (ACiD)
Norco, CA WX: 73.0°F, 12.0% humidity, 1 mph NW wind, 0.00 inches rain/24hrs
--- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)

Hello Nelgin.

<On 08Dec2020 12:30 Nelgin (1:103/705) wrote a message to Nelgin regarding Re: FWD: RE: Send me a test NetMail >
[snip]

If this continues to work properly, I'll be happier than a pig in a mud puddle.

I sent a %LINKED request at 12:08PM CST. Nothing back as yet but I think it takes your system a while to process. Let me know if you see the
message and if it gets stuck.

There it is...

2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported
2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported
2020-12-08 12:29:38 SEAL Echo Manager (1:396/45) To: Nigel Reed (1:124/5016) Imported

Yeah, mailtoss runs every 6 minutes plus transit time. But that notwithstanding, it was received and processed w/o error.

Best regards,
Marc

... I was going to tell you a UDP joke, but I'm not sure you would get it.
--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Hello Digital.

<On 08Dec2020 10:47 Digital Man (1:103/705) wrote a message to Marc Lewis regarding FWD: RE: Send me a test NetMail >

I still cannot completely comprehend the reason why Squish cannot properly interpret NetMail messages in .MSG format that have the added
characters in the @MSGID line... Would that I were a programmer; I'd straighten that crap out "chop-chop." For the present time, it
looks like I'll be in the clear.

Are you sure it wasn't NetMgr that has the issue (and not Squish)?

NetMgr seems to be working just fine with the change-over to a Squish NetMail area. All I needed to do with it is put a $ in front of c:\netmail\netmail. Scans and acts on the required messages w/o issue thus far.

It's still regrettable that FTSC was not more specific in its specification for
the format of the @MSGID line. At best, what's written is debatable.

Best regards,
Marc

--- timEd/2 1.10.y2k+
* Origin: Sursum Corda! BBS-Huntsville,AL-bbs.sursum-corda.com (1:396/45)

Re: RE: FWD: RE: Send me a test NetMail
By: Marc Lewis to Digital Man on Tue Dec 08 2020 02:12 pm

Are you sure it wasn't NetMgr that has the issue (and not Squish)?

NetMgr seems to be working just fine with the change-over to a Squish NetMail area. All I needed to do with it is put a $ in front of c:\netmail\netmail. Scans and acts on the required messages w/o issue thus far.

Okay, so it still could just be NetMgr's fault then (?).

From the examples provided to me by Fred Riccio, it appears Squish doesn't really support exporting netmail to "stored message" (.msg) format very well - none of his Squish-exported netmail messages contain proper zones or points in the message fixed-headers, regardless of the MSGID kludge existence/absence or format. The messages do appear to have the Via kludge lines however, so the information is there if a program really looks for it. I'm not sure if there's a configuration or perhaps a later bug-fix that's missing, but the Squish-exported .msg files that I've seen so far definitely don't look right.

It's still regrettable that FTSC was not more specific in its specification for the format of the @MSGID line. At best, what's written is debatable.

I would argue the FTSC specification was overly-specific: the 32-bit "serialno"
is insufficient for its aims. The "prior art" was the RFC-822 Message-ID defined 10 years earlier with much *less* specificity than the FTSC spec and it's worked well for almost 40 years now. And nobody tries to "parse" an RFC-822 Message-ID and discover surprising failures years later as a result.
--
digital man

Synchronet "Real Fact" #116:
Synchronet v1a r5 (for MS-DOS) was released on February 19, 1992
Norco, CA WX: 75.1°F, 11.0% humidity, 1 mph ENE wind, 0.00 inches rain/24hrs --- SBBSecho 3.11-Linux
* Origin: Vertrauen - [vert/cvs/bbs].synchro.net (1:103/705)