On 05/04/11 09:32 +0200, Manuel Bilderbeek said ... > Y Giridhar Appaji Nag wrote: > > 1. Take a packet trace using ethereal when sending an email. It is > > Fine with me, but you'll have to explain to me step by step what to do, > as I'm not familiar with this tool, i.e. I have never used it.
$ apt-get install ethereal And after you compose your email ... $ sudo ethereal In the main menu of the window that comes up, select Capture -> Start and in the dialog that appears, select the network interface on which the traffic to the IMAP server is going in the drop down list. Click OK. ... send the email, and wait for the failure to happen Click Stop in the capture dialog of ethereal. Save the packet capture file for opening using ethereal later (sudo isn't necessary). Look at the IMAP stream in the list of packets and right click on each of those streams and select "follow TCP stream" in the pop-up menu and analyse the stream for errors etc. In case there is too much traffic from your machine, you can place a filter in the ethereal dialog that appears after Capture -> Start so that only the packets to/from your IMAP server are captured. In case you enter a password when sending the email, and this is not an encrypted session (in which case the packet trace isn't much useful anyway) your userid/password and IMAP server IP, client machine IP are all in the packet trace, so be careful as to who you send the capture file to. > >2. When sending out an email, attach an strace to the MT process and > > Nice idea, but what process should it attach to? There are many running: > > 4841 seems to be the 'root' process...and 4844-4848 seem to have been > forked from 4843. You should attach it the to the root process (4841). Giridhar -- Y Giridhar Appaji Nag | http://www.appaji.net/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
