|Anonymous | Login | Signup for a new account||2019-02-23 10:05 EST|
|My View | View Issues | Change Log | Roadmap | Repositories|
|View Issue Details|
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0004604||SOGo||ActiveSync||public||2018-11-22 13:12||2018-12-08 08:49|
|Target Version||Fixed in Version|
|Summary||0004604: Outlook 16: Sending with alternative identity does not work|
|Description||Sending an email with an alternative identity (alias of mail address) in Outlook (v16) is used. But the mail received does show the main email address instead of the selected alternative sender.|
Main mail account is firstname.lastname@example.org
Alias email is: email@example.com
In SOGo in can select firstname.lastname@example.org - the recipient sees email@example.com.
In Outlook, when selecting user@ as sender, I can send the email, but the recipient receives the mail as firstname.lastname@example.org.
|Additional Information||On the same machine, the same outlook, with an other account (Office 365) the same function works as expected.|
|Tags||No tags attached.|
|The email address specified in Outlook has to be a valid email-address for the used user-account. If no match is found the default-email address of the user-account is used. What's the difference about working and non-working account?|
Thanks fo r this quick reply:
1. the difference is that the working account in outlook is not based on sogo but on office365 (it is a different mailbox with different aliases).
2. in sogo, the aliases can be used to send emails, so in my opinion, the mail address and its aliases are set up correctly.
check what outlook is sending to sogo:
set SOGoEASDebugEnabled=YES and send and email with the alias
check sogo.log for this:
do a 'base64 -d' on the string between <MIME> and check the from-header
Here is a sample:
From: "Person Name" <email@example.com>
Subject: Test 2
Date: Mon, 26 Nov 2018 21:20:30 +0100
X-Mailer: Microsoft Outlook 16.0
The alias does not appear here.
That would mean that Outlooks does not send correctly the information when using activesync? But does correctly when speaking to a exchange server?
Sogo can only work with infos sent in the request.
Outlook's behavior depends obviously on the used protocol.
I wonder if this is due to SOGo not implementing ActiveSync UserInformation, so Outlook is not able to verify that the user is allowed to send as the alternate address? Disclaimer: I don't use Outlook, so can't verify.
I see no "<Settings><UserInformation><GET/>"-Reqeust when connecting OL via EAS.
I still think this is an OL issue.
|2018-11-22 13:12||littlebuddha||New Issue|
|2018-11-23 11:13||tfu||Note Added: 0013191|
|2018-11-23 11:49||littlebuddha||Note Added: 0013192|
|2018-11-23 18:12||tfu||Note Added: 0013193|
|2018-11-26 16:32||littlebuddha||Note Added: 0013197|
|2018-11-28 14:59||tfu||Note Added: 0013199|
|2018-12-03 05:33||Note Added: 0013208|
|2018-12-08 08:49||tfu||Note Added: 0013217|
|Copyright © 2000 - 2019 MantisBT Team|