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
I'm updating Mailman from 2.1.19 to 2.1.34 from source. When I run configure
./configure --prefix=/var/lib/mailman --with-username=list
--with-groupname=list --with-cgi-gid=www-data --with-mail-gid=list
I get an error that dnspython is not installed
checking dnspython... configure: error:
when I then try and install dnspycthon using pip, I get
Requirement already satisfied: dnspython in
/usr/lib/python2.7/dist-packages
Help (please)! Thank you in advance.
Hi all,
I'm running mailman 2.1.x. I haven't had need to create a new list in years, but now I need to. Trying to do so from the web UI here:
<https://mail.rogue-research.com/mailman/create>
results in:
"Error: Unknown virtual host: mail.rogue-research.com".
After searching for this, I now have a partial understanding of the problem.
In my Defaults.py I see:
DEFAULT_EMAIL_HOST = 'foo.rogue-research.com'
DEFAULT_URL_HOST = 'foo.rogue-research.com'
DEFAULT_URL_PATTERN = 'http://%s/mailman/'
foo is the real hostname of the machine. I guess that's how it ended up there? After reading the comments in that file and FAQ 4.29, I *think* the correct solution is to append the following 5 lines to my mm_cfg.py:
DEFAULT_EMAIL_HOST = 'rogue-research.com'
DEFAULT_URL_HOST = 'mail.rogue-research.com'
DEFAULT_URL_PATTERN = 'https://%s/mailman/'
VIRTUAL_HOSTS.clear()
add_virtualhost(DEFAULT_URL_HOST, DEFAULT_EMAIL_HOST)
Is that correct?
Many thanks,
Sean
I am not sure how to figure this out.
Lengthy explanation:
Internally in our Exchange server, that address is a distribution group whose only member is the actual <list-name>@lists.pharmacy.arizona.edu, because the Mailman server is not our mail server. (we have a mildly complicated setup: hybrid OnPrem and O365 exchange + Barracuda spam appliance in front of all of it, which is our actual SMTP server.
Outgoing email from the list server bypasses Exchange and is sent directly to the Barracuda SMTP server.
For two users and ONLY these two users, somewhere between them and mailman and back, the Mailman list is being expanded to put all the members of the list on the CC line. It then gets held for approval with a ’too many addresses’ message.
I have watched them send an email to the affected list; the list address is NOT in their local address cache, and they are NOT entering any other addresses in the email other than the list address. The only address that appears on the email in their Sent folder is the list address.
Other users in our organization can send to these same lists without this happening. In fact one of the affected users can send to *other* lists on our server with no problems. These are two different lists.
I don’t know that this is specifically a Mailman problem (because it’s only happening with specific users) but I cannot see how list members are getting stuffed on the CC line otherwise; because Exchange only knows the list address, not the members; only Mailman does.
TLDR: Somehow the all the list addresses are getting stuck onto the list message which then holds it for approval for ’too many addresses’.
--
Bruce Johnson
University of Arizona
College of Pharmacy
Information Technology Group
Institutions do not have opinions, merely customs
Hello,
I'm trying to set up the mailman (2.1.9) web UI behind a load balancer in
order to offload the TLS to it (because this is an ancient machine which
doesn't support modern TLS versions, and newer browsers are complaining
about it). I need all the links in the web UI to use the new hostname
that's in front of the loadbalancer, instead of the actual hostname behind
the loadbalancer. Am I understanding correctly that DEFAULT_URL_HOST in
mm_cfg.py would be the way to accomplish that? And would that affect only
the URLs used in the web UI, it wouldn't change anything about the actual
mail handling under the hood?
Kevin Bowen
kevin.t.bowen(a)gmail.com <kevin(a)ucsd.edu>
Hi,
I have a kind of interesting problem. We migrated a mailman 2 list that
had emergency moderation enabled to mailman 3 (version 3.3.1). This was
imported into mailman 3 - so emergency moderation is still enabled.
The web interface, however, does not expose the emergency moderation
flag. Is there some way to disable it via the command line?
Thanks a lot,
Johanna
Hi,
Odd issue between two OSes with the same config:
In both cases, the archives are configured for public access.
On one server, archives are accessible while on the other, access is denied
with the error message:
*AH00037: Symbolic link not allowed or link target not accessible:
/usr/local/mailman/archives/public/LISTNAME, referer:
https://lists.server.name/mailman/listinfo/LISTNAME
<https://lists.server.name/mailman/listinfo/LISTNAME>*
root@gw:/usr/local/etc/apache24/Includes # ls -al
/usr/local/mailman/archives/public/LISTNAME/
total 12
drwxrwsr-x 2 root mailman 512 Jul 26 21:49 .
drwxrws--- 58 root mailman 1536 Jul 26 21:49 ..
-rw-rw-r-- 1 root mailman 493 Jul 26 21:49 index.html
<VirtualHost *:443>
ServerAdmin odhiambo(a)gmail.com
ServerName lists.server.name
RewriteEngine On
Redirect Permanent /htdig /icons/htdig
RedirectMatch ^/mailman[/]*$ /mailman/listinfo/
Alias /pipermail /usr/local/mailman/archives/public
<Directory /usr/local/mailman/icons/>
AllowOverride all
Require all granted
</Directory>
Alias /icons /usr/local/www/icons
<Directory /usr/local/mailman/icons/>
AllowOverride all
Require all granted
</Directory>
Alias /images/mailman/ /usr/local/mailman/icons/
<Directory /usr/local/www/icons/>
AllowOverride all
Require all granted
</Directory>
<Directory /usr/local/mailman/archives/public/>
Options Indexes FollowSymlinks *<= one
would think that this is where the issue is, but seems like it's
elsewhere???*
AllowOverride None
Require all granted
</Directory>
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
<Directory /usr/local/mailman/cgi-bin/>
Options FollowSymLinks ExecCGI
AllowOverride None
Require all granted
</Directory>
ErrorLog /var/log/mailman-error.log
CustomLog /var/log/mailman-access.log combined
</VirtualHost>
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft.", grep ^[^#] :-)
Good Day
We have a running 2.1.12 installation that was done long ago via an
external consultant.
It hasn't been changed in years, but I would like to upgrade this to at
least the latest 2.x version and potentially 3.x.
We would also like to migrate this from the current Centos VM to an Ubuntu
EC2 instance
Knowing very little about the structure etc of the data etc, what would be
the best way to go about this?
Regards
--
*Daniel Krause*
*Head of IT*
*Office: **+27 87 238 4238* <0872384238>
*Mobile : **+971 55 418 4733* <0971554184733>
*Email: **daniel(a)noldor.co.za* <daniel(a)noldor.co.za>
*Web: **www.noldor.co.za* <http://www.noldor.co.za/>