|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Victor Duchovni (Victor.Duchovni
morganstanley.com)
Date: Fri Sep 11 2009 - 13:11:06 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Fri, Sep 11, 2009 at 11:04:49AM -0700, Quanah Gibson-Mount wrote:
>
>> Also which postdrop is reporting errors? Is there more than one "postdrop"
>> on the system? More than one Postfix-related sendmail(1) with a different
>> default config directory? ...
>
> There is not one running that I see. Our install process specifically
> disables the system postfix installation as well.
The postdrop(1) helper utility is not a long-running process. It is
invoked (briefly) via sendmail(1) to deposit proto-messages into the
maildrop queue.
If you also have a "system postfix", with a default configuration
directory of /etc/postfix, and someone runs *that* sendmail(1), it
will launch the corresponding postdrop(1), which will try to use
the standard /var/spool/postfix/public/pickup socket, and will
fail to find it.
You may also have some mail waiting in /var/spool/postfix/maildrop/.
Please give the "system postfix" a non-default "syslog_name", or
otherwise figure out which postdrop(1) is complaining.
--
Viktor.
Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.
To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:majordomo
postfix.org?body=unsubscribe%20postfix-users>
If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]