Postfix warnings when starting (harmless?)
Hello, 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.
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" <tabithamc@gmail.com> 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.
On 09/05/07 01:27, Tabitha McNerney wrote:
# 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 <...> 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
<..> Hi Tabitha, this is a misbehaviuor I alrady spotted the first time I installed postfix. If I recall correctly it's a matter of changing in postfix-script the command "ls" with "/bin/ls". On some installation this doesn't show up, because if coreutils (maybe +with_default_names) is installed it disappear. Can you please try changing the lines where the problem arise and report it back, maybe with a diff from the original postfix script? Bye, Gufo
On 5/9/07, Sbranzo <sbranzo@gmail.com> wrote:
On 09/05/07 01:27, Tabitha McNerney wrote:
# 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 <...> 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
<..>
Hi Tabitha,
Hello Gufo ... this is a misbehaviuor I alrady spotted the first time I installed
postfix. If I recall correctly it's a matter of changing in postfix-script the command "ls" with "/bin/ls". On some installation this doesn't show up, because if coreutils (maybe +with_default_names) is installed it disappear.
Thank you for the suggestions. Indeed, in postfix-script, everywhere (only three places, lines 200, 211 and 225) there was a bare "ls" I replaced it with "/bin/ls" and those errors then disappeared. I also changed the ownership of /opt/local/var/spool/postfix/public/.turd_postfix to postfix:postdrop and now when I start postfix on both machines (Intel and PowerPC) there are no warning messages at startup (I only tested with some simple relays and accepting mail from the local domain, nothing otherwise too fancy yet). Can you please try changing the lines where the problem arise and report
it back, maybe with a diff from the original postfix script?
Oops, I went to fast and I already made the postfix-script changes so I don't have a pure diff but the lines I mentioned above (just a find and replace on the only "ls" on those lines with a "/bin/ls" works perfect. Also, on the bug report, I wonder if there is a work around for the TLS / OpenSSL problem? Did you get yours to work by reverting back to OpenSSL 0.9.7 from 0.9.8? Thanks a ton, T.M. Bye,
Gufo
On 09/05/07 18:49, Tabitha McNerney wrote:
Thank you for the suggestions. Indeed, in postfix-script, everywhere (only three places, lines 200, 211 and 225) there was a bare "ls" I replaced it with "/bin/ls" and those errors then disappeared.
Ok, fine.
I also changed the ownership of
/opt/local/var/spool/postfix/public/.turd_postfix
to postfix:postdrop
You should remove /opt/local/var/spool/postfix/public/.turd_postfix, it's a leftover from the installation.
Also, on the bug report, I wonder if there is a work around for the TLS / OpenSSL problem? Did you get yours to work by reverting back to OpenSSL 0.9.7 from 0.9.8?
I already submitted a patch to address sasl and tls problems, now all should work correctly. Gufo
participants (3)
-
markd＠macports.org
-
Sbranzo
-
Tabitha McNerney