Prev: ?best practice to stop " root+:|" exploits
Next: Filter before delivery without procmail or maildrop
From: Jamal Mubarak on 8 May 2010 18:51
I have postfix installed and configured on my Mac OS 10.6.3 machines. It works correctly because the unix mail program works fine and sendmail interface can send emails as well. However, I encounter this strange problem. The printing commands, lpr and lp, have the -m switch which sends an e-mail on completion of a print job. This email is not delivered and in /var/log/mail.log I see the following error:

May 7 00:00:04 MacBookPro postfix/sendmail[6309]: fatal: execvp /usr/sbin/postdrop: Operation not permitted
May 7 00:00:05 MacBookPro postfix/sendmail[6308]: warning: command "/usr/sbin/postdrop -r" exited with status 1
May 7 00:00:05 MacBookPro postfix/sendmail[6308]: fatal: _lp(26): unable to execute /usr/sbin/postdrop -r: Unknown error: 0

Can someone give me a clue as to what is wrong? Funny thing is that sometimes it starts working on its own and then stops again.

Jamal

From: Wietse Venema on 9 May 2010 08:56
Jamal Mubarak:
> I have postfix installed and configured on my Mac OS 10.6.3
> machines. It works correctly because the unix mail program works
> fine and sendmail interface can send emails as well. However, I
> encounter this strange problem. The printing commands, lpr and
> lp, have the -m switch which sends an e-mail on completion of a
> print job. This email is not delivered and in /var/log/mail.log
> I see the following error:
>
> May 7 00:00:04 MacBookPro postfix/sendmail[6309]: fatal: execvp /usr/sbin/postdrop: Operation not permitted
> May 7 00:00:05 MacBookPro postfix/sendmail[6308]: warning: command "/usr/sbin/postdrop -r" exited with status 1
> May 7 00:00:05 MacBookPro postfix/sendmail[6308]: fatal: _lp(26): unable to execute /usr/sbin/postdrop -r: Unknown error: 0
>
> Can someone give me a clue as to what is wrong? Funny thing is
> that sometimes it starts working on its own and then stops again.

Ask Apple. Postfix does not change spontaneously.

Wietse

From: Reinaldo de Carvalho on 9 May 2010 13:18
On Sat, May 8, 2010 at 7:51 PM, Jamal Mubarak <jmubarak2(a)gmail.com> wrote:
> I have postfix installed and configured on my Mac OS 10.6.3 machines.  It works correctly because the unix mail program works fine and sendmail interface can send emails as well.  However, I encounter this strange problem.  The printing commands, lpr and lp, have the -m switch which sends an e-mail on completion of a print job.  This email is not delivered and in /var/log/mail.log I see the following error:
>
> May  7 00:00:04 MacBookPro postfix/sendmail[6309]: fatal: execvp /usr/sbin/postdrop: Operation not permitted
> May  7 00:00:05 MacBookPro postfix/sendmail[6308]: warning: command "/usr/sbin/postdrop -r" exited with status 1
> May  7 00:00:05 MacBookPro postfix/sendmail[6308]: fatal: _lp(26): unable to execute /usr/sbin/postdrop -r: Unknown error: 0
>
> Can someone give me a clue as to what is wrong?  Funny thing is that sometimes it starts working on its own and then stops again.
>

Show permissions of /usr/sbin/postdrop and /usr/sbin/sendmail. lpr/lp
process owner have rights to exec this commands?


--
Reinaldo de Carvalho
http://korreio.sf.net
http://python-cyrus.sf.net

"Don't try to adapt the software to the way you work, but rather
yourself to the way the software works" (myself)

From: Jamal Mubarak on 9 May 2010 18:19

On May 9, 2010, at 12:18 PM, Reinaldo de Carvalho wrote:

> On Sat, May 8, 2010 at 7:51 PM, Jamal Mubarak <jmubarak2(a)gmail.com> wrote:
>> I have postfix installed and configured on my Mac OS 10.6.3 machines. It works correctly because the unix mail program works fine and sendmail interface can send emails as well. However, I encounter this strange problem. The printing commands, lpr and lp, have the -m switch which sends an e-mail on completion of a print job. This email is not delivered and in /var/log/mail.log I see the following error:
>>
>> May 7 00:00:04 MacBookPro postfix/sendmail[6309]: fatal: execvp /usr/sbin/postdrop: Operation not permitted
>> May 7 00:00:05 MacBookPro postfix/sendmail[6308]: warning: command "/usr/sbin/postdrop -r" exited with status 1
>> May 7 00:00:05 MacBookPro postfix/sendmail[6308]: fatal: _lp(26): unable to execute /usr/sbin/postdrop -r: Unknown error: 0
>>
>> Can someone give me a clue as to what is wrong? Funny thing is that sometimes it starts working on its own and then stops again.
>
> Show permissions of /usr/sbin/postdrop and /usr/sbin/sendmail. lpr/lp
> process owner have rights to exec this commands?


Here are my permissions:


-rwxr-sr-x 1 root _postdrop 484912 Feb 11 01:03 /usr/sbin/postdrop
-rwxr-xr-x 1 root wheel 572512 Feb 11 01:03 /usr/sbin/sendmail

-r-xr-xr-x 1 root wheel 52832 Feb 11 01:47 lp
-r-xr-xr-x 1 root wheel 44304 Feb 11 01:47 lpoptions
-r-xr-xr-x 1 root wheel 44400 Feb 11 01:47 lppasswd
-r-xr-xr-x 1 root wheel 44528 Feb 11 01:47 lpq
-r-xr-xr-x 1 root wheel 44304 Feb 11 01:47 lpr
-r-xr-xr-x 1 root wheel 35040 Feb 11 01:47 lprm
-r-xr-xr-x 1 root wheel 73552 Feb 11 01:47 lpstat

On May 9, 2010, at 7:56 AM, Wietse Venema wrote:

> Ask Apple. Postfix does not change spontaneously.

I filed a bug report with Apple with number 7477314. They asked me for some details about my system, including permissions. Then nothing.

I have tried to post to a few forums, including the CUPS forum, but no luck. Can someone offer me some ideas on how to attack this problem?

Jamal

From: Wietse Venema on 9 May 2010 18:56
Jamal Mubarak:
> > Ask Apple. Postfix does not change spontaneously.
>
> I filed a bug report with Apple with number 7477314. They asked
> me for some details about my system, including permissions. Then
> nothing.
>
> I have tried to post to a few forums, including the CUPS forum,
> but no luck. Can someone offer me some ideas on how to attack
> this problem?

This involves getting a trace of system calls (arguments and results)
when the error happens.

Some systems capture a system call trace with commands like:

ktrace -f /file/name -d command
strace -o /file/name -f command
truss -o /file/name -f command

But, things may be different on MacOS.

Above, "command" is the command that starts the entire printing
system. On some systems, "command" would be:

sh /etc/rc.d/cups start
sh /etc/init.d/cups start

But, things may be different on MacOS.

Wietse

 |  Next  |  Last
Pages: 1 2 3 4
Prev: ?best practice to stop " root+:|" exploits
Next: Filter before delivery without procmail or maildrop