public inbox for overseers@sourceware.org
 help / color / mirror / Atom feed
From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: cygwin-announce problems
Date: Wed, 10 May 2000 20:38:00 -0000	[thread overview]
Message-ID: <20000510203814.A26941@shell17.ba.best.com> (raw)
Message-ID: <20000510203800.r7m2Jnc3X4iO4f_KR2uBfqeboLLTKogGtuEQGi699FQ@z> (raw)
In-Reply-To: <20000510223618.A27962@cygnus.com>

On Wed, May 10, 2000 at 10:36:18PM -0400, Chris Faylor wrote:
> Can anyone tell me if there are some kind of problems with the cygwin mailing
> list?  I tried to gateway the cygwin-announce list into the cygwin list but
> I never see any cygwin-announce email in cygwin.

It makes sense if you think about it -- the spam blocker that
insists on the list name being in the To or Cc header will block
these messages.  When they are relayed to cygwin@sourceware.cygnus.com,
the ezmlm-reject for that list sees that "cygwin@sourceware..." is
not in the To or Cc headers and rejects the note.

(To be honest, I had to poke around a little before I figured it out
myself :-)

cygwin@sourceware is still subscribed to cygwin-announce right now, but
it's on its way to being automatically unsubscribed due to bounces.

Your best bet is either to remail the note to cygwin@ after sending it
to cygwin-announce@, or to Cc: cygwin@ on the announcement.

Jason

  parent reply	other threads:[~2000-05-10 20:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-30  6:08 Chris Faylor
2000-05-10 19:36 ` Chris Faylor
2000-12-30  6:08 ` Jason Molenda [this message]
2000-05-10 20:38   ` Jason Molenda
2000-12-30  6:08   ` Chris Faylor
2000-05-10 20:42     ` Chris Faylor
2000-12-30  6:08     ` Jason Molenda
2000-05-12  1:25       ` Jason Molenda

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=20000510203814.A26941@shell17.ba.best.com \
    --to=jason-swarelist@molenda.com \
    --cc=cgf@cygnus.com \
    --cc=overseers@sourceware.cygnus.com \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).