From mboxrd@z Thu Jan 1 00:00:00 1970 Received: by 10.42.165.135 with SMTP id k7cs2673icy; Fri, 19 Nov 2010 02:36:23 -0800 (PST) Received: by 10.224.47.75 with SMTP id m11mr1614490qaf.344.1290162982757; Fri, 19 Nov 2010 02:36:22 -0800 (PST) Return-Path: Received: from rubyforge.org (rubyforge.org [205.234.109.19]) by mx.google.com with ESMTP id t33si3582306qcs.129.2010.11.19.02.36.22; Fri, 19 Nov 2010 02:36:22 -0800 (PST) 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 8CF9C18583C3; Fri, 19 Nov 2010 05:36:21 -0500 (EST) Received: from mail-qy0-f171.google.com (mail-qy0-f171.google.com [209.85.216.171]) by rubyforge.org (Postfix) with ESMTP id E8D0E1858379 for ; Fri, 19 Nov 2010 04:57:51 -0500 (EST) Received: by qyk38 with SMTP id 38so8770868qyk.2 for ; Fri, 19 Nov 2010 01:57:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:in-reply-to :references:date:message-id:subject:from:to:content-type; bh=KESFhf7ueVLXd7dGsMf8osiMCy6acq6NAMQtJAt86sg=; b=XSwAqxyEJushtKIlaru0UHxE1ThxvMSTL/mJhQhBaUZ4Pyw6fW7M6UKWbZieUZ72El 7hYx6Ps/CQq1ARYxvJKs6Iq10KgFdDrLV4HWWjCTKKHp5+GOPssLvqpTRDHYEBtDUp4I 0Pl+k+oXF2Qeuszdpk4yMCNs+hmc/3TidhDos= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=VTOQFfTJL6qaV9FDXFq+D1/N8a08Y9A4RQGav9g0Htj6WJgh35Y1NQ7uqKdtF4xd7r 0IteCkXfYEJKTUyZB60AqE8SlJflfka7gR9MsyXoKHShcJhlDsRgUjw4UCof+595a3Ji +CY8/NTD7S6l73TlIl3v0xryv9meUT3RaTAGk= MIME-Version: 1.0 Received: by 10.229.191.130 with SMTP id dm2mr1591975qcb.256.1290160671586; Fri, 19 Nov 2010 01:57:51 -0800 (PST) Received: by 10.229.237.209 with HTTP; Fri, 19 Nov 2010 01:57:51 -0800 (PST) In-Reply-To: <1290083492-sup-3720@blake> References: <1290083492-sup-3720@blake> Date: Fri, 19 Nov 2010 09:57:51 +0000 Message-ID: From: Shadowfirebird To: sup-talk Subject: Re: [sup-talk] Sup not sending mail body! 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: multipart/mixed; boundary="===============1055561127==" Sender: sup-talk-bounces@rubyforge.org Errors-To: sup-talk-bounces@rubyforge.org --===============1055561127== Content-Type: multipart/alternative; boundary=0016362840728881e0049564f009 --0016362840728881e0049564f009 Content-Type: text/plain; charset=ISO-8859-1 (Replying to myself.) It appears my mail message made it to my gmail account (which I am using for SMTP send), but not to the ruby-talk mailing list. Could there be something about the way sup does headers that is confusing ruby-talk? I'm going to cross-post this to ruby-talk, too. --0016362840728881e0049564f009 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable (Replying to myself.)

It appears my mail message made it to my gmail= account (which I am using for SMTP send), but not to the ruby-talk mailing= list.=A0=A0 Could there be something about the way sup does headers that i= s confusing ruby-talk?

I'm going to cross-post this to ruby-talk, too.
--0016362840728881e0049564f009-- --===============1055561127== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ sup-talk mailing list sup-talk@rubyforge.org http://rubyforge.org/mailman/listinfo/sup-talk --===============1055561127==--