Reply to thread

Message: <blockquote data-quote="reagan+carter" data-source="post: 96357" data-attributes="member: 24635">thanks a lot for testing it out!Nothing to care about with most of the errors: 'table account already exists' or 'table message already exists' simply means that the table already exists and won't be re-created on-the-fly at startup, I could have dropped these errors silently but I didn't.But these ones are far more interesting:2006-12-10 16:41:51.937500 [ERROR][6]: ProviderPOP3 : OnUpdate failed while connecting and fetching content for Provider Jason's Email: Server returned:-ERR authorization failed2006-12-10 16:41:51.953125 [ERROR][6]: Provider: OnUpdate( Jason's Email ) failedThe authentication to your mailbox has failed. The most obvious reason is a password/login couple mismatch. Then a problem with the authentication methods implemented (not compliant with standards?).If you've chosen 'APOP or none' in the Setup window then it first tries to check if your provider actually accepts APOP authentication and in this case proceeds to an APOP transaction, otherwise a simple unprotected USER/PASS (no authentication) is issued.If you ticked 'SASL' then it will first try DIGEST-SASL if applicable, then CRAM-MD5 and finally if CRAM-MD5 is unsupported throws an error.So first try to check if you didn't make a mistake typing your password/login (I'm sure you've already cross-checked your login parameters, but...)then if your server actually accepts either APOP or DIGEST-MD5 or CRAM-MD5. Other authentication methods such as NTLM are currently unsupported. In any other case, that must be a problem with my authentication methods, I was only able to try them out with GMail and some public Cyrus POP3 servers.keep me postedP.S. if the problem is on my side please give me the name of your POP3 service provider and if it gives away free accounts, I will check with them, directly.</blockquote>

Verification