>And, let's clarify, that IDEALLY, I don't want to be using my backup >server at all! I want to be doing POP & SMTP via the Exchange server. So >ultimately, whatever fix we arrive at needs to work for both protocols.
You did try the new username on the Exchange server and not the backup server right? I understand the plan is to get it to work all with Exchange. I was trying to simplify the exchange username in hopes to narrow down the source of the SMTP Auth problem. Another thing to try is replace the space in Doug Starkey with %20 and see if that helps. If not you can always run a stream log of the SMTP session that is failing and send it to me. That will show exactly what is being sent. Just keep in mind, the username and password are in there and are base64 encoded. I'd tell you to delete them for safety, but the point is really to decode that string and make sure it is really sending what we think it is sending. If you decide to go that route, just delete the password portion. That way I can decode the username and verify that it is really sending the entire username. (you will see a section that says AUTH LOGIN. Then two lines that appear to be jibberish. Delete the SECOND of those two lines, that is the password. The first one is the username.) Or, I can send you a small app that does base64 encoding and decoding of strings so you can decode both the username and password and make sure they are really what they should be. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
