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

noreply at bugs.horde.org noreply at bugs.horde.org
Thu Jul 10 20:26:22 UTC 2014


Ticket URL: http://bugs.horde.org/ticket/13346
  Ticket             | 13346
  Updated By         | software-horde at interfasys.ch
  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              | Rejected
  Priority           | 1. Low
  Milestone          |
  Patch              |
  Owners             | Michael Rubinsky

software-horde at interfasys.ch (2014-07-10 20:26) wrote:

> Any suggestions on better wording would be considered.
Why not call it "Always use your default identity" then?

>> Why not just automagically select the default from the list and
>> perhaps add a (default) next to it?
>> Something like this:
>> *Default Identity (default)*
>> Anonymous
>> Mobile
> Because selecting the "Horde Default" means that whenever you change  
> the default identity in the Personal Information preferences, this  
> newly selected default identity would then be honored in those other  
> applications as well. If we just set that value to whatever the  
> currently selected default is, then the user would have to revisit  
> all the other applications and change the value in those as well.
Ah, of course.

> 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.
In 5.1, it was possible to send emails both from IMP and mobile  
without having to fill in any of the fields of the default identity.

I've looked at hooks prefs_init does not have access to application  
data and is cached for the session only, but I'll try with  

More information about the bugs mailing list