Summary | Activesync identities should use the default identity as a default in the Webmail edition |
Queue | Horde Framework Packages |
Queue Version | Git master |
Type | Enhancement |
State | Resolved |
Priority | 1. Low |
Owners | mrubinsk (at) horde (dot) org |
Requester | software-horde (at) interfasys (dot) ch |
Created | 07/10/2014 (4001 days ago) |
Due | |
Updated | 07/12/2014 (3999 days ago) |
Assigned | |
Resolved | 07/12/2014 (3999 days ago) |
Milestone | |
Patch | No |
but thing will still work if they don't.
State ⇒ Resolved
The problem was that in IMP if a From address is not found in the
identity AND a 'maildomain' is configured in IMP's backends.php file,
then a From address can be built from that. ActiveSync doesn't use IMP
to send email, and doesn't have access to IMP's IMAP configuration.
So, for ActiveSync, if we don't find a properly configured identity,
fall back to the device's supplied From address and cross our fingers
that it is accurate.
commit 809d65eeb75ea6c424a2ac73390de5bb74510cd7
Author: Michael J Rubinsky <mrubinsk@horde.org>
Date: Sat Jul 12 00:20:35 2014 -0400
Fix regression when sending ActiveSync email and no From address
is supplied in identity prefs.
Bug: 13346framework/Core/lib/Horde/Core/ActiveSync/Mail.php | 13 +++++++++++--
1 files changed, 11 insertions(+), 2 deletions(-)
http://github.com/horde/horde/commit/809d65eeb75ea6c424a2ac73390de5bb74510cd7
notification from the hook?
from the prefs_init hook,
pref is empty (ignoring the check if the current page IS the prefs
page). Of course, that is left as an exercise for the reader.
the from field has just been automatically populated or if it was
there already.
notification from the hook?
from the prefs_init hook, because I don't know how to be able to tell
later in the process if the from field has just been automatically
populated or if it was there already.
a notification from the hook?
notification from the hook?
New Attachment: setfromatlogin_hook.php
which will fill the Identity's from field using the email address used
at login time.
without having to fill in any of the fields of the default identity.
email. Previously, ActiveSync used to rely on the client sending the
From: header when sending an email, but that was changed since not all
clients do this reliably.
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.
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
appauthenticated.
State ⇒ Rejected
perhaps add a (default) next to it?
Something like this:
*Default Identity (default)*
Anonymous
Mobile
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.
change their default on the PI page, then the dropdown would be
updated
Anonymous (default)
Default Identity
*Mobile*
in use would still be the previously selected one until the user
changed it.
identity and it worked. I think I just did not understand the labels
and it could be a problem for users as well.
Configured Horde Defaults: I thought it was a system wide account, but
it seems to be the identity set as the default on the Personal
Information pref page.
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
The user could select the mobile identity for activesync and If they
change their default on the PI page, then the dropdown would be updated
Anonymous (default)
Default Identity
*Mobile*
State ⇒ Accepted
Assigned to Michael Rubinsky
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.
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?
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.
Priority ⇒ 1. Low
State ⇒ New
Patch ⇒ No
Milestone ⇒
Summary ⇒ Activesync identities should use the default identity as a default in the Webmail edition
Type ⇒ Enhancement
Queue ⇒ Horde Framework Packages
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.
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?