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 use the moderator web page with Firefox, and it stays logged in for as long as I keep the browser open. But with Safari on iPhone and iPad, I often have to log in again when I return to it. Same for every other browser I've tried under iOS. Can anyone tell me why?
-----BEGIN PGP SIGNED MESSAGE-----
I have 2 simple questions about mailman mail lists:
1). I can see there is an option to receive monthly reminder of
password, and the password is sent in plain text. Is the password in
plain text visible to the mail list owner / administrator? Or mailman
stores a secure hash of the password like sha-256 or ripemd-160? If
the password is stored in hash format, how come I can receive it
monthly in plain text?
2). If an email address works for some time but becomes suddenly
invalid (e.g. server down, domain cancelled, etc.) and when messages
are being sent to that address they bounce back with permanent
failure, will mailman remove these email addresses automatically? If
yes, after how many attempts of sending? What if the email address
server is just down for a day or something.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)
-----END PGP SIGNATURE-----
(Context: running MM 2.1.12, works great...)
I know why allowing subscriptions without either a confirmation email or a moderator approval is a Dangerous Thing, but is there a way to get MM to allow it? Our list subscriptions are mostly generated by our lab/tool management software in response to a user getting qualified to use a piece of equipment, and I don't want users to have a choice in this case - they get subscribed, period. (They can later unsubscribe of course, but that means they have to actually do something :)
Does this make any sense?
Michael P. Young (574) 631-3268 (office)
Nanofabrication Specialist (574) 631-4393 (fax)
Department of Electrical Engineering (765) 412-6728 (cell)
University of Notre Dame mike.young(a)nd.edu<mailto:email@example.com>
B-38 Stinson-Remick Hall
Notre Dame, IN 46556-5637