I'm going to take a wild stab in the dark and say perhaps it was done
this way in mystic to have a method for obtaining the origin address that worked in both netmail and echomail.
I think you're supposed to get the Originating address from the INTL kludge in netmail and the origin line in echomail.
Anyway, I have no clue why mystic would work with synchronet netmail and not yours, that's the real mystery :)
Glad you got it working!
I was under the impression that the MSGID is optional, I wonder what
would happen if you sent a netmail without a MSGID at all.
So according to that document, MSGIDs and REPLYIDs are optional, but if they exist then they must be like the document describes.
And they describe the format that Mystic and others use, not the synchronet format.
There must be more documents that describe the syncronet format later, i don't know, there so many documents that are just proposals and what not
i get lost in it lol
I did a little digging in the short time I had, and it looks like netmail mentions use of INTL, FMPT, and TOPT, but I don't see much reference to MSGID whatsoever, as that's usually mentioned with echomail.
I've written a test netmail from my Synchronet BBS to my hub system running HPT and Golded where I can view the kludges nicely.. said netmail from Synchronet does *NOT* contain a MSGID. So it's safe to say that netmail doesn't require it and if you cut it out of netmail completely, you won't have to change your current MSGID format.
Awesome, thank you for looking into this! I'll try without MSGID in NetMail at all tonight and see how it goes.
NuSkooler wrote to All on 01-09-18 22:23 <=-
Avon, g00r00, others --
It worked! For at least now, I modified ENiG to send a standard MSGID *only for
NetMail export* and got my response from fsxNet.
g00r00: I'd really like to understand why Synchronet's MSGID works when
it sends NetMail. The last I checked, they used the same format ENiG
was using, and it was OK, but maybe something is just slightly enough different? If you have any ideas, or examples of Sync MSGID's with
NetMail working or not, I'd love to hear it. Most of the FTN stuff ENiG does is compliant, but the MSGID's for at least EchoMail are nice to
have in the Sync format if I can get away with it :)
Thanks again for your help everyone. I can now either wrap up
0.0.8-alpha and move to the next, or add in some additional NetMail
bells and whistles... hrmm....
Accession wrote to NuSkooler on 01-10-18 06:01 <=-
I did a little digging in the short time I had, and it looks like
netmail mentions use of INTL, FMPT, and TOPT, but I don't see much reference to MSGID whatsoever, as that's usually mentioned with
echomail.
I've written a test netmail from my Synchronet BBS to my hub system running HPT and Golded where I can view the kludges nicely.. said
netmail from Synchronet does *NOT* contain a MSGID. So it's safe to say that netmail doesn't require it and if you cut it out of netmail completely, you won't have to change your current MSGID format.
Hiya Nick...
** waves at Bill & Nick ** :)
** waves at Bill & Nick ** :)
LOL Paul....
There was actually much more to that message but it seems the 'paste' didn't take. Was just about Frontdoor's FM editor that DOES add a
@MSGID to it's netmail and Synchronet tosses it just fine.
| Sysop: | Keyop |
|---|---|
| Location: | Huddersfield, West Yorkshire, UK |
| Users: | 307 |
| Nodes: | 16 (2 / 14) |
| Uptime: | 42:33:43 |
| Calls: | 6,880 |
| Calls today: | 8 |
| Files: | 12,369 |
| Messages: | 5,422,798 |
| Posted today: | 2 |