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'."
Is there an efficient way to change the domain name that mailman is
I have two mailing lists that were created for an organization before
that organization had their own domain. At the time the organization was
sure they did not want their own domain and would not be getting a
Since then, they have chosen to get a domain and set up a web site.
I would like to move their mailing lists onto their domain. It looks
like the process for this is:
1) get the list of subscribers
2) delete the mailing list from the one domain (losing the archives)
3) create the mailing list on the new domain
4) subscribe the list of subscribers
This process doesn't seem too difficult, but I would prefer to keep the
archives, if possible.
Both domains are on the same server, running CentOS7 and PLESK 12.5, if
that makes a difference.
I have waited almost a year for AOL and Yahoo to admit that they messed up and to remove their DMARC policy. My AOL and Yahoo subscribers are pretty upset at me because I won’t let them post. A number now have two subscriptions, one for posting (from GMail) and another for receiving the messages.
So against my better judgement, I included this hack in Cleanse.py;
< from email.Utils import formataddr, parseaddr
>from email.Utils import formataddr
< # Added to deal with DMARC issuej
< name, addrs = parseaddr(msg.get('from'))
< addrs += '.invalid'
< del msg['from']
< msg['from'] = formataddr((name, addrs))
\ No newline at end of file
I found it in the discussion list.
I don’t get compile errors, but Cleanse.pyc is not being updated. I have stopped and restarted Mailman and I have also rebooted, but same non-action. I have not tried ‘compileall’ and am not eager to, either (permissions, where to invoke, etc). Any suggestions?
The host OS is Mac OS X Server 10.5.8 with Mailman 2.1.14
is it possible to automatically reject emails that have attachments with
certain MIME types (e.g., application/msword, …)?
Since there are so many types of files that are unsafe, I also wonder
whether it is possible to specify a white list of safe MIME types (e.g.,
application/PDF) and to reject everything else. Is that possible?
I did some searching but only found solutions for automatically
stripping attachments, which is not what I want.
There is another interesting Phishing Email circulating on campus. I have included the email below. Please notice the "From:" address as it is not from the UT Martin Helpdesk or anyone on our campus. Please just delete the email and don't click where it says "Click Here". (I have removed the hyperlinks from the message below)
If you received the email and clicked on the link, please give the helpdesk a call at 7900 as soon as you can - and remember, the UT Martin Helpdesk will never ask you to send your password over email.
Information Technology Services
I'm attempting to modify the subscription options in the Admin section under "Privacy options: What steps are required for subscription?".
There are currently three option and I'm trying to remove "Confirm" so that the only two options remain - "Require approval" and "Confirm and approve".
In the file "/usr/lib/mailman/Mailman/Gui/Privacy.py" I've tried removing the lines that relate to "Confirm" - and as expected the Admin page looks okay with only the two desired options showing. However, what happens when someone subscribs is they actually get the "Confirm" process - rather than the expected "Requires approval".
Is there another file I need to be looking at also? Or am I most likely just screwing up the "Privacy.py" file?