Enhancement #1821

SOGo: multiple mail address

Added by Giacomo Sanchietti over 8 years ago. Updated almost 7 years ago.

Status:CLOSEDStart date:
Priority:NormalDue date:
Assignee:-% Done:

100%

Category:nethserver-sogo
Target version:v6.5
Resolution:REJECTED NEEDINFO:No

Description

Each user/group can have multiple pseudonyms saved into LDAP database.

Eg:

# tecnici, People, directory.nh
dn: uid=tecnici,ou=People,dc=directory,dc=nh
uid: tecnici
...
mail: bugs@mail.nethesis.it
mail: bugs@nethesis.it
mail: bugs@progettofreedom.it
mail: lj@mail.nethesis.it
mail: lj@nethesis.it
mail: lj@progettofreedom.it
mail: tecnici@mail.nethesis.it
mail: tecnici@nethesis.it
mail: tecnici@progettofreedom.it
...

In SOGo, the user/group is automatically mapped to the first mail field.

We should found a way to workaround this problem, for example creating a new field sogoMail.
This field can be mapped using MailFieldNames sogo option.


Related issues

Related to NethServer 6 - Enhancement #2871: Searching on LDAP address book SOGo shows only first alph... CLOSED
Duplicated by NethServer 6 - Bug #3199: SOGo: missing recipient aliases from LDAP address book CLOSED

History

#1 Updated by Alessio Fattorini over 8 years ago

By design, sogo shows only the first address an not only addresses assocaited

#2 Updated by Filippo Carletti over 8 years ago

  • Target version changed from v6.4-beta1 to ~FUTURE

#3 Updated by Giacomo Sanchietti over 7 years ago

  • Status changed from NEW to CLOSED
  • % Done changed from 0 to 100
  • Resolution set to UPSTREAM

Current SOGo implementation can't do the job.

#4 Updated by Giacomo Sanchietti over 7 years ago

  • Target version deleted (~FUTURE)

#5 Updated by Davide Principi over 7 years ago

  • Target version set to v6.5

#6 Updated by Davide Principi about 7 years ago

  • Resolution changed from UPSTREAM to REJECTED

An enhancement can only be REJECTED.

Here, the enhancement should be provided by SOGo.

#7 Updated by Giacomo Sanchietti almost 7 years ago

  • Related to Enhancement #2871: Searching on LDAP address book SOGo shows only first alphabetically result added

#8 Updated by Alessio Fattorini almost 7 years ago

  • Status changed from CLOSED to ON_DEV
  • % Done changed from 100 to 30

Davide Principi wrote:

An enhancement can only be REJECTED.

Here, the enhancement should be provided by SOGo.

We have find a way regardless of sogo and to mark an email address as primary beacause the user/group automatically mapped to the first mail field could be wrong.
Please let's talk about it

We have already Qmail LDAP schema and we could use the attribute mailalternateaddress for aliases and email address for the "main".
It remains to be implemented in the server-manager the definition of "main address"

Ref Nethesis #464

#9 Updated by Giacomo Sanchietti almost 7 years ago

  • Status changed from ON_DEV to TRIAGED
  • % Done changed from 30 to 20
  • Resolution deleted (REJECTED)

#10 Updated by Giacomo Sanchietti almost 7 years ago

SOGo core can correctly handle multiple mail address for the same user, but the interface will always display only the first one.

This is a bug of SOGo implementation, I don't see any reason to change our underlying implementation.
Other IMAP clients don't have the same behavior.

Example

User named Goofy with the following addresses:
  • a.goofy@domain
  • goofy@domain

Compose a new message and digit "Goofy" in the "To" field.
The auto-completion will always use the first pseudonym (a.goofy@domain).
This is only a cosmetic problem, the message is always sent to the right user.

If the user needs to force the usage of a specific pseudonym, he/she can create a contact inside his/her own phonebook.

The same thing apply even if the user has pseudonyms for multiple domains.

#11 Updated by Davide Principi almost 7 years ago

Giacomo Sanchietti wrote:

This is a bug of SOGo implementation, I don't see any reason to change our underlying implementation.
Other IMAP clients don't have the same behavior.

I agree, handling of multi-value attributes is a client job. From another point of view: implementing the "preferred mail alias" on the Email UI page only to serve this purpose would be too much expensive, considering other solutions are available already.

#12 Updated by Giacomo Sanchietti almost 7 years ago

  • Status changed from TRIAGED to CLOSED
  • % Done changed from 20 to 100
  • Resolution set to WONTFIX

There is no more reason to keep this bug open.

#13 Updated by Davide Principi almost 7 years ago

  • Resolution changed from WONTFIX to REJECTED

Fixed resolution code. Enhancement rejected, see above comments.

#14 Updated by Giacomo Sanchietti about 6 years ago

  • Duplicated by Bug #3199: SOGo: missing recipient aliases from LDAP address book added

Also available in: Atom PDF