They really wanted their firewall. . .

Really, REALLY. . . .

But now that I've put it in, they really really miss being able to hit
our pop server from their personal internet providers.

Can anyone recommend a strategy for working around that situation?

Ideas I've had so far have included:

-Re-piping mail to a temporary cache somewhere in the DMZ (sounds
impractical and bass-ackwards);

-Re-locating our pop server to the DMZ (EEEEK! Especially since it's
still (for now) running on an NT box);

-Running some sort of proxy on the firewall (a prospect which, among
other details, doesn't particularly tickle my lazy bone);

-Trying to trick ipautofw (or something similar) into allowing some form
of limited inbound communication for picking up mail (I have no idea if
this option is fundamentally different from the proxy option above, but
it seems somehow more 'general').

. . . but I have no idea what the real implications (ie, security vs.
convenience) would be for any of the above, with the obvious exception
of option number 2.

Can anyone advise me on this?  It is a convenience issue and (to my way
of thinking at least) secondary to the goals of keeping our net
reasonably secure with a minimum of configuration complication.  We'd
also like to avoid duplication of mail, by which I mean that when mail
is picked up (for example) from within the protected net, it shouldn't
re-appear later when the user connects from home via their ISP.

ALL musings welcome.

Thanks,
m


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
http://www.redhat.com/RedHat-FAQ /RedHat-Errata /RedHat-Tips /mailing-lists
         To unsubscribe: mail [EMAIL PROTECTED] with 
                       "unsubscribe" as the Subject.

Reply via email to