Search result not found.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

On this page

Locize Docs

Introduction

Using locize

Integration

Guides / Tips & Tricks

More

Which integration option should I use?Do I have to use the locize CDN or can I host / bundle the translations directly?How is locize different from the alternatives?Why do I get “The passed json is nested too deeply.” when consuming the API?Is locize only for developers and translators or is project management within the process too?What is the regular way to update the translation memory?Is there any visibility on project’s level of completion that shows how translators are progressing?Why is my namespace suddenly a flat json?How to change the publish format?Why does my namespace contain an array with a lot of null items?Why is the pricing so complicated?How to change credit card or billing information or download the invoices?How to import translations from a file?How to manually publish a specific version?How to delete or rename a namespace?Why is there such a high download amount?Where do I find the namespace backups?How can a segment/key be copied/moved or renamed?Why a new namespace is created, when I upload a translation file?I want to use the locize CDN, but would like to have a fallback that uses local/bundled translationsIs it possible to integrate multiple projects in the same app/website?Why do I see strange new keys marked as ONE, FEW, MANY, OTHERS?How do I open and edit JSON files?i18n vs. i18nexti18next vs. locizeWord CounterHow to style text within locize?What do I have to consider if my translation texts may contain confidential information?How to translate a file and download the results?Should I use versions or branches?Why are we (or our users) not receiving invitation or support emails?

Why are we (or our users) not receiving invitation or support emails?

The Issue

If invitations appears in the Locize but never arrive in your inbox, or if you aren't receiving replies from our support team, your organization's mail server is likely blocking our emails.

This usually happens because corporate firewalls or spam filters (like Mimecast, Proofpoint, or Microsoft 365 Defender) may flag automated emails or emails sent via third-party delivery services (like Amazon SES) as unauthorized.

The Solution: "Allow-listing"

To ensure reliable delivery, please ask your IT or Internal Security department to allow-list (whitelist) Locize. This tells your mail server that emails from us are safe and should be delivered.

Technical Details for your IT Team:

Please provide the following information to your IT department:

  • Sender Domain: locize.com (or locize.app)
  • Secondary Domain (Notifications): mail.locize.com (or mail.locize.app)
  • Sending Service: Amazon SES (Simple Email Service)
  • Region: eu-west-1 (Ireland)
  • IP Ranges: We recommend allow-listing by domain (locize.com or locize.app).

Common Error: 5.7.1 "Delivery not authorized"

If our support team receives a 5.7.1 error when replying to you, it is a definitive sign that your server has a policy blocking our domain. Forwarding this error to your IT team will help them identify the specific rule that needs to be adjusted.

Still having trouble?

If your IT team has confirmed that locize.com is allow-listed and you still aren't receiving emails:

  1. Check your Junk/Spam folders.
  2. Verify that the user's email address in the Locize UI is spelled correctly.
  3. Try inviting a user with a different email domain (e.g., a personal @gmail.com address) to test if the delivery is successful outside of your corporate network.

On this page