From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.169.74 with SMTP id ac10cs85360vdc; Thu, 17 Mar 2011 16:13:58 -0700 (PDT) Received: by 10.43.58.135 with SMTP id wk7mr452479icb.433.1300403635568; Thu, 17 Mar 2011 16:13:55 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id vt18si6458138icb.111.2011.03.17.16.13.54; Thu, 17 Mar 2011 16:13:54 -0700 (PDT) Received-SPF: pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) client-ip=205.234.109.19; Authentication-Results: mx.google.com; spf=pass (google.com: domain of sup-talk-bounces@rubyforge.org designates 205.234.109.19 as permitted sender) smtp.mail=sup-talk-bounces@rubyforge.org Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 1E7331678163; Thu, 17 Mar 2011 19:13:54 -0400 (EDT) Received: from plecavalier.com (plecavalier.com [64.40.149.83]) by rubyforge.org (Postfix) with ESMTP id A8B8C1858346 for ; Thu, 17 Mar 2011 19:10:46 -0400 (EDT) Received: (qmail 28055 invoked from network); 17 Mar 2011 18:10:46 -0500 Received: from xplr-142-46-160-183.xplornet.com (HELO localhost) (142.46.160.183) by thelittlecloset.ca with (DHE-RSA-AES128-SHA encrypted) SMTP; 17 Mar 2011 18:10:45 -0500 From: Philippe LeCavalier To: sup-talk In-reply-to: <1300392204-sup-5911@black-opal.free-dissociation.com> References: <1300371126-sup-4692@plc.intranet.plecavalier.com> <1300375667-sup-4657@panda> <1300385916-sup-3971@plc.intranet.plecavalier.com> <1300392204-sup-5911@black-opal.free-dissociation.com> Date: Thu, 17 Mar 2011 19:10:44 -0400 Message-Id: <1300403326-sup-4036@plc.intranet.plecavalier.com> User-Agent: Sup/0.12.1 Subject: Re: [sup-talk] background or queue msg sending X-BeenThere: sup-talk@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: User & developer discussion of Sup List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org Excerpts from Kevin Riggle's message of Thu Mar 17 16:16:09 -0400 2011: > Excerpts from Philippe LeCavalier's message of Thu Mar 17 15:15:30 -0400 2011: > > Even if Exim or Postfix might act faster than msmtp(what I'm using now) > > sup is set up in a way that it waits for the process to terminate before > > bringing me to the previous buffer. What I'd like to suggest is that sup > > should immediately bring you to the previous buffer. > > Exim or Postfix will both act as the local message queue for you, unlike > msmtp which blocks while it talks to the upstream remote mail server. > It's not so much Sup's blocking as msmtp's blocking here which is the > problem, IME -- talking to the local MTA is wicked fast, and you can set > your local MTA to use your upstream remote mail server as its smarthost > -- and there's no reason to add a message queue to Sup if your MTA can > handle it. > > Given Exim's recent security troubles I'd recommend Postfix. > > - Kevin > -- > Kevin Riggle (kevinr@free-dissociation.com) > http://free-dissociation.com > _______________________________________________ > sup-talk mailing list > sup-talk@rubyforge.org > http://rubyforge.org/mailman/listinfo/sup-talk > Thanks Kevin. I get what everyone is saying now. I just needed explained as you did. Makes total sense to me now. I'm going to give preference to Sascha's suggestion first. But if I'm unsuccessful I'll definitely give a local -full- MTA a try. -- Thanks, Phil _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk