To fix this, we
will try to add the PLAIN authentication mechanism to the test.mc file (we cover
confAUTH_MECHANISMS in the next section), by adding the following line to the test.mc
file and rebuilding the cf file:
define(`confAUTH_MECHANISMS??, `CRAM-MD5 PLAIN??)
After you build a new test.cf file, run the same test again. This time, authentication
succeeds and the /tmp/auth.log file contains, in part, lines like the following:
14062 >>> 250-AUTH CRAM-MD5 PLAIN
14062 >>> 250-DELIVERBY
14062 >>> 250 HELP
This is the Title of the Book, eMatter Edition
Copyright ?© 2007 O??™Reilly & Associates, Inc. All rights reserved.
5.1 Support SMTP AUTH | 191
14062 <<< AUTH CRAM-MD5
14062 >>> 334 PW4gPDIyMDg3MzU4ODAuMTI1NTgxMzFAeW91ci5ob3N0LmRvbWFpbj4K
14062 <<< dGVzdGVyQGxvY2FsaG9zdCAzMDRhNDAwMTBmYWE5MjhiOWYzZTllZmIyOTJkODYxMQ==
14062 >>> 535 5.7.0 authentication failed
14062 <<< AUTH PLAIN dGVzdHVzZXJcMFRlc3RQYXNzd2QK
14062 >>> 235 2.0.0 OK Authenticated
Here, CRAM-MD5 fails as before, but now Thunderbird tries the PLAIN authentication
mechanism and that mechanism succeeds with ???235 2.0.0 OK Authenticated???.
Note that you should probably not use PLAIN if you are expecting authentication over
the Internet, because it allows usernames and passwords to pass in the clear.* To see
for yourself, use mimencode(1) or a similar program to decode the expression following
AUTH PLAIN earlier.
Pages:
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366