Ron DuFresne wrote:
>
> On Wed, 9 Aug 2000, mouss wrote:
>
> > I think you're missing something here.
> > The situation is as follows (original sender correct me if I'm wrong):
> >
> > The guy has internal users accessing (external) web-based mail servers
> > such as yahoo ([advertisement break:-] I only cite this one cos' they're
> > running BSD).
check out: http://www.bsdtoday.com/2000/August/Newswire244.html
for a laugh.
> > So the connection goes between "the two" networks, and thus crosses his
> > firewall.
> > Since this is web-based mail, and not normal-mail-based-mail, smtp filtering
> > has no effect. The question was thus whether he can allow his users to
> > surf the web, but stops them from sending mail attachments.
>
> That is just what I thought was being discussed. So, the real cure here
> is to *not* allow his employees to pop/imap out from his site to their
> external/private accounts, then he has no worries about trying to be anal
> about sub-processes not under his real domain.
>
> Either that, or stand over each employee that's got an external account
> and poke em with sharp sticks as they attempt to do natural things that
> they've been allowed access to do, yes?
>
> Thanks,
>
> Ron DuFresne
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
erm - they're not trying to do pop3/imap, the issue is: how to block users from
attaching sh@% to messages that they compose and send using *HTTP* and hotmail, yahoo,
etc...etc...
--
Marko.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
