|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Wietse Venema (wietse
porcupine.org)Date: Fri Sep 28 2001 - 12:28:28 CDT
Ben Rosengart:
> On Fri, Sep 28, 2001 at 10:16:17AM -0400, Wietse Venema wrote:
> >
> > That seems to be a popular approach. Use expensive equipment only
> > for the first delivery attempt, and use fallback_relay to send all
> > undeliverable mail to a queue on slower storage.
>
> Given the popularity of this, would you consider building equivalent
> functionality into Postfix so it can be done with one instance? That
> way, it could be a configuration option rather than an expert trick.
It is not possible. Now or in the foreseeable future.
Postfix's very design is based on writing a message to disk exactly
once (and using a single queue file per message). This is possible
only when queue files do not move across file system boundaries.
If I have the choice between using two Postfix instances versus
doubling the complexity of Postfix's queue management code, then
I will take the two Postfix instance approach any time, because it
needs less code and therefore it is more reliable. This may waste
a few cycles and bytes.
One has to keep in mind that hardware becomes faster and cheaper
each year. Code is extremely expensive, it slows down as it bloats
over time, and its cost only increases over time.
In fact, I am going back to an earlier idea to have a queue that
does not move queue files at all. It uses append and truncate and
thereby saves a tremendous amount of disk I/O overhead by avoiding
the relatively expensive file create, rename and delete operations.
That approach is even less compatible with moving delayed mail to
a different queue than the present one.
Wietse
-
To unsubscribe, send mail to majordomo
postfix.org with content
(not subject): unsubscribe postfix-users
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]