[Dovecot] Logging IMAP transactions
Mulberry has the ability to log the IMAP exchange client-side. Is there an equivalent logging feature in Dovecot (0.99) to log the IMAP exchange server-side?
My problem is that Mulberry is displaying some complex MIME structures incorrectly (eg. nested/forwarded messages) but it seems to go away if I close a folder and re-open it. I'm suspecting that Dovecot is reporting the wrong structure on first access and then fixes something on subsequent accesses. I'd like to log the FETCH result with the structure information to see if I can spot this happening.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 15-09-2004 01:36, Kenneth Porter wrote: | Mulberry has the ability to log the IMAP exchange client-side. Is there | an equivalent logging feature in Dovecot (0.99) to log the IMAP exchange | server-side? | | My problem is that Mulberry is displaying some complex MIME structures | incorrectly (eg. nested/forwarded messages) but it seems to go away if I | close a folder and re-open it. I'm suspecting that Dovecot is reporting | the wrong structure on first access and then fixes something on | subsequent accesses. I'd like to log the FETCH result with the structure | information to see if I can spot this happening.
Maybe use ethereal, and its nice "Follow TCP stream" plugin?
~ - Jonas
- Jonas Smedegaard - idealist og Internet-arkitekt
- Tlf.: +45 40843136 Website: http://dr.jones.dk/
~ - Enden er nær: http://www.shibumi.org/eoti.htm -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBR/OXn7DbMsAkQLgRAhRbAJ9m1Hj78SI+EDcFeHxEVPc9pQT4LQCfX5Y8 FeXwSaBXWuB3GTW1cFep3Og= =3+oz -----END PGP SIGNATURE-----
On 15.9.2004, at 02:36, Kenneth Porter wrote:
Mulberry has the ability to log the IMAP exchange client-side. Is there an equivalent logging feature in Dovecot (0.99) to log the IMAP exchange server-side?
"rawlog". See bottom of http://dovecot.org/bugreport.html
My problem is that Mulberry is displaying some complex MIME structures incorrectly (eg. nested/forwarded messages) but it seems to go away if I close a folder and re-open it. I'm suspecting that Dovecot is reporting the wrong structure on first access and then fixes something on subsequent accesses. I'd like to log the FETCH result with the structure information to see if I can spot this happening.
0.99.10.8 release fixed some problems with it. Are you using it or newer?
The difference between first access and next one is that first access builds the reply right then while subsequent accesses use cached replies. In some cases they're handled differently.
--On Thursday, September 16, 2004 6:11 PM +0300 Timo Sirainen <tss@iki.fi> wrote:
"rawlog". See bottom of http://dovecot.org/bugreport.html
Thanks, that looks like just what I need.
0.99.10.8 release fixed some problems with it. Are you using it or newer?
dovecot-0.99.10.9-1.FC3.2
I updated to that based on a similar question to the list earlier.
The difference between first access and next one is that first access builds the reply right then while subsequent accesses use cached replies. In some cases they're handled differently.
Does Dovecot start a new process per folder? (Might be that that's a client issue, based on if Mulberry starts a new connection.) I'm seeing the problem fix itself if I close the folder and re-open it, without exiting the client. But I don't think it's consistent.
participants (3)
-
Jonas Smedegaard
-
Kenneth Porter
-
Timo Sirainen