Send emails from custom domain
planned
B
Brad Konia
Currently, SinoSend sends email notifications from the sinosend.com domain. Your explanation is that it's necessary to ensure delivery. However, you can certainly send emails on behalf of another domain without causing delivery problems. It's just a matter of adding DKIM and SPF records to authorize your server to send emails from our domain. Since we're already adding the CNAME record, this shouldn't be an inconvenience for anyone and it would look much more professional. When sending the setup instructions for a custom domain, you can simply include the additional instructions for creating the necessary email authentication records.
Rishi U.
UPDATE 🎉 Sending Email From Custom Domains is LIVE!
You can now add
DKIM DNS
records for your custom domain. After your provider updates, all emails to your recipients will be sent from your custom email instead of support@sinosend.com.This is a beta release, we’ll continue making improvements based on your feedback. If you find any bugs, please do comment here.
Here’s everything you need to know about the current feature and limitations:
Key Features:
- 1 Email domain per account (all tiers)
- Domain must match and be an active custom domain.
- Once your email domain is verified, we will use your profile email address as the sender email address, providing it belongs to the same domain. For example if your login email is a @gmail.com we will not be able to send on behalf of your gmail, it must be a custom domain. (We understand that users want to login from a gmail, but have the option to select another email, and will provide a dropbox for this selection)
- Each team member email with the same domain can send transfers from their custom email address.
Feedback welcome!
Thank you for helping us make this feature even better! 🚀
Screenshots
Rishi U.
UPDATE 🎉 Sending Email From Custom Domains is LIVE!
You can now add
DKIM DNS
records for your custom domain. After your provider updates, all emails to your recipients will be sent from your custom email instead of support@sinosend.com.This is a beta release, we’ll continue making improvements based on your feedback. If you find any bugs, please do comment here.
Here’s everything you need to know about the current feature and limitations:
Key Features:
- 1 Email domain per account (all tiers)
- Domain must match and be an active custom domain.
- Once your email domain is verified, we will use your profile email address as the sender email address, providing it belongs to the same domain. For example if your login email is a @gmail.com we will not be able to send on behalf of your gmail, it must be a custom domain. (We understand that users want to login from a gmail, but have the option to select another email, and will provide a dropbox for this selection)
- Each team member email with the same domain can send transfers from their custom email address.
Feedback welcome!
Thank you for helping us make this feature even better! 🚀
Screenshots
M
MAKBIZ Ventures
Sending "from" our own domain is great.
If we also could have a different reply to address that would be even greater.
That would allow us to set SPF/DKIM on our CNAME we have with you, but have replies go to our main domain. We like to have our main domain's SPF locked down tight.
Maybe as version 2?
B
Brad Konia
Sounds good to me!
Rishi U.
Update. We're testing multiple sender email address per account (same domain) You will be able to select the sender email from the Transfer dropdown window. Refer to the image below.
Emails will be sent from your email address, and not (support@sinosend.com); provided you add the SPF/DKIM authentication key to your DNS provider (which we will provide you)
Early testers say this method works quite well and will be a prelude to setting up teams (seats) sharing one master account. Any thoughts?
Rishi U.
planned
Rishi U.
Technically you are correct! Using a authenticated domain we can send emails triggered by our customers. We thought about this before, and it led to a lot of support emails! But now clearly we have savvy customers :) I've changed this to under review; we will discuss with our providers as to the number of authenticated domain we can support and the overhead involved. great suggestion.