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
I'd be interested in how others have implemented this. Here are the options I've identified so far, with some questions.
* FUDforum - http://www.fudforum.org/forum/
This is a forum with a 'mailing list manager' admin page. For me, the script to send list emails to the web forum only works from the command line, and I can't get postfix to pipe emails to that script (or, at least, I can't get the script to do anything).
Has anyone got over that problem? I've asked on their own forum but no response yet.
* Groupserver - http://groupserver.org/
It looks like an absolute beast to install but is a combined mailing list/web forum. I would would prefer not to leave Mailman so wonder...
When is Mailman 3 likely to be released (roughly) and - if that is ages away - what are the chances of being able to migrate 'back' from Groupserver to Mailman 3?
* PHPBB - https://www.phpbb.com/
They say there is no mailing list feature with version 3.
* Tikiwiki CMS Groupware - https://info.tiki.org/
This has a forum which apparently can mirror a Mailman list - has anyone tried this?
Sorry for all the questions. Answers to any of them would be appreciated!
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
The internal documentation in the admin screens for 2.1.18 is a bit
confusing with regard to Reply-To munging.
In the doc for the from_is_list option we have "It replaces the poster's
address in the From: header with the list address and adds the poster to
the Reply-To: header, but the anonymous_list and Reply-To: header
munging settings below take priority."
Which Reply-To: header munging settings take priority, and how should
one set them so that they don't override from_is_list?
If dmarc_moderation_action overrides from_is_list, as the doc for it
says it does, is it also overridden by Reply-To: header munging
Also, in the doc for reply_goes_to_list, we see "When set to Poster [the
default], no Reply-To: header is added by Mailman". Does this mean that
this overrides from_is_list, which if set says that it causes the
original From header to be inserted into the Reply-To header?
I can probably figure this out, but it might be good to explain this a
bit more completely in the Mailman internal docs. It's not really clear
exactly how these options relate, and how the precedence of settings is
organized. These may be stupid questions, but I can just about
guarantee you that all my list admins will trip on them :(
Lindsay Haisley | "Everything works if you let it"
FMP Computer Services |
512-259-1190 | --- The Roadie
For a list I recently migrated from 2.1.14 on one machine to 2.1.17 on
another, I'm unable to approve pending subscription requests. After making
my choices and clicking "Submit all data", the radio buttons simply reset
themselves with no changes made to the subscriber records.
"check_perms -f" and "check_db" make no complaints about my configuration.
Is this a bug? Could something have gotten botched in the migration? The
lists seem to be operating fine otherwise.
What does this error message mean? "low level unrecoverable exception"
I just installed my own build of mailman 2.1.16 (built under CentOS 5 x84_64)
as an upgrade over the stock 2.1.9 that comes with CentOS 5 and I am getting
this error. What should I be looking for?
Robert Heller -- 978-544-6933 / heller(a)deepsoft.com
Deepwoods Software -- http://www.deepsoft.com/
() ascii ribbon campaign -- against html e-mail
/\ www.asciiribbon.org -- against proprietary attachments