Thank a lot! It works very well! Really cool! Thanks, every one who helped me on this problem.
Su -----Original Message----- From: Mark Keasling [mailto:[EMAIL PROTECTED]] Sent: November 19, 2002 11:55 PM To: Su Li Subject: Re: Timsieved valid commands Hi, On Tue, 19 Nov 2002 23:30:16 -0500, Su Li <[EMAIL PROTECTED]> wrote... > Thanks so much. That is helpful. As my client is used internally within the fire >wall. I am sure SASL will be better solution. But LOGIN or PLAIN is good enough for >authentication for now. I gonna try LOGIN and PLAIN first. > > I still got 2 questions to confirm with you: > > 1. I wounder should I replace "b64data=" in your example with base64 user name and >password, or the syntex should be "b64data=encodedData" where encoded Data is the >actual encoded password? > Sorry, I wasn't clear about that... The first b64data= should be replaced with the encoded username for example the username "cyrus" encoded would become "Y3lydXM=" C: AUTHENTICATE "LOGIN" S: {12} S: VXNlcm5hbWU6 C: {8+} C: Y3lydXM= The second b64data= should be replaced with the encoded password for example the password "pass1234" encoded would become "cGFzczEyMzQ=" S: {12} S: UGFzc3dvcmQ6 C: {12+} C: cGFzczEyMzQ= S: OK > 2. For AUTHENTICATE "PLAIN", I don't need encode password and user name right? > >From my read of the rfc that was my impression. So I would venture to say that you are correct. One thing that tripped me up for a while was the timsieved accepts strings in only two formats: "quoted strings like this" or asynchronous literal: {82+} Or a literal string like this which can contain new lines and probably 8 bit data. Like with IMAP, I originally thought you could send synchronous literals: C: {82} S: + OK send your data C: Or a literal string like this C: which can contain new lines C: and probably 8 bit data. or atomic strings like: atomic-strings-like-this Regards, Mark Keasling <[EMAIL PROTECTED]>
