From: Jeffrey A Law <law@cygnus.com>
To: overseers@sources.redhat.com
Subject: Re: Bypassing the mailing list name restriction
Date: Sat, 30 Dec 2000 06:08:00 -0000 [thread overview]
Message-ID: <7727.966896656@upchuck> (raw)
In-Reply-To: <20000821180216.A14361@cygnus.com>
In message < 20000821180216.A14361@cygnus.com >you write:
> We have a user who is sending email to the cygwin mailing list like this:
>
> To: "cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
>
> Besides the fact that this illustrates a hole in our mailing list
> checking, it also screws up anybody who wants to reply to him since the
> quoted part can be thrown away and, although the message is still
> forwarded through cygwin@hotpop.com, it now is rejected by check-for-listna
> me.sh
> since there is no actual mailing list in the header.
>
> I'd like to modify check-for-listname.sh so that the above trick no longer
> works. Are there any objections to my doing this?
None from me. Go for it.
jeff
WARNING: multiple messages have this Message-ID
From: Jeffrey A Law <law@cygnus.com>
To: overseers@sources.redhat.com
Subject: Re: Bypassing the mailing list name restriction
Date: Mon, 21 Aug 2000 15:26:00 -0000 [thread overview]
Message-ID: <7727.966896656@upchuck> (raw)
Message-ID: <20000821152600.OO6W7NdhRV3XsXnvDRUiA1DuuMz_w9Rg_0J2ouNE_0Y@z> (raw)
In-Reply-To: <20000821180216.A14361@cygnus.com>
In message < 20000821180216.A14361@cygnus.com >you write:
> We have a user who is sending email to the cygwin mailing list like this:
>
> To: "cygwin@sourceware.cygnus.com" <cygwin@hotpop.com>
>
> Besides the fact that this illustrates a hole in our mailing list
> checking, it also screws up anybody who wants to reply to him since the
> quoted part can be thrown away and, although the message is still
> forwarded through cygwin@hotpop.com, it now is rejected by check-for-listna
> me.sh
> since there is no actual mailing list in the header.
>
> I'd like to modify check-for-listname.sh so that the above trick no longer
> works. Are there any objections to my doing this?
None from me. Go for it.
jeff
next prev parent reply other threads:[~2000-12-30 6:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-30 6:08 Chris Faylor
2000-08-21 15:03 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-08-21 15:45 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-08-21 20:18 ` Chris Faylor
2000-12-30 6:08 ` Jason Molenda
2000-08-21 20:32 ` Jason Molenda
2000-12-30 6:08 ` Chris Faylor
2000-08-21 20:57 ` Chris Faylor
2000-12-30 6:08 ` Jeffrey A Law [this message]
2000-08-21 15:26 ` Jeffrey A Law
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=7727.966896656@upchuck \
--to=law@cygnus.com \
--cc=overseers@sources.redhat.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).