> ## Documentation Index
> Fetch the complete documentation index at: https://www.spacebring.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.
# MAIL FROM and footer
> Step-by-step instructions to configure your custom MAIL FROM address and footer, troubleshoot email delivery issues, and improve deliverability
Spacebring lets you configure a custom MAIL FROM address and customize the footer of your transactional emails so your emails to customers look more professional, reflect your brand, and are easier for customers to recognize and trust in their inbox.
This guide also helps you troubleshoot delivery issues and improve email deliverability.
## Set up custom MAIL FROM
By default, all transactional emails are sent from [`hello@transactional.spacebring.com`](mailto:hello@transactional.spacebring.com) and include Spacebring's postal address in the footer to comply with anti-spam regulations. With custom MAIL FROM, you can replace the default sender with your own email address.
This helps your customers better recognize your business and improves email deliverability in certain scenarios.
Custom MAIL FROM is a subscription add-on. [Pricing](https://www.spacebring.com/pricing)
1. On the left-side panel, click **(...)** menu next to your network name.
2. Go to **Network settings** > **General** > **Information** tab.
3. Under **MAIL FROM**, click **Subscribe** and [complete checkout](/docs/administration/billing/make-changes-to-spacebring-subscription#upgrade-subscription) to add the add-on to your Spacebring subscription.
4. Enter your sender email address in the **MAIL FROM** field.
5. Under **DNS configuration**, copy the record and add it to your domain registrar's DNS settings.
6. Spacebring detects and approves the record within up to 30 minutes. Once verified, all emails to your customers are sent from your address.
Changing only the part before the @ in your MAIL FROM address — for example from `hello@yourdomain.com` to `support@yourdomain.com` — applies immediately without a new DNS record, as long as the domain is already verified.
Instructions for setting DNS records in common registrars:
* [GoDaddy](https://www.godaddy.com/help/manage-dns-records-680)
* [Google Domains](https://support.google.com/domains/answer/3290350)
* [Namecheap](https://www.namecheap.com/support/knowledgebase/subcategory/2237/host-records-setup/)
* [WordPress](https://wordpress.com/support/domains/custom-dns/)
* [WIX](https://support.wix.com/en/article/managing-dns-records-in-your-wix-account)
* [Squarespace](https://support.squarespace.com/hc/en-us/articles/360002101888-Adding-custom-DNS-records-to-your-Squarespace-managed-domain)
### Improve deliverability for your custom address
* Avoid generic prefixes like "info@". Specific ones — such as "members@" or "hello@" — are viewed as more trustworthy by mail providers and are less likely to end up in spam folders.
* Set up a DMARC record. It lets recipient servers verify your identity and significantly improves your reach:
1. Log in to your domain registrar account.
2. Open the DNS settings or control panel.
3. Create a new record with the following data:
| **Type** | TXT |
| --------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Name** | `_dmarc` |
| **Value** | `v=DMARC1; p=none; sp=none; pct=100; rua=mailto:[example@yourdomain.com](mailto:example@yourdomain.com);`
**Note:** Replace [`example@yourdomain.com`](mailto:example@yourdomain.com) with a managed email address where you wish to receive DMARC reports from mail servers. |
| **TTL** | leave the default value |
### How custom MAIL FROM works
With a custom MAIL FROM email address configured, all transactional emails — including invitation emails, payment confirmations, and invoices — are sent from your custom email address. This ensures consistent branding for all your Spacebring-generated communications.
**Migrate custom MAIL FROM to a different hosting provider**
1. Open the DNS panel with your current hosting provider and note the **Name** and **Value** of the record you previously set for your custom MAIL FROM — look for the TXT record whose name contains `_domainkey`.
2. Open the DNS panel with your new hosting provider and add the same record there.
3. Once the record is active with the new provider, delete it from your previous hosting provider.
**Migrate custom MAIL FROM to a different domain name**
1. On the left-side panel, click **(...)** menu next to your network name.
2. Go to **Network settings** > **General** > **Information** tab.
3. Enter your new domain's email address in the **MAIL FROM** field to generate a DNS record for the new domain.
4. Copy the record shown under **DNS configuration** and add it to your new domain's DNS panel.
5. Remove the DNS record associated with the old domain.
## Customize email footer
You can customize the footer of transactional emails with your business identity information — company name, postal address, and other legal or compliance details shown on every automated email. For this, the [owner](/docs/administration/owners) should do the following:
1. On the left-side panel, click **(...)** menu next to your network name.
2. Go to **Network settings** > **General** > **Information** tab.
3. In the **Email** section > **Footer** field, enter your company name and business address.
After this, all future transactional emails will be sent to users with your business information in the footer as plain text.
To comply with the CAN-SPAM Act, you must include your valid physical postal address. [Learn more](https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business)
## Troubleshoot email delivery issues
If your customer is not be receiving a certain email, follow these steps to troubleshoot delivery issues:
If a member cannot find the email invitation, go to Spacebring > **Customers** > select the user > inspect the **Invitation** section.
If the email wasn't delivered successfully, you will see a "The invitation to...couldn't be delivered..." error message. If you do not see an error message, it means that the email was successfully delivered, and the issue is on the user's side of the email inbox.
### If you see an error, follow these steps:
1. Make sure the invitee's email address is correct. If you made a typo, remove the user using the **Remove** button and reinvite with the correct email.
2. If the email address is correct, the user's email service provider rejects Spacebring emails. Sometimes, corporate email inboxes have specific policies to restrict emails from new senders. Ask your member to contact their IT team if their email system is flagging Spacebring emails. They may want to whitelist [hello@transactional.spacebring.com](mailto:hello@transactional.spacebring.com) or add it to their contacts: [Gmail](https://support.google.com/mail/answer/8151?hl=en-GB\&co=GENIE.Platform%3DDesktop\&sjid=2909698575983550517-EU#), [Outlook](https://support.microsoft.com/en-us/office/add-recipients-to-the-safe-senders-list-in-outlook-be1baea0-beab-4a30-b968-9004332336ce), [Yahoo](https://in.help.yahoo.com/kb/new-mail-for-desktop/add-edit-delete-contacts-yahoo-mail-sln28059.html).
3. You can also additionally [configure the custom MAIL FROM address](/docs/general/mail-from-and-footer) for your account. After this, the emails will be sent from your custom email address. In some cases, this may help resolve delivery issues.
Once your member resolves the issue, use the **Resend invite** button to send the invitation again.
### If you do not see an error, try these tips:
* Ask the user to check spam folders and other email filters, just in case emails are being sent there due to the email service provider filters.
* Ask the user to allow emails Spacebring ([hello@transactional.spacebring.com](mailto:hello@transactional.spacebring.com)) as described in point 2 above.
* Invite the user using their alternative secondary email address, such as @gmail.com or @hotmail.com.
If a member cannot find the invoice sent to the email, try the following:
* Ask the user to check if they are looking for an invoice in the correct inbox. Users can always check under what email they have a registered account in the app on the **Account** page.
* Double-check if the invoice was sent. [Send an invoice](/docs/billing/invoices/issue)
* For company invoices, ensure that the company manager is selected and has a valid email address. [Select company managers](/docs/customer-management/companies#add-company-members-and-managers)
If a user is not receiving the OTP code to log in, ask them to do the following:
1. Check the **Promotions** or **Spam** folders and any other email filters as the emails may be getting redirected there by mistake.
2. Whitelist [hello@transactional.spacebring.com](mailto:hello@transactional.spacebring.com) or add it to their contacts: [Gmail](https://support.google.com/mail/answer/8151?hl=en-GB\&co=GENIE.Platform%3DDesktop\&sjid=2909698575983550517-EU#), [Outlook](https://support.microsoft.com/en-us/office/add-recipients-to-the-safe-senders-list-in-outlook-be1baea0-beab-4a30-b968-9004332336ce), [Yahoo](https://in.help.yahoo.com/kb/new-mail-for-desktop/add-edit-delete-contacts-yahoo-mail-sln28059.html).
3. If the user has already logged in on another device, ask them to check the login code sent as a [push notification](/docs/account/notifications#push-notifications) to that device as well.
**FAQs**
It depends on how quickly you add the DNS record to your domain registrar.
We check the record automatically every 30 minutes and start sending from your address once it's verified. DNS changes can take up to 48 hours to propagate, so verification may take that long if your registrar hasn't updated yet.
The custom MAIL FROM feature supports one sender email address only.
All transactional emails will be sent from this single address to maintain consistency and avoid confusion for recipients.
Emails to your customers are sent from the default [hello@transactional.spacebring.com](mailto:hello@transactional.spacebring.com) address again immediately.
If the issue persists after completing all troubleshooting steps, [contact our support team](/docs/administration/contact-support). Share the actions you've already taken, and specify the user's email address.