That the third MX record is not on the primary domain, but a sub-domain; this way no mail goes to it without it being [email protected] I tell Google:
take all mail coming in for [email protected] and direct it to [email protected] You have your "Control" in Google, which determines mass delivery to other systems. -Will On Thu, May 14, 2009 at 3:42 PM, Daniel C. <[email protected]> wrote: > On Thu, May 14, 2009 at 3:33 PM, William Attwood <[email protected]> > wrote: > > What will happen is the lower the number, the higher the priority; if > mail. > > isn't responding, it will try mail2, if that doesn't respond, it'll try > > mail3 - if in the end none respond, it will wait a certain amount of time > > and try again; eventually, if none work, it will bounce it back to you > > undeliverable. > > That much I'm familiar with, yeah. > > > To get around the possibility of random e-mail delivery, I actually went > > this route: > > > > This is from my bind zone file: > > IN MX 1 aspmx.l.google.com. > > IN MX 5 alt1.aspmx.l.google.com. > > IN MX 5 alt2.aspmx.l.google.com. > > automail.domain.com. IN MX 1 automail.domain.com. > > automail.commissionriver.com. IN A XXX.XXX.XXX.XXX > > What part of the last MX record prevents it from receiving random mail? > > Dan > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > -- Warm regards, William Attwood Idea Extraordinaire [email protected] Don Marquis <http://www.brainyquote.com/quotes/authors/d/don_marquis.html> - "Procrastination is the art of keeping up with yesterday." /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
