From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.54) id 1FTmrt-00023r-KH for garchives@archives.gentoo.org; Wed, 12 Apr 2006 21:27:18 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.6/8.13.5) with SMTP id k3CLQu5w028637; Wed, 12 Apr 2006 21:26:56 GMT Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.238]) by robin.gentoo.org (8.13.6/8.13.5) with ESMTP id k3CLLHl8020509 for ; Wed, 12 Apr 2006 21:21:18 GMT Received: by wproxy.gmail.com with SMTP id i13so1278181wra for ; Wed, 12 Apr 2006 14:21:17 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=d7DPQEvLuyHQpofGMZkwU8e3gDPNy8CJvE2br2ywS5DfgPtdLF1qE6EpEsfy9yXcbRQQMLpyl5qSU46RiSC3v9ys6E5Ef0C6joY3MJZ5B9kpyldSbxhDWtz2Gb14OdLxVVNgCuW+k0XwjpQ9VUrgfOONA4BMR3uswtd7CJMjLPo= Received: by 10.64.204.12 with SMTP id b12mr505994qbg; Wed, 12 Apr 2006 14:21:17 -0700 (PDT) Received: by 10.64.242.13 with HTTP; Wed, 12 Apr 2006 14:21:17 -0700 (PDT) Message-ID: Date: Wed, 12 Apr 2006 14:21:17 -0700 From: "Joshua Schmidlkofer" To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] mirror email servers In-Reply-To: <443C8962.9010307@patrickwatson.org> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Disposition: inline References: <200604112018.52947.uwix@iway.na> <443C8962.9010307@patrickwatson.org> Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by robin.gentoo.org id k3CLLHl8020509 X-Archives-Salt: 5cccfc54-b1d8-4573-8cd0-71833821f0b3 X-Archives-Hash: d0b9d7b3aef705c5754ec60bd3cb5bc7 > That's close to what I use. However, MX entries alone aren't the > solution. You also have to configure the mail servers to forward the > mail on to the final destination once it comes back online. I'm not sure > how to do that myself, and don't really have to time to put much effort > into it since my mail server is only for small scale personal use. I > just use dyndns.org's "Backup MX" service: > http://www.dyndns.com/services/mailhop/backupmx.html. Even if that isn't > a solution for you, it's at least a place to start looking. > Patrick is correct here, if you can, use a third-party service. They will always (sometimes?) have higher maintenance standards than stuff that you do. However, this is _very_ simple with postfix. MX for mydomain.com mydomain.com mail is handled by 10 server1.mydomain.com. mydomain.com mail is handled by 20 server2.mydomain.com. mail server 1: Accepts mail for mydomain.com mail server 2: Postfix, with relay_domains = mydomain.com mydestination = server2.mydomain.com maximal_queue_lifetime = 30d bounce_queue_lifetime = 1d - Maximal queue lifetime affects how long it reties delivery. - Bounce queue lifetime will help alleviate problems with spammers overflowing the bounce queue. -- gentoo-user@gentoo.org mailing list