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?
I run a mailman system for a number of mailing lists. Recently I've
noticed that a number of our pages aren't fully translated, when I think
they probably should be. The server is a Debian 7.2 (wheezy) server and
Mailman is 2.1.15. Python is 2.7.3, if that's of any use. There's
nothing obvious in the 'error' log in /var/log/mailman. Any other logs I
As an example:
You can see that the top is in English and the bottom is in Portugese
Can anyone give me any useful pointers as to what can be done to fix? My
google-fu has rather failed me on this one.
Open Knowledge - www.okfn.org
Skype - notmatt
On 07/11/2014 19:42, Mark Sapiro wrote:
> On 11/07/2014 03:52 AM, Hal wrote:
>> For not allowing text/html
>> But does the above apply to *all* archived postings, or does it only
>> filter anything that comes in from now on?
> It applies to all posts that arrive after you make those settings, buth
> in the archive and in the messages delivered to the list. It won't
> affect messages already archived or in the mylist.mbox file, even if you
> rebuild the archive.
That's fine, but good to know for later.
So for any new messages from now on I want my list to work this way:
1) HTML formatted postings should be converted to plain text before
reaching other members.
2) HTML formatted postings can retain their formatting for the archive
(I believe the archive is in the HTML format anyway?), but if it only
archives whatever is sent to list members I don't mind. The important
thing is that members receive plain text messages.
3) Since many people have their email programs set by default to send in
HTML these days I just want Mailman to do its filtering, then continue
by sending the posting as plain text without any moderator request or
alerting the sender.
4) I'd like to block all attachements (list members should only receive
plain text files).
40kb is already set for Max_message_size (in "General options" within
the list administration web interface) which seems to have worked fine
(as far as I know).
Furthermore I understand that Filter_filename_extensions (in the
"Content filtering" section) in addition removes any attachements based
on specific filename *extensions* regardless of their file size?
I see exe, bat, cmd and a bunch of other filetypes I've never heard of
(geared towards Windows/DOS users I suppose -I'm a Mac user) are listed,
but I suppose I could block .zip and those pesky .vcf/.vcard and
"winmail.dat" files the same way.
When such extensions are encountered, are they just removed from the
messages while the message posting itself is passed on to list members,
or is the whole posting stopped for approval first?
I'm thinking out loud here, so feel free to chime in for better ideas,
but I'm thinking there are two kind of attachement groups which need
different actions to be taken:
Deliberate attachements: zip files, gif/jpg images etc. which a poster
wants to share. The message/attachement should be stopped from reaching
the list and an email sent to the poster with a "your message has been
blocked. Please resend your message, this time without an attachement"
type of message.
Accidental attachements: winmail.dat, .vcf or .vcard an so on. Many
users don't know (as with HTML postings) that their email program is set
up to send this stuff. IMHO those attachements don't have anything to do
with the actual content of their postings, so Mailman should just remove
the attachement(s), then pass on the rest of the message to the list.
Having said that, have I understood things correctly by setting up my
"Content filtering" options as follows? (based on what you've said and
what I've read here:
Filter_mime_types: (left blank)
pass_filename_ext.: (left blank)
>>> A different obfuscation for email addresses would require source code
>>> modification. I.e., there's no 'plugin' for it.
>> Is this a feature that could be suggested for the upcoming Mailman 3?
>> Perhaps an optional user-configuration through the web admin interface?
> Mailman 3 uses different and 'pluggable' archiving. The archiver that is
> bundled with MM 3 is called Hyperkitty. I'm not sure what address
> obfuscation it does.
Thanks. I'll look into it.
>> Failing that, is there a way I could have the (currently private)
>> archive have a filter before HTTP access?
> You could create your own CGI or other web process to access the
> archives and present them any way you want.
Being ignorant on the subject, what kind of pre-written CGI script
should I try to find (i.e. "search engine to web archive gateway" or
something like that?).
You previously suggested htdig (http://www.htdig.org/) with your patches
for allowing my visitors to search through both the Mailman archives and
my website. Assuming this is a more ready-to-use solution than the other
search engines out there, are there features I will be missing out on
(e.g. the ability to use CSS and Ajax for making its search results
appear more in line with the rest of my website) and is it still secure?
I've read that malicious code can sometimes be entered as search phrases
and damage the database if the search engine isn't using "parametrized
I've found other search engines (Nutch, Lucene, Solr, Tipue search,
Xapian and Ajax live search) but I have no idea if they're suitable for
my use and how well they work or how difficult they are to set up.
Opinions from anyone are highly appreciated.
Hi, I know from past experience that the OS X version of Mailman is met with some contempt because of what Apple did with it .. but I have it working well for several years on a 10.7.5 Lion Server, and it has been very stable.
However, I want to explore hosting some of the virtual domains I have setup on my server.
Hosting multiple virtual domains without any issues, however want to start using mailman with some of those virtual domains.
I saw this support article at:
Mac OS X Server v10.6: Configuring the Mail service so Mailman can support virtual domains - Apple Support <http://support.apple.com/en-us/HT3878>
but this is for 10.6 ... looks like it "might" work for 10.7 ...
Paths look the same ... anyone have any ideas?
If it does work, will mail from that mailing list show originated from the virtual, versus "real" domain?
I found this, so it seems that there is no single way to change the site admin contact address, as messages seems to be associate with the list admin, according to the %(owneraddr)s in the bounce.txt
Fra: Henrik Rasmussen
Sendt: 28. november 2014 12:55
Emne: Custom contact address, not site admin
Some standard mails from Mailman, like "bounce action notice", urges the user to contact the Mailman site-list address*). While I still want system mails, meant for the site admin, to go to the site admin address, I would like to customize the contact address displayed in mails and on the web GUI, to show our helpdesk e-mail address instead.
Normally I would edit the file /usr/lib/mailman/messages/uk/LC_MESSAGES/mailman.po and run /usr/lib/mailman/bin/msgfmt.py /usr/lib/mailman/messages/da/LC_MESSAGES/mailman.po, but not all messages can be customized this way.
What is the best way to customize the site admin contact address in each e-mail and web-gui page, to display our helpdesk contact address?
*) Example of standard mail from Mailman: "Questions? Contact the Mailman site administrator at mailman(a)list.example.com<mailto:firstname.lastname@example.org>."
I currently have Mailman 2.1.14 installed in the website directory of a.com
I would like to:
1. Upgrade it to 2.1.18-1.2. Have it outside the website directory.3. Use it not only for a.com but also b.com (I will not need to have the same list names for both domains).
If I were to install from scratch outside the websites' directories, I imagine it would be simple enough to get it to work for b.com.
But what would I need to do to get the a.com mailing list to start using the new Mailman installation? (Would I just be able to move certain files across to reproduce the archive, etc?)
I am sorry for asking such a basic question, and would be happy to be directed to the right FAQs on the subject(s).
Best wishes and thanks