On Wed, 9 Nov 2005, John Peacock wrote:
> [EMAIL PROTECTED] wrote:
> > (The last similar issue I had was the difference between
> > "connection" and "transaction" notes, and my understanding is that
> > "transaction" notes should be able to be set and read between any plugins
> > - providing the setting plugin runs first, of course.)
It appears that my description, above, was written in my
confusion. I actually 'thought' the opposite: "connection" notes, which I
used in the example originally posted, are what I expected to be read from
any plugin after being set.
> connection != transaction
>
> A "connection" begins when a server connects to the host and ends when
> it disconnects.
>
> A "transaction" begins with HELO/EHLO and ends when the message has been
> accepted or denied (QUIT actually disconnects the connection) or the
> remote server RSET's the transaction.
>
> A single "connection" can (in principle) contain multiple "transactions"
> but in practice, I am personally unaware of common MTA's which will
> spool multiple transactions in a single connection.
>
> I believe that if you use $self->qp->connection->notes everywhere, you
> will be much happier.
So, that's actually what I *THOUGHT* I did, but it turns out that
I set the "connection->note", I actually read the "transaction->note". And
I didn't even pick up on it, with an example on the previous line of the
plugin that wasn't working! I knew it was something stupid. That's what I
get for waking up in the middle of the night and thinking I'm awake enough
to program :-)
Thanks for getting me to re-examine what I did.
--
Roger Walker First time contacting me at [EMAIL PROTECTED]
"HIS Pain - OUR Gain" Please use http://www.rope.net/roger.html
