|
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: Thu Nov 01 2007 - 12:49:34 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Thu, Nov 01, 2007 at 08:51:55AM -0700, Kevin Stevens wrote:
> >What version of Postfix is shipped with Leopard?
> >
> > $ postconf mail_version mail_release_date
>
> mail_version = 2.4.3
> mail_release_date = 20070531
Yes, substantially more recent, good to see Apple catching up
periodically.
> Not sure what Tiger used, but obviously it was quite a bit older.
Tiger had 2.1.5.
> >>After running for about an hour (hard to tell exactly), I'll suddenly
> >>see a bounce notice like this:
> >>
> >>Oct 30 19:46:42 babelfish postfix/local[2780]: AC02A768D9:
> >> to=<kes
pursued-with.net>, orig_to=<zixxer
pursued-with.net>,
> >> relay=local, delay=0.56, delays=0.45/0.05/0/0.06, dsn=5.1.1,
> >> status=bounced (unknown user: "kes")
> >
> >Sounds like a "netinfo" problem. Is there some sort of "netinfo"
> >listener
> >that is recycled each hour? Perhaps the C-library getpwnam(3) fails
> >for
> >long-running processes as a result.
>
> I thought of that, but what's confusing to me there is I thought the
> local daemons were short-lived spinoffs from master anyway, so why
> would it matter?
They are not that short-lived, if deliveries happen at least 100s
apart (max_idle) each local(8) daemon can live for up to 100 deliveries
(max_use), so the total lifetime can be as high as 10,000 seconds, but
is more likely lower:
L = 100 * N / M
L = daemon lifetime
N = average # of daemons running
M = message rate
If you have 10 local delivery agents, and 1 message per second, the
lifetime is ~1000s.
> Unless master does the lookup and passes it off to
> local. But in that case, why is the mail accepted for delivery at all?
No local(8) is doing its own lookups.
> > $ make mypwd
> > $ ./mypwd kes postfix nobody
>
> Egad. I'll have to work on that one.
I don't know a more efficient way to test reliability of password
lookups. When failure sets in, does it really fail all local recipients
indefinitely? Is "reload" enough to solve the issue? Once the problem
happens, you can "ktrace" the local delivery agent and perhaps learn
what is breaking.
--
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 ]