Currently I'm thinking to work with SendGrid and I have an issue.
I want to Know if I can parse incoming emails from multiple domains.
I read the documentation from Parse Webhook Settings, and I only see just one domain.
So, is there a way to receive from multiple domains?
Yes, you can. You can pretty much have as many domains as you'd like. You can do that by adding multiple hosts. My example has different hosts on the same domain, but you can have different domains there.
Related
I have found that it is recommended to use different subdomains to differentiate the reputation of different types of emails (for example: marketing or transactional).
However, using AWS SES I realize that the EMAIL FROM and the from field are two different things.
I have set my EMAIL FROM to be #mail.mydomain.com.
When it comes to reputation and deliverability, should I also split my from fields into subdomains, or is it enough to use subdomains for different EMAIL FROMs?
Or put another way. Do I run more risks if I send emails from contact#mydomain.com than contact#mail.mydomain.com even if the EMAIL FROM is already from a subdomain?
Thank you very much!
I manage a voluntary group project that uses one gmail account for all of its interactions. Up til this year there were two users of the account. Now there are three, and we are looking at maybe three more. Madness! We are constantly chasing each other to see who will handle a given message. Would be so much better to route messages to specific accounts for a given person to deal with. But we still need to have a central archive for all incoming and outgoing messages.
I'm looking at the use of redirects, and am trying to 'frame' a broader concept of what to do, and then get a grip on whatever the necessary details are.
Here's what I think I'm trying to do. Some of it is not very clear!
Whether Gmail will work that way is what I don't know.
Set up a non-gmail domain, e.g. mymail.org.
Within that domain, create six accounts, like info#mymail.org, events#mymail.org, and so on.
Set up our existing gmail account to both send and receive mail addressed to each of those six accounts.
Have gmail redirect incoming messages based on the incoming address.
Have the replies to those messages look like they come from the incoming address. (So that further replies get routed correctly.)
Have a copy of each incoming and outgoing message stored on the one gmail account. This is crucial for recordkeeping or oversight.
Am I asking for something feasible? If not, what is?
Incidentally, I tried using the mymail+bit#gmail.com method of routing for a while. Didn't help much.
You might want to look into Google workspace. I think they must have something along the lines of what you are looking for.
I'm trying to understand a few concepts around sendgrid, whitelabeling and different servers that I plan to deploy the same sendgrid account in.
So my questions are:
1) Is whitelabelling purely for masking the via sendgrid.me and will I have any issues if I dont use it with my current setup(i.e. same account on several domains)
2) How does sendgrid deal with messages that have a "From" email that doesnt match the domain the email is sent from? Cause I read that it would silently drop them but instead I see that emails do get delivered however the statistics in sendgrid's dashboard are not being updated.
3) Upon creating a demo account I was asked to provide the domain from which the emails will be triggered but since I want to deploy this in several different domains will I need multiple accounts or is there an alternative option when you go for a paid plan?
Mike
Yes - whitelabelling will replace the sendgrid.me with your own domain.
You can also setup multiple domains inside SendGrid and assign each to a subuser. That will get you one SendGrid account, with multiple whitelabelled domains and separate sender reputation for each.
SendGrid will attempt delivery of whatever you ask it to send -- if you send an email with a different from domain than the signed sending domain, it's up to the receiving mail server to decide whether to block, flag as spam, or allow the email. Different receiving domains will behave differently.
It's generally best practice to always have your from domain match your signed sender domain.
Once you have one domain setup, you can setup additional domains using SendGrid subusers -- more info here.
If you have a complicated multi-domain setup, you might want to check out a templating API, like sendwithus, for making things easier to manage. They'll integrate directly with your SendGrid subusers on your behalf.
I have questions regarding using domain name while sending email via sendgrid.
1) Sendgrid recommend that one should not use "noreply#domain.com" as their domain. I came to know about it after reading the following documentation:
http://sendgrid.com/blog/why-you-should-not-use-noreplydomain-com-in-your-emails/
Does anyone has any clue which domain names are best handled by Sendgrid? I am thinking to use "info # domain.com" instead of
"noreply#domain.com".
2) By the way, it's the word "noreply" that is creating problem, am I right? I am new to these things and still understanding domain related terms.
Thanks
SendGrid will handle your email the same way regardless of the from domain. The recommendation not to use noreply# is just so the people receiving your email can more easily communicate with you.
SendGrid by default does not provide any mailboxes or inbound mail processing. You can use the Inbound Parse Webhook to receive emails, but that is more intended for use cases where you need to programmatically deal with the incoming email.
In the case of just being able to receive email responses, it is probably easier to create a mailbox via your hosting company, or to use something like a gmail account and have your host/registrar forward your mail there.
I'm using the SendGrid Parse API to accept emails from users at ANYTHING#example.com, but I want to also be able to receive emails to Google Apps at support#example.com. Is this possible, and if so, how?
It's not really possible but you have a few options. You could have some code in your parse API callback that forwards emails that match certain rules to a different address (you'd have to rebuild the messages from the parsed values), or you could add a subdomain with a different MX record and use that for either support or parsing but not both.