No, the connect hook has already fired by the time that the TLS connection is
established.
But if the switch to TLS has basically the same effect as opening a new
connection, we should probably run the connect-hook again at that time.
Or we could have an additional 'connect_tls' (or
Michael Holzt wrote:
But if the switch to TLS has basically the same effect as opening a new
connection, we should probably run the connect-hook again at that time.
Or we could have an additional 'connect_tls' (or 'connect_restart'?)
hook (which could also be used on port 465 for the deprecated
Just thinking out loud here, but how about this for an interface to
generically provide hooks to new SMTP extensions (as pseudocode):
sub register_extension {
my ($COMMAND, capability, command, $pre, $post) = @_;
}
This would work like this (using AUTH as an example):
- $COMMAND
On 9-Aug-06, at 7:17 AM, Michael Holzt wrote:
I consider TLS beeing implemented by unrecognized_command unclean
anyway.
Ironically I consider the way AUTH was implemented to be unclean.
It's all a matter of perspective.
On Wed, Aug 09, 2006 at 05:44:56PM +0200, Emmanuel Lacour wrote:
Hi,
I'm writing a plugin which does some lookups on an LDAP server in
different hooks (mail, rcpt). It works, but it reconnects to LDAP on
every hook call :(
Is it possible to have a persistent connection at least for each
Emmanuel Lacour wrote:
If it is possible to keep this connection for more than one message,
this would be great :) But I really can't see how to do that :(
I ran into a similar issue with MySQL connections.
The trouble is that there are several instances of qpsmtpd so any
persistent
On 9-Aug-06, at 12:47 PM, Michael Holzt wrote:
I consider TLS beeing implemented by unrecognized_command unclean
anyway.
Ironically I consider the way AUTH was implemented to be unclean.
It's all a matter of perspective.
Oh, i'm sure we can agree that both ways are not too clean. I think
the
On 2006-08-09 19:02:42 +0100, Robin Bowes wrote:
Emmanuel Lacour wrote:
If it is possible to keep this connection for more than one message,
this would be great :) But I really can't see how to do that :(
I ran into a similar issue with MySQL connections.
The trouble is that there are
At Wed, 9 Aug 2006 09:13:45 -0700,
Ask Bjørn Hansen wrote:
On Aug 9, 2006, at 7:31, John Peacock wrote:
Just thinking out loud here, but how about this for an interface to
generically provide hooks to new SMTP extensions (as pseudocode):
sub register_extension {
my ($COMMAND,
