Posting filters not working/Passwords
I'm still having problems with setting my list to members-only. When I set it to members-only, everyone's messages bounce. This applies to members mass-subscribed when Mailman was installed for me as well as members who joined (and confirmed) after the list was running on Mailman.
Here's what I have set:
Must posts be approved by an administrator?: No Restrict posting privilege to list members?: Yes Addresses of members accepted for posting to this list without implicit approval requirement: No addresses listed
Some other pertainent facts: When my ISP transferred the membership roster from our old MajorDomo server to mailman, they did (I think) a mass subscribe, and they did NOT ask these existing 300 members to confirm. Some of these transferred members are able to request their passwords and they get back a pseudo-random 4 character password. But some members complained they cannot get a password. And when they try to find their password, I (as admin) get a message saying that that member "lacks a password". Perhaps this is causing the posting filter problem.
So, I have two questions:
What can I do, other that fix the passwords, that will allow me to set my list to "Restrict posting privilege to list members"?
How can I assign passwords to already subscribed members? I have no direct access to the machine that Mailman is installed on.
Thanks,
John Broman List Owner Corvette Restoration and Preservation List (CRPL)
bruce@perens.com wrote:
Rather than remove it, provide a check box to enable/disable it per list in the admin forms, or per user in the user's options. Then everybody will be happy.
Great.
i think that the passwd option are very important when you set your user/subscriber option, if you dont have a passwd anybody can change your option :-( . i am sure that noone want this
I won't give up subscription confirmation for anything, though. Too many times my lists have been used to maliciously mail-bomb someone.
Now, confirmation I completely agree with.
me too
Thanks
Mailman-Users maillist - Mailman-Users@python.org http://www.python.org/mailman/listinfo/mailman-users
"John C. Broman, Jr." wrote:
- What can I do, other that fix the passwords, that will allow me to set my list to "Restrict posting privilege to list members"?
I had a similar problem, I had changed the 'public name for this list' by adding a space in it (even though it says very clearly only to change case). Thus, it was rejecting the e-mail from others beacuse the list wasn't an exact match in the to/cc part of the header.
- How can I assign passwords to already subscribed members? I have no direct access to the machine that Mailman is installed on.
I have the problem of blank passwords during a mass-subscribe as well, here is the e-mail that is sent to me. I've ignored it so far...
-------- Original Message -------- From: general-admin@jos.org Subject: General@jos.org user regveryj@jdcorp.deeree.com missing password! To: general-admin@jos.org
Mailman noticed in .MailUserPassword() that:
User: 'regveryj@jdcorp.deeree.com' List: generallacks a password. Please notify the Mailman system manager at this site!
I apologize for being annoying/harsh in my past e-mail. Mailman is way cool stuff -- I'm thrilled to be a user.
Best Regards,
:) Clark Evans
John,
I believe both of your problems will be fixed, or work-around-able in the next beta, released RRSN. You don't say what version of Mailman you're using, so I'll assume 1.0b9.
"JCBJ" == John C Broman, Jr <stingray@wizard.net> writes:
JCBJ> 1) What can I do, other that fix the passwords, that will
JCBJ> allow me to set my list to "Restrict posting privilege to
JCBJ> list members"?It seems that on some systems, using the envelope sender to check against member addresses is broken. Using the envelope sender over the From: field is moderately less easy to spoof, but doesn't work for everyone. The next release will have a system-wide default USE_ENVELOPE_SENDER that can be set to false to use the From: field always. This ought to fix your problem (I may make this the default for the final release).
JCBJ> 2) How can I assign passwords to already subscribed members?
JCBJ> I have no direct access to the machine that Mailman is
JCBJ> installed on.These members actually do have passwords. The problem is that if the user was subscribed with an address containing non-lower-case letters, the address matching code in the password mailer was broken. This is fixed in the next release.
My suggestion would be to upgrade to 1.0b10 when it's released.
-Barry
On 25 Mar 99, at 0:13, Barry A. Warsaw wrote:
John,
I believe both of your problems will be fixed, or work-around-able in the next beta, released RRSN. You don't say what version of Mailman you're using, so I'll assume 1.0b9.
"JCBJ" == John C Broman, Jr <stingray@wizard.net> writes:
JCBJ> 1) What can I do, other that fix the passwords, that will JCBJ> allow me to set my list to "Restrict posting privilege to JCBJ> list members"?It seems that on some systems, using the envelope sender to check against member addresses is broken. Using the envelope sender over the From: field is moderately less easy to spoof, but doesn't work for everyone. The next release will have a system-wide default USE_ENVELOPE_SENDER that can be set to false to use the From: field always. This ought to fix your problem (I may make this the default for the final release).
The interim fix if this is driving you crazy like it was me is to edit MailList.py and change "sender = msg.GetEnvelopeSender()" on line 1024 to "sender = msg.GetSender()" and rebuild.
This one consumed almost my full time for three days after I moved my lists from majordomo to mailman while I searched for a fix. Having to approve every post on four very busy lists is almost a full time job all by itself.
Richard B. Pyne, KB7RMU rpyne@kinfolk.org http://pyne.kinfolk.org/rbp2
At 12:13 AM 3/25/99 -0500, Barry A. Warsaw wrote:
I believe both of your problems will be fixed, or work-around-able in the next beta, released RRSN. You don't say what version of Mailman you're using, so I'll assume 1.0b9.
Yes, I'm using 1.0b9. And forgive me: RRSN???
Thanks!
John Broman
participants (4)
-
Barry A. Warsaw -
Clark Evans -
John C. Broman, Jr. -
Richard B. Pyne