Hello Rob.
Of late, my old Squish tosser (OS/2) is having an insurmountable problem with NetMails containing data other than the Node number and the time/date code. Here is an example:
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
Date : Thu Nov 12, 16:04 25 pvt rcv From : Nigel Reed 7205:124/5016
To : areafix 7205:396/45
Subj : xxxxxxxx ============================================================ =================== =
TZUTC: -0600
MSGID: 7205@1:124/5016 24130381
-o-o-o-o-o-o-o-o-CUT-o-o-o-o-o-o-o-o-o-
That apparent message number followed by the @ symbol in the MSGID line completely throws Squish for a loop as far as the Zone number is concerned. Both the from and to address are Zone 1 addresses but for some reason Squish cannot fathom the xxxx@ in the MSGID line.
Is there anything that can be done to correct this? Maybe omitting the apparent message number or some kind of spacing? I am not any kind of programmer so I cannot give any suggestions. I can only say that it is ONLY messages coming from a Synchronet system that causes this problem and ONLY when it is NetMail. Echomail is unaffected apparently.
I am at a complete loss. Your help will be very much appreciated!
Of late, my old Squish tosser (OS/2) is having an insurmountable problem with NetMails containing data other than the Node number and the time/date code. Here is an example:[snip]
That apparent message number followed by the @ symbol in the MSGID line completely throws Squish for a loop as far as the Zone number is[snip]
concerned. Both the from and to address are Zone 1 addresses but for
some reason Squish cannot fathom the xxxx@ in the MSGID line.
I am at a complete loss. Your help will be very much appreciated!
It sounds like Squish is trying to parse the source address from
the MSGID? It definitely should not be doing that. Squish is open
source, do you have the means to recompile it if somewhere were to
supply a source code fix/patch for it?
Next I need to ask about the @MSGID line itself. (I am still digging to find the FidoNet technical spec that covers it.) I was told *years* back
that the only thing that was supposed to be in that line were the originating Node number and the hex date/time code - nothing else. Perhaps
the person telling me this (long deceased) may have misinterpreted something... So let me ask you; what's the spec for that line?
Hello Digital.
<On 30Nov2020 20:04 Digital Man (1:103/705) wrote a message to Marc Lewis regarding Problem with legacy tosser (Squish) and Sync's MSGID >
Of late, my old Squish tosser (OS/2) is having an insurmountable problem with NetMails containing data other than the Node number and the time/date code. Here is an example:[snip]
That apparent message number followed by the @ symbol in the MSGID line completely throws Squish for a loop as far as the Zone number is concerned. Both the from and to address are Zone 1 addresses but for[snip]
some reason Squish cannot fathom the xxxx@ in the MSGID line.
I am at a complete loss. Your help will be very much appreciated!
It sounds like Squish is trying to parse the source address from
the MSGID? It definitely should not be doing that. Squish is open source, do you have the means to recompile it if somewhere were to supply a source code fix/patch for it?
First, thanks for taking a look at my message and for your suggestion. I would indeed be interested in a re-compilation of the Squish executable, but have absolutely no method of accomplishing that. I should note that on occasion I run the DOS version of the executable (though not very often) so both the OS/2 and the DOS versions would need to be re-compiled.
Next I need to ask about the @MSGID line itself. (I am still digging to find the FidoNet technical spec that covers it.) I was told *years* back that the only thing that was supposed to be in that line were the originating Node number and the hex date/time code - nothing else. Perhaps the person telling me this (long deceased) may have misinterpreted something... So let me ask you; what's the spec for that line?
As I mentioned before, and there's absolutely no disrespect intended, Synchronet's NetMail messages are the ONLY ones that cause Squish to go nuts... In fact, only a couple years ago or so, Squish had zero problems with NetMail messages from Synchronet... Until the apparent message numbers started appearing in that line. What prompted the change in that line's format?
Also, if there's someone you know of that can re-compile Squish's executable with the recommended changes, please let me know. If you prefer to do it outside of EchoMail, e-mail me at marc.lewis@sursum-corda.com or marc.w@marclewis.org.
<On 30Nov2020 20:04 Digital Man (1:103/705) wrote a message to Marc Lewis regarding Problem with legacy tosser (Squish) and Sync's MSGID >[snip]
Of late, my old Squish tosser (OS/2) is having an insurmountable[snip]
problem with NetMails containing data other than the Node number
and the time/date code. Here is an example:
That apparent message number followed by the @ symbol in the MSGID line completely throws Squish for a loop as far as the Zone number is concerned. Both the from and to address are Zone 1 addresses but for[snip]
some reason Squish cannot fathom the xxxx@ in the MSGID line.
I am at a complete loss. Your help will be very much appreciated!
It sounds like Squish is trying to parse the source address from
the MSGID? It definitely should not be doing that. Squish is open source, do you have the means to recompile it if somewhere were to supply a source code fix/patch for it?
It's probably easier to get the DOS version recompiled than the
OS/2 version. Have you persued either? There should be free tools available to do both. https://github.com/sdudley/maximu
deceased) may have misinterpreted something... So let me ask
you; what's the spec for that line?
Oh, I have a whole (rather long) FAQ on that subject: http://wiki.synchro.net/faq:misc#ftn_msgid
As I mentioned before, and there's absolutely no disrespect intended, Synchronet's NetMail messages are the ONLY ones that cause Squish to go nuts... In fact, only a couple years ago or so, Squish had zero problems with NetMail messages from Synchronet... Until the apparent message
numbers started appearing in that line. What prompted the change in
that line's format?
Before June of this year, Synchronet did not put message-IDs in FTN NetMail messages. This is the requested-changed that added them:
http://cvs.synchro.net/commitlog.ssjs#42030
So I don't think there was any recent change in the FTN Message-ID
Format used by SBBS/SBBSecho, but rather the inclusion of the
MSGID's in NetMail messages to begin with.
Also, if there's someone you know of that can re-compile Squish's[snip]
executable
The only other OS/2 advocate I can think of off hand is Sean
Dennis. I could help with the C code change if he or someone can
handle the build part for DOS and OS/2.
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 339 |
Nodes: | 16 (2 / 14) |
Uptime: | 03:15:22 |
Calls: | 7,467 |
Calls today: | 3 |
Files: | 12,691 |
Messages: | 5,628,147 |