Subj : Help request
To   : Mark Lewis
From : Mike Luther
Date : Sun Dec 05 2010 09:48 pm

Aha!

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

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

ml> 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)

You are viewing proxied material from vert.synchro.net. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.