On 19 Sep 2004, at 11:40, Michael Holzt wrote:
1: Why call the first one in the rcpt chain at all? Just make it a connect plugin.
I could do this, and in fact i have attached an modified version of 'check_relay' which just does that. As it has otherwise the complete same functionality as 'check_relay', you might think about replacing the stock 'check_relay' with my version.
There seems to be one problem though (i think i remember we had this
already as a topic some time ago): It seems that a transaction->relaying
set in a connect plugin got lost by the time the rcpt plugins is
called. Currently the usual workaround in code (e.g. also done in the SMTP
AUTH Handler) is to set $ENV{RELAYCLIENT} instead.
I think i already suggested adding a connection->relaying flag, which
value is copied to transaction->relaying when a new transaction is startet.
This would allow us to get rid of using $ENV{RELAYCLIENT} as a flag, we
just should set it right before calling a queue plugin.
Hmm. Perhaps relaying is purely a function of the connection. I just wasn't sure where the right place to put it was. Would it make more sense to be part of the connection?
The default relaying setting is based on IP, which is part of the connection. But is AUTH part of the connection or part of the transaction?
Matt.
