Wietse Venema:
Curtis:
In the mean time, it seems like using doing postsuper -r to re-activate
old queue files would be a good alternative. Hopefully that resolves the
expiration cycle issue that is caused when you inject a queue file directly
into the maildrop queue?
If that's
Wietse:
Curtis:
This is safe only when the maildrop queue is stopped, that is,
1) No submissions with the Postfix sendmail command while these
files are in the maildrop directory, otherwise mail will be
lost.
I'm still trying to understand why mail would be lost. Since it
On Wed, May 27, 2009 at 11:05:50AM -0600, Curtis wrote:
I'm still trying to understand why mail would be lost. Since it would be
impossible for the Postfix sendmail command to overwrite one of these files
due to a filename conflict (we write the files using filenames that would
never be used
Curtis:
Wietse:
Curtis:
This is safe only when the maildrop queue is stopped, that is,
1) No submissions with the Postfix sendmail command while these
files are in the maildrop directory, otherwise mail will be
lost.
I'm still trying to understand why mail would
Victor Duchovni:
the same time. If postsuper (which runs durin reload) is to be
allowed to race against your code, your mode 0700 file names have to
match the usual Postfix hex file names:
usec-5-hex-digitsinode-hex-digits
this is an undocumented interface, so you have to be willing
I've already been down this road. Forget about playing with queue file names,
permissions and all the other back door methods of accessing the queues, and
use the utilities supplied.
Calling an external app to make things happen isn't quite as elegant as being
able to drop files where you want
On Wed, May 27, 2009 at 02:25:24PM -0400, Wietse Venema wrote:
Victor Duchovni:
the same time. If postsuper (which runs durin reload) is to be
allowed to race against your code, your mode 0700 file names have to
match the usual Postfix hex file names:
Victor Duchovni:
On Wed, May 27, 2009 at 02:25:24PM -0400, Wietse Venema wrote:
Victor Duchovni:
the same time. If postsuper (which runs durin reload) is to be
allowed to race against your code, your mode 0700 file names have to
match the usual Postfix hex file names:
Sorry, the RELEASE_NOTES don't discuss undocumented behavior.
By review, I meant read the code... Postfix is open-source
software, if they are willing to take on the burden of supporting local
customization (their injection system can be viewed as a
customization),
and the reasons to
Wietse:
Without stopping Postfix, importing files safely could be done with
a new postdrop command-line option. This would be a privileged
option, since real queue files contain records that users are not
allowed to provide.
That would be terrific... and would seemingly resolve all concerns.
On Wed, May 27, 2009 at 01:47:27PM -0600, Curtis wrote:
For those wondering why we can't just commit to only using the provided
utilities to manipulate queue files, it's because we are giving individual
users the ability to view messages that were placed in the hold queue and
release them up
Wietse Venema:
The Postfix queue is designed to be a short-term message store
where files can be located quickly based on their name alone.
I don't think it is a good idea to re-purpose this design for
routine long-term storage of messages waiting for approval, or to
break the design by
The Postfix queue is designed to be a short-term message store
where files can be located quickly based on their name alone.
I don't think it is a good idea to re-purpose this design for
routine long-term storage of messages waiting for approval, or to
break the design by making file locations
Terry:
For those wondering why we can't just commit to only using the
provided
utilities to manipulate queue files, it's because we are giving
individual
users the ability to view messages that were placed in the hold queue
and
release them up to 30 days after the messages were
Viktor:
If the files are guaranteed to only have a single recipient at the
point
in your processing stream at which they are held, you don't have to
do
anything nearly so complex. Just retain the file's original name and
inode, by renaming it into a suitable directory tree in the same file-
Curtis:
In the mean time, it seems like using doing postsuper -r to re-activate
old queue files would be a good alternative. Hopefully that resolves the
expiration cycle issue that is caused when you inject a queue file directly
into the maildrop queue?
If that's postsuper -r from hold queue
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
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
Curtis:
We're not manually creating them, these are archived queue files that were
pulled from the hold queue, and then later released by being dropped into
the maildrop queue (using the technique discussed earlier in this thread).
This is safe only when the maildrop queue is stopped, that is,
Curtis:
We're not manually creating them, these are archived queue files that
were
pulled from the hold queue, and then later released by being dropped
into
the maildrop queue (using the technique discussed earlier in this
thread).
This is safe only when the maildrop queue is stopped,
On Fri, May 22, 2009 at 03:51:49PM -0600, Curtis wrote:
Curtis:
We're not manually creating them, these are archived queue files that
were
pulled from the hold queue, and then later released by being dropped
into
the maildrop queue (using the technique discussed earlier in this
On Wed, Feb 11, 2009 at 6:51 PM, Wietse Venema wie...@porcupine.org wrote:
Curtis:
Hi,
I'm looking for a safe way to re-inject an archived queue file that
was backed up and removed (via postsuper) from the hold queue. (Not
just this once, but on a regular basis.) I realize that it would be
On Thu, Feb 12, 2009 at 06:51:20AM -0700, Curtis wrote:
So, on a box that I know has nothing else feeding into the maildrop
queue, it would be safe to skip the step of dropping it in the idle
queue of a second instance (on the same filesystem) and running
postsuper -s to get a properly named
On Thu, Feb 12, 2009 at 08:46:51AM -0700, Curtis wrote:
Perfect. Does the pickup command have a trigger like qmgr that I can
use with postkick to get the queue file picked up from the maildrop
queue immediately? I'm guessing not since there's no mention of it in
the man page, but I thought
24 matches
Mail list logo
