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'."
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
Is there anything open-source to make a Mailman legacy archive searchable?
What would be useful is a way for visitors to a website to be able to
search the Mailman archives using a keyword and have it display those mail
messages. I'm also thinking of having a tag cloud made up of the most
commonly used words from the given Mailman archive. So when one of those
tag cloud words is clicked on it lists as an index those messages. Any
Today I check the subscribers list ("Membership Management...
Section") on one of our lists and called up
the legend using "Click here to include the legend for this table."
After clicking on that link, the page did indeed display the legend,
but the page now starts with:
Error: The form lifetime has expired. (request forgery check)
Ralf Hildebrandt Charite Universitätsmedizin Berlin
ralf.hildebrandt(a)charite.de Campus Benjamin Franklin
http://www.charite.de Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
My mailing lists run on a relay server installed as per FAQ 4.88
Accessing the web interface across the internet works fine but accessing
while on the host network is not so fine.
Instead of the DSL (dyndns) address I use the server name or IP address
and all goes fine unless I query the mailing list addresses. Then i am
returned to login again and so on ad infinitum. Same if I try to list
I note that when I mouse-over the menu options the browser bottom line
shows the server name (or IP) address that I have used. When I
mouse-over the 0-9A-Z membership listing then the DSL forwarding address
FAQ 4.29 would indicate that I could change the DEFAULT_URL_HOST setting
for existing lists using fix_url.py - in this case perhaps to the IP
I suppose that would foul up admin access from across the internet but
as that is only me we could live with that.
Before fools rush in where angels fear to tread - is this the way to go?
Maybe there is a route to have the best of both worlds (easy access from
the internet and the local network)
many thanks in advance
I used the following when setting up Mailman 2.14:
./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=www --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python
To upgrade PHP from 5.2 to 5.3 the website hosts have to enable suexec (I don't quite understand this but bear with me!) which breaks Mailman, I think because it runs as a different user to before.
Can I reconfigure Mailman using this?
./configure --prefix=ZZZ/mailman --with-mail-gid=daemon --with-cgi-gid=users --with-username=ZZZ --with-groupname=users --with-python=ZZZ/bin/python
This is the with-cgi-gid setting that the hosting people suggest, but I would be grateful for confirmation from someone on this expert list.
What else would I need to do?
Thanks very much in anticipation.
I'm trying to setup an mailman on an existing mailserver. I want to use
the same domain as I'm using for normal mail.
But putting VIRTUAL_MAILMAN_LOCAL_DOMAIN = 'localhostasd' in my
mm_cfg.py file. But no @localhost is added to every row in
I'm using the stock mailman found on CentOS, version 2.1.9.
We are a scout group with 50 Mailman lists for different groups. The members
of the lists are automatically imported from our member-system every hour.
This works like a charm.
One of the lists (Alla) contains all members and I would like to limit the
senders for all other lists using this list Alla.
When I put @Alla (the name of the list with all members) in the
accept_these_nonmembers-field for any list I get an error message:
Error: Bad email address for option accept_these_nonmembers: @Alla
We are running Mailman 2.1.9 on CentOS 5.2 and there are no upgrades for
Mailman in the repos.
What is the reason for the errors and what should I do to limit senders to
If it is related to the version of Mailman, is there a patch or workaround
and does someone know a repo I could use to upgrade?