Le dimanche 30 avril 2006 à 10:08 -0500, Rod Engelsman a écrit : > All I'm saying is that a lot of the pieces for this thing already exist > in the OOo code base. In fact, you could prototype a fair amount of this > thing right now just using macros. Heck, OOo even already has half of an > email client; it can send emails directly without calling an external > MUA for email-merge. So it wouldn't be trivial, but it wouldn't be > anything like starting completely from scratch to create an application.
There are worlds of difference between being able to send a few mails (in your own semi-broken syntax, provided the MTA does not throw some exotic auth at you) and having a full-featured pim. Nowadays a good PIM requires : - being able to manage all the kinds of mail auth which exist (unlike the sending bit, receive auth is always mandatory) - have a good HTML engine (you do want to be able to read mail other people sent you, right ?) - have a robust read/write LDAP backend - have a robust read/write webcal backend - signing/crypting support (x500 and PGP) - spam/phishing filtering - incoming mail filters - smart quote euristics - IM bridges - attachement handling (no you can't just pass them to the OS, you have to check they're trusted before) - read/write support of common mail store backends (mailbox, maildir, pst...) - searching - groupware sharing functions etc Any shell script can send mails, that does not make them "half a PIM". Sending is *easy* -- Nicolas Mailhot
