On Sun, 2 Sep 2007 18:48:00 +0200
"Peter J. Holzer" <[EMAIL PROTECTED]> wrote:
> > + $self->respond(250, $from->format . ", sender OK - your transaction
> > id is ".$self->transaction->id);
> I like that, although I suspect that most clients will just discard it.
But some clients show the t
On 2007-08-23 18:50:33 +0200, Hanno Hecker wrote:
> But it would be easy to add / generate a transaction id after every
> reset_transaction() call. This could be logged instead of (or as
> addition to) the PID.
[...]
> Index: lib/Qpsmtpd/SMTP.pm
> ==
I currently use the following in our sql logging plugin to generate a unique
id in the database:
my @sname = split(/\./, $self->qp->config("me"));
my $sqlIdent = $sname[0].$$.'r'.int( (( time ^ $$ ) * rand($$)) /
rand(time/$$));
With each mx box running at ~30 cps we get dups often enough I'm con
JT Moree wrote:
> Hanno Hecker wrote:
>>> Is there a message ID that is unique to each message?
>> Not until the sending client has submitted a 'Message-ID' header ;-)
>
>> But it would be easy to add / generate a transaction id after every
>> reset_transaction() call. This could be logged instead
Hanno Hecker wrote:
>> Is there a message ID that is unique to each message?
> Not until the sending client has submitted a 'Message-ID' header ;-)
> But it would be easy to add / generate a transaction id after every
> reset_transaction() call. This could be logged instead of (or as
> addition to
