On Fri, 17 Oct 2003, dick hoogendijk wrote:
On Fri, 17 Oct 2003 10:26:44 -0500 (CDT) Joe Laffey <[EMAIL PROTECTED]> wrote:
> Oct 17 09:43:59 raw courieresmtp: > id=002DD19F.3F8AC57D.000048EE,from=<>,addr=<[EMAIL PROTECTED]>: 454 > 4.3.3 TLS not available
Maybe a secure TLS connection is not possible ?
I wondered that, but why would it not simply try unencrypted? I do not have my server set up to use TLS.
The server replied with a 4xx code to the STARTTLS command (enable encryption).
All that the sender can infer from that is that the command failed with a 4xx status code. Nothing more, nothing else. Any 4xx status code means that the receiving server is temporarily unable to process the command, and that the sender should try again later.
That's all it means, nothing more, nothing else. If the server did not support encryption altogether, this would've been indicated in a different way (the server would not advertize the STARTTLS ESMTP capability).
The sender here cannot assume why the command failed. All the sender knows is that the command was rejected with a temporary failure indication. The sender cannot conclude that this is because the recipient does not support encryption. Another possibility, just as valid, is that the receiving mail server is currently running low on memory and cannot accept more mail, and the sender should try again later.
pgp00000.pgp
Description: PGP signature
