On Tue, 22 Apr 2008 14:06:55 +0100 "mike scott" <[EMAIL PROTECTED]> wrote:
> On 22 Apr 2008 at 8:51, Jerry Feldman wrote: > ... > > A number of years ago (probably about 10) I exchanged some email with > > David Harris on this. When I moved from Windows to Linux as my primary > > desktop platform, I used exmh, then converted to sylpheed, then > > sylpheed-claws, then claws-mail. (Claws was at one time an extension of > > sylpheed). Claws-mail is available on both Linux and Windows, and is > > very light weight. At the time I moved my email to Linux, I was dual > > booting, and I wrote a C program to convert the Pegasus mail format > > files (at that time Pegasus used its own format) to mh (mh uses a > > directory structure as folders with 1 message per file). > > I looked at claws - unsuitable for the way things are set up here. > Pegasus and TB have one overwhelming advantage for me - each can be > set up with all the mailboxes and configuration data on a central > server, common to windows, freebsd and linux workstations. Which > means on our home LAN, we can get at the exact same mail and news > configurations from any machine the code runs on. It took some > fiddling, I'll grant, but it /can/ be done. I've not yet seen any > other mail reader that could do likewise. > > What I don't fully understand is the peg team's comment about needing > a complete rewrite to run on *nix. I'd have hoped the display stuff > would have been made modular enough to make this a ready job. I can't > really see what else could cause a problem. <cynicmode>I wonder if > poor code quality is the reason they won't go open > source.</cynicmode> > > Anyway, pegasus is obviously out of the question. Maybe anyone > putting forward ideas for an OOo-integrated mail client could take on > board the comment above about access to the same mailboxes and > configuration from multiple workstations. I remember Sun used to say > years ago that "the network is the computer" - it would be nice to > think we might get there one day :-) This is exactly why OO.o should not have its own client. The way you process your email. I believe that claws does support the way you want, but each email client has its own personality. Most modern email clients support the IMAP4 protocol, which is what you are using. This protocol allows users to view email on the server. Claws does support this, but I have seen some issues on the claws list. Pegasus mail has been around for a very long time, and started as an MS-DOS client. When I first used it under Windows 3.0, it was still a DOS client. I don't buy the Pegasus team's answer that it cannot be ported (and porting is what I have done for many years, mainly from 32-bit to 64-bit DEC Alpha and Intel IA64). I think what they are really saying is that the amount of work is not worth the effort. One conversation I had at one time was for them to use WINE. A Windows application can be ported to Linux using the WINE libraries. -- -- Jerry Feldman <[EMAIL PROTECTED]> Boston Linux and Unix PGP key id: 537C5846 PGP Key fingerprint: 3D1B 8377 A3C0 A5F2 ECBB CA3B 4607 4319 537C 5846
signature.asc
Description: PGP signature
