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
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 transaction log
On Wed, 22 Aug 2007 12:48:09 -0700
JT Moree [EMAIL PROTECTED] wrote:
Sydney Bogaert wrote:
You assume here that the process numbers are different for each message.
While it will work for forkserver and tcpserver, that is not the case
with prefork or Apache (also preforking).
Is there a
I wrote some small helper scripts for parsing logs. Would they be
useful enough to include in qpsmtpd?
--
JT Moree
You assume here that the process numbers are different for each message.
While it will work for forkserver and tcpserver, that is not the case
with prefork or Apache (also
Sydney Bogaert wrote:
I wrote some small helper scripts for parsing logs. Would they be
useful enough to include in qpsmtpd?
You assume here that the process numbers are different for each message.
While it will work for forkserver and tcpserver, that is not the case
with prefork or Apache
On Wed, 2007-08-22 at 13:06 -0700, James W. Abendschan wrote:
On Wed, 22 Aug 2007, Sydney Bogaert wrote:
You assume here that the process numbers are different for each message.
While it will work for forkserver and tcpserver, that is not the case
with prefork or Apache (also preforking).
