[email protected] wrote: > We also us Google as a filtering system for are own mail > servers. But only for inbound. Heres how we do it. > > Background: > MX records point to all googles mail server + are mail > servers. But on are mail server have all inbound mail blocked > (port 25 inbound is closed) on the MX ip address. These > server (are mail servers) have 2 ipaddress. On the second IP > on that same server we have open port 25. > > Heres how it all plays out: > All mail coming to [email protected] goes though this. > > [email protected] => [email protected] > (gmail server) => cfrank...@ipaddress (in house server). > > But for all out going mail we still and can do this. > > [email protected] (in house server) => > [email protected] > > > So for us, not only is gmail acting like a big brother > filter, but also as a backup for us so we can take down are > server, but still have mail "flow" > in. This setup allows us to still do are own in house > archiving/monitoring. With alot of flexibility.
But at the same time you've tripled your bandwidth usage: A. Incoming to ASSP(would already be used so won't count this one) B. Outgoing to Google (assuming you mean to Postini) C. Incoming from Google Sounds like an expensive backup solution (not only the bandwidth, but Google's cost), but it's a definite backup solution. We thought about something like that, but the numbers were too high. Kind Regards, Brett ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ Assp-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/assp-user
