I want all mails sent to the list to come from the list's email address...
But, in this case, if the user forgets to sign their name at the
bottom of their mail body, effectively the mail to the list is
Is there a way to add the user name (or email address) to the top of
each mail so that the mails have the name of the sender, while the
mail itself comes from the list address?
I have looked high and low for an answer, but noone seems to have the solution.
I received the following error this morning. So I rerun configure again with the following command: ./configure --with-cgi-id=apache --prefix=/var/mailman. I'm still getting the same error. Is there any place that I can look for so that I can debug this problem better? Perhaps, looking at the config history file or something. Any other places that I can check the cause of this error?
"Mailman CGI error!!!
The Mailman CGI wrapper encountered a fatal error. This entry is being stored in your syslog:
Group mismatch error. Mailman expected the CGI
wrapper script to be executed as group "nobody", but
the system's web server executed the CGI script as
group "apache". Try tweaking the web server to run the
script as group "nobody", or re-run configure,
providing the command line option `--with-cgi-gid=apache'."
we recently updated our (vhost patched) Mailman installation
from 2.1.14 to 2.1.18-1 (https://launchpad.net/~msapiro) in order to
workaround Yahoo's recent change to their SPF policy that this
version addresses. Virtual mailing list hosting worked fine up until
Here is an example of our mm_cfg.py :
DEFAULT_EMAIL_HOST = 'list.ourdomain.com'
DEFAULT_URL_HOST = 'list.ourdomain.com'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
VIRTUAL_HOST_OVERVIEW = On
If we change the default values above and run the below command, the
available mailing lists move from the old default to the new.
bin/withlist -l -a -r fix_url --
All add_virtualhost configuration lines are ignored.
Since withlist is able to read the changes in our mm_cfg.py, this
does not strike me as an issue with our configure options which were
I am unaware of a method we can use to further debug this, such as a
command that would effectively dump out Mailman's configuration
options, thus validating if it is even reading the add_virtualhost
President - Rocket Scientist
On 05/10/2013 06:35 AM, Xie, Wei wrote:
> Here we have one customer to request migrating all old archived files of
> mailing list ‘kinejapan’ under directory
> /usr/local/mailman/archives/private/kinejapan prior to 2009 (as attached
> file) to Yale university. Yale university IT guys needs us to create a
> mbox file for these old archived file to be easy for them to run
> command ‘archdo migration.
> I check there is no file kinejapan.mbox under directory
> /usr/local/mailman/archives/private/kinejapan.mbox to match these old
> archived files as attached. This mailing list was maintained by our
> pre-mailman admin, who passed away 2011, so I do not know why the mbox
> file was missing.
If ARCHIVE_TO_MBOX is set to 0 in mm_cfg.py, Mailman will not
create/update LISTNAME.mbox/LISTNAME.mbox files.
> Do you know whether there is a tool/method to convert these old archived
> files/directories as attached into a mbox file?
Lots of information is lost if there is no .mbox file.
You can do as well as anything with
cat /usr/local/mailman/archives/private/kinejapan/*.txt > kinejapan.mbox
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
Bug in Mailman version 2.1.15
We're sorry, we hit a bug!
Please inform the webmaster for this site of this problem. Printing of
traceback and other system information has been explicitly inhibited, but the
webmaster can find this information in the Mailman error logs.
The above message shows up on the web pages, unfortunately the last log written
to is qrunner, error is empty, so no info on what it is about.
The last thing changed is the adres of the main pages.
It looks like the mail-system is not affected, any idea what is going on?
Would like to show some logging, but it simply is not there.
Linux-User #469851 with the Linux Counter; http://linuxcounter.net/
Antw.: Omdat het de volgorde verstoord waarin mensen tekst lezen.
Vraag: Waarom is top-posting een slechte gewoonte?
Vraag: Wat is het meest ergerlijke in e-mail?
Why be difficult, when with a bit of effort, you can be impossible?
Have had to do some tracking of mailman activity for management. I'm familiar with the mailman logs, web server access_log, and linux sendmail logs.
Is there any place where the flow of mail into and out of mailman, along with when log entries are made, documented anywhere? Especially a moderated message. Qrunner activity, that kind of thing. I've poked around the FAQ and other things online, but didn't find much. I did find some mailman 3 info though (I'm 2.1.7)
I'm maintaining and moderating a couple of Mailman lists and when I was
looking for an easy moderation tool, I've stumpled upon 'Mailman Moderator'
for iOS . Unfortunately the app isn't quite stable  and the original
programmer isn't working on it anymore.
After exchanging a couple of mails, he agreed to open source it here (MIT
Maybe somebody else will pick it up and polish it a little.
With kind regards,
: It often crashes after moderation, no loading indicator, setup is
finicky (If you're not putting the base url exactly to
admindb/mailinglistname, it fails), the icon could be nicer.
(In Wirklichkeit gar nicht anwesend.)
I'm about to migrate a Yahoo Groups mailing list to mailman. Yahoo
Groups offers four delivery modes:
- individual emails
- daily digests
- no mail
- special announcements only
and I have list members set to all four of them. The first three I can
easily deal with, but I'm not sure how to handle those set to the last.
As far as I can tell, the only difference between a Special Announcement
and a regular post in Yahoo Groups is that a moderator can tick a
checkbox when writing a Special Announcement on Yahoo's web UI.
I've scanned the FAQs and can't see anything obvious about this, nor can
I see anything in the mailman web UI. I could just decide not to support
this special announcements feature, but if I wanted to support it, what
would be a good approach? The only thing I can think of would be to
create a second list, mylist-announce, and subscribe everyone to that as
well as mylist. But that makes user management tricky, requires new
members to subscribe to both, unsubscribe from both, etc.
Have I missed something obvious? If not, is there another, simpler,