Guy Hulbert wrote: > There have been several adequate suggestions. This is only a problem if > it goes into the qpsmtpd core since some of the suggestions are reported > to be in use already. how is this a problem. those uses should still work even if we start with the same variable because they would overwrite what is in core. The plugin maintainers can update as they have time.
good idea about the requirements. > 1. A unique ID per message (on one server). > 2. Ability to distinguish per recipient. > 3. Ability to identify the server. 2) per recipient or per message? I don't see a way to make an id per recipient since any message can have multiple recipients. 3) which server are we talking about? > A sequence solves (1) except for simultaneous processing of <snip> > A counter solves 2. > > Any tag which is unique per server solves 3. It is probably simpler to > make this configurable by the end-user. if A solves 1, B solves 2, and C solves 3 then A+B+C should solve all three and it's pretty simple to do so let's just do it. While letting the end user make changes is nice it defeats the purpose of putting a transaction ID into core where everyone can know and rely on it working the same way. -- JT Moree
