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

[I didn't cc this message to kde-core-devel since I don't have write=20
access and didn't want to bother the moderator.]

On Tuesday 16 October 2001 13:28, Don Sanders wrote:
> On Tuesday 16 October 2001 18:31, Cornelius Schumacher
>
> wrote:
> > The categories can be used for grouping addresses. I will
> > add the function "Addressee::List
> > AddressBook::findByCategory( const QString & )". Then you
> > can easily get all entries belonging to a certain
> > category. Each entry can have multiple categories. Does
> > this fulfil the requirements of distribution lists or is
> > there something else, which has to be added?
>
> I believe this fulfills the requirements. (Aliases are
> distribution lists of length one so they are done too).

I don't think so. Distribution lists are lists of email addresses and=20
not lists of address book entries. If an address book entry has several=20
email addresses (and I guess a lot of entries do) how should we know=20
which of those email addresses the message should be sent to.
I'm afraid we can't use categories for our purposes.
For our purposes we need aliases which can be associated with single=20
email addresses. The GUI for this could and should be provided by KMail=20
(or maybe libkdenetwork so that it's reusable in other apps).

I didn't have a look at the API so maybe the following is already=20
possible.
It would be very nice if every app could add custom entries (I guess=20
this is possible) and custom subgroups to address book entries. If the=20
latter is possible we could simply generate a subgroup for every email=20
address which has an alias or which appears in a distribution list. In=20
fact now that I think about it, it would already be enough to be able=20
to create custom entries because we could simply put all aliases into a=20
list with the email address as key. But then we would probably have to=20
search for the email addresses which belong to a distribution list on=20
our own without being able to use some convient API functions.

One powerful feature of aliases can't be achieved this way. With the=20
above implementations it's not possible to build a hierarchy of=20
aliases. OTOH I don't think that this is very important although it=20
would make managing large distribution lists which basically consist of=20
smaller distribution lists much easier.

Regards,
Ingo
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE7zK3XGnR+RTDgudgRAjuiAKDgtVHlko/hRKYEWttNIwPZSv4sLwCgnuQI
7C9iINVXzZuoXGkz0zhsyuA=3D
=3Dpceq
-----END PGP SIGNATURE-----
_______________________________________________
kmail Developers mailing list
kmail@mail.kde.org
http://mail.kde.org/mailman/listinfo/kmail