I can't get to the pending request page for a mailing list.
(My web clients just say "waiting for response" and finally give up.)
I think it is because there are too many pending requests after some
problems. (config.db is almost 10MB.)
How can I do this some other way?
I've asked this question once or twice before, but no response yet.
How do I manually convert a standard, previously existing, concatenated
MBOX format archive into a mailman archive?
Also, no response to my question about mailman 2-beta2
Posts that must be approved by administrator do not make it into
1) is this is a known bug?
2) Is there a way to take the <list>.mbox file (which appears to be okay
for whatever strange reason..) and manually just add the messages that
are not in the pipermail archive to the pipermail archive?
I'm running the latest cvs (just updated again this morning just to be sure)
but their doesn't seem to be any more posts being send out on the list??
they all arrive on the approval page, but once approved they vanish into
nothing... I'm not sure how long this has been going on though...
anybody else having the same trouble?
Has anyone had success re-writing the template e-mails so they are
generic enough for an announce only list as well as a regular
I was wondering if there is a list of variables and an identification
of their source, that can be used in the e-mail template:
%(listname)s, %(welcome)s,%(real_name)s. For example, it would be
nice to switch the %(listname) with the "terse phrase identifying
this list" but I can only find references to that variable in the
listinfo web page (MM-List-Description) and can't seem translate it
to a variable that the e-mail templates understand.
Thanks for any help.
I was experimenting with beta2 over the last week and was eagerly awaiting
beta3. I installed beta3 and ran into two problems. The first was the
"newlist" bug, which is now fixed. The second is that everytime "qrunner" is
run by cron, an email is sent to root (via the mailman alias). Here is the
text of that email:
Reading database ...
Adding message to /home/mailman/archives/private/junk
Writing mail ...
Writing /home/mailman/archives/private/junk/index.html ...
Writing /home/mailman/archives/private/junk/threads.html ...
Writing database ...
I solved this for now by simply redirecting stdout to /dev/null in the
crontab. This was not a problem with beta2. What changed?
BTW, I am using MHonArc as an external archiver, if it matters. However, I
was also running MHonArc with beta2.
Despite these minor problems, I am very pleased with Mailman and am planning
on running some real mail lists with beta3 very soon (unless something major
At 06:37 PM 6/29/2000, Jim Hebert wrote:
>[re: embed pw and pw-conf as hardcoded, hidden inputs]
>You could use either a server side solution (php, xssi, whatever) or a
>fields random values.
>ashamed at his stupid hacks sometimes =)
I was wondering how the code for random assignment of password is
implemented in the admin's membership mass-subscribe function. What if
there was a reserved word, say RANDU, that the subscription script would
recognize. If you created a subscription box like I did, but in the hidden
field put in RANDU, it would call the random algorithm that is used by mass
subscribe to assign a password for the user.
Those tiny boxes sure are convenient, it would be nice if a little hook
like this could be put in to support it.
My name is Jeff, and I am the founder of MyJokeMail.com, a very popular daily
humor providor. I currently have over 5000 people on my mailing list, but I
figured I would switch to Mailman to maintain my subscription list.
However, now I am feeling like this was a big mistake. Allow me to explain.
All I need is a list where subscribers can write to a generic address (like
jokemail-list(a)myjokemail.com ) and be sent a "Confirm Letter", to which they
respond and are automatically added. I was under the assumption that Mailman
can do that stuff.
Instead, all I see is a program where my subscribers would have to go to a
separate webpage that Mailman provides, and submit their address there.
What's worse is that they even have to have a password. This is nothing like
I though this program would be like.
Another thing: having 5000 people, isn't there an easy way to transfer all
of them over to a file, instead of pasting their names in batches of 30
addresses to the configuration page?
So I guess I am writing this for advice. Does this program do any of the
above things that I am looking for? I dont need my subscribers to have a
password...simply a letter to confirm their subscription request upon
submission. They also shouldnt have to go to a separate webpage, but
instead, could directly email the list for a subscription if need be.
Please help....my list is in desperate need for an upgrade, and I am anxious
to get the ball rolling.
Jeff Mash, Founder
> All I need is a list where subscribers can write to a generic address (like
> jokemail-list(a)myjokemail.com ) and be sent a "Confirm Letter", to which they
> respond and are automatically added. I was under the assumption that Mailman
> can do that stuff.
> Instead, all I see is a program where my subscribers would have to go to a
> separate webpage that Mailman provides, and submit their address there.
> What's worse is that they even have to have a password. This is nothing like
> I though this program would be like.
Of course you can subscribe via email; a message to <list>-request with
"help" in the subject is probably the easiest way to get instructions
on how to do that. See templates/help.txt for what that message
would contain, if you haven't yet installed Mailman.
> Another thing: having 5000 people, isn't there an easy way to transfer all
> of them over to a file, instead of pasting their names in batches of 30
> addresses to the configuration page?
When you say "transfer all of them over to a file", do you mean
"transfer them to be subscribers to the Mailman mailing list by
putting their names in a file and then submitting that file
as input to Mailman"?
The "mass-subscribe" option on the Membership Management page
will take more than 30 at a time, so that's not a limitation
you need to worry about as far as I know...but easier than
that is to use ~mailman/bin/add_members. Read the top part
of that file for documentation.
> So I guess I am writing this for advice. Does this program do any of the
> above things that I am looking for? I dont need my subscribers to have a
> password...simply a letter to confirm their subscription request upon
Mailman requires that your users have passwords; it's simply part
of the program. Many people have asked for this to be configurable,
but it is not yet. But the password can be randomly assigned,
and can be changed by the user through the web page at any time.
Here's a fix that's probably safe, and fixes the "newlist" problem.
Of course I'm not sure if it's the right final fix, but I figure
while Barry's examining the problem, this might be worth a try
for some of you.
The issue is that list.Lock() now wants to reload the list config.db
(with list.Load()), and that doesn't exist in the case of list.Create().
So this fix just catches the "Unknown List" error from Load(),
and ignores it, on the theory that the only time that should
happen is when the list is in the process of being created.
I've installed it on my beta3 production site, and will let you
know if it seems to cause any other errors.
diff MailList.py.orig MailList.py
> except Errors.MMUnknownListError:
-----BEGIN PGP SIGNED MESSAGE-----
Chuq Von Rospach <chuqui(a)plaidworks.com> writes:
>> I've stuck with v1.1 in production systems here.
> I'm making the move from a heavily modified majordomo system, myself,
> so 1.1 was never of interest to me.
I'm also planning to upgrade from Majordomo, though doubtless not nearly
as heavily modified as your own. I've already moved my smaller, lower
traffic lists, but I can't move my two biggest lists until at the very
least I get the announce option that I posted about on the the dev list
a couple of days ago.
I would dearly love to get the bounce handling and web admin for those
lists right now, but for all of how fabulous that would be I just can't
sacrifice the current functionality Majordomo gives me for -announce
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.1 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.5 and Gnu Privacy Guard <http://www.gnupg.org/>
-----END PGP SIGNATURE-----