Ari Moisio wrote:
>
> I have several mailing lists with memebers sometimes mailing from some
>other address they are subscribed. I have manually accepted each message
>but would like to permanently enable these senders addresses. However i
>could not find any setting to allow postings from no
Hi!
I have searched all list configuration but cannnot find how to disable
member_posting_only-feature with web interface.
I have several mailing lists with memebers sometimes mailing from some
other address they are subscribed. I have manually accepted each message
but would like to perm
> "Brad" == Brad Knowles <[EMAIL PROTECTED]> writes:
Brad> Programmers tend to think that everyone else in the
Brad> world is a programmer, and then are amazed when others are
Brad> not capable of doing the things that they find so easy.
I only said it's a shame that this te
At 10:32 AM +0900 2005-04-21, Stephen J. Turnbull wrote:
It's a shame that we don't take more advantage of the flexibility that
is offered by this feature. It is _really_ easy to experiment with
Mailman 2.1 if you know a little Python.
If you know a little Python.
If you can afford
> "Brad" == Brad Knowles <[EMAIL PROTECTED]> writes:
Brad> At 9:06 PM -0400 2005-04-19, kalin mintchev wrote:
>> what is not clear in the statement members_postings_only='yes'?
>> 'yes' or 'only'? i guess i'm hanging on "only". wouldn't you?
Brad> The problem is that Ma
At 9:06 PM -0400 2005-04-19, kalin mintchev wrote:
what is not clear in the statement members_postings_only='yes'?
'yes' or 'only'? i guess i'm hanging on "only". wouldn't you?
The problem is that Mailman checks for things such as attachment
size, etc... to try to determine whether or not the m
> Date: Tue, 19 Apr 2005 21:06:43 -0400 (EDT)
> From: "kalin mintchev" <[EMAIL PROTECTED]>
> Subject: Re: [Mailman-Users] member_posting_only
> To: "Brad Knowles" <[EMAIL PROTECTED]>
> Cc: mailman-users@python.org
> Message-ID: <[EMAIL PROT
> "kalin" == kalin mintchev <[EMAIL PROTECTED]> writes:
kalin> my point was/is that the 'members_posting_only' is supposed
kalin> to be for members ONLY but it's not...
As I understand the word "post" it implies delivery to the list
members. So this option is doing what it says: prev
> Most of those kinds of messages, on my lists, and I have over 60, are
> spam. You can set Mailman to discard all "held" messages, so you won't
> ever see them. They will also discard member posts from different
> addresses, etc., but this may be a small price to pay for not having to go
> thro
>
> jc
ok. in my first post i mentioned that this is mailman version 2.0.13.
those options don't exist there... but thanks...
>
>
--
--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-
On Apr 19, 2005, at 8:42 PM, JC Dill wrote:
I think you are missing the big picture. There are many different
ways that lists can be configured. The "only" term applies to the
*automatic* handling by mailman, not to the choices made by the list
owners and admins. Mailman automatically posts
kalin mintchev wrote:
Those messages aren't approved -- they're held.
ok, Brad. thanks. sure. they are held. held for approval. they are not
"approved". true.
are they from subscribed members? some. most are not.
but the setting says members_postings_only = 'yes' (ONLY!)
That is the setti
> Those messages aren't approved -- they're held.
ok, Brad. thanks. sure. they are held. held for approval. they are not
"approved". true.
are they from subscribed members? some. most are not.
but the setting says members_postings_only = 'yes' (ONLY!)
ok.
but there are about 60-70% mess
> Yes, this means that I (or a moderator) needs to read through the
> held queue and rescue any stray messages, but it only takes a few
> minutes a day.
>
> I think holding questionable messages is the best default because it
> allows the list-owner to remedy the situation. If the default was to
At 6:17 PM -0400 4/19/05, kalin mintchev wrote:
>thanks Dan. i disagree thought. i don't see how you'd recognize a member
>of the list except by the email address. how'd you possibly know that the
>email address that's in the From header on the message you are about to
>approve belongs to one of th
>
> On Apr 19, 2005, at 3:42 PM, kalin mintchev wrote:
>> right. but.. if they are not on the list they should not be approved - i
>> mean the posting is allowed ONLY to members (member_posting_only) so why
>> is mailman holding messages for approval that's not coming from members at
>> all?
>
> I
At 4:46 PM -0400 2005-04-19, kalin mintchev wrote:
Because they're not on the list, their posts are held for
moderation, hence the notification.
right. but.. if they are not on the list they should not be approved - i
mean the posting is allowed ONLY to members (member_posting_only) so why
is
> Because they're not on the list, their posts are held for moderation,
hence the notification.
right. but.. if they are not on the list they should not be approved - i
mean the posting is allowed ONLY to members (member_posting_only) so why
is mailman holding messages for approval that's not co
hi...
mailman version 2.0.13
Restrict posting privilege to list members? - yes.
i get a lot of messages to go to the Administrative requests page to
aprove messages that are from people who are NOT on the list at all.
what's up with that?
--
On Saturday, October 25, 2003, at 02:03 am, Cole wrote:
Until very recently I was running Lyris which I was fairly happy with.
However edicts came down from above and I am now trying to fine tune
the configuration of Mailman 2.0.6 which I inherited from someone
else. In short I am very new to
Until very recently I was running Lyris which I was fairly happy with. However edicts
came down from above and I am now trying to fine tune the configuration of Mailman
2.0.6 which I inherited from someone else. In short I am very new to Mailman.
I have set the member_posting_only to "yes" which
On Fri, 24 Oct 2003, Richard Barrett wrote:
>
> On Wednesday, October 22, 2003, at 09:34 pm, Andrew Watson wrote:
>
> > My ISP is running mailman 2.0.7
> > Due to spam, I recently changed my list options to:
> >
> > Restrict posting privilege to list members? ( member_posting_only ) -
> > yes
On Wednesday, October 22, 2003, at 09:34 pm, Andrew Watson wrote:
My ISP is running mailman 2.0.7
Due to spam, I recently changed my list options to:
Restrict posting privilege to list members? ( member_posting_only ) -
yes
Since the change, i have noticed no difference. I must still manually
My ISP is running mailman 2.0.7
Due to spam, I recently changed my list options to:
Restrict posting privilege to list members? (
member_posting_only ) - yes
Since the change, i have noticed no difference. I must still manually
discard every spam posting.
Is this option non-functional in 2.0.7?
According to Peter Hutnick:
> Does non-subscriber mail bounce? I'd like to be able to configure
> this. I would actually like to have non-subscriber mail held for
> approval. Call me the human spam filter!
Non-subscriber mail is held for approval, just like moderated lists.
+gg
--
[EMAIL
> According to Peter Hutnick:
>> This ties in nicely with a question that I asked earlier.
>>
>> Is there a way to configure Mailman so that subscribers do not
>> need approval, but non-subscribers do?
>
> Isn't that the option "Restrict posting privilege to list
> members? (member_posting_only
According to Peter Hutnick:
> This ties in nicely with a question that I asked earlier.
>
> Is there a way to configure Mailman so that subscribers do not need
> approval, but non-subscribers do?
Isn't that the option "Restrict posting privilege to list members?
(member_posting_only)" on "priva
27 matches
Mail list logo
