From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: overseers@sourceware.cygnus.com Subject: Re: cygwin-announce problems Date: Sat, 30 Dec 2000 06:08:00 -0000 Message-id: <20000512012531.A14921@shell17.ba.best.com> References: <20000510223618.A27962@cygnus.com> <20000510203814.A26941@shell17.ba.best.com> <20000510234221.A4961@cygnus.com> X-SW-Source: 2000/msg00493.html 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 From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jason Molenda To: Chris Faylor Cc: overseers@sourceware.cygnus.com Subject: Re: cygwin-announce problems Date: Fri, 12 May 2000 01:25:00 -0000 Message-ID: <20000512012531.A14921@shell17.ba.best.com> References: <20000510223618.A27962@cygnus.com> <20000510203814.A26941@shell17.ba.best.com> <20000510234221.A4961@cygnus.com> X-SW-Source: 2000-q2/msg00186.html Message-ID: <20000512012500.cQmuW4mXLSlUjKcRi0HJFySuygVPNIin_xhkue3Uif4@z> 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