Dear Community,
Today I discovered an unexpected behavior (that’s probably how Apple would describe it) of the mail server or SOGo on Netserver 8.
Mail.app Version 1.6.3 and 1.6.4
SOGo Version 5.12.1
The goal was to allow certain users (from SOGo) to send emails with email sender addresses that aren’t actually their own (e.g., for consistent external communication).
So far, I had only tested this for myself, or rather, used it when I wanted to send from one of my alias addresses (no dedicated mailboxes). For this purpose, I created a “new identity” with this address in SOGo and was able to send from this address accordingly. “Delegation” wasn’t necessary, or rather, it wasn’t possible, because the alias address didn’t have its own account and was assigned to me anyway. So, it worked as expected.
Now, others should be able to send from addresses on other accounts. To do this, I set up a “delegation” in the mailbox of the delegating mailbox via SOGo – initially for the group of users who were to be “delegated.” The first user then created a “new identity” accordingly (entries correct) and attempted to send. SOGo immediately issued an error message like this:
5.7.1 we@domain.tld: Sender address rejected: not owned by user test.user - mail@otherdomain.tld
This only partially surprised me, as delegation to groups might not even be implemented. So I removed the group delegation and delegated the user instead. This user was immediately offered to me as I typed it in (I don’t know how it worked with the group). I noticed that this was the “more correct” approach because the SOGO account of the “delegate” didn’t require a “new identity”; instead, the desired sender name could be selected directly. But sending didn’t work here either, with the same error message.
I then updated mail.app from 1.6.3 to 1.6.4, but that didn’t change anything. The offered core update didn’t change anything either.
In mail.app under “Settings > Mail Relay,” the option “Force Sender/Login Match” is, of course, enabled – we don’t want everyone to be able to send as they please.
Until now, I was under the impression that the “delegate” function allowed me to send as someone else despite the option being set? Or does “delegate” only serve to automatically set the desired identities?
What requirements must be met for Person A to be able to send using Person B’s address?
Regards, Yummiweb