OS: Solaris 10
PREFIX = '/usr/mailman'
Server setup: 1 server for web management, 1 server for MTA/qrunner.
/usr/mailman is NFS mounted on both servers
I've been having the following issue my mailman lists:
A user is either subscribed or unsubscribed according to the logs, but
then if I look at the member list, the action has not been done (or has
been undone). For example, here is where I remove a subscriber and then
look at the list members and they are still in the list:
[mailman@myhost] ~/logs |> grep testlist subscribe | grep acase
Sep 28 17:15:14 2011 (4401) testlist: new acase(a)example.com, admin mass sub
Sep 28 17:19:36 2011 (5821) testlist: deleted acase(a)example.com; member
[mailman@myhost] ~/logs |> ../bin/list_members testlist | grep acase
[mailman@myhost] ~/logs |>
The same also happens when subscribing. I will mass subscribe users (or
when users confirm subscription via email/web), the logs indicated that
they have been subscribed successfully, but then when I go look them up,
they are not listed on the members list.
This happens sporadically, but I am generally able to reproduce the error
if I do it a couple times in a row.
I'm suspicious there may be a locking issue and config.pck is reverting to
config.pck.last. I found this thread rather helpful in analyzing
potential problems, but I have yet to figure anything out:
In addition if I just run the following commands over and over, then the
bug never seems to come up. This is part of why I am worrying about
Is there a good way to test locking between servers? I've run the
tests/test_lockfile.py, but it reports it is OK.
Any and all help would be GREATLY appreciated. We've been trying to
triage this bug for weeks and it is terribly disruptive for our users.
Barry said to email this list with an interest in helping with UI for MM3.
I’ve done UI development for cPanel, Inc. for the past couple years.
I’m fluent with Perl and JS/CSS/HTML/etc. I messed with Python a tiny
bit about 8 years ago; I’m hoping to beef up my skills in that area as
part of helping out with MM3. I’d say I’m reasonably well-versed in SMTP.
I’ve used Git and SVN; Bazaar will be new to me.
I’m looking forward to helping out.
On Sep 27, 2011, at 12:44 AM, Stephen A. Goss wrote:
>I've attached a branch with the Postgres support code that I've cooked
Fantastic, thanks! Do be sure to add a merge proposal.
>3. There is now an alternate mailman_pg.sql file which is used to create
>the tables. Currently, two foreign key constraints are commented out
>because those are violated in Mailman 3 (apparently this doesn't bother
>SQLite). Some column TYPES are different from mailman.sql. Classes are
>created in a slightly different order due to FK constraint creation
>requires the referenced table to actually exist. The primary key indexes
>defined after each class are probably redundant, as those are created
>automatically for SERIAL columns defined as PRIMARY KEY in Postgres.
Do you have any thoughts on whether the two .sql files can possibly be shared?
My biggest concern is that it will be difficult-ish to keep them in sync as I
add or modify the SQLite version. If it's not possible, so be it.
I took a quick look at the Python changes, and I think I'm going to refactor
the code to not hardcode so much in stock.py. For example, I'll probably
rename StockDatabase to SQLiteDatabase and add a PostgresDatabase class,
adding a common super class. That way, you'd only need to put this in your
Don't worry about that too much, I can make that change when I merge your
>4. Probably more FK constraint violations exist that my tests haven't
I'd definitely like to be able to run the test suite against Postgres, if even
for now it's a manual select (e.g. because Postgres would obviously have to be
installed and configured in order to work).
I am very happy to announce the release of the eighth alpha for Mailman 3.0,
code named "Where's My Thing?". This is the last planned alpha release, as I
want to work toward the first beta in order to meet my goal of an 11/11/11
final release (of the core engine at least).
If you've been holding off looking at Mailman 3, I invite you to do so now.
Once beta 1 is released I will not be adding any new features. I do hope to
put up a few live test lists soon, so stay tuned.
There have been a large number of fixes and new features, especially in the
REST API. My thanks go to Stephen Goss who has contributed greatly to this
release, with bug reports, wish list items, patches, and merge proposals.
Full details of what's new in 3.0a8 is available here:
The tarball can be downloaded from Launchpad or the Cheeseshop:
The full documentation is also online: