-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

There is one in December's Linux Magazine (called Linux Pro in the US)
which may be in Chapters by now, but it's always a little slow getting
over here. I also have one in January's Linux Journal which obviously
isn't out yet. The LJ one hasn't been officially accepted yet, so
there's a chance that one won't materialize.

The Linux Magazine article is a general intro to the Citadel groupware
server using Kontact for the PIM stuff (but there's a LOT more to
Citadel) and the LJ one is focussed specifically on Kontact/Citadel as
an Outlook/Exchange replacement. I selected Kontact for the reasons I
specified in my original posting, although if you have infinite patience
there's not reason why you couldn't back Evo or Thunderbird/Sunbird onto
Citadel. Kontact is by far the most complete and easiest to configure.

However, I realize that you're not necessarily looking to back your PIM
onto a groupware server so YMMV.

J

Kin Wong wrote:
> Jon wrote:
> 
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> I've written a few articles on Groupware which necessitates mucking
>> around with various clients.
>>
> Very interesting -- where would one find these articles.
> 
> 
> _______________________________________________
> clug-talk mailing list
> [email protected]
> http://clug.ca/mailman/listinfo/clug-talk_clug.ca
> Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
> **Please remove these lines when replying

- --
Key fingerprint: BDE0 DE52 B8C0 0CDF 7653 E5A2 D861 7877 0D3B 813E
http://www.jonwatson.ca
+1.403.875.6048
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFce+W2GF4dw07gT4RAhoHAJ4/I95geuX4U9bhMVzPmrkJGJPxqACfdboc
d3PIGgO1dQixjKt6lQKmMz0=
=Wowa
-----END PGP SIGNATURE-----

_______________________________________________
clug-talk mailing list
[email protected]
http://clug.ca/mailman/listinfo/clug-talk_clug.ca
Mailing List Guidelines (http://clug.ca/ml_guidelines.php)
**Please remove these lines when replying

Reply via email to