On Thu, Feb 05, 2009 at 10:02:47AM -0500, Doug Jaquays wrote:
> > Does:
> >
> > # postkick public pickup W
> >
> > move mail out of the queue in a more timely fashion?
>
> It does not seem to be anymore effective than mailq -q.
>
> Is there any more verbose logging that I can enable for this situation?
> PHP just cares that the message gets dumped into the queue and only
> returns yes it worked or no it didn't, which of course it works.
>
> It really seems like the timer to wakeup pickup isn't working properly,
> though I can't find any reason why it wouldn't be and nothing solid to
> say it isn't.
Search your logs for error/warning/panic/fatal messges from "pickup".
Add (temporarily) a "-v" flag to the pickup service in master.cf.
Read your logs carefully.
> It's frustrating to see that other systems set up exactly
Well, not *exactly* the same, but you have not yet found out how
this one is different.
The "pickup" daemon needs to be able read and write the "maildrop" queue,
and the permissions of the public/pickup socket need to be correct. The
maildrop queue should not contain any files that cause pickup severe
indigestion (fatal error on processing the queue file in question).
--
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:majord...@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.
