So, after applying the patch, results are mixed.
Things one should know reading the rest of this:
I create users like firstname.lastname@example.org and email@example.com etc.
They get an email alias like firstname.lastname@example.org and email@example.com
AD properties are populated to reflect the alias as the primary email and things like Fisrt name, last name, etc. are filled correctly.
Email clients are configured on the alias, using username lmst01 to acces the mailbox firstname.lastname@example.org
In all clients, the @domain.com part is dropped from the username while logging on or setting credentials.
First annoyance is to be expected in my setup: (Sending mail)
Mailheader when sending mail from SOGo is correct.
EAX works as expected, including the mail header being wrong compared to how the return address is set in SOGo:
X-Spam-Status: No, score=-100.0, required= 4.0
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) * on
otherserver.otherdomain.net * at Fri, 24 Nov 2017 07:47:37 +0100
X-Spam-Status: No, score=-100.0, hits=-100.0, required= 8, autolearn=disabled,
X-Spam-Report: * -0.0 SHORTCIRCUIT No description available.
* -100 USER_IN_WHITELIST From: address is in the user's white-list
Received: from myserver.domain.com (172.16.1.12) by
remote.someotherdomain.net (192.168.50.2) with Microsoft SMTP Server id
8.3.485.1; Fri, 24 Nov 2017 08:33:49 +0100
Received: from myserver.domain.com (localhost [127.0.0.1]) by
myserver.domain.com (Postfix) with ESMTP id 3B96B180336F5 for
<email@example.com>; Fri, 24 Nov 2017 08:33:49 +0100 (CET)
Received: from localhost (localhost [127.0.0.1]) by myserver.domain.com
(Postfix) with ESMTP for <firstname.lastname@example.org>; Fri, 24 Nov 2017
08:33:49 +0100 (CET)
From: Jeroen Visser <email@example.com>
Date: Fri, 24 Nov 2017 08:33:57 +0100
X-Mailer: Microsoft Outlook 16.0
>>>>> Return-Path: firstname.lastname@example.org <<<<<<
X-Antivirus: avast! (VPS 171123-2, 23-11-2017), Inbound message
IMAP works as expected, correct headers for my use-case and correctly displayed for common use-case, but not for mine
But, and that is what this was about;
Note that for some reason, the first picture in this post has me looking up a user and it displays the accountname (my situation is weird, granted)
But I would expect that to be consistent … note this last pic displaying the users who have rights on this mailbox. This is mailbox email@example.com user firstname.lastname@example.org
When looking for the Test Account user, it displays … the alias … as I would like … ehr ??
Rights are not correctly set in my scenario:
Manually setting rights to email@example.com works, as expected.
- EAX return address in the email header is wrong
- Looking for user in SOGo when SENDING mail yields primary email addres (username in my case)
- Looking for user in SOGo when SETTING ACL’s yields alias email which has been set throughout SOGo settings like below: