• Help request

    From Mike Luther@1:117/100 to All on Fri Dec 3 21:19:32 2010
    Can someone help me configure FE 1.46 properly for NETMAIL here? How is it set up as to the configuration and the GROUP mode so that it is only 'seen by' the Net 117 HUB, yet properly punches out any NETMAIL other than to the local nodes in Net 117 to the Regional HUB here for us in R19?

    Does NETMAIL really have to be set up in only its' own GROUP that has only a 'seen by' of the 117/100 HUB here?

    Thanks!

    Mike Luther 1:117/100 and NC of Net 117 in R19 here.



    ---
    * Origin: BV HUB CLL(979)696-3600 (1:117/100)
  • From mark lewis@1:3634/12 to Mike Luther on Sun Dec 5 16:39:19 2010

    MikeL> Can someone help me configure FE 1.46 properly for NETMAIL here?
    MikeL> How is it set up as to the configuration and the GROUP mode so that
    MikeL> it is only 'seen by' the Net 117 HUB, yet properly punches out any
    MikeL> NETMAIL other than to the local nodes in Net 117 to the Regional
    MikeL> HUB here for us in R19?

    MikeL> Does NETMAIL really have to be set up in only its' own GROUP that
    MikeL> has only a 'seen by' of the 117/100 HUB here?

    i'm not sure i'm understanding your problem, mike... the default general netmail area (that is managed by FE and a dynamic mailer like FD) doesn't have a group assignment...

    can you explain a bit more, please?

    )\/(ark
    member, FastEcho Beta Team


    * Origin: (1:3634/12)
  • From Mike Luther@1:117/3001 to Mark Lewis on Sun Dec 5 21:48:38 2010
    Aha!

    MikeL> Does NETMAIL really have to be set up in only its' own GROUP that
    MikeL> has only a 'seen by' of the 117/100 HUB here?

    i'm not sure i'm understanding your problem, mike...
    the default general netmail area (that is managed by
    FE and a dynamic mailer like FD) doesn't have a group
    assignment...

    can you explain a bit more, please?

    I think you may have hit the nail on the head. As I got this whole monstor of 117/100 years ago whne it actually was left on the front porch (!) it had a "Netmail" enbtry in the FE area lists! That group in which it still 'is' shows
    that you at 396/345 are shown to 'see' it. Which I now think I understand is how this junk NetMail stuff may be showing up to you on the FTP server connection I poll you from. Yes,the traffic goes into a 'hold' que as is 'normal' for your traffic outbound. But you shouldn't show up as 'seen by' for
    this as an 'echo' area at all as far as I can understand this.

    This defined NETMAIL area is defined in the 'ADMINISTRATIVE' area here,and it is a 'standard' Fido area on 1:117/100 here. 1:117/100 does have a default NETMAIL editor for the system and as well the MAX BBS application for it does also define tne NETMAIL area and SQUISH handles it properly for NETMAIL as well
    as the IE operation. I can read/receive and originate NETMAIL in either tool an things work the same.

    Thus should I simply remove this strange 'NETMAIL' area in the FE area and see what happens?

    Thanks!

    Mike@117/3001 (Max in this case)

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Roger Nelson@1:3828/7 to Mike Luther on Mon Dec 6 07:18:05 2010
    On Sun Dec-05-2010 21:48, Mike Luther (1:117/3001) wrote to Mark Lewis:

    Aha!

    MikeL> Does NETMAIL really have to be set up in only its' own
    GROUP that
    MikeL> has only a 'seen by' of the 117/100 HUB here?

    i'm not sure i'm understanding your problem, mike...
    the default general netmail area (that is managed by
    FE and a dynamic mailer like FD) doesn't have a group
    assignment...

    can you explain a bit more, please?

    I think you may have hit the nail on the head. As I got this whole monstor of 117/100 years ago whne it actually was left on the front
    porch (!) it had a "Netmail" enbtry in the FE area lists! That
    group in which it still 'is' shows that you at 396/345 are shown to
    'see' it. Which I now think I understand is how this junk NetMail
    stuff may be showing up to you on the FTP server connection I poll
    you from. Yes,the traffic goes into a 'hold' que as is 'normal'
    for your traffic outbound. But you shouldn't show up as 'seen by'
    for this as an 'echo' area at all as far as I can understand this.

    This defined NETMAIL area is defined in the 'ADMINISTRATIVE' area
    here,and it is a 'standard' Fido area on 1:117/100 here. 1:117/100
    does have a default NETMAIL editor for the system and as well the
    MAX BBS application for it does also define tne NETMAIL area and
    SQUISH handles it properly for NETMAIL as well as the IE operation.
    I can read/receive and originate NETMAIL in either tool an things
    work the same.

    Thus should I simply remove this strange 'NETMAIL' area in the FE
    area and see what happens?

    Thanks!

    mark should not show up at all in net 396! He is 1:3634/12.


    Regards,

    Roger
    --- timEd/386 1.10.y2k+
    * Origin: NCS BBS - Houma, LA - (1:3828/7)
  • From Mike Luther@1:117/3001 to Roger Nelson on Mon Dec 6 11:51:08 2010
    Thanks Roger ..

    mark should not show up at all in net 396! He is 1:3634/12.

    It's Marc Lewis who I have worked for years with using the address 1:396/45 here. There has always been an interesting what-if between Marc Lewis and Mark
    Lewis, grin!


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Roger Nelson@1:3828/7 to Mike Luther on Mon Dec 6 17:06:36 2010
    On Mon Dec-06-2010 11:51, Mike Luther (1:117/3001) wrote to Roger Nelson:

    Thanks Roger ..

    You're welcome.

    mark should not show up at all in net 396! He is 1:3634/12.

    It's Marc Lewis who I have worked for years with using the address 1:396/45 here. There has always been an interesting what-if
    between Marc Lewis and Mark Lewis, grin!

    I sometimes got confused until I noticed mark doesn't use the Shift key very much. (-: It's been a running joke between he and I and I'm sure he's beyond tired of it by now, so this will serve as my last mention of it.


    Regards,

    Roger
    --- timEd/386 1.10.y2k+
    * Origin: NCS BBS - Houma, LA - (1:3828/7)
  • From Robert Wolfe@1:261/20 to Mike Luther on Mon Dec 6 19:29:00 2010
    Mike Luther wrote to Roger Nelson <=-

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)

    I'm curious -- is this available via telnet and if so, should I put
    it in my ZOC/2 dialing directory? ;)

    ... Reality is for people who can't cope with their drugs.
    ___ MultiMail/OS/2 v0.49

    --- Maximus/2 3.01
    * Origin: Omicron Theta * Grand Island, NY * robertwolfe.org (1:261/20)
  • From mark lewis@1:3634/12 to Mike Luther on Mon Dec 6 23:02:02 2010

    MikeL> Does NETMAIL really have to be set up in only its' own
    MikeL> GROUP that has only a 'seen by' of the 117/100 HUB
    MikeL> here?

    i'm not sure i'm understanding your problem, mike...
    the default general netmail area (that is managed by
    FE and a dynamic mailer like FD) doesn't have a group
    assignment...

    can you explain a bit more, please?

    MikeL> I think you may have hit the nail on the head. As I
    MikeL> got this whole monstor of 117/100 years ago whne it
    MikeL> actually was left on the front porch (!) it had a
    MikeL> "Netmail" enbtry in the FE area lists! That

    that sounds like a secondary netmail area where netmail is imported into the BBS for users to be able to access it...

    group in which it still 'is' shows that you at 396/345 are shown to

    ahhh... you're confusing me (marK) with the other one (marC) ;)

    MikeL> 'see' it. Which I now think I understand is how
    MikeL> this junk NetMail stuff may be showing up to you
    MikeL> on the FTP server connection I poll you from.
    MikeL> Yes,the traffic goes into a 'hold' que as is
    MikeL> 'normal' for your traffic outbound. But you
    MikeL> shouldn't show up as 'seen by' for this as an
    MikeL> 'echo' area at all as far as I can understand
    MikeL> this.

    yeah, i'm not sure without seeing more details... if it is really a NETmail area, there should be NO seen-by lines... VIA lines, yes, but not seen-bys...


    )\/(ark
    member, FastEcho Beta Team


    * Origin: (1:3634/12)
  • From Mike Luther@1:117/3001 to Robert Wolfe on Mon Dec 6 22:19:32 2010
    Hi Robert..

    Mike Luther wrote to Roger Nelson <=-

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)

    I'm curious -- is this available via telnet and if so, should I put
    it in my ZOC/2 dialing directory? ;)

    You know what you get when you try to cross the Safari on a drunk Rhino? Sfharashino you'll get there, chuckle. You'll have to, as far as I know, use SIO's VMODEM to accomplish things like this. But I use ZOC2 together with VMODEM to connect to a lot of sites in my private wanderings I maintain over OS/2.

    The 1:117/100 HUB which I also maintain here as NC for Net 117 does not have Telnet connections however. It's the system I'm working with that has IM and FASTECHO and so on on it for which I was posting help requests.


    Sleep well; OS/2's still awake! ;)

    Mike @ 1:117/3001

    --- Maximus/2 3.01
    * Origin: Ziplog Public Port (1:117/3001)
  • From Roy Witt@1:387/22 to Mike Luther on Wed Dec 8 17:06:48 2010

    06 Dec 10 11:51, Mike Luther wrote to Roger Nelson:

    Thanks Roger ..

    mark should not show up at all in net 396! He is 1:3634/12.

    It's Marc Lewis who I have worked for years with using the address 1:396/45 here. There has always been an interesting what-if between
    Marc Lewis and Mark Lewis, grin!

    The Mark (mark lewis) you replied to is listed as 1:3634/12, not Marc as
    in 1:396/0...

    Be aware that FE writes a file for outbound netmail, i.e. for FD purposes.

    There can be only one NETMAIL area setup in FE, AFAIK.

    R\%/itt

    "Peltier was responsible for the close range execution of FBI agents..."
    --- Twit(t) Filter v2.1 (C) 2000-10
    * Origin: SATX Alamo Area Net * South * Texas, USA * (1:387/22)