Re: [Evolution] New problems with 0.15 and IMAP

Sorry for the delay in getting back to you.....

I've attached the scripts I use to start and stop the ssh tunnel to my
imap server.  All you should have to do is change the hostnames in the
ssh tunnel script to your server's name, substitute your server login
for in the appropriate place, chmod +x it and set evo to use localhost
as the mail server.  As it binds to the imap port on your machine, it
needs to be run as root.  If that's not possible, you can change the
first '143' to a non-privileged port (I like 11111) and then set evo to
use 'localhost:11111'.



On Fri, 2001-10-05 at 17:49, Ujwal S. Sathyam wrote:
    How do you set up ssh access with IMAP? Is there a FAQ?
    On Fri, 2001-10-05 at 14:28, Matthew Schick wrote: 
        On Fri, 2001-10-05 at 15:49, Ujwal S. Sathyam wrote:
            Yeah, I have trouble with IMAP access too. Sometimes it just seems
            to become VERY slow, and sometimes it just freezes. I don't think it
            has anything to do with the network since I can telnet into the mail
            server on port 143, and the response there is very quick. In
            Evolution, when I switch back an forth between IMAP folders, things
            slow down to a crawl, and I can see all those connections on the
            status bar, but nothing seems to be happening. I also ran ethereal
            to capture packets, but I did not see too much IMAP traffic. Of
            course it could be server side, bu other IMAP clients are behaving
        I had noticed this a couple of weeks ago, but with yesterday's snapshot
        everything is much, much faster and hang-free.  If you have ssh access
        to your imap server, I would highly recommend using the tunneling with
        compression.  Seems to speed things up considerably........
            On Fri, 2001-10-05 at 12:35, Julia A. Case wrote: 
                On Fri, 2001-10-05 at 03:17, Mikael Wahlberg wrote:
                > And from time to time, Evo sort of freezes when I am reading an IMAP
                > folder. 
                I was begining to think I was the only one seeing this (I saw it in both
                beta 4 and beta 5)  it seems that during IMAP scans at the end it just
                hangs (CPU usage goes to MAX and stays there for a period of time)  And
                I notice that there is no IMAP traffic during that time period.  It
                seems to be worse when there are large and large numbers of folders in
                the IMAP directory (on the one server I have about a gigabyte of email
                in several hundred folders, don't ask).
                [  Julia Anne Case  ] [        Ships are safe inside the harbor,       ]
                [Programmer at large] [      but is that what ships are really for.    ]
                [   Admining Linux  ] [           To thine own self be true.           ]
                [ Windows/WindowsNT ] [ Fair is where you take your cows to be judged. ]
Matthew Schick, BRP Internet Solutions
matt brightredproductions com

Attachment: imap-kill
Description: Text document

SSH=$(netstat -pat|grep imap|grep ssh|cut -f 1 --delimiter=" " -)

if [ "$SSH" ]
        echo "Can't bind to IMAP port, exiting"
        ssh -C -f -l yourserverusername -L sleep 32000 > /dev/null 
        echo "Imap Tunnel Started!"

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]