From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.52.169.74 with SMTP id ac10cs84560vdc; Thu, 17 Mar 2011 15:43:14 -0700 (PDT) Received: by 10.43.50.199 with SMTP id vf7mr596733icb.125.1300401793944; Thu, 17 Mar 2011 15:43:13 -0700 (PDT) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id f13si6402206ibb.9.2011.03.17.15.43.13; Thu, 17 Mar 2011 15:43:13 -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; dkim=neutral (body hash did not verify) header.i=@gmail.com Received: from rubyforge.org (rubyforge.org [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 816F73C8041; Thu, 17 Mar 2011 18:43:13 -0400 (EDT) Received: from mail-bw0-f50.google.com (mail-bw0-f50.google.com [209.85.214.50]) by rubyforge.org (Postfix) with ESMTP id 5E5AE185836B for ; Thu, 17 Mar 2011 18:42:56 -0400 (EDT) Received: by bwz2 with SMTP id 2so3502017bwz.23 for ; Thu, 17 Mar 2011 15:42:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=KCzZcyI7jGLlsFO8FJNbBgA8UegDD3m/nfqV+EBuRAU=; b=JscRHT0vMj/tiBVVQX0tTnRwUnJbbgOCEBBz+mHtR8J8Z0ZXxhhnqnSHFkikMWhbzc oU10PpqlbWPDk7A00HnJaysC+iUR/lk7eyzWrnV1vqsnian4IDINUCQLkQK9MDI49Pww b3sBMwZA2m9V9KK3MzjKlUqsSGBd58hm7Zofg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=kW5FojI9xKTJ8W7PbK/P8Tmnmkyk40x5/Un2eQzToUZU8PikTbp7QfiGdYoTUNz0ei P1+OjdX/nl+UbKVEzEXdotv+tzSTTkBdMv8AJc5xTK9I2WA/gtfWSYpAeIwt4IXt3tlW V/qWjwsELlB1T1wyKH3NGOc7k3w28RclQeZTw= Received: by 10.204.172.129 with SMTP id l1mr295370bkz.99.1300401776147; Thu, 17 Mar 2011 15:42:56 -0700 (PDT) MIME-Version: 1.0 Received: by 10.204.59.81 with HTTP; Thu, 17 Mar 2011 15:42:36 -0700 (PDT) In-Reply-To: <1300371126-sup-4692@plc.intranet.plecavalier.com> References: <1300371126-sup-4692@plc.intranet.plecavalier.com> From: Sean Escriva Date: Thu, 17 Mar 2011 15:42:36 -0700 Message-ID: To: Philippe LeCavalier Cc: sup-talk 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org On Thu, Mar 17, 2011 at 7:17 AM, Philippe LeCavalier wrote: > > Hi All. > > Does anyone know of a way to background or perhaps queue > sending mail. Sup has me so efficient I've even lost the patience to > wait for msgs to be sent. I really want to hit 'y' and move on. > > Any thoughts, experiences? My first though was manipulating the buffers > so that the previous buffer would get called back before the mail gets > confirmed as sent and then the confirmation itself could still be > displayed in the notification area. It sounds like you're refering to how msmtp blocks while talking to your smtp server. As others have mentioned exim or postfix will do the job. My preference is postifx. If you are already using msmtp, perhaps the msmtpq script would be preferable for you, there's a readme that details usage: http://msmtp.git.sourceforge.net/git/gitweb.cgi?p=msmtp/msmtp;a=tree;f=scripts/msmtpq;h=edde598fe8394b371a8c67a0dc910423ae88904b;hb=HEAD _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk