Re: [Mailman-Users] Mountain Lion Server Issue after migration from Lion

2013-04-01 Thread Allan Herman 
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  wrote:

> Allan Herman wrote:
> 
>> Here are the logs.
>> 
>> Mar 29 18:14:08 x.yy.ca postfix/postscreen[2793]: PASS NEW 
>> [98.136.217.31]:34253
>> Mar 29 18:14:08 x.yy.ca postfix/smtpd[2798]: connect from 
>> nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]
>> Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: sacl_check: 
>> mbr_user_name_to_uuid(mail...@yy.ca) failed: No such file or directory
>> Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: warning: recipient 
>> rejected  uid falls below minimum allowed: 78 < 501
>> Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: NOQUEUE: reject: RCPT 
>> from nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]: 550 5.1.1 
>> : Recipient address rejected: User unknown in local 
>> recipient table; from= to= proto=SMTP 
>> helo=
>> Mar 29 18:14:09 x.yy.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.
> 
> 
> 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  gets a ton of
> Mac OS X Lion hits, but a cursory look didn't show much in the way of
> solutions.
> 
> Whereas
>  finds
> nothing. Is this some Apple specific Postfix check?
> 
> -- 
> Mark Sapiro The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mountain Lion Server Issue after migration from Lion

2013-03-29 Thread Allan Herman 
Here are the logs.

Mar 29 18:14:08 x.yy.ca postfix/postscreen[2793]: PASS NEW 
[98.136.217.31]:34253
Mar 29 18:14:08 x.yy.ca postfix/smtpd[2798]: connect from 
nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]
Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: sacl_check: 
mbr_user_name_to_uuid(mail...@yy.ca) failed: No such file or directory
Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: warning: recipient 
rejected  uid falls below minimum allowed: 78 < 501
Mar 29 18:14:09 x.yy.ca postfix/smtpd[2798]: NOQUEUE: reject: RCPT from 
nm19-vm8.bullet.mail.gq1.yahoo.com[98.136.217.31]: 550 5.1.1 
: Recipient address rejected: User unknown in local 
recipient table; from= to= proto=SMTP 
helo=
Mar 29 18:14:09 x.yy.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  wrote:

> 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 The highway is for gamblers,
> San Francisco Bay Area, Californiabetter use your sense - B. Dylan
> 

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

Re: [Mailman-Users] Mountain Lion Server Issue after migration from Lion

2013-03-29 Thread Mark Sapiro 
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 The highway is for gamblers,
San Francisco Bay Area, Californiabetter use your sense - B. Dylan

--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org

[Mailman-Users] Mountain Lion Server Issue after migration from Lion

2013-03-29 Thread Allan Herman 
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?
--
Mailman-Users mailing list Mailman-Users@python.org
http://mail.python.org/mailman/listinfo/mailman-users
Mailman FAQ: http://wiki.list.org/x/AgA3
Security Policy: http://wiki.list.org/x/QIA9
Searchable Archives: http://www.mail-archive.com/mailman-users%40python.org/
Unsubscribe: 
http://mail.python.org/mailman/options/mailman-users/archive%40jab.org