• usenet mess

    From Ratz@21:2/114 to All on Tuesday, August 27, 2019 14:40:19
    I have this happening when a new usenet msg arrives from the feed from
    21:1/10 so I have been jumping into message editor daily and sorting them out.

    Has anyone figured a way to sort them, using groups maybe or a batch
    file. The mutil incoming.ini uses my node number to sort and does not differentiate between fsxnet@21:1/100 and usenet@21:1/10.

    -- FSXNet --------------------------------------------------------------
    NEW LINUX.DEBIAN.L10N.TURKISH 2 2 0 27 Aug 2019
    NEW NEWS.MISC 46 46 0 27 Aug 2019
    NEW REC.GAMES.PBM 2 2 0 27 Aug 2019
    NEW SCI.ENGR.CIVIL 2 2 0 27 Aug 2019
    NEW SCI.SPACE.STATION 1 1 0 27 Aug 2019
    NEW FXN: BBS Support/Dev 342 2 0 26 Aug 2019
    NEW FXN: Chat, Testing & More.. 5,373 81 1 27 Aug 2019
    FXN: ENiGMA 1/2 BBS Support/Dev 76 0 0 12 Aug 2019
    FXN: Magika BBS Support/Dev 362 0 0 26 Aug 2019

    help!


    ---
    |04R|12a|14t|15z |07s|08ysop|01Å|07f|08ree|07s|08ide.|07b|08bs.|07i|08o

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Freeside BBS - freeside.bbs.io (21:2/114)
  • From Bucko@21:4/131 to Ratz on Tuesday, August 27, 2019 19:45:41
    On 27 Aug 2019, Ratz said the following...

    I have this happening when a new usenet msg arrives from the feed from 21:1/10 so I have been jumping into message editor daily and sorting
    them out.

    Has anyone figured a way to sort them, using groups maybe or a batch
    file. The mutil incoming.ini uses my node number to sort and does not differentiate between fsxnet@21:1/100 and usenet@21:1/10.

    -- FSXNet --------------------------------------------------------------
    NEW LINUX.DEBIAN.L10N.TURKISH 2 2 0 27 Aug 2019 NEW NEWS.MISC 46 46 0 27
    Aug 2019 NEW REC.GAMES.PBM 2 2 0

    Why not just create a new Group. Then when you assign access just use the new group number at the end for the UseNet.. Or am I missing something?!?!?

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: The Wrong Number Family Of BBS' - Wrong Number ][ (21:4/131)
  • From Black Panther@21:1/186 to Ratz on Tuesday, August 27, 2019 18:14:48
    On 27 Aug 2019, Ratz said the following...

    Has anyone figured a way to sort them, using groups maybe or a batch
    file. The mutil incoming.ini uses my node number to sort and does not differentiate between fsxnet@21:1/100 and usenet@21:1/10.

    What I do here, is set each one up as their own group. fsxNet vs usenet.
    Also, when I have them created in Mystic, I'll also add something to the
    first part of the description to indicate the network. Such as:

    fsx General Chat
    fsx Mystic Echo
    u alt.bbs
    u alt.bbs.mystic

    That way, I can sort the list, and they are grouped together and easier to find.


    ---

    |03B|09lack |03P|09anther|03(|09RCS|03)|07

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Avon@21:1/101 to Ratz on Wednesday, August 28, 2019 12:54:28
    On 27 Aug 2019 at 02:40p, Ratz pondered and said...

    I have this happening when a new usenet msg arrives from the feed from 21:1/10 so I have been jumping into message editor daily and sorting
    them out.

    Has anyone figured a way to sort them, using groups maybe or a batch
    file. The mutil incoming.ini uses my node number to sort and does not

    Using groups is the way to go.

    Usenet echos will be sent to your fsxNet address so will auto create using whatever settings you have for the creation of new echomail bases.

    Then tag the usenet bases and use global editor to apply a new ACS group
    code to the list/read/post etc. settings for each base.

    At Agency this works well for me, and reading the replies of others to your question it seems to work well for them too :)

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Agency BBS | Dunedin, New Zealand | agency.bbs.nz (21:1/101)
  • From Ratz@21:2/114 to Black Panther on Tuesday, August 27, 2019 20:55:32
    What I do here, is set each one up as their own group. fsxNet vs usenet. Also, when I have them created in Mystic, I'll also add something to the first part of the description to indicate the network. Such as:

    that is what I do now if I am understanding you right. I have this
    setup in mail_import.ini for this address:
    ----------------------------------
    ;fsxNet - defaults
    21:2/114_acs_list = s10g2
    21:2/114_acs_read = s20g2
    21:2/114_acs_post = s20g2
    21:2/114_acs_news = s20g2
    21:2/114_acs_sysop = s255g2
    21:2/114_use_realname = 0

    this will catch the usenet messages as well since they are sent to this node address so i have to change the group manually the first time (to g9 in my case).

    So the NEXT usenet message to this echo is sorted to group 9 and all is
    good but any new messages to say ALT.EXAMPLE.WHATEVER will show up in FSX's group 2. So I have to fix that echo.

    Is this how you are set up? it seems there should be a simple/automated way
    to do it and I am just being dense and not seeing it. =]


    ---
    |04R|12a|14t|15z |07s|08ysop|01Å|07f|08ree|07s|08ide.|07b|08bs.|07i|08o

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Freeside BBS - freeside.bbs.io (21:2/114)
  • From Black Panther@21:1/186 to Ratz on Tuesday, August 27, 2019 19:28:24
    On 27 Aug 2019, Ratz said the following...

    ;fsxNet - defaults
    21:2/114_acs_list = s10g2
    21:2/114_acs_read = s20g2
    21:2/114_acs_post = s20g2
    21:2/114_acs_news = s20g2
    21:2/114_acs_sysop = s255g2
    21:2/114_use_realname = 0

    this will catch the usenet messages as well since they are sent to this node address so i have to change the group manually the first time (to
    g9 in my case).

    What I did, while I was using mutil, is have it set to put them into my
    usenet group. I was adding more usenet echos than Avon was adding echos to fsxNet.

    So, my defaults, using your example, would be set to g9. This would put anything new coming to your 21:2/114 address into g9, which should be your usenet group.

    If new echos are added into fsxNet, you would have to manually change them to g2. There are just a lot fewer of those added. :)

    So the NEXT usenet message to this echo is sorted to group 9 and all is good but any new messages to say ALT.EXAMPLE.WHATEVER will show up in FSX's group 2. So I have to fix that echo.

    The messages themselves would just be put into the message base with the
    proper tag. So whatever settings you have for the base, would apply to all
    the messages within it.

    Is this how you are set up? it seems there should be a simple/automated way to do it and I am just being dense and not seeing it. =]

    It's really not too bad once you get your head wrapped around the way it
    works. :)

    I hope that made sense...


    ---

    |03B|09lack |03P|09anther|03(|09RCS|03)|07

    --- Mystic BBS v1.12 A43 2019/03/02 (Linux/64)
    * Origin: Castle Rock BBS - bbs.castlerockbbs.com (21:1/186)
  • From Ratz@21:2/114 to Avon on Tuesday, August 27, 2019 21:34:15
    hiya Avon

    Thanks for the reply it seems I am already doing what everyone else does, I
    was just looking for something less hands on.

    Is there an areafix option to freeze the echos I am subscribed to now and ignore any new ones that are added on your end?


    ---
    |04R|12a|14t|15z |07s|08ysop|01Å|07f|08ree|07s|08ide.|07b|08bs.|07i|08o

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Freeside BBS - freeside.bbs.io (21:2/114)
  • From Ratz@21:2/114 to Black Panther on Tuesday, August 27, 2019 21:40:05
    What I did, while I was using mutil, is have it set to put them into my usenet group. I was adding more usenet echos than Avon was adding echos
    to fsxNet.

    Hot damn! I KNEW i was missing something simple. This will work just fine, I think there has been maybe one new echo for fsx this year so perfect.

    Thanks sir!


    ---
    |04R|12a|14t|15z |07s|08ysop|01Å|07f|08ree|07s|08ide.|07b|08bs.|07i|08o

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Freeside BBS - freeside.bbs.io (21:2/114)
  • From Ratz@21:2/114 to Bucko on Tuesday, August 27, 2019 22:08:16
    Why not just create a new Group. Then when you assign access just use
    the new group number at the end for the UseNet.. Or am I missing something?!?!?

    Hi Bucko,

    No you aren't I just didn't explain myself very well i guess. =]

    I think I have a fix now though, thanks. I didn't realize when I had Avon
    set me up with usenet that there would be so much of it.

    --- Mystic BBS v1.12 A43 2019/03/03 (Windows/32)
    * Origin: Freeside BBS - freeside.bbs.io (21:2/114)