------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.
http://www.exim.org/bugzilla/show_bug.cgi?id=248
------- Comment #7 from ph10@??? 2007-01-30 16:39 -------
(In reply to comment #6)
> I suspected that passed-on connections could pose problems, but then I thought
> that TLS would always be started by the same process that sent the first
> EHLO, and that no further EHLOs were needed. I can see that it is possible to
> send a message without TLS first, then pass on the connection to the next
> delivery process, which issues STARTTLS and the new EHLO, but under what
> circumstances would that happen?
Always! The first process has to shut down TLS before it passes the connection
to a new process. The new process then starts it up again. That's the only way
I could make it work, since the TLS processing data is held in the process and
cannot be passed on.
> I was mostly concerned about callout verifications, after which
> $sender_ip_address and $sender_port will still be set.
The easiest would then be to reset in that particular case. Or we could
document it as a feature. (Only joking).
--
Configure bugmail:
http://www.exim.org/bugzilla/userprefs.cgi?tab=email
