Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: Shadowfirebird <shadowfirebird@gmail.com>
To: sup-talk <sup-talk@rubyforge.org>
Subject: Re: [sup-talk] Sup not sending mail body!
Date: Fri, 19 Nov 2010 09:57:51 +0000	[thread overview]
Message-ID: <AANLkTimyQBMeq_JiH0UpPFpEsAebpvF8YDuoOJAuNsq2@mail.gmail.com> (raw)
In-Reply-To: <1290083492-sup-3720@blake>


[-- Attachment #1.1: Type: text/plain, Size: 287 bytes --]

(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.

[-- Attachment #1.2: Type: text/html, Size: 310 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
sup-talk mailing list
sup-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-talk

      reply	other threads:[~2010-11-19 10:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 12:34 Shadowfirebird
2010-11-19  9:57 ` Shadowfirebird [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimyQBMeq_JiH0UpPFpEsAebpvF8YDuoOJAuNsq2@mail.gmail.com \
    --to=shadowfirebird@gmail.com \
    --cc=sup-talk@rubyforge.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox