On 06/18/2014 11:07 AM, Jim Reid wrote:
> On 18 Jun 2014, at 15:45, Michael Orlitzky
> wrote:
>
>> Nitpick: the ".local" TLD is reserved by RFC 6762, ".invalid" may
>> be a better long-term choice.
>
> I'll raise you another nitpick. .invalid is reserved by RFC6761 and
> in the IANA registry of
On 18 Jun 2014, at 15:45, Michael Orlitzky wrote:
> Nitpick: the ".local" TLD is reserved by RFC 6762, ".invalid" may be a
> better long-term choice.
I'll raise you another nitpick. .invalid is reserved by RFC6761 and in the IANA
registry of Special-Use Domain Names, just like .local:
http://w
On 06/17/2014 11:58 PM, Jose Borges Ferreira wrote:
> If you wanto to deliver do 1.2.3.4 and , if fails, then try 8.9.10.11
> then you can create a dns entry with those IP an MX
>
> ex:
> some_entry.local IN MX 10 1.2.3.4
> some_entry.local IN MX 20 8.9.10.11
>
> then setup transport_maps to:
>
On Wed, Jun 18, 2014 at 2:30 AM, Joey J wrote:
> We have 2 gateway servers in multiple locations so that we have redundancy
> and of course corresponding mx records pointing to both.
> This handles if GW1 fails, go to GW2
>
> Now once at a GW the transport map handles the routing of the messages f
On 6/17/2014 8:30 PM, Joey J wrote:
> We have 2 gateway servers in multiple locations so that we have
> redundancy and of course corresponding mx records pointing to both.
> This handles if GW1 fails, go to GW2
>
> Now once at a GW the transport map handles the routing of the
> messages for domain
We have 2 gateway servers in multiple locations so that we have redundancy
and of course corresponding mx records pointing to both.
This handles if GW1 fails, go to GW2
Now once at a GW the transport map handles the routing of the messages for
domain.com as shown:
domain.com smtp
