• Netmail

    From apam@21:1/126 to All on Mon Jan 20 14:12:55 2020
    Hi

    I'm fiddling with Titan trying to get netmail to work, and I can't seem
    to figure it out - it can't seem to get past 21:1/100

    Here's what I've tried:

    Netmail from Titan -> Magicka works

    Netmail from Titan -> Mystic works

    Netmail from Magicka -> Mystic -> Magicka -> Titan works

    Netmail from Magicka -> Titan works

    I am trying to send a netmail from my fsx point to another fsx node,
    it's routed so should go along this path:

    21:1/126.1 -> 21:1/126 -> 21:1/100 -> 21:1/125

    I'm fairly certain the netmail is getting sent via binkd to Risa HUB but
    for some reason the packet doesn't make it any further. I'm sure I'm
    doing something wrong, but can't figure it out - is anyone able to take
    a look at the packet I'm sending and see if they notice what I'm doing
    wrong?

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Avon@21:1/101 to apam on Mon Jan 20 19:15:38 2020
    On 20 Jan 2020 at 02:12p, apam pondered and said...

    I'm fairly certain the netmail is getting sent via binkd to Risa HUB but for some reason the packet doesn't make it any further. I'm sure I'm
    doing something wrong, but can't figure it out - is anyone able to take
    a look at the packet I'm sending and see if they notice what I'm doing wrong?

    Can you give me a packet name or time to look for ?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From apam@21:1/126 to Avon on Mon Jan 20 17:08:14 2020
    On 20 Jan 2020 at 02:12p, apam pondered and said...

    I'm fairly certain the netmail is getting sent via binkd to
    Risa HUB but for some reason the packet doesn't make it any
    further. I'm sure I'm doing something wrong, but can't figure
    it out - is anyone able to take a look at the packet I'm
    sending and see if they notice what I'm doing wrong?

    Can you give me a packet name or time to look for ?

    I just sent another one at 5:02pm my time.

    I think judging by your netmail, the problem is I've set the message to
    crash when it shouldn't be.

    magimail see's the crash flag and sets the destination to 21:1/100
    instead of setting the destination as the one in the packet.

    That's my theory, not sure if it's right we'll see if the 5:02 pm packet
    makes it through.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Avon@21:1/101 to apam on Mon Jan 20 20:23:00 2020
    On 20 Jan 2020 at 05:08p, apam pondered and said...

    I just sent another one at 5:02pm my time.

    I think judging by your netmail, the problem is I've set the message to crash when it shouldn't be.

    magimail see's the crash flag and sets the destination to 21:1/100
    instead of setting the destination as the one in the packet.

    That's my theory, not sure if it's right we'll see if the 5:02 pm packet makes it through.

    Local time here is just after 8pm ... looks like it arrived at 1/100 and
    tossed in addressed to you at the HUB which won't end well.

    ! Jan 20 20:03:38 Import from c:\mystfsx\echomail\in\
    + Jan 20 20:03:38 Extracting 5da6de53.mo9
    - Jan 20 20:03:38 unzip -oqqjC "c:\mystfsx\echomail\in\5da6de53.mo9"
    "*.pkt" -d c:\mystfsx\temputil\
    + Jan 20 20:03:38 Importing 2550bd00.pkt (21:1/126 to 21:1/100)
    + Jan 20 20:03:38 Netmail from apam (21:1/126) to apam (21:1/100)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From apam@21:1/126 to Avon on Mon Jan 20 17:32:04 2020
    Local time here is just after 8pm ... looks like it arrived at
    1/100 and tossed in addressed to you at the HUB which won't end
    well.

    Sorry about that. Hopefully by "won't end well" doesn't mean catastrophe
    at the hub, but rather just a disappearing packet.

    I'm fairly certain it's magimail doing something...

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Avon@21:1/101 to apam on Mon Jan 20 20:37:39 2020
    On 20 Jan 2020 at 05:32p, apam pondered and said...

    Sorry about that. Hopefully by "won't end well" doesn't mean catastrophe at the hub, but rather just a disappearing packet.

    I'm fairly certain it's magimail doing something...

    Nothing to be sorry about :) Yep I just mean it drops into a bucket no one
    can read.

    I've never really understood the packet addressing completely either. But I think you can have a destination address within the packet but then another address encapsulated elsewhere? Dunno, it's getting late here...

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From apam@21:1/126 to Avon on Mon Jan 20 23:08:48 2020
    I've never really understood the packet addressing completely
    either. But I think you can have a destination address within the
    packet but then another address encapsulated elsewhere? Dunno, it's getting late here...

    Yep it's 11pm here now, and I've made no progress. The packet has a
    header with the origin and destination in it, so does each message. So I
    have all those set right and mystic still imports instead of routing it.

    I did notice that Mystic seems to require the INTL kludge for routing,
    even if the messages are in the same zone.

    I don't understand why it routes packets from crashmail but not my
    packets, when i've spent the last five or six hours comparing packets
    and they are identical (except for the origin and destinations which are
    both correct. and the message content.)

    Well time for bed

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Avon@21:1/101 to apam on Tue Jan 21 08:29:45 2020
    On 20 Jan 2020 at 11:08p, apam pondered and said...

    Yep it's 11pm here now, and I've made no progress. The packet has a
    header with the origin and destination in it, so does each message. So I

    are you attempting to send to/from a point address in the current tests?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From apam@21:1/126 to Avon on Tue Jan 21 08:32:35 2020
    On 20 Jan 2020 at 11:08p, apam pondered and said...

    Yep it's 11pm here now, and I've made no progress. The packet
    has a header with the origin and destination in it, so does
    each message. So I

    are you attempting to send to/from a point address in the current
    tests?

    No, these tests I setup a test net with mystic as the hub.

    Andrew


    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From apam@21:1/126 to Avon on Tue Jan 21 08:56:06 2020
    are you attempting to send to/from a point address in the
    current tests?

    No, these tests I setup a test net with mystic as the hub.

    Ok, so it's definitely something weird with mystic.. I just sent a
    netmail via scinet and it worked (netsurge uses hpt i believe).

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Netsurge@21:4/154 to apam on Mon Jan 20 23:24:46 2020
    Ok, so it's definitely something weird with mystic.. I just sent a
    netmail via scinet and it worked (netsurge uses hpt i believe).

    I do. Drop a copy of the packet in my inbound and i'll take a look at it for you.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From apam@21:1/126 to Netsurge on Tue Jan 21 14:52:38 2020
    Ok, so it's definitely something weird with mystic.. I just
    sent a netmail via scinet and it worked (netsurge uses hpt i
    believe).

    I do. Drop a copy of the packet in my inbound and i'll take a look
    at it for you.

    Just sent 21144546.test-pkt to you :)

    Thanks very much...

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Netsurge@21:4/154 to apam on Wed Jan 22 23:24:42 2020
    Just sent 21144546.test-pkt to you :)

    I don't see anything wrong with it. It is per FTSC specs. I would like to see what Mystics logs say. Didn't g00r00 just up the verbosity of the logs in the latest alpha. As you already know, I use hpt so I can't check on my Mystic system, but if you can get them from Avon or someone else running Mystic that might help.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From apam@21:1/126 to Netsurge on Thu Jan 23 14:35:59 2020
    Just sent 21144546.test-pkt to you :)

    I don't see anything wrong with it. It is per FTSC specs. I would
    like to see what Mystics logs say. Didn't g00r00 just up the
    verbosity of the logs in the latest alpha. As you already know, I
    use hpt so I can't check on my Mystic system, but if you can get
    them from Avon or someone else running Mystic that might help.

    Thanks for taking a look, much appreciated :)

    I don't have any logs on that particular packet as I just created a
    fresh one for you to look at, but here was my last test in my fake
    happynet setup. Note, the packet was addressed to Al at 637:1/101, I
    sent it to Al as there was no Al user on my mystic system.

    Please note, I spaced it out to stop Magicka from wrapping the log
    lines.

    + Jan 20 23:06:46 Process: Importing EchoMail

    + Jan 20 23:06:46 Waiting for BUSY nodes

    - Jan 20 23:06:46 LINKS:

    - Jan 20 23:06:46 Node 3 637:1/102@happynet

    - Jan 20 23:06:46 Node 2 637:1/101@happynet

    ! Jan 20 23:06:46 Import from /home/andrew/mystic/echomail/in/

    + Jan 20 23:06:46 Extracting 00000002.MO0

    - Jan 20 23:06:46 unzip -oqqjC "/home/andrew/mystic/echomail/in/00000002.MO0" "*.pkt" -d /home/andrew/mystic/temputil/

    + Jan 20 23:06:46 Importing 20230546.pkt (637:1/102 to 637:1/100)

    + Jan 20 23:06:46 Netmail from apam (637:1/102) to Al (637:1/100)

    ! Jan 20 23:06:46 Import from
    /home/andrew/mystic/echomail/in/unsecure/

    + Jan 20 23:06:46 Results: 0 echo, 1 net, 0 dupes, 0 tossed in 0.04s


    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Netsurge@21:4/154 to apam on Thu Jan 23 09:35:48 2020
    I don't have any logs on that particular packet as I just created a
    fresh one for you to look at, but here was my last test in my fake happynet setup. Note, the packet was addressed to Al at 637:1/101, I
    sent it to Al as there was no Al user on my mystic system.

    So is the issue that it isn't routing it?

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From apam@21:1/126.2 to Netsurge on Fri Jan 24 11:20:29 2020
    So is the issue that it isn't routing it?

    Yes

    Andrew

    --- TitanFTN (Windows/x86)
    * Origin: Titan Test BBS (21:1/126.2)
  • From Netsurge@21:4/154 to apam on Thu Jan 23 22:50:16 2020
    Yes

    I take it you have tried routing to multiple FTNs like fsx/fido/scinet across multiple hubs running different tossers and it's only failing with Mystic.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From apam@21:1/126 to Netsurge on Fri Jan 24 14:05:17 2020
    Yes

    I take it you have tried routing to multiple FTNs like
    fsx/fido/scinet across multiple hubs running different tossers and
    it's only failing with Mystic.

    I think so (not sure exactly what you mean). I sent one from a scinet
    point, through happyland to scinet hub to nocturnal and it worked, I
    also sent one from a happynet node to happynet hub (running my fork of crashmail) to nocturnal and it worked.

    It's just when I was using testing using mystic as a happynet hub, and
    also using fsxnet (where paul uses mystic as the hub i connect to).

    The odd thing is, it's only my packets it doesn't route if I go the
    other direction, ie with a packet generated by crashmail, it works fine.
    Logic would say it's something different about my packet, but I just
    can't seem to put my finger on it.

    Andrew

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Netsurge@21:4/154 to apam on Sun Jan 26 00:38:48 2020
    The odd thing is, it's only my packets it doesn't route if I go the
    other direction, ie with a packet generated by crashmail, it works fine. Logic would say it's something different about my packet, but I just
    can't seem to put my finger on it.

    Seems like the issue is with Mystic. If mail netmail is being routed fine through other mailers like HPT of Synchronet's tosser, and none of us can see anything wrong with the packet, then occam's razor it is.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)
  • From g00r00@21:1/163 to Netsurge on Sun Jan 26 13:29:15 2020
    Seems like the issue is with Mystic. If mail netmail is being routed fine through other mailers like HPT of Synchronet's tosser, and none of us
    can see anything wrong with the packet, then occam's razor it is.

    I think the challenge is that its successfully routing messages sourced from those tossers though, just not from Titan.

    Either way I have a copy of a packet so I will dig around. It could just be a routing that isn't configured.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: |08--[|15!|07dreamland BBS bbs.dreamlandbbs.org (21:1/163)
  • From apam@21:1/126 to Netsurge on Mon Jan 27 15:01:50 2020
    The odd thing is, it's only my packets it doesn't route if I
    go the other direction, ie with a packet generated by
    crashmail, it works fine. Logic would say it's something
    different about my packet, but I just can't seem to put my
    finger on it.

    Seems like the issue is with Mystic. If mail netmail is being
    routed fine through other mailers like HPT of Synchronet's tosser,
    and none of us can see anything wrong with the packet, then occam's
    razor it is.

    gOOrOO found the problem, turns out I shouldn't have had colons between
    TOPT, FMPT and INTL kludges. I guess other tossers were more forgiving
    which threw us off a bit.

    Anyway, it's all working now.

    Thanks

    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Avon@21:1/101 to apam on Mon Jan 27 19:22:08 2020
    On 27 Jan 2020 at 03:01p, apam pondered and said...

    gOOrOO found the problem, turns out I shouldn't have had colons between TOPT, FMPT and INTL kludges. I guess other tossers were more forgiving which threw us off a bit.
    Anyway, it's all working now.

    Cool. Good that it was caught with help :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From apam@21:1/126 to Avon on Mon Jan 27 17:06:57 2020
    On 27 Jan 2020 at 03:01p, apam pondered and said...

    gOOrOO found the problem, turns out I shouldn't have had
    colons between TOPT, FMPT and INTL kludges. I guess other
    tossers were more forgiving which threw us off a bit.
    Anyway, it's all working now.

    Cool. Good that it was caught with help :)

    Yeah, that one really had me stumped, I guess I was focusing too much on
    the headers rather than the body. Guess that's why more sets of eyes are
    better :)

    Andrew


    --- MagickaBBS v0.13alpha (Linux/x86_64)
    * Origin: HappyLand - telnet://magickabbs.com:2023/ (21:1/126)
  • From Netsurge@21:4/154 to apam on Mon Jan 27 22:01:02 2020
    gOOrOO found the problem, turns out I shouldn't have had colons between TOPT, FMPT and INTL kludges. I guess other tossers were more forgiving which threw us off a bit.

    Anyway, it's all working now.

    Glad to hear it.

    |15frank |08// |15netsurge
    |07disksh0p|08!|07bbs |08% |07bbs.diskshop.ca |08% |07mystic goodness |11SciNet |03ftn hq |08% |07https://scinet-ftn.org

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: % disksh0p!bbs % bbs.diskshop.ca % SciNet ftn hq % (21:4/154)