strange pop protocol? [solved]

Stefan Palme kleiner77 at
Fri May 1 01:10:32 EDT 2009

On Thu, 2009-04-30 at 20:48 +0200, kleiner77 at wrote:
> On Thu, 2009-04-30 at 14:15 -0400, Wesley Craig wrote:
> > On 30 Apr 2009, at 13:10, Stefan Palme wrote:
> > > No, the pop server does not hang. After this "QUIT" message the client
> > > disappears. The next connection from the same client (or from any  
> > > other
> > > client) works normally - client can fetch at least one email.
> > 
> > Have you enabled cyrus telemetry for this user?  I'd probably look at  
> > that.  
> Never heard about "telemetry" until now, but just have found how
> to enable will. Will take a look at the generated logs...
> > The behavior you're describing doesn't make a ton of sense.

After a long night of debugging and network sniffing I had to
learn, that the problem was NOT the cyrus imap server, but 
wireshark :-(

The pop3 sessions in question have been pop3/ssl sessions, so I used
wiresharks feature to decode this SSL stream (I am running the server,
so I have access to the corresponding rsa key).

Decoding of the first three or four pop3 request/response pairs
obviously worked, but after the "RETR 2" command from the client,
wireshark only printed data sent by the client - data sent by the
server simply was "hidden" in wiresharks output.

Thanks for the great hint concerning "telemetry" - the telemetry logs
showed the *complete* pop3 session, with everything as expected :-)


More information about the Info-cyrus mailing list