I have a domain (ex:- mydomain.com). I am using sendgrid mail service to send and receive mails. When I send any mail using sendgrid V3 API from address user#mydomain.com it is working fine. But I when try to use sub-domain user#username.mydomain.com sendgrid throwing 403 error (domain is not authenticated). Looks like it is accepting only root domain with out any subdomains. I would like to send emails from different custom subdomains.(like freshdesk and zendesk which allocates a different sub-domain for every user). Is there any way that I can overcome this probelm ?
Any little help would really be appreciated.
According to the info at SendGrid's Knowledge Center, you should be able to resolve your issue by properly setting up CNAME records for your sub-domains so that they point to sendgrid.net. See https://sendgrid.com/docs/glossary/cname/ for details.
Basically you need to 1) create a sub user 2) for the newly created sub user, go to Setting -> Sender Authentication to create your subdomain.
Then you need to go to Setting -> API Key to retrieve the access token for the new sub user. And use that access token when you send email and make sure to use the From address such as user#username.mydomain.com
You have to verify your subdomain also, similar as you verified your domain.
There will be 3 CNAME records given to you by Sendgrid which you can add into you DNS records in your domain.
(Only add first CNAME records Don't add last 2 records as it will be same as you already added for domain while domain(mydomain.com) verification
TYPE - CNAME
HOST - username.mydomain.com
VALUE - u2444223323.wl65.sendgrid.net
Related
Recently I have created a website for a client using Laravel/PHP. and then hosted on a cloud hosting provider vultr.com, the client didn't give me access to their domain (abc.com). they just pointed the domain to new hosting and the site is live.
The problem came when I wanted to configure email SMTP. I am using Mailgun for the emails. but for using service like mailgun you have to changes the nameservers in the domain setting. in my case, the client doesn't want to use the domain (abc.com) for emails because the domain is in their owner's name. so they are not changing the nameservers.
So my question is their anyways that I use some other domain or service for sending emails but
not the domain abc.com which is pointed to my hosting.
Also, they don't want to add the A record in the domain. the client just doesn't want to use the same domain for emails.
I hope I made my point clear.
Thanks
Case 1, You can create a subdomain and use dedicated for email like mail.domain.com, in subdomain update DNS recode and use for delivery its also not affect your main domain, in case you use sub email as abc#mail.domain.com for your emails.
Case 2, also an option to use the different domain name for emails and update DNS recode like PTR and DKIM, PTR, SPF
I am trying to use sendGrid with Google Cloud Composer and providing SENDGRID_MAIL_FROM value noreply-composer#domain (noreply-composer#gmail.com), while running the airflow dag receiving error 403: Forbidden
. I did some research and got to know that from should be verified in the sender list. But if I just want to send alert mail with noreply user, this username physically doesn't exist and can not be verified.
Does anybody know workaround for the same, so I can send the mail with noreply username?
Elaborating more to my comment, according to SendGrid documentation pages, each sender identity should be verified using either Domain Authentication or Single Sender Verification. Based on the intro of Single Sender Verification as of most common use case restriction:
You can send only from the address you verify rather than any address
on an authenticated domain.
With said this, you might have to validate email account ownership for each FROM email address entry.
Domain Authentication will probably help to overcome the above mentioned limitation, however it requires to edit DNS records of the domain provider name resolution service:
You can send from any email address on your authenticated domain.
After adding CNAME, TEXT or MX particular records to your DNS service, they need to be validated in SendGrid UI.
I encourage you to check out the relevant tutorial to give more essential outcome.
We have a domain using Gmail for business for emails, we are changing our domain , is it possible to route\forward all email to new domain (we are using same address for new emails, only the part after the # is changed)
Thank you
My organization recently added a second domain. This is done from your domain panel. See help. I would just recommend adding the the new domain as a alias of the old one, so that both email endings are recognized. See google warning about changing the primary domain
Don't forget to set up authentication on the new emails and update the authentication on your DNS providers site if you are rerouting to a new nameserver. Our emails were hitting spam filters for a week before we caught it.
I setup MX records for my domain.
According to the tutorial, all other records should be removed.
I removed the old records and have since realized that I still want a regular e-mail account,
info#mydomain.com
How do I setup my MX records to handle this?
Mandrill's tutorial said that no other MX records are allowed.. I want to have info#mydomain route exist as well.
It's not possible to have a traditional inbox for a domain as well as have Mandrill accept email for that domain. Instead, you'll likely want to have Mandrill handle only a subdomain, like inbound.domain.com, and set up the routes for that subdomain. Your root domain could then be used for traditional inboxes for sending and receiving mail.
Alternately, you can set up your root domain to be handled by Mandrill. Whenever you get mail to info#yourdomain.com, you'd process the webhook POST, and use the information from that POST to create a new outbound message to some other inbox where you can receive mail.
We have custom cms that currently sits on a vendor's subdomain, such as cms.vendor.com. It sends email out as coming from user#vendor.com and it seems to be working fine (using Email Queuing + SwiftMailer)
Our vendor asked us to put in the functionality for his users to be able to select from a dropdown, 3-4 other emails address associated with them from other domains he owns. Basically we need to be able to send out emails from our server labeled as being sent from #hisdomains.com, multiple domains.
I am a web programmer and have no clue when it comes to relaying messages. How would I go about being able to send out emails from his other domains? Does he need to setup permissions on his mail servers, or do I need to get into his SMTP servers to send out?
What are some things I should look out for when it comes to SPAM and gmail trusting us?
EDIT:
Not sure if my original question was clear enough. Vendor owns three domains: mysite.com, myothersite.com, mythirdsite.com. He wants a user from our crm to be able to send emails he has on those domains. So my dedicated server will be trying to send an email out as user#mysite.com, user#myothersite.com, and user#mythirdsite.com in the FROM: header.
As long as your server is allowed to send on behalf of a domain your vendor owns, you should not have a problem; just change the From: header to something else when you send out the e-mail.
Stuff like SPF, Sender ID and DKIM have to be properly configured to allow your server to send on behalf of any domain.
See also: http://en.wikipedia.org/wiki/E-mail_authentication
Any domain where the mx record resolves to the same server will work. so user#any.domain will email the same user on the mx contingent server.
To answer your question - just make sure that the mx records in the DNS zone file for each domain name points to the same server as the domain you want to share emails on.
also dependent on server configuration (like shared or whatever) I'm assuming it's dedicated with a simple email server installed. I'm not sure on cPanel/shared servers. but possibly the same.