Hello all,

First of all sorry if this is not the right place for feature requests, please redirect me in the good way.

I'm very interested in SOGO and tried yesterday the online demo. One thing I would need and that doesn't appear to exist (at least in the demo setup) is link between address book cards. Maybe it's clearer with an example:

1) Go to address book
2) Make a diffusion list
3) Put some people in there
4) Save the list
5) Go to the individual card of someone in the list
6) Change his mail address, save
7) The address won't change from the diffusion list.

The behaviour is that the address is copied at the moment of the list creation. You surely have reasons to do that way, but in production use I can imagine the mess of address books. People have many contacts, some of them change addresses quite often. To have many copies of the address and have to change all of them manually isn't the good way, in my opinion. It would be better to have one entry and that other ones be pointers/alias to this one.

This behaviour would be suitable to different address books too, in my opinion. It would be better to have "groups" than address books. People should still have the choice to duplicate cards, but in the goal to make some changes. To have man times the same card in different address books doesn't make any sens for me.

What surprises me is that most of programs I've tried have this duplication behaviour. For me, it's like developers never used their programs to do many lists of contacts. If you are interested in a good example, look at the Mac OS X address book. This, is for me a good implementation.

Well, sorry to be critic against SOGO in my first mail. The whole project seams very interesting. I can't forget to thank the developers to make this open source and freeware. I know that such a development take a lot of time. Please don't take this message as a "your dev suck" but as a "hey guys, your dev could be even better if...".

Best regards,

Vitorio


--
[email protected]
https://inverse.ca/sogo/lists

Reply via email to