>Do you have any of the authorization options checked in the advanced >receiving options?
Nope, no options are turned on. This is a default, unmodified install of Entourage that is doing this. All I did was install and launch Entourage for the first time, configured my account, and told it to connect. And it isn't limited to just my copy, as the problem was actually reported to me from another user. I wrote the POP server and am trying to find out why entourage is doing this (what RFC is being followed... or is it a bug in Entourage), so I can modify my POP server to work with it. Again, it only seems to happen in testing with MY pop server. Other's that don't support APOP Entourage just sends the USER command like it should. But I can't for the life of me figure out WHY it doesn't like my pop server. I have even gone so far as to duplicate the welcome banner of pop servers Entourage WILL work with... no luck. So then I figured maybe Entourage has a bug that keeps it from working properly with POP servers running on the same computer. So I ran my POP on another computer, even so far as to give it a valid DNS entry... still the same problem. As soon as Entourage connects, it sends an AUTH command. So... maybe one of the Entourage programmers is on this list, and can tell me under what circumstances Entourage will start a POP session with "AUTH" so I can figure out what I am doing to trip it... or find out if it is a bug in Entourage (and if so... is there something I can do to work around it) -chris <http://www.mythtech.net> -- To unsubscribe: <mailto:[EMAIL PROTECTED]> archives: <http://www.mail-archive.com/entourage-talk%40lists.letterrip.com/> old-archive: <http://www.mail-archive.com/entourage-talk%40lists.boingo.com/>
