I am subscribed to many Mozilla mailing lists as firstname.lastname@example.org, which means that I should be allowed to post to any of them. But when I just replied to a post that was crossing to a list I'm not on, I got "In order to protect our mailing lists from spam, we require that all posters be subscribers of the list to which they are posting. We support several different ways of submitting your post. Pick the one that works best for you. If you wish to continue using e-mail to post, please visit https://lists.mozilla.org/listinfo/dev-extensions and subscribe to the list. Once you have been subscribed, you may resubmit your post." Suspect this was regressed by bug 348858. Needs a fast fix, this is pretty painful.
I just checked, and you aren't subscribed to dev-extensions. That would be why you're getting the reject notice...
Status: NEW → RESOLVED
Last Resolved: 10 years ago
Resolution: --- → INVALID
No, being subscribed to _any_ mozilla list should be enough to let me post to _any_ mozilla list. It's been that way for quite a long time.
Status: RESOLVED → REOPENED
Resolution: INVALID → ---
Correction -- you're subscribed, but you're subscribed as email@example.com, not firstname.lastname@example.org. (In reply to comment #3) > No, being subscribed to _any_ mozilla list should be enough to let me post to > _any_ mozilla list. It's been that way for quite a long time. Ah, that's a hack added to our mailman instance that doesn't apply to how it's set up now. I can add that back in...
Assignee: server-ops → reed
Status: REOPENED → RESOLVED
Last Resolved: 10 years ago → 10 years ago
Resolution: --- → FIXED
Summary: list posting permissions tightened incorrectly → Add back support for allowing posting if user is subscribed to any mailing list
Summary: Add back support for allowing posting if user is subscribed to any mailing list → Add support to new reject method for allowing posting if user is subscribed to any mailing list
Product: mozilla.org → mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.