Re[2]: Can't stop CRAM-MD5?

2002-11-03 Thread John



 Try just plain SMTP auth..account/properties/transport/SMTP
 authentication, then click  perform SMTP auth check use settings
 of mail
 retrieval.  Uncheck Require MD5, and do *not* check on the bottom
Pop before SMTP


I have done all that- that is the problem- I can't see how to
actually stop it from doing the cram check- it does it even if you
don't check that box-













































































Current version is 1.61 | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html



Re[2]: Can't stop CRAM-MD5?

2002-11-03 Thread John


 Did you double check also on the transport POP auth (Receive Mail)
 to see
 that MD5 was not checked? Also the account/properties/transport  
 panel was okay and set to regular.


Yes, did all of that.  Any other ideas?  TB is set to automatically
use cram if it can, even if you don't check the box.  For some
reason, my server must look like it accepts cram checks, even though
it doesn't.






Current version is 1.61 | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html



Re[2]: Can't stop CRAM-MD5?

2002-11-03 Thread John
G Now that is interesting... I don't remember TB! doing that before
...
G (long ago)..

G For reference, qmail does not support auth or MD5 auth, or POP
before
G SMTP, or SMTP before POP, in its basic installation. One must add
G additional packages and actually build them into qmail.


If that is the case, then I wonder why it is trying to use md5?  My
server claims that they do not support it-



Current version is 1.61 | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html



Re[2]: Can't stop CRAM-MD5?

2002-11-03 Thread John

G This is what I thought.. I believe you have cable. They don't
usually
G support auth, cable companies that is..

G Can you call tech support and ask them why you are getting the
5.7.1.
G error, or more specifically the

G Server reply - sorry, that domain isn't in my list of allowed
rcpthosts
G (#5.7.1)

G They can check their logs.



Well, I do have cable, but this problem isn't with the cable server,
it is
with fatcow.com

I had this problem with pocomail, but there was a setting in the ini
file to disable md5.  I was hoping there was a similar setting
somewhere with TB, apparently not.

I guess I'll just have to hope that fatcow will patch their server
(very unlikely) or I'll have to give up TB.



Current version is 1.61 | Using TBUDL information:
http://www.silverstones.com/thebat/TBUDLInfo.html