From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 09E58138350 for ; Mon, 6 Apr 2020 12:41:32 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id D1AA6E0A02; Mon, 6 Apr 2020 12:41:26 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 7AD1EE09EF for ; Mon, 6 Apr 2020 12:41:26 +0000 (UTC) Received: from [192.168.1.100] (c-98-218-46-55.hsd1.md.comcast.net [98.218.46.55]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mjo) by smtp.gentoo.org (Postfix) with ESMTPSA id 5DCCE34F01E for ; Mon, 6 Apr 2020 12:41:25 +0000 (UTC) Subject: Re: [gentoo-user] Alternate Incoming Mail Server To: gentoo-user@lists.gentoo.org References: <20200406123504.fkcuaiiahsemympv@ad-gentoo-main> From: Michael Orlitzky Message-ID: Date: Mon, 6 Apr 2020 08:41:20 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 In-Reply-To: <20200406123504.fkcuaiiahsemympv@ad-gentoo-main> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit X-Archives-Salt: e722c9c7-a6ad-4983-b4b8-e480315becbe X-Archives-Hash: 9511ca3c868e2826e7ec391ce2bb679e On 4/6/20 8:35 AM, Ashley Dixon wrote: > > What do you think; is this at all possible ? Has anyone here done anything like > this before ? > There's no need, the SMTP specification says that senders must retry every message, and should continue retrying for at least 4 or 5 days: https://tools.ietf.org/html/rfc5321#section-4.5.4 Your incoming mail will arrive whenever the server comes back up. We regularly reboot our MX in the middle of the day and no one notices. Whatever solution you'd come up with to solve this problem will cause more downtime than that =)