553 5.7.1: Sender address rejected: not owned by user
Your own outgoing mail server refused the message because the From address doesn't belong to the account you signed in with.
Sign-in problem Your app or device couldn't sign in to your own mail server, so the message was never sent. Fix the sign-in settings.
What the bounce message looks like
The wording changes from one provider to another. These are typical examples:
553 5.7.1 <[email protected]>: Sender address rejected: not owned by user [email protected]Common causes
- The From address in your app is different from the account used to sign in
- A website contact form that sends "from" the visitor's address
How to fix it if you sent the email
- Send from the same address you sign in with.
- On website forms, send from your own address and put the visitor's address in Reply-To.
If you manage the receiving or sending mail system
- Allow the account to send as that address, if it should.
Free tool: paste the full bounce into the bounce message decoder to get a plain-English reading of every code in it.
Questions people ask
- What does 553 5.7.1 mean?
- Your own outgoing mail server refused the message because the From address doesn't belong to the account you signed in with.
- Is 553 5.7.1 a hard or soft bounce?
- Sign-in problem. Your app or device couldn't sign in to your own mail server, so the message was never sent. Fix the sign-in settings.
- Should I remove the address after a 5.7.1 bounce?
- No. The message never left your own mail server. Fix the sign-in or sender settings and send again.