Ok.. so I have found this piece of code in my smtp.py file:<br><br> def _registerAuthenticators(self):<br> # Register Authenticator in order from most secure to least secure<br> self.registerAuthenticator(CramMD5ClientAuthenticator(self.username))<br>
self.registerAuthenticator(LOGINAuthenticator(self.username))<br> self.registerAuthenticator(PLAINAuthenticator(self.username))<br> <br>so if I switch the order around to put PLAINAuthenticator first will this hopefully work?<br>
<br><div class="gmail_quote">On 24 July 2012 14:54, Phil Mayers <span dir="ltr"><<a href="mailto:p.mayers@imperial.ac.uk" target="_blank">p.mayers@imperial.ac.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 24/07/12 14:29, Itamar Turner-Trauring wrote:<br>
<br>
> 3. The SMTP server's CRAM-MD5 implementation is buggy.<br>
<br>
If I understand the issue correctly, this is the case. The server<br>
incorrectly advertises CRAM-MD5, but it never succeeds since the server<br>
lacks the relevant secret.<br>
<br>
Obviously this is bad, but apparently many GUI clients handle such<br>
broken servers, by falling back to PLAIN auth. I can't say I've ever<br>
seen it in the wild though.<br>
<br>
<br>
Although I haven't used it in a while, my recollection was that<br>
Twisted's SMTPClient implementation did a similar thing, and tried the<br>
auth methods it was supplied "in order".<br>
<br>
It may be that the OP is using some wrapper API or local code that is<br>
mis-using this functionality, or of course that I am mis-remembering it.<br>
<div class="HOEnZb"><div class="h5"><br>
_______________________________________________<br>
Twisted-Python mailing list<br>
<a href="mailto:Twisted-Python@twistedmatrix.com">Twisted-Python@twistedmatrix.com</a><br>
<a href="http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python" target="_blank">http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python</a><br>
</div></div></blockquote></div><br>