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 <m...@msapiro.net> wrote: > Allan Herman wrote: > >> 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(mail...@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 >> <mail...@yyyyyy.ca>: Recipient address rejected: User unknown in local >> recipient table; from=<aaaa...@bbbbb.com> to=<mail...@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. > > > 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 <m...@msapiro.net> The highway is for gamblers, > San Francisco Bay Area, California better 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
