There is a ticket on that. It wouldn't be hard to fix, but I'm not sure what the effect is either (no clear explanation from reporter) and I wonder if a fix upstream may happen at some point because I would think this wouldn't be a problem on OS X only. But it has persisted since 2.2 I think.
http://trac.macosforge.org/projects/macports/ticket/10644 Mark "Tabitha McNerney" <[EMAIL PROTECTED]> on Wednesday, May 9, 2007 at 4:27 AM -0800 wrote: >I just installed the most current version of the Postfix port (2.3.8) >under MacPorts 1.4.0 and 1.4.3 with the ldap, pcre, sasl and tls variants: > > > >$ port installed postfix >The following ports are currently installed: > postfix @2.3.8_0+ldap+pcre+sasl+tls (active) > > >on two different machines (an Intel Mac and a PowerPC Mac respectively >both running 10.4.9). I've disabled Apple's postfix (per the >recommendation in the comments generated by MacPorts after successfully >installing). I also bought yesterday the excellent book on Postfix, " The >Book of Postfix" and have used it to create a very simple single domain >configuration (baby steps). > >When I start postfix, it certainly runs persistently but I have not yet >tried to send mail yet, because the following warnings are dumped out on >to the command line after starting it: > > > ># postfix start > >/opt/local/etc/postfix/postfix-script: line 200: ls: command not found >postfix/postfix-script: warning: not owned by root: >/opt/local/libexec/postfix >/opt/local/etc/postfix/postfix-script: line 200: ls: command not found >postfix/postfix-script: warning: not owned by root: /opt/local/etc/postfix >/opt/local/etc/postfix/postfix-script: line 200: ls: command not found >postfix/postfix-script: warning: not owned by root: >/opt/local/var/spool/postfix >/opt/local/etc/postfix/postfix-script: line 1: ls: command not found >usage: find [-H | -L | -P] [-EXdsx] [-f file] [file ...] [expression] >/opt/local/etc/postfix/postfix-script: line 1: ls: command not found >postfix/postfix-script: starting the Postfix mail system > >The warnings about the command "ls" not being found in the >postfix-script on lines 200 and line 1 is quite strange (when I vi >postfix-script line 1 is not attempting to use the ls command but line >200 is). This is what line 200 looks like calling ls, enclosed in the do >and done: > > > >do > ls -lLd $dir | (grep " root " >/dev/null || > $WARN not owned by root: $dir) >done > > >This is strange because my bash profile PATH is just fine (I give >/opt/local the priority and then tack on $PATH after that, and when I try >independently on the command line, the ls command works just fine). > >As for the complain about the ownership, I did notice that the directory: > > > >/opt/local/var/spool/postfix > > >is owned by root:admin but most of the contents in said directory are >owned by postfix:admin and postfix:postdrop > >Are the above warnings normal? Can they be safely ignored? Or should I >take some sort of rectifying action? It bothers me to see warnings (I >would love for it to just run cleanly). > >Thanks a ton anyone, > >T.M. > >P.S. The warnings above are the exact same on the Intel and the PowerPC >machine aforementioned. _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-users
