Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email firstname.lastname@example.org
From: Victor Duchovni (Victor.Duchovnimorganstanley.com)
Date: Fri May 22 2009 - 15:03:11 CDT
On Thu, May 21, 2009 at 07:48:43PM -0600, Curtis wrote:
> It would appear that we're seeing a side effect of dropping files into the
> maildrop queue like this. if there are messages in the maildrop directory
> when a "postfix reload" is run, we're seeing duplicate messages.
Yes, "postfix reload" runs "postsuper", which will fix-up the names of
files. To avoid this, you'd have to do that yourself, before marking the
file mode 0700. The first 5 bytes are a microsecond timer measured just
after the created file's inode is obtained via lstat(2) and before it
is renamed to:
Getting all of this right is done by sendmail/postdrop.
> .then the message gets sent a second time (or at least I'm guessing that's
> how the duplicate happens). I guess the answer is to either run that
> second instance of postfix that doesn't get hit with a "reload" very often
> or. would running "postsuper -s" solve it?
Running "postsuper -s" causes a race, and is too expensive. Why are you
manually creating queue-files again?
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:
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.