-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
In message <[email protected]>, Jeremy Harris
<[email protected]> writes
>On 06/02/14 14:14, Richard Clayton wrote:
>>
>> begin authenticators
>>
>> smarthost_login:
>> driver = plaintext
>> public_name = LOGIN
>> client_send = : [email protected] : password
>>
>> other_login:
>> driver = cram_md5
>> public_name = CRAM-MD5
>> client_name = otherusername
>> client_secret = otherpassword
>
>> but once one starts to worry about CRAM-MD5 then one needs client_name
>> and client_secret lines instead....
>>
>> What advice can be offered apart from not starting from here ?
>
>You put the cram-specific bits in the cram authenticator, and the
>login-specific bits in the login authenticator, yes?
yes ... and I then got complaints
authentication required but no common mechanisms were found
- --
richard Richard Clayton
Those who would give up essential Liberty, to purchase a little temporary
Safety, deserve neither Liberty nor Safety. Benjamin Franklin 11 Nov 1755
-----BEGIN PGP SIGNATURE-----
Version: PGPsdk version 1.7.1
iQA/AwUBUvO2K+INNVchEYfiEQJWswCfVs4lAb8T63BDcsw8XSb0RfzRATUAn1lv
0aF8ftexnk4McSgbt3/YI2ob
=dXdc
-----END PGP SIGNATURE-----
--
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/
