Re: [Mailman-Users] Problem Migrating Mailman to New Server

2008-10-26 Thread Mark Sapiro 
Dennis Putnam wrote:

OK, now I understand what you are asking. I restarted mailman and let it
run for several minutes with no error in /var/log/mailman/error. Then I
submitted a help to -request. That is when the error occurred. I suppose
it might mot be the help request per se but rather anything that causes
mailman to do something. I tried to run a couple of other commands and
they all do the same thing. I am reluctant to actually send a test to
the list out of fear it might destroy something and make matters worse.
Here is the traceback.

Oct 24 17:30:09 2008 (5961) Uncaught runner exception: [Errno 13]
Permission denied:
'/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1'
Oct 24 17:30:09 2008 (5961) Traceback (most recent call last):
  File /usr/lib/mailman/Mailman/Queue/Runner.py, line 112, in _oneloop
self._onefile(msg, msgdata)
  File /usr/lib/mailman/Mailman/Queue/Runner.py, line 170, in _onefile
keepqueued = self._dispose(mlist, msg, msgdata)
  File /usr/lib/mailman/Mailman/Queue/ArchRunner.py, line 73, in _dispose
mlist.ArchiveMail(msg)
  File /usr/lib/mailman/Mailman/Archiver/Archiver.py, line 216, in
ArchiveMail
h.processUnixMailbox(f)
  File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 580, in
processUnixMailbox
self.add_article(a)
  File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 632, in
add_article
article.parentID = parentID = self.get_parent_info(arch, article)

  File /usr/lib/mailman/Mailman/Archiver/pipermail.py, line 664, in
get_parent_info
article.subject)
  File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 311,
in getOldestArticle
self.__openIndices(archive)
  File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 251,
in __openIndices
t = DumbBTree(os.path.join(arcdir, archive + '-' + i))
  File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 61, in
__init__
self.lock()
  File /usr/lib/mailman/Mailman/Archiver/HyperDatabase.py, line 77, in
lock
self.lockfile.lock()
  File /usr/lib/mailman/Mailman/LockFile.py, line 243, in lock
self.__write()
  File /usr/lib/mailman/Mailman/LockFile.py, line 422, in __write
fp = open(self.__tmpfname, 'w')
IOError: [Errno 13] Permission denied:
'/var/lib/mailman/archives/private/mailman/database/2008-October-date.lock.dap002.5961.1'

Oct 24 17:30:09 2008 (5961) SHUNTING:
1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212


ArchRunner is trying to archive a message it found in qfiles/archive/.
It has encountered the lock permission denied and moved the message to
qfiles/shunt/1224883807.7050669+416c5717ff6f07bcc5748843bf07afb92dc4b212.pck
 What is the message (use bin/dumpdb or bin/show_qfiles to see it).


Here is the process (shouldn't this be running as 'mailman'?):

mail  5961  0.1  0.7  11100  7356 ?R17:28   0:00
/usr/bin/python /usr/lib/mailman/bin/qrunner --runner=ArchRunner:0:1 -s


How are you starting Mailman. Are you running bin/mailmanctl as root or
starting it as a 'service' as root?

If so, it should be setting the uid and gid of itself and the runners
as those of MAILMAN_USER and MAILMAN_GROUP from Defaults.py/mm_cfg.py
and supplemental groups as those associated with MAILMAN_USER.

So, if I understand your configuration, MAILMAN_USER:MAILMAN_GROUP are
mailman:mail. If that's correct, I would expect the runners to be
running as user 'mailman'. That may be the cause of the permissions
error.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9

Re: [Mailman-Users] Giving Non-Administrator Access To Simple AdminFunctions

2008-10-26 Thread Mark Sapiro 
Steve Lund wrote:

I am currently administering a small Mailman 2.11 list for our volunteer 
organization. Another individual needs the basic ability to 
subscribe,  unsubscribe and possibly list members. This person thinks that 
they are a lot more computer literate than they are and I don't want to 
give them the password to the web configuration interface for fear that 
they will mess something up that will take me hours to figure out and fix.

I am an embedded hardware engineer and not a programmer but I am careful 
enough not to change settings or list parameters without thoroughly testing 
the changes. So far I have managed to stay out of trouble! :-)

Is it possible to do these rudimentary functions via the e-mail interface? 
If so can you point me to some documentation on how to do this? The only 
information I have found on the email interface seems to be directed to an 
individual user changing their own parameters and not to admin functions.


There is no e-mail interface for list admin tasks per-se, but the admin
can list members via email and can _request_ subscription and
unsubscription via email, but these latter function will send a
confirmation request to the user and the user must confirm.

Send a blank email with subject 'help' to the listname-request address
for documentation of the email commands available.


Would I then have to add this person as an administrator and then just not 
tell them about the other email commands or the existence of the web interface?


For subscribe and unsubscribe, the person doesn't need any privileges.
The relevant email commands are

  subscribe [password] [digest|nodigest] [address=address]

address is the address to subscribe. password is not for
authentication; it is the initial list password for the user. This
results in a confirmation request to address.

  unsubscribe [password] [address=address]

address is the address to unsubscribe. password is the list password
associated with address if known. If the password is provided
correctly, address will be unsubscribed. Otherwise, a confirmation
request will be sent to address.

To get a membership list, you can set a list moderator password
different from the list admin password and give the moderator password
to this person. You don't add this person to the list's 'moderator'
attribute unless you want her/him to also get notices about posts,
etc. waitin moderator action. The moderator password will allow the
person to authenticate for the list's admindb interface, but she/he
can't change list settings from there.

Then the person can send

  who password

to the list-request address to get a full list of members (hidden or
not), where password is the moderator password.


That's the best you can do by email. Otherwise, you have to give the
person the list admin password, and they have to use the admin
Membership Management pages, and of course, they have access to all
the rest.

-- 
Mark Sapiro [EMAIL PROTECTED]The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list
Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Security Policy: http://wiki.list.org/x/QIA9