Great! It works. /etc/hosts is no solution due to the fact that MX will first have a look in DNS. But initiated from local that is a really good hint but it feels a little bit dirty :-)
I have done it with shorewall and it is temporary a good solution. After all I will install a separated DMZ NIC to be sure with everything. Again thousand thanks for answering so fast. Cheers Michael -----Ursprüngliche Nachricht----- Von: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Im Auftrag von Tom Eastep Gesendet: Donnerstag, 28. Februar 2008 02:24 An: Shorewall Users Betreff: Re: [Shorewall-users] from LAN through local eth1 to public eth0 and back to LAN through local eth1 Tom Eastep wrote: > Michael Weickel - iQom Business wrote: > >> >> Is there anybody out there who can help with that issue? >> > > This is Shorewall FAQ 2 -- only on port 25 rather than port 80. That having been said, a simple solution would be to add an entry in /etc/hosts on each MX mapping the other MX name to it's LOCAL IP address. -Tom -- Tom Eastep \ Nothing is foolproof to a sufficiently talented fool Shoreline, \ http://shorewall.net Washington USA \ [EMAIL PROTECTED] PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Shorewall-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/shorewall-users
