[Tickets #13346] Re: Activesync identities should use the default identity as a default in the Webmail edition

[noreply at bugs.horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/13346
------------------------------------------------------------------------------
  Ticket             | 13346
  Updated By         | Michael Rubinsky <mrubinsk at horde.org>
  Summary            | Activesync identities should use the default identity
                     | as a default in the Webmail edition
  Queue              | Horde Framework Packages
  Version            | Git master
  Type               | Enhancement
-State              | New
+State              | Accepted
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Rubinsky
------------------------------------------------------------------------------


Michael Rubinsky <mrubinsk at horde.org> (2014-07-10 15:48) wrote:

> In a webmail context, unless I don't understand what the "Horde  
> default" is, it doesn't make sense to use one system-wide identity  
> for all the email accounts which will be managed by the system. On  
> top of that, users will have no idea what it means.
>
> So I think the default for the Activesync identity in both the  
> Activesync and Kronolith prefs should be set to Default Identity as  
> a default.

It already IS, unless I am misunderstanding what you are saying.

> Also, it's not possible to send emails from a mobile device unless  
> the default identity has the email address field populated. This was  
> not necessary in the past, so maybe, if empty, that field could be  
> populated at login time with the email address provided?

This was already discussed on the mailing list. A properly configured  
identity is a REQUIREMENT for using email in Horde, period. IMP  
doesn't work without one either. If you don't want the user to be  
responsible for setting this up on their own then use a hook to  
populate it. IIRC, the pref_init hook can be used for something like  
this.