• Magitoss

    From Dumas Walker@21:1/175 to Apam on Sat Feb 10 13:53:08 2018
    I have a couple of packets waiting for magitoss to pick up. They are in the /fido/in directory that is set up in the config. However, magitoss acts as if they are not there.

    The node number is 21:1/175.8
    The packets are called:
    0000p008.FR0
    0000p008.SA0

    This idiotic hex format that fido networks uses frustrates me to no end. ARe those named properly, or does sbbsecho have an issue with how it is formating the names. Or should the name have changed when it was moved? mystic's fidotoss id'ed them as being for 21:1/175.8 but was somehow not able to move them over, so I have copied them over into the directory in question.

    Any assistance would be appreciated. Thanks!
    --- SBBSecho 3.03-Linux
    * Origin: CCO BBS - capitolcityonline.net:26 (21:1/175)
  • From apam@21:1/125 to Dumas Walker on Sun Feb 11 10:02:14 2018
    I have a couple of packets waiting for magitoss to pick up. They are in the /fido/in directory that is set up in the config. However, magitoss acts as if they are not there.

    The node number is 21:1/175.8 The packets are called: 0000p008.FR0 0000p008.SA0

    Magimail is ignoring the packets because of the 'p' character in the file
    name. I will have to research what is the correct way of doing things.

    Andrew


    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From apam@21:1/125 to Dumas Walker on Sun Feb 11 12:20:22 2018
    The node number is 21:1/175.8 The packets are called: 0000p008.FR0 0000p008.SA0

    I've just pushed an update that should work with these point files.
    You'll need v0.9-patch or v0.10-alpha

    To update, in your Magicka BBS directory..

    git pull
    git checkout v0.9-patch

    then make www

    Andrew


    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Dumas Walker@21:1/175 to apam on Sat Feb 10 21:53:20 2018
    Re: RE: Magitoss
    By: apam to Dumas Walker on Sun Feb 11 2018 12:20:23

    I've just pushed an update that should work with these point files.
    You'll need v0.9-patch or v0.10-alpha

    To update, in your Magicka BBS directory..

    git pull
    git checkout v0.9-patch

    then make www

    Thanks! As soon as the pi is done updating from jesse to stretch, I will give this a shot!
    --- SBBSecho 3.03-Linux
    * Origin: CCO BBS - capcity2.synchro.net - 1-502-875-8938 (21:1/175)
  • From Tiny@21:1/130.4 to apam on Sun Feb 11 21:37:40 2018
    Quoting apam to Dumas Walker <=-

    I've just pushed an update that should work with these point files.
    You'll need v0.9-patch or v0.10-alpha

    Dumb question... I run Magicka as a point and have never had an issue
    what's the difference? (Pure curiousity on my part)

    Shawn

    ... Success usually comes to those too busy to look for it.
    --- Blue Wave/386
    * Origin: A Tiny slice o pi (21:1/130.4)
  • From Black Panther@21:1/186 to Tiny on Sun Feb 11 15:44:42 2018
    On 02/11/18, Tiny said the following...

    I've just pushed an update that should work with these point files. You'll need v0.9-patch or v0.10-alpha

    Dumb question... I run Magicka as a point and have never had an issue
    what's the difference? (Pure curiousity on my part)

    There's no such thing as a dumb question. Dumb answers on the other hand. :)

    I believe it was because Synchronet adds the 'p' in the filename for a point system. I think that's where Magitoss was having an issue.

    Andrew will correct me if I'm wrong, but that was my understanding. :)


    ---

    Black Panther
    a.k.a. Dan Richter
    Sysop - Castle Rock BBS (RCS)
    telnet://bbs.castlerockbbs.com
    http://www.castlerockbbs.com
    The sparrows are flying again....

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From apam@21:1/125 to Tiny on Mon Feb 12 09:58:20 2018
    Dumb question... I run Magicka as a point and have never had an issue
    what's the difference? (Pure curiousity on my part)

    Just synchronet being weird.

    Andrew

    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From apam@21:1/125 to Black Panther on Mon Feb 12 09:59:10 2018
    I believe it was because Synchronet adds the 'p' in the filename for a point system. I think that's where Magitoss was having an issue.

    Andrew will correct me if I'm wrong, but that was my understanding. :)

    Yep that's correct.

    Andrew


    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Accession@21:1/200 to apam on Mon Feb 12 12:23:40 2018
    On 02/11/18, apam said the following...

    The node number is 21:1/175.8 The packets are called: 0000p008.FR0 0000p008.SA0

    Magimail is ignoring the packets because of the 'p' character in the file name. I will have to research what is the correct way of doing things.

    The "p" in the filename designates a point address, and case sensitivity shouldn't matter.

    Regards,
    Nick

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From Accession@21:1/200 to Tiny on Mon Feb 12 12:26:58 2018
    On 02/11/18, Tiny said the following...

    Dumb question... I run Magicka as a point and have never had an issue
    what's the difference? (Pure curiousity on my part)

    Looks like Dumas was using another software as the point, and MagicaBBS as
    the boss. The opposite of what you're doing. So you're sending out whatever file name MagicaBBS creates, and your other software is processing it correctly. The other way around, MagicaBBS just wasn't dealing with a certain style of point bundle naming, it seems.

    Regards,
    Nick

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From apam@21:1/125 to Accession on Tue Feb 13 12:00:00 2018
    The "p" in the filename designates a point address, and case
    sensitivity shouldn't matter.

    Yes, in Synchronet, and according to Synchronet, bundle names can be
    anything at all (just the extension is specific)

    Crashmail / Magimail expects bundle names to be hexadecimal characters
    (even for points), and will disregard anything that has a non-hexadecimal character in the bundle name (such as 'p').

    So I'm not sure which is correct. I'm thinking Synchronet is probably
    doing something non-standard, given that I've not seen this before in
    other BBS/Mailers I've had set up. On the other hand, the only mention of
    what a bundle name should be that I can find via google is the Synchronet documentation.

    So for now I've just allowed the 'p' (or 'P') in bundle names and the
    rest should be hexadecimal. I guess for now that will do and if some
    other program starts sending bundles with other non hexadecimal
    characters I'll deal with it then.

    Andrew

    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Static@21:2/140 to apam on Tue Feb 13 03:10:08 2018
    On 02/13/18, apam said the following...

    So I'm not sure which is correct. I'm thinking Synchronet is probably doing something non-standard, given that I've not seen this before in other BBS/Mailers I've had set up. On the other hand, the only mention of what a bundle name should be that I can find via google is the Synchronet documentation.

    There were proposals for standardizing bundle filenames long ago but nothing came of it officially AFAIK. The only FTSC requirement was that they be in 8.3 format. Beyond that mailers just did whatever they deemed appropriate in order to avoid filename collisions.
    If multiple mailers/tossers have been taking a common approach, it's de-facto.

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: Subcarrier BBS (21:2/140)
  • From Tiny@21:1/130.4 to Black Panther on Tue Feb 13 10:32:06 2018
    Quoting Black Panther to Tiny <=-

    I believe it was because Synchronet adds the 'p' in the filename for a point system. I think that's where Magitoss was having an issue.
    Andrew will correct me if I'm wrong, but that was my understanding. :)

    Right-o! ;)

    Shawn

    ... Forty-two?! 7.5 million years and all y-- oh, you were running Window
    --- Blue Wave/386
    * Origin: A Tiny slice o pi (21:1/130.4)
  • From Bill McGarrity@21:2/141 to apam on Tue Feb 13 18:17:00 2018
    apam wrote to Accession on 02-13-18 12:00 <=-

    The "p" in the filename designates a point address, and case
    sensitivity shouldn't matter.

    Yes, in Synchronet, and according to Synchronet, bundle names can be anything at all (just the extension is specific)

    Running under a BSO mailer they can use any bundle or pkt name as the .*LO file will use the binary address for the mailer. Inside that file is the path/name of the bundle/pkt that's to be transfered.

    Crashmail / Magimail expects bundle names to be hexadecimal characters (even for points), and will disregard anything that has a
    non-hexadecimal character in the bundle name (such as 'p').

    May I ask why someone, other than the host route echomail/netmail?

    So I'm not sure which is correct. I'm thinking Synchronet is probably doing something non-standard, given that I've not seen this before in other BBS/Mailers I've had set up. On the other hand, the only mention
    of what a bundle name should be that I can find via google is the Synchronet documentation.

    As I said, Synchronet is in complience with a BSO style mailer but can, if desired, create a mail attach depending on the switches used.

    So for now I've just allowed the 'p' (or 'P') in bundle names and the
    rest should be hexadecimal. I guess for now that will do and if some
    other program starts sending bundles with other non hexadecimal
    characters I'll deal with it then.

    Most all BSO mailers work as I stated above and again, why would someone other than the point's host route echomail/netmail.

    Netmail is a different animal but works on the same principle as the tosser will create a *.?LO file of said netmail, see it's a point and route it through the host. The host should then forward it to the point. No where should anyone other than the host be in contact with the point.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
    --- MultiMail/Win32 v0.50
    * Origin: TequilaMockingbird Online - Badlands of NJ (21:2/141)
  • From Bill McGarrity@21:2/141 to apam on Tue Feb 13 18:39:32 2018
    Re: RE: Magitoss
    By: apam to Accession on Tue Feb 13 2018 12:00:01

    OK..just to show you how the files are created, here is a section of my log with my reply to your message.

    + 18:18 [7276] call to 21:2/100@fsxnet
    18:18 [7276] trying error404bbs.ddns.net [108.204.225.235]:24555...
    18:18 [7276] connected
    + 18:18 [7276] outgoing session with error404bbs.ddns.net:24555 [108.204.225.235]
    - 18:18 [7276] OPT CRAM-MD5-327fc5861180d8e53e402e55d74b63f2
    + 18:18 [7276] Remote requests MD mode
    - 18:18 [7276] SYS fsxHUB Tholian [NET2]
    - 18:18 [7276] ZYZ Todd Zieman
    - 18:18 [7276] VER Mystic/1.12A38 binkp/1.0
    + 18:18 [7276] addr: 21:2/0@fsxnet
    + 18:18 [7276] addr: 21:2/100@fsxnet
    + 18:18 [7276] pwd protected session (MD5)

    + 18:18 [7276] sending c:\fd\outbound.015\5a837240.pkt as 5a837240.pkt (2657)

    As you can see above, Synchronet created 5a837240.pkt with my reply.
    Synchronet also created a file named: 00020064.clo with the following information: c:\fd\outbound.015\5a837240.pkt and place them both in the outbound.015 folder. (015 is hex for 21)

    Binkd would see the *.clo file sitting in the z21 folder check the
    INA address and do an outgoing session.where the .pkt would then be
    transfered to 21:2/100

    - 18:18 [7276] receiving 0000ffd7.tuf (1090 byte(s),
    off 0) + 18:18 [7276] 0000ffd7.tuf -> c:\fd\secure\0000ffd7.tuf
    18:18 [7276] got *.[mMwWtTfFsS][oOeEhHrRaAuU][0-9a-zA-Z], delayed creating c:\sbbs\data\fidoin.now

    As you can see above, 21:2/100 also sent me a bundle named 0000ffd7.tuf. The name of that bundle has nothing to do with my address in binary.

    + 18:18 [7276] rcvd: 0000ffd7.tuf (1090, 1090.00 CPS, 21:2/0@fsxnet)
    + 18:18 [7276] sent: c:\fd\outbound.015\5a837240.pkt (2657, 2657.00 CPS, 21:2/100@fsxnet)
    + 18:18 [7276] done (to 21:2/100@fsxnet, OK, S/R: 1/1 (2657/1090 bytes))
    18:18 [7276] Creating c:\sbbs\data\fidoin.now
    18:18 [7276] session closed, quitting...

    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: 6697
    Radio: radio.tequilamockingbirdonline.net:8010/live
    --- SBBSecho 3.03-Win32
    * Origin: TequilaMockingbird Online - Badlands of NJ (21:2/141)
  • From apam@21:1/125 to Bill McGarrity on Wed Feb 14 17:17:32 2018
    May I ask why someone, other than the host route echomail/netmail?

    I don't know why the people who wrote crashmail chose to check that
    bundles had hexidecimal characters as the filename, my guess is to differentiate between bundles and other files that may arrive in the
    inbox, but that's just a guess.

    As I said, Synchronet is in complience with a BSO style mailer but can,
    if desired, create a mail attach depending on the switches used.

    So it seems. Are you suggesting I remove the check altogether? I'm not
    keen on it, the crashmail people must have put it in there for a reason,
    but then I'm sure they are human too.

    Andrew

    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Accession@21:1/200 to apam on Thu Feb 15 08:42:18 2018
    On 02/13/18, apam said the following...

    Yes, in Synchronet, and according to Synchronet, bundle names can be anything at all (just the extension is specific)

    You can compare that to FTSC documentation if you wish, but just supporting
    it as you've done would probably be better, since I doubt Rob is going to change Synchronet to conform to lesser 30yr old documentation. ;)

    So I'm not sure which is correct. I'm thinking Synchronet is probably doing something non-standard, given that I've not seen this before in other BBS/Mailers I've had set up. On the other hand, the only mention of what a bundle name should be that I can find via google is the Synchronet documentation.

    Only other place I would suggest looking is ftsc.org, which may or may not
    come up in a google search since 99% of the documentation is quite old, and probably not even accessed as much as Synchronet's wiki and website have been.

    Regards,
    Nick

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From Bill McGarrity@21:2/141 to apam on Thu Feb 15 18:56:00 2018
    apam wrote to Bill McGarrity on 02-14-18 17:17 <=-

    May I ask why someone, other than the host route echomail/netmail?

    I don't know why the people who wrote crashmail chose to check that bundles had hexidecimal characters as the filename, my guess is to differentiate between bundles and other files that may arrive in the inbox, but that's just a guess.

    Bundles are normally multiple pkt's compressed and the extension normally has something to do with the day of the week and a # (*.mo0, tu1, we3.. etc). A *.pkt is standalone and will normally have ALL the info within the header with regard to any kludges.

    As I said, Synchronet is in complience with a BSO style mailer but can,
    if desired, create a mail attach depending on the switches used.

    So it seems. Are you suggesting I remove the check altogether? I'm not keen on it, the crashmail people must have put it in there for a
    reason, but then I'm sure they are human too.

    I am not that familiar with crashmail to say either yes or no. Most likely crashmail can only handle 3D addressing so that is the reason it's built that way. If you have Fido, I'm sure there is a crashmail echo where you can ask.


    --

    Bill

    Telnet: tequilamockingbirdonline.net
    Web: bbs.tequilamockingbirdonline.net
    FTP: ftp.tequilamockingbirdonline.net:2121
    IRC: irc.tequilamockingbirdonline.net Ports: 6661-6670 SSL: +6697
    Radio: radio.tequilamockingbirdonline.net:8010/live


    ... Look Twice... Save a Life!!! Motorcycles are Everywhere!!!
    --- MultiMail/Win32 v0.50
    * Origin: TequilaMockingbird Online - Badlands of NJ (21:2/141)
  • From apam@21:1/125 to Accession on Fri Feb 16 11:39:22 2018
    You can compare that to FTSC documentation if you wish, but just supporting it as you've done would probably be better, since I doubt Rob is going to change Synchronet to conform to lesser 30yr old
    documentation. ;)

    Yeah, there's nothing there, the only 'technical standard' describes the
    flow files and stuff, not the names of the bundles themselves.

    I don't expect Rob to change synchronet, at present I've changed things
    so that it still checks for hexidecimal characters, but also allows for a
    p where synchronet puts one. What I'm wondering is if I should remove the
    check altogether and only check the extensions.

    Andrew


    --- MagickaBBS v0.10alpha (Linux/x86_64)
    * Origin: Exotica BBS - telnet://exoticabbs.com:2023/ (21:1/125)
  • From Accession@21:1/200 to apam on Tue Feb 20 08:43:56 2018
    On 02/16/18, apam said the following...

    Yeah, there's nothing there, the only 'technical standard' describes the flow files and stuff, not the names of the bundles themselves.

    I don't expect Rob to change synchronet, at present I've changed things
    so that it still checks for hexidecimal characters, but also allows for a p where synchronet puts one. What I'm wondering is if I should remove the check altogether and only check the extensions.

    I don't think there's any specific information out there on the format of an actual bundle filename, besides the extension - and most mailers these
    days only check the extension as far as whether or not to process them. So I would assume you removing that check and stick with the extensions would be acceptable, but you may want to check with some other FTN programmers to be certain.

    Regards,
    Nick

    --- Mystic BBS v1.12 A38 2018/01/01 (Linux/64)
    * Origin: _thePharcyde telnet://bbs.pharcyde.org (Wisconsin) (21:1/200)
  • From Blue White@21:1/175.8 to apam on Tue Feb 13 19:51:16 2018
    So for now I've just allowed the 'p' (or 'P') in bundle names and the
    rest should be hexadecimal. I guess for now that will do and if some
    other program starts sending bundles with other non hexadecimal
    characters I'll deal with it then.

    that is the first time I have ever seen a letter in a packet name that was
    not a-f.



    ... Direct from the Ministry of Silly Walks
    --- MultiMail
    * Origin: Possum Lodge South capitolcityonline.net:7636 (21:1/175.8)
  • From Atreyu@21:1/176 to Static on Mon Jul 30 15:02:04 2018
    On 13 Feb 18 03:10:08, Static said the following to Apam:

    There were proposals for standardizing bundle filenames long ago but nothing came of it officially AFAIK. The only FTSC requirement was that they be in 8 format. Beyond that mailers just did whatever they deemed appropriate in ord to avoid filename collisions.
    If multiple mailers/tossers have been taking a common approach, it's de-fact

    Arcmail-named files are pretty much accepted as "standard" nowadays.

    Atreyu

    --- Renegade vY2Ka2
    * Origin: Joey, do you like movies about gladiators? (21:1/176)