Responses interspersed below. Wasn't it chris [EMAIL PROTECTED] who once said...
>>As for who "set up" this mess... you can talk to me. Although I had help >>from and "Exchange expert", their background is with PC's not Macs. >>Exchange is working great for everyone using Outlook 2003. And I can even >>use it decently with Entourage 2004. I'd just like to make it work with >>[EMAIL PROTECTED] > >Do you use any Exchanges features? Or is it just acting as a mail server? >If so, you bought a really expensive mail server (ie: there are just as >good, if not far better mail servers available cheaper than Exchange... >many are free!). > >Of course, if you use Exchange's other features, like calendaring and >junk like that, then that is a different story. > >>What directions do "who" provide? In Outlook 2003 when they log onto >>their computer, they are logging into the Active Directory domain. That >>links them to their Exchange mailbox... end of discussion. > >I assumed you were going thru some kind of a provider or IT department >and not running this on your own (your first email said you were forced >to migrate to Exchange, so I took that as someone else was in control of >the mail server). I AM the IT department!!! "Forced" is from non-IT management. And the plan IS to use other Exchange features. > How do Outlook users connect from outside the network? They do not, currently. But that's just because none of them have taken their laptops off-site lately. >Can they connect from home? Or is their no outside server access? I tried >to telnet to smtp.pecandeluxe.com but I got no response (it did resolve >an IP address however, so something else may have been blocking the >reply). Yeah, meet my firewall. And probably Postini. >>So, I'm guessing in your little "hack" of [EMAIL PROTECTED], the SMTP Auth is >>reading from the Email account string? I could see where that is causing >>problems. > >Correct, the hack takes the same username and password as used by the POP >logon. However, since it works for POP, it should work for SMTP. What may >be more likely is that your server doesn't support the Auth type I've put >into Emailer. I'd be able to check that if I could telnet to your mail >server. If you want to do that for me, all you need to do is telnet to >the SMTP server (port 25) and send the command "EHLO pecandeluxe.com". >The server should reply with a banner message, one of the lines should >say "AUTH" and list some types (Plain, Login, CRAM-MD5, Kerberos, etc). >It needs to list "Login" as one of the types. If it doesn't, the current >hacked version of Emailer won't work. If it doesn't, but it DOES list >"Plain" as one of the types... I'm currently working on a version that >does that type (I'm having a problem creating the correct string, if >anyone is a decent C++ programmer, contact me). As soon as I get it >working, you are welcome to a copy of that version. Here are the two Auth statements: 250-AUTH GSSAPI NTLM LOGIN 250-AUTH=LOGIN >If it doesn't list Plain or Login, then you are probably out of luck >unless you can disable SMTP Auth entirely and go with another auth method >(like IP authentication or POP Auth). > >>But the funny thing is that when I try to send using my "backup" server >>as the SMTP server, I still get an authentication failure. I did not >>think my "backup" server was doing SMTP Auth (other than checking valid >>IP's to prevent relays). If it is and it is receiving "pecandeluxe/doug >>starkey/doug_starkey" as the account, then that could be where my problem >>is on that end. > >I was able to telnet to your bigbrother.pecandeluxe.com server, and it >doesn't look like it support SMTP Auth at all (at least it doesn't >advertise that it does, and it actually refuses the EHLO command, which >means it claims it doesn't support extended SMTP commands, which means it >shouldn't support SMTP Auth either which is part of extended SMTP). It >does reply to the older HELO command. 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 >This means the SMTP Auth hacked version should NOT work with your backup >mail server. Try the regular version and see if that works. 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. >Oh, that reminds me... when did you get the SMTP Hacked version of >Emailer? The first release I did I forgot to change the HELO to EHLO. >Some mail servers will disable extended SMTP commands if the HELO command >is issued instead of EHLO. Exchange may in fact support the SMTP Auth >hacked version of emailer, but is refusing the AUTH command. If you have >the original release you are sending the wrong opening command. >Redownload it from my web site <www.mythtech.net/SMTP_AUTH_Login.sit> and >see if the problem goes away. 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? 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. Thanks, Chris. ___________________________________________________________________________ To unsubscribe send a mail message with a SUBJECT line of "unsubscribe" to <[EMAIL PROTECTED]> or <[EMAIL PROTECTED]>
