>>> On Tue, Feb 3, 2009 at  1:49 PM, Victor Duchovni
<victor.ducho...@morganstanley.com> wrote: 
> On Tue, Feb 03, 2009 at 01:34:10PM -0500, Brian Evans - Postfix List wrote:
> 
>> The php mail() command (on *nix) defaults to come in through the pickup
>> daemon (using the sendmail(1) command).
>> It can also be sent in via the smtpd daemon.
>> 
>> Intentionally send a message through your app and immediately check your
>> log.
>> Read and understand entry to delivery(or relay).
>> 
>> If you need assistance with the logs, please post a transaction here.
> 
> No log messages are generated when mail is deposited in the "maildrop"
> queue. If "pickup" is not finding the mail in a timely fashion it is
> because:
> 
>     - The "pickup" master.cf entry is busted (no wakeup timer)
> 
>       pickup    fifo  n       -       n       60      1       pickup

This line appears correct.  There is no difference between it and the pickup 
lines in the other postfix installations we have that work properly.

> 
>     - The "pickup" fifo has been deleted from /var/spool/postfix/public
> 
>       Make sure $queue_directory contains a private/pickup fifo.

This is a /var/spool/postfix/public/pickup fifo, there is not a 
/var/spool/postfix/private/pickup fifo

> 
>     - File permissions are wrong
>       
>       postfix set-permissions

I didn't see anything wrong, and it would seem that permissions would 
completely stop delivery not just stop it until something jolts it back into 
action.

>       
>     - The O/S is buggy
> 
>       Disable SELinux, App-armor, ...

This is entirely possible, though we have other SLES servers running the same 
environment without issue.  I did just turn off AppArmor on the server with 
this problem, so we'll see what happens.

>       
>       or <http://tomayko.com/writings/that-dilbert-cartoon>
I'm guessing this won't help :)

-Doug

This email may contain confidential and privileged material for the sole use
of the intended recipient and MSU-KCMS. Any review or distribution
by others is strictly prohibited. If you are not the intended recipient,
please contact the sender and delete all copies.

Reply via email to