>Here are the two Auth statements: >250-AUTH GSSAPI NTLM LOGIN >250-AUTH=LOGIN
Great, so it supports the right stuff. >Odd, this is what I got for the EHLO: >220-bigbrother.pecandeluxe.com Stalker Internet Mail Server V.1.8b9d14 is >ready. >220 ESMTP is spoken here. You are very welcome >EHLO pecandeluxe.com >250-bigbrother.pecandeluxe.com your name is not pecandeluxe.com >250-HELP >250-ETRN >250-AUTH=LOGIN >250-AUTH LOGIN PLAIN CRAM-MD5 >250 EHLO Very odd... I also use SIMS so I know it works fine with the SMTP Auth version of Emailer. But that isn't even remotely what I got from the outside. This is what I get: iMac:~ chrisbartlett$ telnet bigbrother.pecandeluxe.com 25 Trying 70.242.214.77... Connected to bigbrother.pecandeluxe.com. Escape character is '^]'. 220 ********************************************************************0****0* ***0 ***************2******200**22*2******0*00 EHLO mt.net 500 5.3.3 Unrecognized command HELO mt.net 250 DURANDAL.pecandeluxe.local Hello [70.111.125.114] quit 221 2.0.0 DURANDAL.pecandeluxe.local Service closing transmission channel Connection closed by foreign host. iMac:~ chrisbartlett$ I'm guessing you are running some kind of outside SMTP proxy or mail forwarder that is intercepting the connection from me. >It was working just fine before the cut-over to Exchange. And it is still >working, so long as I set up my accounts the "old" way. Makes sense, I can bet SIMS has NO idea what that username string is you are passing it (the one that works with Exchange). >I downloaded it within the last couple of weeks (got it so I could access >my Comcast account). How recently did you make this change? I made the change maybe 2 or so weeks after I originally released the hack. I silently replaced the version on my web site with the corrected version. So if you downloaded it recently like you say, you should have the correct version. If in doubt, just redownload it. Or, open it with ResEdit and check STR# 3400 Entry #8. It should say EHLO (normal Emailer is HELO). >Just let me finish by saying I appreciate your time on this. Your hack >seems very stable and functional. I just know (from the long history of >this list) that [EMAIL PROTECTED] has always been problematic. I'll reach out to an Exhange using buddy and see what he has to say about the way it handles log ons. I'm going to still guess the string you are using as the username is needlessly complex. Maybe my friend can shed some light on a better way to gain access. -chris <http://www.mythtech.net> ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
