You might be able to get away with running a local DNS server on your mailserver (djbdns's tindydns / dnscache would be easy). Only define that domain in DNS; and don't point to any root servers -- effectively, DNS sandbox it. You may want to add firewall rules to prevent IP-addressed based recipients, if your users get clever. Then, in your corporate DNS, point mx to your mail server like normal.
best, Jeff
On Nov 21, 2003, at 11:44 AM, Gerardo Gregory wrote:
Been tasked with setting up a virtualdomain that is private for internal corporate communication.
Currently I have Courier-MTA, maildrop for local delivery, PAM auth, and some virtul domains already setup using userdb.
The domain I am asked to setup needs to only be able to send / receive mail from within that domain. How do I create this type of restrictions?
Is it even do-able?
TIA,
Gerardo A. Gregory
------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
