Olivier MJ Crepin-Leblond:
> Dear Wietse,
>
> thank you for your detailed explanation.
> In the future, would you consider having unique identifiers generated
> by an algorithm which would take into account the CPU ID (or other
> unique identifier), process ID & time, so as to make it a unique ID
> worldwide, or is this not something which you would find to be of
> interest?
The RFC822 Message-ID field is supposed to uniquely identify the
message, not the transaction. This is easy to achieve when each
MTA instance uses a different name.
The RFC3463 3463 ENVID field is supposed to uniquely identify the
transaction, not the message, for the purpose of delivery status
notifications.
The RFC3885 MTRK command provides a way to request message tracking
based on the RFC3463 3463 ENVID field.
Generally, it seems unrealistic to expect that Postfix will achieve
global dominance, therefore the next best approach IMHO is to deploy
an Internet standard that has global support. Given enough demand
(or a sufficient quality design, in advance of implementation)
Postfix may eventually support this.
Wietse
> I am asking this, in view of future possible instances of the law re:
> legal status of an email & its authoritative tracking.
>
> Just curious. Thanks,
>
> Olivier
>
> ----- Original Message -----
> From: "Wietse Venema" <[EMAIL PROTECTED]>
> To: "Postfix users" <postfix-users@postfix.org>
> Sent: Friday, November 14, 2008 12:40 PM
> Subject: Re: Queue ID gets reused? Not unique?
>
>
> > Durk Strooisma:
> > > >> I was examining my Postfix logs and saw two sequential sessions
> using
> > > >> the same queue ID. I was a bit surprised as I had the
> assumption that
> > > >> queue IDs were generated randomly, which means they should be
> > > >> practically unique.
> > > >
> > > > Postfix behaves as documented. Please point out where the
> documentation
> > > > made the promise to you that queue IDs are unique.
> > >
> > > Thanks. Well, the documentation is fine. Actually, I think it's
> one of best
> > > among software projects. The only information I couldn't find was
> about the
> > > creation of queue IDs. Therefore I found myself in the situation I
> couldn't
> > > refute my assumption.
> >
> > Sometimes I am in the mood to pull people's leg.
> >
> > More seriously, I take pride in documenting the behavior that is
> > guaranteed. The algorithm that assigns queue IDs may change,
> > therefore the documentation makes no promises about how it's done.
> >
> > Currently the ID is the name of a short-lived file. A future queue
> > implementation may use persistent files. In that case the queue ID
> > may need to be assigned in some other way. The only hard requirement
> > is that no two messages have the same ID while they are in the
> > Postfix queue.
> >
> > Wietse
>
>
>
