[EMAIL PROTECTED] wrote: > I think that sounds appropriate, as TLS essentially starts a new > connection.
It's a required part of the RFC, see RFC-2487 Section 5.2: > Upon completion of the TLS handshake, ... [t]he server MUST discard any > knowledge obtained from the client... > Can anyone confirm if the connect hook will fire after TLS (it's > listed after TLS in the config/plugins file)? No, the connect hook has already fired by the time that the TLS connection is established. That happens later at STARTTLS (by hooking into unrecognized_command), which is typically immediately after EHLO has completed. The order of lines in config/plugins only determines what order *within* *each* *hook* the plugins will fire. > Can anyone please suggest a simple way to pass a note from the > connection plugin to everything after TLS? You can't. What information are you trying to pass? Can you redo whatever analysis you performed before, say in a rcpt hook? John
