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 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
Hi!
What is the character set coding for the log files, please?
I'm using MM 2.1.29
I'm asking because a list admin want to view them via a web browser and I
need to config Apache.
Thanks.
Brett
Hi,
I have a list to migrate to Mailman3 from Mailman2 but the domain of the list may change at some point in the future. I was hoping to marry up the 2 events but its not looking likely at the moment.
From what I have tested the Hyperkitty archives can be imported into any list so long as it exists. My question relates to importing the Mailman configuration files.
If we take a Mailman configuration file for list(a)domain1.com<mailto:list@domain1.com>, if I import that into a new Mailman3 list list(a)domain2.com<mailto:list@domain2.com> will it cause a problem?
Taking that a step further could we import list(a)domain1.com<mailto:list@domain1.com> into list2(a)domain2.com<mailto:list2@domain2.com>?
I am aware I could just export the users and re-import into a new list if all else fails.
Suggestions welcome.
Thanks.
Andrew.
The biggest difference for me is that Mailman 2 was a swine to install
and get working, but it was eventually possible.
In comparison with that, Mailman 3 has proved completely impossible.
It's not as if I'm trying to install on anything obscure: it's a very
standard Debian Buster setup running Exim4.
I don't understand what the problem is, but following instructions I can
find anywhere on the web leave me with a setup that simply doesn't work.
With Debian, it should be a simple matter of "sudo apt-get install
packagename" but that certainly isn't the case for Mailman!
Now I'm looking for an alternative way to run mailing lists. Can anyone
suggest either a good alternative, or a way to get Mailman 3 to install?
--
Iain
Hello
One member of a mailman mailing list on my system receives an error
message when posting to the list:
You are not allowed to post to this mailing list From: a domain which
publishes a DMARC policy of reject or quarantine, and your message has been
automatically rejected. If you think that your messages are being rejected
in error, contact the mailing list owner at nssf-styre-owner(a)nssf.us.
In /var/log/mailman/error, I have:
DNSException: No Nameservers available for
username(a)blindeforbundet.no (_dmarc.blindeforbundet.no)
There are not published any DMARC policy for the domain.
I'm running mailman-2.1.30-1.fc31.x86_64 on a Fedora 31 server.
I hope someone on tis list can help me figure out what's going on, and
hopefully a fix.
Thanks in advance
Lars
We've been running a mailman server, pushing more than 45 lists, for as long as I've been here, and recently spammers and phishers have found us.
We're trying to find the right combination to filter in the "List of non-member addresses whose postings will be automatically discarded." under Privacy Options, Sender Filters. All we've been able to come up with are individual domains. When we try to block
guido.sarducci(a)spammer.phisher.it, -- while we'd like to block all of .it, what we find is we can either do the individual address, or the entire spammer.phisher.it domain.
What's the magic combination?
And the hints say use ^, we found * worked for us.... confusion abounds
using mailman version 2.1.20
--
Jeff
