> The Raptor tech we talked with said one has to use the
> filters to prevent listening ports from being reached
> on untrusted interfaces.
I believe I've found the info required to fix the problem at my
firewall. http://www.raptor.com/cs/FAQ/entv5basictrafficmethods.html is a
description of the different ways that Raptor can pass traffic. The summary
of the fix is Raptor "local tunnels" which are packet filtering. It'll have
to wait until I get back from vacation, but once that's in place things
should be back to normal.
But before I go, in response to Racer X:
>> the more i think about this, the more i think that
>> fallback MX records aren't really necessary anymore.
There are several reasons I think they are still useful:
1) Redundancy. All machines die at some time or other. I'd rather
not have the added pressure of knowing that mail will start bouncing if it
isn't fixed in X amount of time while I'm trying to fix it.
2) Maintenance. You can take your mail server down for maintenance
and not worry about where the mail sits in the meantime - I'd rather it sit
and wait on my server than on someone elses!
3) Upgrades. You can test upgrades on a fallback MX before moving
them on up.
On that note, I'm leaving for the caribbean. Have a good week, all!
--
gowen -- Greg Owen -- [EMAIL PROTECTED]
