[Mailman-Users] Mailman list sends but doesn't receive mail.
joemailgroups at gmail.com
Sun May 8 08:22:20 CEST 2011
Mark and all members,
Considering the mm_cfg.py file has been edited to display the following:
MTA = 'Postfix'
DEFAULT_EMAIL_HOST = 'domain.com'
DEFAULT_URL_HOST = 'www.domain.com'
POSTFIX_STYLE_VIRTUAL_DOMAINS = ['domain.com']
VIRTUAL_HOST_OVERVIEW = Off
Should I expect to find the name of the server (not the name of the domain)
on any of the e-mail sent by Mailman to subscribers ?
After discussing the case with several people and a little bit of research I
have come across a solution that seems to have prevented the mm_cfg.py from
being edited by Apple's Server Admin application. Changing permissions
didn't work as it was still edited probably by a process running as root. I
tried instead to lock the file using the chflags command and it seems to
have worked. Now, as I make changes to system settings using Apple's Server
Admin application the mm_cfg.py files remains as is and isn't changed back.
The command I used was:
sudo chflags uchg /usr/share/mailman/Mailman/mm_cfg.py
This has allowed the mm_cfg.py configuration file to remain as above with
the name of the domain associated with Mailman. As it was before, any
changes made in Server Admin would cause the domain name to be replaced with
the computer name 'a.main.private' and this would show on e-mails sent by
Assuming this change will be permanent and the domain name will remain in
the configuration file, should I expect the computer name to show up on any
of the mail sent out to subscribers by Mailman, including the one sent
monthly to remind subscribers about list rules ?
I have received some mail from Mailman that looks as follows:
From: mailman-owner at a.main.private (sent by mailman-bounces at domain.com)
Subject: a.main.private mailing list memberships reminder
Now that the configuration has been changed should I expect to see the
domain name where the name of the server appears ? Or is it normal to have
the server's name appear in some parts of mail sent by Mailman ?
Thank you as always for your help.
PS: content of the e-mail if it is helpful.
This is a reminder, sent out once a month, about your
a.main.private mailing list memberships. It includes your
subscription info and how to use it to change it or unsubscribe from a
You can visit the URLs to change your membership status or
configuration, including unsubscribing, setting digest-style delivery
or disabling delivery altogether (e.g., for a vacation), and so on.
In addition to the URL interfaces, you can also use email to make such
changes. For more info, send a message to the '-request' address of
the list (for example, mailman-request at a.main.private)
containing just the word 'help' in the message body, and an email
message will be sent to you with instructions.
If you have questions, problems, comments, etc, send them to
mailman-owner at a.main.private. Thanks!
Passwords for member1 at gmail.com:
List Password // URL
list1 at domain.com coceopxi
On 4/18/11 10:54 AM, "Mark Sapiro" <mark at msapiro.net> wrote:
> JRC Groups wrote:
>> Since there is a process in Apple's Server Admin application that keeps
>> changing Mailman's mm_cfg.py file I think it is safe to assume it expects to
>> find this file there to keep it updated and its removal may likely cause a
>> Would it be possible to have a copy of this file moved to a different
>> location and have Mailman look at the different location for this file while
>> leaving the old one behind as a "dummy" file so that Apple's System Admin
>> application finds the file it expects to find ? The changes would not impact
>> Mailman as the mm_cfg.py it is using for its configuration is the one in the
>> new location.
>> Do you think this would work ?
> You would have to move the entire Mailman $prefix directory and then
> you would have to edit the prefix in all files that reference it
> including Defaults.py and all the paths.py files in Mailman's bin/,
> cron/ and tests/ directories and the MTA aliases and apache config,
> and you would have to set the new location in whatever Apple launchd
> processes that start Mailman and run Mailman's 'cron' jobs, and that
> would probably tell the Apple processes where the new mm_cfg.py was
> It would be much easier to simply install Mailman from source in some
> other location, move your lists and archives, update your MTA and
> apache configs and tell Apple to quit running Mailman.
> Mark Sapiro <mark at msapiro.net> The highway is for gamblers,
> San Francisco Bay Area, California better use your sense - B. Dylan
More information about the Mailman-Users