I took the liberty of re-reading your post and have a few questions.  At
first glance, it looks as though you have a routing issue, not something
specifically related to email.  Forwarding should be to an IP address,
independent of physical hardware.  I don't think it should matter
whether you put all you IP addresses on one port (Ethernet lines) or
multiple ports.  Unless these ports are physically plugged into
different subnets in which case you will need to route between the

You reference Ethernet lines as hosting domains.  I am assuming that you
have assigned different IP interfaces (addresses) to these interfaces.
When you moved to ETHLIN01, did you just move the IP
interface from ETHLIN03 to ETHLIN01?  Can you define what you did

Are both physical ports connected to the same hub/switch?

What are the IP addresses for the various domains?

Can you define what you did in terms of IP definitions?

Andy Nolen-Parkhouse

Kyle's original post follows:

We have implemented internet email forwarding as described from the
following link:

On ETHLIN01 interface we are hosting and
while on ETHLIN03 we host  Currently, the forwarding
for the domains hosted on ETHLIN01 but not ETHLIN03.  I have moved to ETHLIN01 and the forwarding works, but I would like
add more domains to ETHLIN03 and use this functionality. Has anyone ran
this or something similar before? Any ideas on where to point me?


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 by and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.