reopen 370714
--

Perhaps this is an invalid bug, but it would be nice to await my clarification _before_ simply closing it.

remote_smtp_smarthost:
 debug_print = "T: remote_smtp_smarthost for [EMAIL PROTECTED]"
 driver = smtp
 hosts_try_auth = ${if exists {CONFDIR/passwd.client}{DCsmarthost}{}}
 tls_tempfail_tryclear = false

However, if no password has been set, the passwd.client file still exists and all access to the smarthost fails because it can't auth and won't try without it.


|+--------------------------------------------------------+
||hosts_try_auth|Use: smtp|Type: host list*|Default: unset|
|+--------------------------------------------------------+
|
|This option provides a list of servers to which, provided they
|announce authentication support, Exim will attempt to authenticate as
|a client when it connects. If authentication fails, Exim will try to
|transfer the message unauthenticated. See also hosts_require_auth, and
|chapter 33 for details of authentication.

Please note "if authentication fails, exim will try to transfer the
message unauthenticated".

If you still think this is wrong, please show an example of a message
transmission failing and outline a way to fix the issue.

The problem is when used in conjunction with the next line:

        tls_tempfail_tryclear = false

When both were set (and no password available in the file), the system would just sit forever waiting. I'm not exactly sure what it was waiting for (I didn't do a TCP-level trace), but removing either line caused it to start working again.

I suggest not having the passwd.client file exist unless there is actually something to put in it.

Perhaps it would be best to have "tryclear = true" in all cases. Setting a password for one smarthost could cause others to stop working.

                                          Brian
                                 ( [EMAIL PROTECTED] )

-------------------------------------------------------------------------------
            The only bad mistakes are those you fail to learn from.


--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to