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).
> 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
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
"Cutting the space budget really restores my faith in humanity. It
eliminates dreams, goals, and ideals and lets us get straight to the
business of hate, debauchery, and self-annihilation." -- Johnny Hart
***testing, only testing, and damn good at it too!***
OK, so you're a Ph.D. Just don't touch anything.
-
[To unsubscribe, send mail to [EMAIL PROTECTED] with
"unsubscribe firewalls" in the body of the message.]
