Hi list, hi Timo, John and Peter,
I was on the wrong way, sorry, it's not dovecot to blame, it's definitely Zonealarm to blame. What lead me wrong is that multiple users of my old server were switched from another pop3 software to dovecot and the effect suddenly arose, so I kept dovecot as my suspect/scapegoat.
Timo Sirainen wrote:
On Sat, 2007-03-03 at 01:18 +0100, Michael Kress wrote:
+OK Dovecot ready. u-ERR invalid command u s-ERR invalid command s e-ERR invalid command e r-ERR invalid command r -ERR invalid command t-ERR invalid command t e-ERR invalid command e s-ERR invalid command s t-ERR invalid command t p-ERR invalid command p o-ERR invalid command o p-ERR invalid command p
-ERR invalid command
None of these come from Dovecot. It appears your proxy doesn't like the POP3 client.
That's right, to be more precise (and this might help others reading this thread) it's the combination ZoneAlarm + AntiVir Mailguard that doesn't work. After applying the solution from this thread http://forum.antivir.de/thread.php?threadid=19079 (sorry it's in German). I totally solved my issue without touching dovecot or anything other on the server side. The solution in a few words: I just had to switch ZA into a "learning mode" = "Medium Security" so it could gather what the client wants to do i.e. to talk pop3 with the server. After that I could switch ZA back to "High Security". Weird, but it works.
So your problem has nothing to do with Dovecot itself, and it can't be fixed in Dovecot side.
agreed. Thanks anyways for your analysis and sorry again for the confusion. At least it's clear for future users of the combination dovecot + ZA + AV Mailguard that the combination needs a special way of treatment on the client side (ZA). Maybe it's worth a FAQ entry? Have a good time Michael
-- Michael Kress, kress@hal.saar.de http://www.michael-kress.de / http://kress.net P E N G U I N S A R E C O O L