> Everybody in the company has an email address of > [EMAIL PROTECTED] and their mail is forwarded to > [EMAIL PROTECTED] We would like any mail that is sent from our system > to the abc.com be resolved locally before it is sent.
Much clearer, though not easy. You want to have the abc.com domain be partitioned across two servers with automatic address rewriting. IMail's peering function will allow this, if you can get the parent company to (a) change their SMTP banner, if they're not running IMail; and (b) accept the VRFY command (which is doubtful). You should realize that what you're describing is beyond the original intent of the SMTP protocol. If a domain is local to a host, all delivery is expected to be local, barring hand-managed forwarding to remote addresses. Peering lets you have some "wildcard" forwarding, which is very cool, but it really is meant for non-MX peers all running IMail. Another option is simply to have users use the @def.com addressing from the outset: unless they're forced to use only a centrally managed address book at the parent, why not set up the IMail LDAP service as their local address book and tell them that they'll get much faster intra-site delivery if they use that method? -Sandy To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
