From: Jason Molenda <jason-swarelist@molenda.com>
To: Chris Faylor <cgf@cygnus.com>
Cc: overseers@sourceware.cygnus.com
Subject: Re: cygwin-announce problems
Date: Fri, 12 May 2000 01:25:00 -0000 [thread overview]
Message-ID: <20000512012531.A14921@shell17.ba.best.com> (raw)
Message-ID: <20000512012500.cQmuW4mXLSlUjKcRi0HJFySuygVPNIin_xhkue3Uif4@z> (raw)
In-Reply-To: <20000510234221.A4961@cygnus.com>
On Wed, May 10, 2000 at 11:42:21PM -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.
> Oh well. I was trying to avoid having to remember to do this every time
> we sent email to cygwin-announce.
I just thought of a workaround. As a parting gift to Jeff Law ;-),
I wrote a replacement for ezmlm's listname-in-to/cc checker. My
replacement, in addition to being a lot slower, allows you to have
declare multiple valid listnames. So the ezmlm listname-check for
the cygwin list would be disabled, my listname-checker would be
used in its place (infra/bin/check-for-listname.sh), and both
"cygwin@sourceware.cygnus.com" and "cygwin-announce@sourceware.cygnus.com"
would be allowed as valid listnames for the cygwin list.
I think it'd work. ezmlm might still have some further clever
protections to prevent mailing lists from looping and might detect
that a mailing list note is being sent through another mailing
list. I don't think I've ever tried to include a list in a list
like this, so I honestly don't know off hand.
In any event, to avoid odd messages from ezmlm, I'd unsubscribe
cygwin@sourceware from the cygwin-announce list right now and wait
a couple of weeks for ezmlm to get the bounces out of its system.
Otherwise cygwin-announce will send ezmlm warnings about 'I had
trouble delivering the following notes ... ' to cygwin and the
cygwin users will roar in confusion.
Jason
next prev parent reply other threads:[~2000-05-12 1:25 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
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 [this message]
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=20000512012531.A14921@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).