I have created a list that requires email confirmation. Right now, a new
subscriber receives an confirmation email, clicks on the confirmation link,
and is sent to a page where they must click on "Subscribe to list" to
confirm their address. I would prefer it if subscriptions were confirmed
immediately upon clicking the confirmation link. Any suggestions would be
How do I get a full list of subscribers via the Mailman web control panel
(sadly 2.1.15 because Namecheap still haven't upgraded)?
Sorry for such a newbie question, but the arguments with my shared hosting
service have turned my brain to jelly.
I can see the subscribers 100 at a time, but I want to get a full list,
preferrably with everyone's settings, and ideally as a text file or
I am forced to move my list because the host has decided that they will
count each outbound message from the list as a separate email, so I violate
the 200 per hour limit every time someone posts or responds ... we have
over 900 active members.
I am using Mailman version 2.1.12.
One of my list admins have complained that he's list does not send out digest mails, which is most likely because he set digest_size_threshhold to 1000.
But he also complains that no digest mails are being sent when he set _send_digest_now to Yes.
He also set digest_send_periodic to Yes.
We're confused that the digest_send_periodic text is saying "Should a digest be dispatched daily when the size threshold isn't reached?" as he wants the digest to be sent weekly as set in digest_volume_frequency.
The /var/log/cron shows that the /usr/lib/mailman/cron/senddigests is being run daily at noon.
1) Where can I see if digest mails are in fact being sent out?
2) Where will Mailman log digest issues?
3) Does the digest_send_periodic daily affect the digest_volume_frequency weekly?
Systemadministrator, Core Services
UNIVERSITY OF COPENHAGEN
Corporate IT, Operation & Support
Nørregade 10, P.O. Box 2177
DK1017 Copenhagen K
Tel: +45 35322626
Dir: +45 35322704
Fax: +45 35322707
I am new to the list and new to mailman. I have Mailman extracted to its
own file on Ubuntu but I do not know how to setup the software or to start
it. I reviewed the GNU Mailman - List Admin Manual but did not see how to
start the software. I have Ubuntu running on a virtual drive. Any help
We've discovered that if scrub_nondigest is set to Yes, the text of html messages (perhaps html-only?) is removed and replaced with a link to it. When users follow the link, the html tags in the text are visible because the angle brackets have been replaced with html codes.
Is there a way to prevent scrub_nondigest removing these message parts? Is there a way to at least stop the angle brackets getting converted to codes?
Further info on the problem is that the list admin just released 47 mails 30 minutes ago (please note that the digest_size_threshhold is now = 0, was previously 1000). Until now the list have sent 22 digest-mails with a single mail in each digest mail, all named Volume 20, but with increasing Issue number from 1 to 22. The numbering is expected, but the mails should've been send as a collection, not as individual mails.
Right now the settings are
nondigestable = True
scrub_nondigest = False
digestable = True
digest_is_default = 1
mime_is_default_digest = 0
digest_size_threshhold = 0
digest_send_periodic = 1
digest_header = ''
digest_volume_frequency = 3
There is no /var/lib/mailman/lists/LISTNAME/digest.mbox for the list in question, or any other list. Though I don't know which other lists do send digest mails.
The list admin now have Emergency-moderated the list. I guess this is just to stop all incoming traffic from being sent out, and have no effect on what the list admin do release, right?
Fra: Henrik Rasmussen
Sendt: 12. august 2014 09:32
Til: Mark Sapiro; mailman-users(a)python.org
Emne: SV: [Mailman-Users] Mailman digest issues
On 08/12/2014 03:00 AM, Mark Sapiro wrote:
>On 08/11/2014 06:15 AM, Henrik Rasmussen wrote:
>> I am using Mailman version 2.1.12.
>> But he also complains that no digest mails are being sent when he set _send_digest_now to Yes.
>Did he press "Submit Your Changes" after setting _send_digest_now to Yes? If so, and if there were digested messages and digest members with delivery enabled, something else is wrong.
Yes he did. I did too, afterwards.
>What response did he get when pressing "Submit Your Changes" after setting _send_digest_now to Yes? What's in Mailman's error log.
I got the message "There was no digest to send". No messages regarding this list in /var/log/mailman/error (or any other log in this directory for that matter).
The smtp log show that the list do send message (to normal-members I guess), but I can't verify if messages are sent to digest-members. The list admin say no mails are sent to digest-members.
>> He also set digest_send_periodic to Yes.
>> We're confused that the digest_send_periodic text is saying "Should a digest be dispatched daily when the size threshold isn't reached?" as he wants the digest to be sent weekly as set in digest_volume_frequency.
>digest_volume_frequency has nothing to do with how often periodic digests are sent. It only controls how often the vvv is incremented and ii is reset in the "List_name Digest, Vol vvv, Issue ii" >Subject: header of the digest.
I am still confused, even after reading section 2.6 in http://www.gnu.org/software/mailman/mailman-admin.pdf. In my understanding, (and I know I'm wrong here) if the volume number is changed weekly, but digest mails are sent daily, all digests will contain the same volume number all week long. What is the difference between volume number and issue number, and when do Mailman send what?
>> 1) Where can I see if digest mails are in fact being sent out?
>Your MTA logs and Mailman's smtp log. Also, digest messages are accumulated in lists/list_name/digest.mbox, and when a digest is sent, this file is removed.
How can I tell normal from digest? Will the digest mails mention Digest I the SMTP log. If so, no digests have been sent.
>> 2) Where will Mailman log digest issues?
>Mailman's error log and in the output from cron/senddigests (for periodic digests.
No errors in the error log. Cron/senddigests -l LISTNAME. However, shows
[root(a)mailman.example.com]# /usr/lib/mailman/cron/senddigests -l Sci-diku-imageworld
Traceback (most recent call last):
File "/usr/lib/mailman/cron/senddigests", line 106, in <module>
File "/usr/lib/mailman/cron/senddigests", line 84, in main
mlist = MailList.MailList(listname, lock=0)
File "/usr/lib/mailman/Mailman/MailList.py", line 130, in __init__
File "/usr/lib/mailman/Mailman/MailList.py", line 626, in Load
>Note, that often the output, if any, from Mailman's cron jobs is mailed to the 'mailman' user which happens to be the site list. If the site list is not configured to accept non-member posts, and the >site admin is not a member of the site list, this output is often lost.
>You can either set the site list as above or add a MAILTO= directive with a deliverable address to Mailman's crontab.
>Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
I have forgotten my password on a couple of ancient mailman lists
which I started many years ago and which occasionally get spam posts.
(a) Is there any way of finding (or changing) the password
without superuser privilege?
(b) If one does have superuser privileges what is the simplest way
to change the password on a mailman list?
(I still have this privilege since I used to run the system,
but prefer not to use it if it can be avoided.)
e-mail: gayleard /at/ eircom.net
School of Mathematics, Trinity College, Dublin 2, Ireland
Hello, Mailman experts.
I've been doing some development work for a Tokyo-based NPO that offers
participation in a number of Mailman lists as one of the benefits of
membership in the organization. Because membership in the organization is a
requirement for participating in the Mailman discussions, the organization
has not been providing members with direct access to the Mailman
administrative features for subscribing and unsubscribing, but instead has
been providing a homegrown administrative interface that uses PHP and curl
to simulate user interactions via POST.
When a recent update to Mailman introduced CSRF tokens, however, this
approach broke down and the organization has been struggling to figure out
how to manage the lists ever since. We know that Mailman 3 provides an API,
which is exactly what we need, but because the site and Mailman lists are
both on shared hosting, we are currently only able to use Mailman 2.1.x.
Can anyone recommend a good approach to managing subscriptions in an
automated way using either PHP or Python until such time as we can get our
host to upgrade to Mailman 3?
Any suggestions or pointers would be greatly appreciated.
With many thanks in advance,
Can Held Messages be Accept-ed via an email message, by
including the list password in the body of the message?
For example, as list Moderator, I receive the Held Message
The test(a)corp.com mailing list has 1 request(s) waiting for your
Please attend to this at your earliest convenience. This notice of
pending requests, if any, will be sent out daily.
From: kenny.thomas(a)onlinesalesdata.com on Wed Aug 6 13:21:46 2014
Subject: Attention Required
Cause: Post by non-member to a members-only list
Is there a way to send email to test-request(a)corp.com to Accpt the
Thanks in advance,