Just released an update to support the INTL kludge, so that inbound netmails display the correct destination node.

Thanks to Nick for all the test netmails!

- Mark
  
--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air,

$ WEATHERMAN was quoted saying . . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Just released an update to support the INTL kludge, so that inbound
netmails display the correct destination node.

Thanks to Nick for all the test netmails!

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Cool, good to see it working.

|07M|11er|03cy|07ful Fate |08(|15hTc|08)|07

--- Enthral BBS v.634 (PI/2 Linux armv7l)
* Origin: haunting The

Cool, good to see it working.

Fixed two things this weekend. Added INTL kludge support for netmails to WWIVTOSS. Also, Nick Andre found the issue with the latest version of DB that was effecting my BBS instance. It was very productive!

For some reason I though it was Mystic that didn't use the MSGID: kludge in netmails. That isn't the case - it is Synchronet only from what I have seen so
far.

Nick let me know about the [FMPT] kludge for inbound netmails from point systems. If the sender system (Synchronet) doesn't use MSGID:, I not only have
to read in the INTL - but check for FMPT and if it has a value, add that to the
sender's node info. The INTL kludge doesn't have point information (if there is one).

I was not aware of that, so I will have to add some logic for Sychronet systems
that use INTL only - to support point systems also.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (46:1/263.0)

$ WEATHERMAN was quoted saying . . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Fixed two things this weekend. Added INTL kludge support for netmails to WWIVTOSS. Also, Nick Andre found the issue with the latest version of DB that was effecting my BBS instance. It was very productive!

For some reason I though it was Mystic that didn't use the MSGID: kludge
in netmails. That isn't the case - it is Synchronet only from what I have seen so far.

Nick let me know about the [FMPT] kludge for inbound netmails from point systems. If the sender system (Synchronet) doesn't use MSGID:, I not only have to read in the INTL - but check for FMPT and if it has a value, add
that to the sender's node info. The INTL kludge doesn't have point information (if there is one).

I was not aware of that, so I will have to add some logic for Sychronet systems that use INTL only - to support point systems also.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Good stuff to know, i'll make to make note of that as i work on a mail tosser myself. :) It's always the little things that casue the big issues, each system doing thigns differently.

Glad to see it's working now though.

|07M|11er|03cy|07ful Fate |08(|15hTc|08)|07

--- Enthral BBS v.634 (PI/2 Linux armv7l)
* Origin: haunting The chapel >>--> htc.zapto.org <--<< (46:1/140)

Good stuff to know, i'll make to make note of that as i work on a mail tosser myself. :) It's always the little things that casue the big
issues, each system doing thigns differently.

Yes, I had no idea what was causing the mysterious no node information on certain netmails for years. Then I thought it was something particular with Mystic, but it is actually Synchronet.

It isn't anything wrong with Synchronet, just that there is no MSGID: kludge in
netmails. Most other BBS systmes have that in netmails.

Either way, I wanted to add support to read that information in properly. It seems to work working, but now need to add Synchronet netmail point support.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weath

$ WEATHERMAN was quoted saying . . ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Yes, I had no idea what was causing the mysterious no node information on certain netmails for years. Then I thought it was something particular
with Mystic, but it is actually Synchronet.

It isn't anything wrong with Synchronet, just that there is no MSGID:
kludge in netmails. Most other BBS systmes have that in netmails.

Either way, I wanted to add support to read that information in properly.
It seems to work working, but now need to add Synchronet netmail point support.

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Ya, I think the fido spec might have something about not requiring MSGID, or even Origin Lines. I think it's better to include them for wider support, but then you also have to take into account software that doesn't.

Then there is the fun with CHARSET and the gbest way to support that. Fidonetworks can get a bit complicated.
:)

|07M|11er|03cy|07ful Fate |08(|15hTc|08)|07

--- Enthral BBS v.634 (PI/2 Linux armv7l)
* Origin: haunting The chapel >>--> htc.zapto.org <--<< (46:1/140)

Ya, I think the fido spec might have something about not requiring MSGID, or even Origin Lines. I think it's better to include them for wider support, but then you also have to take into account software that
doesn't.

I agree, for it can't hurt to have them in there. At the same time, I don't mind adding support to WWIVTOSS to get it functioning with all the different setups.

I just noticed that when creating a netmail to a Synchronet point address, WWIVTOSS was updating the INTL kludge with the point address. I understand that is not the proper way and D'Bridge won't route it properly.

I need to remove the point information from the INTL kludge and add the TOPT kludge for outbound.

Will get to that soon.

- Mark

--- WWIVToss v.1.51
* Origin: http://www.weather-station.org * Bel Air, MD -USA (46:1/263.0)