Comment 7 for bug 298298

Revision history for this message
Robin J (robin-jeffries) wrote : Re: [Bug 298298] Re: test to see if non members posts to xxx-yyygetthrough

I think that we are not communicating.
An existing conversation would be
<email address hidden><kathy-jan15%<email address hidden>>
I want you to send to <email address hidden> (see
the - instead of the +)

Is that what you did (as I recall, the headers suggested to me that it
wasn't)

Robin

On Wed, Jan 21, 2009 at 4:32 PM, Kathy Gee <email address hidden> wrote:

> >> Did you try the more
> direct one of sending to kathy-jan15-books to see if that works
>
> Yes, I believe that was my first test (recorded below). I used a
> non-member account to send to an existing conversation and the system
> rejected it with this message:
>
> " You are not allowed to post to this mailing list, and your message has
> been automatically rejected. If you think that your messages are
> being rejected in error, contact the mailing list owner at
> <email address hidden>."
>
> Or is there another scenario I should be testing?
>
> -----Original Message-----
> From: <email address hidden> [mailto:<email address hidden>] On Behalf Of
> Robin J
> Sent: Tuesday, January 20, 2009 8:56 PM
> To: Kathy Gee
> Subject: Re: [Bug 298298] Re: test to see if non members posts to
> xxx-yyygetthrough
>
> If the bcc: trick works, it would because there are "magic" characters
> in
> the bcc: field that tickle some sort of bug in mailman, and since we
> can't
> see the bcc field, I don't know how to debug that. Did you try the more
> direct one of sending to kathy-jan15-books to see if that works (it
> shouldn't, but that's the only way I can think of to test that
> loophole).
> That shouldn't even get to mailman, but it looked like it was on
> systers
> (it was being posted)
> Robin
>
> On Tue, Jan 20, 2009 at 10:33 AM, Kathy Gee <email address hidden>
> wrote:
>
> > Here is the system response I got when sending a message to
> > "kathy-jan15+books" as a BCC (left blank for TO). Looks like the
> system
> > generated the same error message. I'm not sure if this is what you
> are
> > looking for:
> >
> > You are not allowed to post to this mailing list, and your message has
> > been automatically rejected. If you think that your messages are
> > being rejected in error, contact the mailing list owner at
> > <email address hidden>.
> >
> > Kathy
> >
> >
> > ---------- Forwarded message ----------
> > From: Kathy Gee <email address hidden>
> > To: undisclosed-recipients:;
> > Date: Tue, 20 Jan 2009 10:29:33 -0800
> > Subject: Sending mail from non-member ...
> > to an existing conversation (i.e. kathy-jan15+books@...) as a BCC
> >
> > -----Original Message-----
> > From: <email address hidden> [mailto:<email address hidden>] On Behalf
> Of
> > Robin J
> > Sent: Monday, January 19, 2009 3:03 PM
> > To: Kathy Gee
> > Subject: Re: [Bug 298298] Re: test to see if non members posts to
> > xxx-yyy getthrough
> >
> > That isn't the test we need. We had a problem with spam getting
> through
> > to
> > the list, and it was going to addresses like kathy-jan15-books@.....
> > My guess is that the real issue is that the spammer was sending via a
> > bcc:,
> > but just in case, I wanted to test this on the new system.
> >
> > Robin
> >
> > On Mon, Jan 19, 2009 at 11:10 AM, Kathy Gee <email address hidden>
> > wrote:
> >
> > > This is fine on the ABIWT system. I will "commit release" this bug.
> > > Here is the system's respond when I tried to send to a existing
> > > conversation from a non-member:
> > >
> > > You are not allowed to post to this mailing list, and your message
> has
> > > been automatically rejected. If you think that your messages are
> > > being rejected in error, contact the mailing list owner at
> > > <email address hidden>.
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Kathy Gee <email address hidden>
> > > To: <email address hidden> <kathy-jan15%<email address hidden>> <
> kathy-jan15%<email address hidden> <kathy-jan15%<email address hidden>>> <
> > kathy-jan15%<email address hidden> <kathy-jan15%<email address hidden>> <
> kathy-jan15%<email address hidden> <kathy-jan15%<email address hidden>>>>
> > > Date: Mon, 19 Jan 2009 10:47:18 -0800
> > > Subject: Test from non-member to existing thread
> > > Sending this post to "kathy-jan15+books" conversation as a
> non-member.
> > > Will system let this go through or will it come back with a system
> > respond
> > > with an error message? Let's see!
> > >
> > > ** Changed in: systers/production
> > > Status: New => Fix Released
> > >
> > > --
> > > test to see if non members posts to xxx-yyy get through
> > > https://bugs.launchpad.net/bugs/298298
> > > You received this bug notification because you are a direct
> subscriber
> > > of the bug.
> > >
> > > Status in Systers Mailman Distribution: Fix Released
> > > Status in Systers-mailman Series: production: Fix Released
> > >
> > > Bug description:
> > > In the production system, we have the bug that non-member email to
> > things
> > > like systers-books gets through to systers. We need to test this on
> > the dev
> > > system. I would suggest that you start by creating a thread
> > > dev-test+new+books@sheinvents and then send to
> > dev-test-books@sheinventsas a non-member and see it if gets through.
> If
> > that doesn't work, we should
> > > try a few more corner cases.
> > >
> >
> > --
> > test to see if non members posts to xxx-yyy get through
> > https://bugs.launchpad.net/bugs/298298
> > You received this bug notification because you are a bug assignee.
> >
> > Status in Systers Mailman Distribution: Fix Released
> > Status in Systers-mailman Series: production: Fix Released
> >
> > Bug description:
> > In the production system, we have the bug that non-member email to
> > things like systers-books gets through to systers. We need to test
> this
> > on the dev system. I would suggest that you start by creating a
> thread
> > dev-test+new+books@sheinvents and then send to
> > dev-test-books@sheinvents as a non-member and see it if gets through.
> > If that doesn't work, we should try a few more corner cases.
> >
> > --
> > test to see if non members posts to xxx-yyy get through
> > https://bugs.launchpad.net/bugs/298298
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in Systers Mailman Distribution: Fix Released
> > Status in Systers-mailman Series: production: Fix Released
> >
> > Bug description:
> > In the production system, we have the bug that non-member email to
> things
> > like systers-books gets through to systers. We need to test this on
> the dev
> > system. I would suggest that you start by creating a thread
> > dev-test+new+books@sheinvents and then send to
> dev-test-books@sheinventsas a non-member and see it if gets through. If
> that doesn't work, we should
> > try a few more corner cases.
> >
>
> --
> test to see if non members posts to xxx-yyy get through
> https://bugs.launchpad.net/bugs/298298
> You received this bug notification because you are a bug assignee.
>
> Status in Systers Mailman Distribution: Fix Released
> Status in Systers-mailman Series: production: Fix Released
>
> Bug description:
> In the production system, we have the bug that non-member email to
> things like systers-books gets through to systers. We need to test this
> on the dev system. I would suggest that you start by creating a thread
> dev-test+new+books@sheinvents and then send to
> dev-test-books@sheinvents as a non-member and see it if gets through.
> If that doesn't work, we should try a few more corner cases.
>
> --
> test to see if non members posts to xxx-yyy get through
> https://bugs.launchpad.net/bugs/298298
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in Systers Mailman Distribution: Fix Released
> Status in Systers-mailman Series: production: Fix Released
>
> Bug description:
> In the production system, we have the bug that non-member email to things
> like systers-books gets through to systers. We need to test this on the dev
> system. I would suggest that you start by creating a thread
> dev-test+new+books@sheinvents and then send to dev-test-books@sheinventsas a non-member and see it if gets through. If that doesn't work, we should
> try a few more corner cases.
>