• Magimail multiple AKAs

    From vk3jed@21:1/50 to All on Thu Dec 13 14:48:38 2018
    OK, silly question time: How do I structure magimail.prefs to handle
    multiple AKAs. I want to configure both FSX and VKRadio in Magimail, but
    the examples in the docs don't make it clear how the config file is laid
    out for multiple AKAs.

    Does anyone have an example of how their AKAs and AKA specific
    information (e.g. message areas) are laid out?

    --- MagickaBBS v0.12alpha (Linux/i686)
    + Origin: Bush Track BBS (@6)
    * Origin: FTN-MNET Gateway (21:1/50)
  • From apam@21:1/125 to vk3jed on Thu Dec 13 14:44:21 2018
    OK, silly question time: How do I structure magimail.prefs to handle multiple AKAs. I want to configure both FSX and VKRadio in Magimail,
    but the examples in the docs don't make it clear how the config file
    is laid out for multiple AKAs.

    You would have:

    AKA 21:1/xxx
    DOMAIN fsxnet

    AKA xxx:xxx/xxx
    DOMAIN vkradio

    (change the x's to the right numbers)

    You would also need
    multiple node lines (one for each uplink, I give each one a different
    default group) multiple route lines (so netmail goes to the right uplink)

    Does anyone have an example of how their AKAs and AKA specific
    information (e.g. message areas) are laid out?

    I can send you my magimail.prefs if you like

    Andrew

    --- MagickaBBS v0.12alpha (Linux/x86_64)
    * Origin: The Fat Sandwich - sandwich.hopto.org:2023 (21:1/125)
  • From Tiny@21:1/130.4 to vk3jed on Thu Dec 13 19:08:06 2018
    vk3jed wrote to All <=-

    Does anyone have an example of how their AKAs and AKA specific
    information (e.g. message areas) are laid out?

    Here's how I do it:

    GROUPNAME A "fsxNet"
    CHANGE * 21:*/*.* Normal
    PACKER "ZIP" "zip -j %a %f" "unzip -j %a" "PK"
    GROUPNAME B "DBNet"
    CHANGE * 201:*/*.* Normal
    ***etc****

    AKA 21:1/130.4
    DOMAIN fsxnet

    AKA 201:1000/2.4
    DOMAIN dbnet

    AKA 618:500/32.4
    DOMAIN micronet

    ***ETC***

    Shawn
    ... An easily understood, workable falsehood is more useful than the truth
    --- Blue Wave/386
    * Origin: A Tiny slice o pi (21:1/130.4)
  • From Vk3jed@21:1/109 to apam on Fri Dec 14 09:27:00 2018
    On 12-13-18 14:44, apam wrote to vk3jed <=-

    You would also need
    multiple node lines (one for each uplink, I give each one a different default group) multiple route lines (so netmail goes to the right
    uplink)

    Yeah I figured that mych by myself, but it was the overall order and context that wasn't shown.

    Does anyone have an example of how their AKAs and AKA specific
    information (e.g. message areas) are laid out?

    I can send you my magimail.prefs if you like

    Thanks, your config clarified a lot of things. Hopefully get a chance to tweak mine later today.


    ... Mental compatability not covered by warranty.
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)
  • From Vk3jed@21:1/109 to Tiny on Fri Dec 14 09:29:00 2018
    On 12-13-18 19:08, Tiny wrote to vk3jed <=-

    vk3jed wrote to All <=-

    Does anyone have an example of how their AKAs and AKA specific
    information (e.g. message areas) are laid out?

    Here's how I do it:

    That didn't actually answer my question, because it was more the relationship between the AKA configuration and the message areas for each AKA. I now have apam's config file, so it's all clear. :)


    ... Accuracy is our watchword -- we NEVER make misteaks!
    === MultiMail/Win v0.51
    --- SBBSecho 3.03-Linux
    * Origin: Freeway BBS Bendigo,Australia freeway.apana.org.au (21:1/109)