The mail server responded: 5.7.1 Sender address rejected: not owned by user

[matsch]

Hi,

I created additional identities but when trying to send an email with this identity, getting the error:
The mail server responded: 5.7.1 <"New identity email address> Sender address rejected: not owned by user "e.email address
The new identity is well define in https://ecloud.global/apps/ but when sending with Postbox getting this error…

Thanks in advance for your help

M

[harvey186]

could you pls share a screenshot where/how do you have added a new e.email account under apps ??

@matsch

The new identity is well define in https://ecloud.global/apps/

[smu44]

@matsch : can you login here with any additional identity ?

[harvey186]

whom do you ask and for what it is used ??

[smu44]

Sorry @harvey186, this message was for @matsch (used the wrong “reply” button …).
I have no idea what could be an “additional identity”, but I know enough Postfix to recognize his messages
So, in this case we may have an Nextcloud (maybe RainLoop ?) account without email account (Postfix mailbox).
That’s why I think the Postfix Admin is useful : to verify the email account against Postfix, not Nextcloud.

[smu44]

Just checked : the purpose of RainLoop identities (in RainLoop settings) is to provide a merged view (and “from” when writing/replying) with existing accounts.
So @matsch, if you want multiple identities you’ll have to create them first (it’s free anyway ).

[harvey186]

@smu44

RainLoop identities (in RainLoop settings

But I can’t image that this will work, because the railoop is full integrated in the ecloud setup with e.email domain. The railoop IMAP / SMTP server setup will get his information from login data.

but … that’s all theoretical because I don’t know the edrive setup in detail

[smu44]

@harvey186

The railoop IMAP / SMTP server setup will get his information from login data.

For the “main” identity, yes.
But in RainLoop you can also add other identities, as a facility to write email from them.
However this identities are not managed by /e/ Cloud, so RainLoop can’t manage logins or accounts.
As an exemple :

So I think it cannot work in /e/, as users have no access to Postfix aliases (for e.email addresses) and Postfix is secured to forbid sending emails from another account. (ie sending as JohnDoe@gmail.com when logged on as JohnDoe@e.email).

So, as I can see in my own hosted /e/ Cloud, this “identities” feature should be disabled, unless the /e/ server configuration is specific on this subject (I guess it isn’t ).

When writing :

@smu44

Just checked : the purpose of RainLoop identities (in RainLoop settings) is to provide a merged view (and “from” when writing/replying) with existing accounts.
So @matsch, if you want multiple identities you’ll have to create them first (it’s free anyway ).

I was wrong, even if it is a /e/ account I think it will not work (identity spoofing protection at Postfix level).
Sorry for that, I should have checked Postfix configuration more carefully …

@Manoj : could an /e/ Cloud administrator confirm ?

[Manoj]

As required have passed the query to the /e/cloud admin to respond.

[thilo]

@smu44 is correct with his/her last post

I was not aware of the identity feature but it should be disabled on ecloud.global.

Would someone be so kind to open up a issue on gitlab.e.foundation accordingly?

[smu44]

Thanks everyone !

Done https://gitlab.e.foundation/e/backlog/-/issues/1315
Please let me know if it needs more details.

[off topic] : I’m a man, and don’t plan to change

[thilo]

Thanks man ()!
[Nick2gender() is often a throwing an exception so I got careful using it…]