Can't connect using Secure pop3.

[zap]

I just did a clean 4.5 OS install on Suse 10.0 OSS.

Almost everything works fine, only problem is secure POP3 service.

When outlook 2003 connects to port 995 I get prompted to type in username and pwd. just like if it was incorrect to begin with. I know the usr/pwd is correct (same usr/pwd works fine through webmail). Outlook says the server responded this error msg. '-ERR only valid after entering TLS mode'

I have tried to enable POP proxy and using port 7995 but without any luck.

Any ideas?

Thanks
Zap.

[anand]

it looks like in 4.5 if you connect the POP3 SSL port (995), we expect you to STARTTLS before we allow you to enter your username/password. Yikes, this is very broken.

Not sure from your description if this is the same problem you are running into though.

As a workaround you can set zimbraPop3CleartextLoginEnabled to TRUE.

[anand]

Just filed: http://bugzilla.zimbra.com/show_bug.cgi?id=13970

[urban@abak]

same problem here... enabling clear text login does still not work, though... we'll see what happens after we restart the server...

[urban@abak]

is there a solution for this somewhere on the horizon? even clear text login does not work... what can we do?

[phoenix]

is there a solution for this somewhere on the horizon? even clear text login does not work... what can we do?

Doesn't the bug that anand file do what you want? If so, then vote on it.

[urban@abak]

what do you mean if it doesn't do what i want? i'm not really good at this bugzilla... all i know is that it still ain't working. we set up the enable clear text login to true and it doesn't work. now i have disabled this option and still no good. it would be kindly appreciated if you could help as we have quite a few users using it.

[phoenix]

What I mean is, does the bugzilla entry listed above address your problem? If it does then vote on it. There isn't any workaround or fix until that bug is resolved.

[urban@abak]

anyone having the same problems may use this as a workaround the problem...

[phoenix]

same problem here...

So after all that, you didn't have the same problem.