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
anonymous...!
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.
Thank you!
Mal
Hi,
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'."
Thanks
Mary
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi,
I have Mailman up and running. I just sent an e-mail to 5 lists and
the e-mail came duplicated to the recipients. I checked the header and
the only difference is the following:
1. Header:
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00
autolearn=unavailable version=3.3.1
2. Header:
X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00
autolearn=ham version=3.3.1
How can a avoid duplicates in future? What is the reason?
BR
Marco
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBAgAGBQJVCfIsAAoJEC1y3OsA+e10t2MP/0lS3W8F000CYn4MQ1M7Zfqj
lzJskw5ysngsspQOCZ9kjBuHmh/TGHusZB90wkapMdAwlbuAypQKB6T7L6nwhKy4
xRkCxKJ6hZybb8g5pvatPnODbFfJE96kOAD9d6B1r5hv56FTE+/TG/50/kCQC4do
9AxsoBUD0hNcSwwTjazMGwGZ4NqDDVLXsrauCR02jB+VdqiZgGrGVnQUS6KRHKB+
fOc3VDxh/jbizRCkh8NFQfwW039QnLQyo+HM/pnYQyDcmsfyPg80/TMoyZLhR6PN
NK3AZi+BykM8l7SfyWjmkltHERxYe3ouupQ0wPbWbOY/RCQ0gUUWb28CGZ3HChV6
eypbvPwnXk45WXvQuyhFsU7/KvWVBcb3MNezEm6Q/h5gQyI9FVmEABzjzsvkXxBg
j9WhfiatL3ZN1cpCvb1RPxkP4hZ5YHf1fy9QqgXahLl+nuXSQu7IyKR0vJOXdq00
riB3Su7BWPV/lhaXXV6N9PA2TjjJ69tQ8oOfuB4UTJ19Wme1Zwo6J1pWkjY/xZsL
izz9BrJeMZas2WqyBwHy2/mibyBMmG6nOW1F+FfqXSb/G/GZSA/yMg/5hb0GMgEc
Fbihuiq2TW/TgkPkF+Bx6o+XtKAMA8yVAxrkOEo6YLbD28aga9uAKlai2ypiFQll
6aCeU5gwScRf5mlvnaay
=Fkgv
-----END PGP SIGNATURE-----
Hello,
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
this upgrade.
Here is an example of our mm_cfg.py :
VIRTUAL_HOSTS.clear()
DEFAULT_EMAIL_HOST = 'list.ourdomain.com'
DEFAULT_URL_HOST = 'list.ourdomain.com'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
VIRTUAL_HOST_OVERVIEW = On
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
add_virtualhost('list.customerdomain.com', 'customerdomain.com')
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
limited :
./configure --prefix=/usr/lib/mailman
--with-var-prefix=/var/lib/mailman --with-cgi-gid=apache
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
configuration lines.
--
Regards,
Chris
Chris Miller
President - Rocket Scientist
ScratchSpace Inc.
(831) 621-7928
http://www.scratchspace.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
I have several mailing lists on a Mailman server which are
synchronized with a database via a cronjob.
Now my question: is it possible to not only synchronize the e-mail
adresses but also the names?
BR
Marco
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Icedove - http://www.enigmail.net/
iQIcBAEBAgAGBQJVE9tLAAoJEC1y3OsA+e10PJIQAJaFxuLSFHjy7NJObs9B4U5i
v/Yv2OdqR/RRN+5yRq9sUfOu8PUyXuXpdS7g67OgUID9PAueAEasnVQOHSjAgxD2
+ChRTp3wh8Aomfzr4UTqiflEcmW6BGE+I1xFxNd6KzdR24ampf2Vz7ogzkzM2HGB
IK0tvTk9t9/IUKqedzf4lzsMFs4rTEIyuCUMje9IRwwIZVn/dCpjIfd+cbk0W6b1
tl1Mdd83vajzanf3ncLUG2/Sk8Cjm4kdHVYFQbT92jcR4wV+esjHBNClCDO41rJO
JXb9/2bKd4C9XcRVP3Vz18mm3ogyn+C126TQLi1y+GauitqZqa+Yypjr76+C415D
e4O2AVDbyRAkBSz/pSw07T4Og4pGjxUmGIM3WJZPDY01b9wSg8y5J7LaLbTZHS7F
MbaPiZ6tQNQEmP6zxp40GRp//ZuWI6TBVhNAYnj3MuKROz0+pNjGprV83maYOCtp
9LX52d5Bkyc7WuAW8lFJ9OnxUWsTD0YcmNM3JXaEe5KAdJL1TI1rV7iMmQQy411a
iXVWez1Q2OgQ7cnbw67kMOlkbtI9X5BRygDXO3TnvbiYV/tn//Rrzf9gKVUvc9Qt
HK4vpINMF+0eBlg2lQGEh/b/C05UH5zVhK4t3fXNLSJ+8thxsLJz10S91ehuxgTH
Plblbk7bIHBvT7OPxuXu
=lpm4
-----END PGP SIGNATURE-----
When I reply to a message on a mailing list, what is the “right” way to do it?
Should I be deleting previous thread text from my response?
Should I be adding anything in?
Is there some general ideas for the “right” way to reply to a message on a list?
as
I am pleased to announce the release Mailman 2.1.20.
Python 2.4 is the minimum supported, but Python 2.7 is recommended.
This release has one new feature, a few bug fixes, an update to the
Polish message catalog and a fix for a recently discovered security
vulnerability.
See the attached README for more details.
Mailman is free software for managing email mailing lists and
e-newsletters. Mailman is used for all the python.org and
SourceForge.net mailing lists, as well as at hundreds of other sites.
For more information, please see:
http://www.list.orghttp://www.gnu.org/software/mailmanhttp://mailman.sourceforge.net/
Mailman 2.1.20 can be downloaded from
https://launchpad.net/mailman/2.1/http://ftp.gnu.org/gnu/mailman/https://sourceforge.net/projects/mailman/
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi Mark.
Mark Sapiro wrote:
> This is a Debian packaging issue. If it were an issue with Mailman
> per
I do not understand.
I set
IMAGE_LOGOS = '/mailman/images/'
in mm_cfg.py
Then the html returned by http://mydom.ain/mailman/listinfo
reads
<table WIDTH="100%" BORDER="0">
<tr>
<td><a href="http://www.gnu.org/software/mailman/index.html"><img
src="/mailman/images/mailman.jpg" alt="Delivered by Mailman"
border="0" /><br>version 2.1.15</a></td>
<td><a href="http://www.python.org/"><img
src="/mailman/images/PythonPowered.png" alt="Python Powered"
border="0" /></a></td>
<td><a href="http://www.gnu.org/"><img
src="/mailman/images/gnu-head-tiny.jpg" alt="GNU's Not Unix"
border="0" /></a></td>
<td><a href="http://www.debian.org/"><img
src="/images/mailman/debianpowered.png" alt="Debian Powered"
border="0" /></a></td>
</tr>
</table>
at the bottom. Note how the path is different for the last image
/images/mailman/debianpowered.png
instead of /mailman/images/debianpowered.png as is for the other three
images.
I do not see how packaging can influence the html produced by
Mailman's python code.
Best wishes
Roland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVGxLAAAoJELxQU5sfwHE5V5wH/1WAiugoei8Qfpvi2QoK0aSY
iRqhMjWnytaZhvi7wQUynU9rFhGHKK6RuV9nYv3EroE+y8O8wkc5txR0UhApibRs
GowmxrllJDCBmAOnpg3Z0+A0vRpnBm07SoNiaZ98OS4a34o6RWhNlcM/xDFL28a4
11BgaBOESWLDm/U6IyclGNTASHbL0NnOubw5q09ksRH2O3PNdh6+mvANHMzRhSrx
XdEYTYCnRpxV29fXlsMaRjRiid5Mn/duhIdVUakC/wYggShlKMhnFDRfqbYJJWiz
HN4DfDCKxnT8xnlBC/LLiDRkhhDFeTNYtRO3YkVncMj8QMihj2KnBBNfS4B4ie8=
=+4z6
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello Mailman developers,
There is a small bug I noticed when configuring Mailman on my Server
with some unusual URL paths.
The four images at the bottom of the Mailman page
mailman.jpg
PythonPowered.png
gnu-head-tiny.jpg
debianpowered.png
all reside in the same Linux directory /usr/share/images/mailman/
The first three are addressed via the path variable IMAGE_LOGOS.
Only the fourth image has the fixed address
/images/mailman/debianpowered.png
independently of how I define the variable IMAGE_LOGOS in mm_cfg.py
I worked around this bug by adding
Alias /images/mailman/ /usr/share/images/mailman/
to my /etc/apache2/conf.d/mailman.conf
Sorry, I do not know how to properly report bugs nor whether this is
of any interest at all.
Anyways, thanks for all the good work!
Roland
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
iQEcBAEBAgAGBQJVGvtsAAoJELxQU5sfwHE5W04H/ipJPaC3QIl8kRcLlZy+Ss0e
XIVDyrldfJ3jH+rz5Xlo0nFd8S9A3wg1mSh66JagHr3Ag6HaKRQuHRP+cQAQvrjV
Obcs1MrNXYAz1Td1S9yibi/yj7a3YBQZwpS2Yytep689/Xw53fM9DH2ZMUPeb9KK
lqSIuxl2IzCEz1C6Pw5VqTzKDb0SmDeUtq9YPM8DLq97CZzUaltvkM1VlS6mmcuS
KbzPG+07GbsR6dUpeLNWkhKNRggudMacnIfxdEBi31JV/pheaA4KJbYxpArtXKpp
7eLjMfEgSEcpP0VIDHTa3xVtzNerv+5/lHUBoeN4y9woU3GWVauozBNyC1i5TAE=
=aU5H
-----END PGP SIGNATURE-----
A security vulnerability in Mailman has been found and fixed. It has
been assigned CVE-2015-2775. The details of this vulnerability and fix
will be announced next Tuesday, 31 March 2015, at which time both a
patch for this specific vulnerability and Mailman 2.1.20 will be released.
In addition to this security fix, Mailman 2.1.20 includes a new feature
allowing a list owner to change a list member's address through the
admin Membership Management... Section, and a couple of minor bug fixes.
The new feature is a fix for <https://launchpad.net/bugs/266809>.
The bugs fixed are: <https://launchpad.net/bugs/1426825>,
<https://launchpad.net/bugs/1426829> and
<https://launchpad.net/bugs/1427389>.
The security vulnerability, the details of which are currently private,
is <https://launchpad.net/bugs/1437145>.
The security vulnerability only affects those installations which use
Exim, Postfix's postfix_to_mailman.py or similar programmatic (not
aliases) MTA delivery to Mailman, and have untrusted local users on the
Mailman server.
--
Mark Sapiro <mark(a)msapiro.net> The highway is for gamblers,
San Francisco Bay Area, California better use your sense - B. Dylan
