Notices

Have you tried installing claws-mail instead?

No, I heard its interface is not at all touch&small screen friendly? Or is it not?

I have yet to try it but I've heard good things and have been meaning to give it a chance.

Although I'm not using CSSU I am using CSSU's modest. If I am not connected then it takes a while until the list of e-mails is shown (10 seconds or so). I can then quickly read already-downloaded messages.

Note that I'm not using the "offline IMAP" option. Modest already downloads e-mails in its default configuration.

If I'm on-line, then the list of e-mails opens quickly.

I guess modest tries to connect whenever you open the e-mail list, and only shows them after some time-out...

Add.: For gmail I use standard IMAP. For my other accounts I use Nokia Messaging, and there the list of e-mails opens instantly, even when disconnected. Opening individual e-mails is also slightly faster than with standard IMAP accounts.

Turns out the only thing needed was to use Nokia Messaging. Now it works like a charm, IMAP-style.

I don't want to open new thred for one simple question regarding Modest, is there any way to change e-mail size limit in .conf file like it is in MeeGo? Other day I was trying to send 19 Mb message and it was "too big to send".

Thanks for help in advance.

I do not think so. You can install gconf-editor and see the keys there, I think you cna limit the size of incoming messages, not outgoing.

Anyway, your problem was probably with your smtp server - e-mail usually are not allowed to be this big, I think anything bigger than 8MB might be rejected by your server, but it of course depends on the server's configuration.

Server will eat as much as 20Mb thats the limit (tested, for sure). Bad news in that case. I thought I just can't find ".conf" file. That is quite important to me, well it was.

Hm, who knows what went wrong. smtp protocol however somehow makes files larger than they are when sending them (i.e. 12MB file will take up say 18MB when send through mail, the encoding is somehow inefficient), so maybe that is the problem. If I were you, I would maybe try to send several files of varying lenght and see if none of them gets trough or if some do and whether is is predictable (that i.e. anything over 16,5 MB will not be sent).

Thx, I'll play with it later on. But I honestly doubt it that sending 18Mb worth of stuff can cause reject it due to "encoding".