Mountain Lion server trouble
I tried the instructions on http://www.livetime.com/mountain-lion-mailman-mailing-list/ to install mailman on 10.8 server, but have hit a snag. The build seemed to go perfectly, but the change to the httpd_server_app.conf file breaks apache. Previously, the OS X wiki service was working properly, but after the change, the system log shows apache failing to launch and a failed spawn every 10 seconds. When I comment out the change to httpd_server_app.conf, everything is back to normal.
Help?
The change to httpd_server_app.conf is: Include /private/etc/apache2/extra/httpd-mailman.conf
The content of /private/etc/apache2/extra/httpd-mailman.conf is:
# Config file for linking the mailman mailing list manager to MacOSX Server Web Server. #
ScriptAlias /mailman/ "/usr/local/mailman/cgi-bin/" Alias /pipermail/ "/usr/local/mailman/archives/public/" Alias /icons/ "/usr/local/mailman/icons/" <Directory "/usr/local/mailman/archives/public/"> Options FollowSymLinks MultiViews Indexes AllowOverride None Order allow,deny Allow from all </Directory>
Allan
Allan Herman wrote:
I tried the instructions on http://www.livetime.com/mountain-lion-mailman-mailing-list/ to install mailman on 10.8 server, but have hit a snag. The build seemed to go perfectly, but the change to the httpd_server_app.conf file breaks apache.
Have you seen our FAQ at <http://wiki.list.org/x/O4A9>? It doesn't have Mountain Lion specific information, but it covers installation of the source distribution of Gnu Mailman on Mac OS X which is what we recommend.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Primarily, subject to the following comments, I followed the steps in the Snow Leopard instructions at this page: http://www.mail-archive.com/mailman-users@python.org/msg56963.html
In step 1, I will note that for ML, one would get XCode from the app store, rather than install developer tools. Also, as I was installing on OS X server, postfix was installed and running.
Steps 2 and 3, no changes.
Added step 3A to migrate data. When I upgraded from Lion Server to ML server, the installer moved my old mailman data to /Library/Server/Migrated/private/var/mailman/. I copied over my existing data and configuration as follows: sudo cp -a /Library/Server/Migrated/private/var/mailman/archives/* /usr/local/mailman/archives/ sudo cp -a /Library/Server/Migrated/private/var/mailman/data/* /usr/local/mailman/data/ sudo cp -a /Library/Server/Migrated/private/var/mailman/lists/* /usr/local/mailman/lists/ sudo cp -a /Library/Server/Migrated/private/var/mailman/qfiles/* /usr/local/mailman/qfiles/
Step 4 is significantly different, as the apache config files are changed in ML server. Here, I created the file /private/etc/apache2/extra/httpd-mailman.conf containing the following:
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
Alias /pipermail/ /usr/local/mailman/archives/public/
Alias /icons/ /usr/local/mailman/icons/<Directory "/usr/local/mailman/cgi-bin"> order allow,deny allow from all </Directory> <Directory "/usr/local/mailman/archives/public"> order allow,deny allow from all </Directory> <Directory "/usr/local/mailman/archives/public"> Options FollowSymLinks </Directory>
The above is substantially the same as the lines added to httpd.conf in the source instructions, except that it adds the alias for the icons. This alias is instead of copying the icons to /usr/share/httpd/icons, where apache won't find them in ML server.
Further, ML Server's apache does not use the httpd.conf file, but rather, /Library/Server/Web/Config/apache2/httpd_server_app.conf. In order to incorporate the configuration we put into the httpd-mailman.conf, above, httpd_server_app.conf is edited to add the following line:
#Mailman Include /private/etc/apache2/extra/httpd-mailman.conf
I put the above right after "Include /Library/Server/Web/Config/apache2/other/*.conf"
4(e) re cron jobs was followed without change
In step 5,
- the real main.cf file, under ML Server, is in /Library/Server/Mail/Config/postfix
- assuming postfix is running, you will already have something like "alias_maps = hash:/etc/aliases" already. Don't change what you have already. Just tack on ",hash:/usr/local/mailman/data/aliases" to it. Note the comma.
Step 6 followed
Step 7 unnecessary, because of the import
Step 8 followed.
With the exception of one small glitch, it seems to be working well.
On 03-23-2013, at 10:31 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Thank you for posting this. I have linked this post from the FAQ at <http://wiki.list.org/x/O4A9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mar 29, 2013, at 4:32 PM, Allan Herman <nxnw@rogers.com> wrote:
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Primarily, subject to the following comments, I followed the steps in the Snow Leopard instructions at this page: http://www.mail-archive.com/mailman-users@python.org/msg56963.html
As the author of the original, thank you for the update. Note that what I wrote was for OS X "client", not Server. But I am stuck for now at Lion and after one attempt on a test system, not sure I want to try to move my server beyond Lion. Apple has changed way too much in Mountain Lion - compatibility with previous OS versions is just not in Apple's goals (and it's the mail server piece that has stopped me - never even got to Mailman).
-- Larry Stone lstone19@stonejongleux.com http://www.stonejongleux.com/
In my case, the upgrade from Lion Server to Mountain Lion Server was pretty smooth. Almost everything (contact server, calendar server, file server, profile manager, DNS, OD, iChat server) worked fine without further attention after the upgrade.
Expected issues were the loss of mailman and the loss of server side mail rules (primarily vacation messages).
Unexpected, but easily fixed, was postfix being dead after the update. The failure was due to the config directory being moved from /etc/postfix/ to /Library/Server/Mail/Config/postfix/ — my main.cf and master.cf files had many paths to files that were no longer in /etc/postfix/. After a bit of editing, all was fine. Mostly, I just had to change /etc/postfix/ to Library/Server/Mail/Config/postfix/. The only one that was a bit trickier was the aliases file. My recollection was that, originally, the file was at /etc/aliases and the one in /etc/postfix was a symlink, so I just recreated that, with the symlink in Library/Server/Mail/Config/postfix. I am thinking of reversing that however, as the idea of having all server config files in one place (Library/Server/... is appealing.
On 03-29-2013, at 6:27 PM, Larry Stone <lstone19@stonejongleux.com> wrote:
I was able to install mailmain 2.1.15 and migrate my existing data after I upgraded my server from Lion to Mountain Lion, as detailed in http://www.mail-archive.com/mailman-users@python.org/msg62432.html.
It's mostly fine, except that I can't send an email to mailman@mydomain. Postfix is rejecting the address. That is particularly odd, as I can send emails to mailman-requests@mydomain and to the various addresses associated with my other mailman list on the same server.
As such, it strikes me that this is an issue with mailman's aliases, rather than a postfix issue.
Any ideas?
Allan Herman wrote:
It's mostly fine, except that I can't send an email to mailman@mydomain. Postfix is rejecting the address.
What is the exact message from Postfix? The full log message from Postfix's log rather than just the reason from the DSN would be most helpful.
That is particularly odd, as I can send emails to mailman-requests@mydomain and to the various addresses associated with my other mailman list on the same server.
As such, it strikes me that this is an issue with mailman's aliases, rather than a postfix issue.
More likely it is some 'mailman' alias in another Postfix alias_maps file or maybe a transport_maps file.
Just in case, what is the contents of /usr/local/mailman/data/aliases?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Here are the logs.
Mar 29 18:14:08 xxxxx.yyyyyy.ca postfix/postscreen[2793]: PASS NEW [98.136.217.31]:34253 Mar 29 18:14:08 xxxxx.yyyyyy.ca postfix/smtpd[2798]: connect from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31] Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: sacl_check: mbr_user_name_to_uuid(mailman@yyyyyy.ca) failed: No such file or directory Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: warning: recipient rejected <mailman> uid falls below minimum allowed: 78 < 501 Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: NOQUEUE: reject: RCPT from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]: 550 5.1.1 <mailman@yyyyyy.ca>: Recipient address rejected: User unknown in local recipient table; from=<aaaaaaa@bbbbb.com> to=<mailman@yyyyyy.ca> proto=SMTP helo=<nm19-vm8.bullet.mail.gq1.yahoo.com> Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: disconnect from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]
Either there is no alias for mailman or postfix is identifying mailman with the user "mailman" before processing aliases. I though postfix precesses aliases first, however.
Here is the alias file:
# This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own.
# The ultimate loop stopper address mailman-loop: /usr/local/mailman/data/owner-bounces.mbox
# STANZA START: mymailinglist # CREATED: Fri Mar 29 14:31:02 2013 mymailinglist: "|/usr/local/mailman/mail/mailman post mymailinglist" mymailinglist-admin: "|/usr/local/mailman/mail/mailman admin mymailinglist" mymailinglist-bounces: "|/usr/local/mailman/mail/mailman bounces mymailinglist" mymailinglist-confirm: "|/usr/local/mailman/mail/mailman confirm mymailinglist" mymailinglist-join: "|/usr/local/mailman/mail/mailman join mymailinglist" mymailinglist-leave: "|/usr/local/mailman/mail/mailman leave mymailinglist" mymailinglist-owner: "|/usr/local/mailman/mail/mailman owner mymailinglist" mymailinglist-request: "|/usr/local/mailman/mail/mailman request mymailinglist" mymailinglist-subscribe: "|/usr/local/mailman/mail/mailman subscribe mymailinglist" mymailinglist-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mymailinglist" # STANZA END: mymailinglist
# STANZA START: mailman # CREATED: Fri Mar 29 14:35:21 2013 mailman: "|/usr/local/mailman/mail/mailman post mailman" mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/local/mailman/mail/mailman join mailman" mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman" mailman-request: "|/usr/local/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman
On 03-29-2013, at 6:04 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
Clearly, Postfix is doing something to validate users way before alias processing. Alias processing does not occur until the message is accepted and queued and ready to be delivered by the 'local' transport.
What does 'postconf -n' show? In particular, what's smtpd_recipient_restrictions?
Note that <http://www.google.com/#q=postfix+sacl_check> gets a ton of Mac OS X Lion hits, but a cursory look didn't show much in the way of solutions.
Whereas <http://www.google.com/search?q=sacl&sitesearch=www.postfix.org> finds nothing. Is this some Apple specific Postfix check?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Actually, I think this makes sense now.
Unless the sender is authenticated, I reject messages at the handshake if the addressee is not a local recipient. Local recipients include aliases.
I think the next directive is the key:
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
My suspicion is that the addressee is evaluated in the above order (first, actual accounts, then aliases). In this flukey instance, because "mailman" is an actual system account, it is evaluated as such before postfix evaluates it as an alias to a listserver account. It then rejects it because it is a system account rather than a user account (uid falls below minimum allowed: 78 < 501). This is why mailman-request@... works, but not mailman@...
Accordingly, I don't think anything is actually wrong that warrants further digging. I only use the "mailman" list, which was set up by default, for testing. Any reason I can't delete it and make a "testing" list?
Thanks.
On 03-29-2013, at 7:01 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
Accordingly, I don't think anything is actually wrong that warrants further digging. I only use the "mailman" list, which was set up by default, for testing. Any reason I can't delete it and make a "testing" list?
You can't delete it for a few reasons, the most important of which is mailmanctl will refuse to run the qrunners if it isn't there. Also, there will be issues with cron/mailpasswds
Further, the site list address is exposed on the web admin and listinfo overview pages.
But, its name doesn't have to be 'mailman'. You can call it anything you want by putting, e.g.,
MAILMAN_SITE_LIST = 'testing'
in mm_cfg.py, however 'testing' probably isn't the best name as monthly reminders are From: the -owner of this list and its posting address is exposed on the web admin and listinfo overview pages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Allan Herman wrote:
I tried the instructions on http://www.livetime.com/mountain-lion-mailman-mailing-list/ to install mailman on 10.8 server, but have hit a snag. The build seemed to go perfectly, but the change to the httpd_server_app.conf file breaks apache.
Have you seen our FAQ at <http://wiki.list.org/x/O4A9>? It doesn't have Mountain Lion specific information, but it covers installation of the source distribution of Gnu Mailman on Mac OS X which is what we recommend.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Primarily, subject to the following comments, I followed the steps in the Snow Leopard instructions at this page: http://www.mail-archive.com/mailman-users@python.org/msg56963.html
In step 1, I will note that for ML, one would get XCode from the app store, rather than install developer tools. Also, as I was installing on OS X server, postfix was installed and running.
Steps 2 and 3, no changes.
Added step 3A to migrate data. When I upgraded from Lion Server to ML server, the installer moved my old mailman data to /Library/Server/Migrated/private/var/mailman/. I copied over my existing data and configuration as follows: sudo cp -a /Library/Server/Migrated/private/var/mailman/archives/* /usr/local/mailman/archives/ sudo cp -a /Library/Server/Migrated/private/var/mailman/data/* /usr/local/mailman/data/ sudo cp -a /Library/Server/Migrated/private/var/mailman/lists/* /usr/local/mailman/lists/ sudo cp -a /Library/Server/Migrated/private/var/mailman/qfiles/* /usr/local/mailman/qfiles/
Step 4 is significantly different, as the apache config files are changed in ML server. Here, I created the file /private/etc/apache2/extra/httpd-mailman.conf containing the following:
ScriptAlias /mailman/ /usr/local/mailman/cgi-bin/
Alias /pipermail/ /usr/local/mailman/archives/public/
Alias /icons/ /usr/local/mailman/icons/<Directory "/usr/local/mailman/cgi-bin"> order allow,deny allow from all </Directory> <Directory "/usr/local/mailman/archives/public"> order allow,deny allow from all </Directory> <Directory "/usr/local/mailman/archives/public"> Options FollowSymLinks </Directory>
The above is substantially the same as the lines added to httpd.conf in the source instructions, except that it adds the alias for the icons. This alias is instead of copying the icons to /usr/share/httpd/icons, where apache won't find them in ML server.
Further, ML Server's apache does not use the httpd.conf file, but rather, /Library/Server/Web/Config/apache2/httpd_server_app.conf. In order to incorporate the configuration we put into the httpd-mailman.conf, above, httpd_server_app.conf is edited to add the following line:
#Mailman Include /private/etc/apache2/extra/httpd-mailman.conf
I put the above right after "Include /Library/Server/Web/Config/apache2/other/*.conf"
4(e) re cron jobs was followed without change
In step 5,
- the real main.cf file, under ML Server, is in /Library/Server/Mail/Config/postfix
- assuming postfix is running, you will already have something like "alias_maps = hash:/etc/aliases" already. Don't change what you have already. Just tack on ",hash:/usr/local/mailman/data/aliases" to it. Note the comma.
Step 6 followed
Step 7 unnecessary, because of the import
Step 8 followed.
With the exception of one small glitch, it seems to be working well.
On 03-23-2013, at 10:31 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Thank you for posting this. I have linked this post from the FAQ at <http://wiki.list.org/x/O4A9>.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
On Mar 29, 2013, at 4:32 PM, Allan Herman <nxnw@rogers.com> wrote:
OK, here are steps taken for a (mostly) successful installation on Mountain Lion server, including migration from the apple-supplied mailman previously running under Lion.
Primarily, subject to the following comments, I followed the steps in the Snow Leopard instructions at this page: http://www.mail-archive.com/mailman-users@python.org/msg56963.html
As the author of the original, thank you for the update. Note that what I wrote was for OS X "client", not Server. But I am stuck for now at Lion and after one attempt on a test system, not sure I want to try to move my server beyond Lion. Apple has changed way too much in Mountain Lion - compatibility with previous OS versions is just not in Apple's goals (and it's the mail server piece that has stopped me - never even got to Mailman).
-- Larry Stone lstone19@stonejongleux.com http://www.stonejongleux.com/
In my case, the upgrade from Lion Server to Mountain Lion Server was pretty smooth. Almost everything (contact server, calendar server, file server, profile manager, DNS, OD, iChat server) worked fine without further attention after the upgrade.
Expected issues were the loss of mailman and the loss of server side mail rules (primarily vacation messages).
Unexpected, but easily fixed, was postfix being dead after the update. The failure was due to the config directory being moved from /etc/postfix/ to /Library/Server/Mail/Config/postfix/ — my main.cf and master.cf files had many paths to files that were no longer in /etc/postfix/. After a bit of editing, all was fine. Mostly, I just had to change /etc/postfix/ to Library/Server/Mail/Config/postfix/. The only one that was a bit trickier was the aliases file. My recollection was that, originally, the file was at /etc/aliases and the one in /etc/postfix was a symlink, so I just recreated that, with the symlink in Library/Server/Mail/Config/postfix. I am thinking of reversing that however, as the idea of having all server config files in one place (Library/Server/... is appealing.
On 03-29-2013, at 6:27 PM, Larry Stone <lstone19@stonejongleux.com> wrote:
I was able to install mailmain 2.1.15 and migrate my existing data after I upgraded my server from Lion to Mountain Lion, as detailed in http://www.mail-archive.com/mailman-users@python.org/msg62432.html.
It's mostly fine, except that I can't send an email to mailman@mydomain. Postfix is rejecting the address. That is particularly odd, as I can send emails to mailman-requests@mydomain and to the various addresses associated with my other mailman list on the same server.
As such, it strikes me that this is an issue with mailman's aliases, rather than a postfix issue.
Any ideas?
Allan Herman wrote:
It's mostly fine, except that I can't send an email to mailman@mydomain. Postfix is rejecting the address.
What is the exact message from Postfix? The full log message from Postfix's log rather than just the reason from the DSN would be most helpful.
That is particularly odd, as I can send emails to mailman-requests@mydomain and to the various addresses associated with my other mailman list on the same server.
As such, it strikes me that this is an issue with mailman's aliases, rather than a postfix issue.
More likely it is some 'mailman' alias in another Postfix alias_maps file or maybe a transport_maps file.
Just in case, what is the contents of /usr/local/mailman/data/aliases?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Here are the logs.
Mar 29 18:14:08 xxxxx.yyyyyy.ca postfix/postscreen[2793]: PASS NEW [98.136.217.31]:34253 Mar 29 18:14:08 xxxxx.yyyyyy.ca postfix/smtpd[2798]: connect from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31] Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: sacl_check: mbr_user_name_to_uuid(mailman@yyyyyy.ca) failed: No such file or directory Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: warning: recipient rejected <mailman> uid falls below minimum allowed: 78 < 501 Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: NOQUEUE: reject: RCPT from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]: 550 5.1.1 <mailman@yyyyyy.ca>: Recipient address rejected: User unknown in local recipient table; from=<aaaaaaa@bbbbb.com> to=<mailman@yyyyyy.ca> proto=SMTP helo=<nm19-vm8.bullet.mail.gq1.yahoo.com> Mar 29 18:14:09 xxxxx.yyyyyy.ca postfix/smtpd[2798]: disconnect from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]
Either there is no alias for mailman or postfix is identifying mailman with the user "mailman" before processing aliases. I though postfix precesses aliases first, however.
Here is the alias file:
# This file is generated by Mailman, and is kept in sync with the # binary hash file aliases.db. YOU SHOULD NOT MANUALLY EDIT THIS FILE # unless you know what you're doing, and can keep the two files properly # in sync. If you screw it up, you're on your own.
# The ultimate loop stopper address mailman-loop: /usr/local/mailman/data/owner-bounces.mbox
# STANZA START: mymailinglist # CREATED: Fri Mar 29 14:31:02 2013 mymailinglist: "|/usr/local/mailman/mail/mailman post mymailinglist" mymailinglist-admin: "|/usr/local/mailman/mail/mailman admin mymailinglist" mymailinglist-bounces: "|/usr/local/mailman/mail/mailman bounces mymailinglist" mymailinglist-confirm: "|/usr/local/mailman/mail/mailman confirm mymailinglist" mymailinglist-join: "|/usr/local/mailman/mail/mailman join mymailinglist" mymailinglist-leave: "|/usr/local/mailman/mail/mailman leave mymailinglist" mymailinglist-owner: "|/usr/local/mailman/mail/mailman owner mymailinglist" mymailinglist-request: "|/usr/local/mailman/mail/mailman request mymailinglist" mymailinglist-subscribe: "|/usr/local/mailman/mail/mailman subscribe mymailinglist" mymailinglist-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mymailinglist" # STANZA END: mymailinglist
# STANZA START: mailman # CREATED: Fri Mar 29 14:35:21 2013 mailman: "|/usr/local/mailman/mail/mailman post mailman" mailman-admin: "|/usr/local/mailman/mail/mailman admin mailman" mailman-bounces: "|/usr/local/mailman/mail/mailman bounces mailman" mailman-confirm: "|/usr/local/mailman/mail/mailman confirm mailman" mailman-join: "|/usr/local/mailman/mail/mailman join mailman" mailman-leave: "|/usr/local/mailman/mail/mailman leave mailman" mailman-owner: "|/usr/local/mailman/mail/mailman owner mailman" mailman-request: "|/usr/local/mailman/mail/mailman request mailman" mailman-subscribe: "|/usr/local/mailman/mail/mailman subscribe mailman" mailman-unsubscribe: "|/usr/local/mailman/mail/mailman unsubscribe mailman" # STANZA END: mailman
On 03-29-2013, at 6:04 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
Clearly, Postfix is doing something to validate users way before alias processing. Alias processing does not occur until the message is accepted and queued and ready to be delivered by the 'local' transport.
What does 'postconf -n' show? In particular, what's smtpd_recipient_restrictions?
Note that <http://www.google.com/#q=postfix+sacl_check> gets a ton of Mac OS X Lion hits, but a cursory look didn't show much in the way of solutions.
Whereas <http://www.google.com/search?q=sacl&sitesearch=www.postfix.org> finds nothing. Is this some Apple specific Postfix check?
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
Actually, I think this makes sense now.
Unless the sender is authenticated, I reject messages at the handshake if the addressee is not a local recipient. Local recipients include aliases.
I think the next directive is the key:
local_recipient_maps = proxy:unix:passwd.byname $alias_maps
My suspicion is that the addressee is evaluated in the above order (first, actual accounts, then aliases). In this flukey instance, because "mailman" is an actual system account, it is evaluated as such before postfix evaluates it as an alias to a listserver account. It then rejects it because it is a system account rather than a user account (uid falls below minimum allowed: 78 < 501). This is why mailman-request@... works, but not mailman@...
Accordingly, I don't think anything is actually wrong that warrants further digging. I only use the "mailman" list, which was set up by default, for testing. Any reason I can't delete it and make a "testing" list?
Thanks.
On 03-29-2013, at 7:01 PM, Mark Sapiro <mark@msapiro.net> wrote:
Allan Herman wrote:
Accordingly, I don't think anything is actually wrong that warrants further digging. I only use the "mailman" list, which was set up by default, for testing. Any reason I can't delete it and make a "testing" list?
You can't delete it for a few reasons, the most important of which is mailmanctl will refuse to run the qrunners if it isn't there. Also, there will be issues with cron/mailpasswds
Further, the site list address is exposed on the web admin and listinfo overview pages.
But, its name doesn't have to be 'mailman'. You can call it anything you want by putting, e.g.,
MAILMAN_SITE_LIST = 'testing'
in mm_cfg.py, however 'testing' probably isn't the best name as monthly reminders are From: the -owner of this list and its posting address is exposed on the web admin and listinfo overview pages.
-- Mark Sapiro <mark@msapiro.net> The highway is for gamblers, San Francisco Bay Area, California better use your sense - B. Dylan
participants (3)
-
Allan Herman -
Larry Stone -
Mark Sapiro