I am using the Mandrill mail server for sending emails to users and I have my own domain added to Mandrill to send out mails. Suppose I have configured Mandrill to use info#mydomain.com to send out emails and then it should send emails which it does. And any replies sent to info#mydomain.com will be forwarded to traditional mailboxes.
Now I have a doubt on receiving emails via Mandrill, once I add an inbound domain and route its path to my desired location, it should be ready to receive emails. Well I have read questions on SO and it has been said that if someone wants to use traditional mailboxes for receiving mails then it's better not to use Mandrill or use a custom sub domain.
Also it has been said that it is not possible for Mandrill to receive email which is already configured or forwarded to some other traditional mailboxes.
So I added a sub domain to Mandrill's inbound domain like inbound.mydomain.com and receive emails on this domain which will be received by Mandrill and will be send to the desired route which we set up. Now I will have to change my sender domain with the same that is inbound.mydomain.com to make users reply to this domain which will be received at Mandrill. What I want is :
Send emails using info#mydomain.com
Receive emails to my location using inbound domains
Related
All I have is an email client (emClient) and a working sendgrid account. When prompted to enter an email address, I can happily put anything#mydomain.com and it will confirm that it works with SMTP. I can also send emails using this client. I authenticate with the username apikey and my api key.
However, these emails are permanently stuck in the "outbox" and are constantly sent over and over again, presumably because the client has no confirmation that they were sent. When trying to set up a new account under this domain, I setup my "incoming server" as smtp.sendgrid.net and provide my credentials and it sort-of works (after prompting me for my authentication?).
As you can see, SMTP authenticates just fine and this makes sense as I am seemingly able to send email. However, both IMAP and POP3 when I select them in the "incoming server" are stuck on this "testing" stage until they fail.
Now, if we skip ahead to me sending something out - basically, it works. I receive the email on the destination, it does not get marked as spam and it comes from my domain and my name.
However, when I attempt to receive an email on the anything#mydomain.com one, it just doesn't do anything. I don't get an error from gmail that it wasn't delivered, it simply just doesn't get delivered.
For my domain settings, I have the following configured:
Twilio SendGrid developer evangelist here.
While SendGrid allows you to send emails over SMTP or via the API, SendGrid is not a full mailbox that you can connect to over POP3 or IMAP. You cannot connect to SendGrid using an email client, that is not what it is intended for. SendGrid is not a mailbox, but a way to programmatically send and receive emails and other email based events.
The way to receive incoming emails is via the inbound parse webhook. When you have set that up, incoming emails to your configured domain will cause a webhook, an HTTP request, to be sent to a URL you configured, with all the information about the email.
I want to send mass email with GMail API.
Currently I add all the addresses at the To section.
But every recipient should receive the mail and see only his address and not the other ones. Is there a method/API that I can use for this?
As far as I know, Gmail was not created for sending bulk emails as it restricts the number of recipients and has tons of other limitations. You should try to use third-party service for this.
Here you can find Gmail API limitation. It says
100 Recipients per message sent via SMTP (by POP or IMAP users) or the Gmail API
I'm using the SendGrid API to send the mail. It is working fine if, from and to domains are different. But it is not working if both from and to domains are same.
If the sent "from" email address' domain name is #yahoo.com or other large email provider, then all "DMARC" compliant mail servers will bounce the email unless the email was originated from the email provider's mail servers.
Otherwise, their should be no issue with sending emails where the "from" and "to" domain is the same.
For reference, this is yahoo's DMARC policy currently (as of 2/5/2019):
(https://help.yahoo.com/kb/SLN24050.html)
Yahoo recently updated the DMARC record with "p=reject" for Yahoo domains. This was done to protect our users from increasing email spam that uses Yahoo email addresses from other mail servers.
All DMARC compliant mail receivers (including Yahoo, Hotmail, and Gmail) are now bouncing emails sent as Yahoo email addresses that aren't sent through Yahoo servers.
The scenario goes like this:
Email setup for outgoing mail server has been done with email address like help#companydomain.com(example) and configured it.
Under General settings, I have used alias domain as companydomain.com. Also I have set email aliases for each user.
Now any user has set his email as help#companydomain.com can send mails and add followers(Add followers will drop a mail to followers) and the mails are received to any email client like thunderbird .
But when other users send mail, it does not deliver to email client like thunderbird and outlook.
Pretty much confused on how to configure the outgoing email gateway server in odoo. Any suggestions would really be helpful.
I want to use Mailgun to send/receive messages programatically via API.
BUT I need to have also some mailboxes available using Thunderbird or other mail client.
For example I want to have user mailboxes at:
support#
sales#
admin#
And all other e-mails will be for API send/receive.
I can not forward my mail to GMail because I need to reply from the same address (sales#mydomain.com).
Please help.
There is a limitation to using the routing feature and that is that if you delegate a domain to be used by Mailgun you cannot use it with an email client.
That means that, for example, if you want to route emails to user#domain.com and then still use that email address with your favourite email client (be it Thunderbird, Outlook or Gmail) you can't do it. That is because of the way you've configured your MX records (email records in your DNS).
When you use Mailgun's routing functionality you delegate MX records to mailgun, which receives your emails, parses them and routes them according to your preferences.
So how do we solve your problem?
What you can do instead is set up your MX record on a subdomain.
Using subdomain.mydomain.com and pointing its MX records to mailgun will allow you to receive and parse emails through Mailgun.
This way you can have:
admin#subdomain.mydomain.com
sales#subdomain.mydomain.com
etc
will be handled by mailgun
while
admin#mydomain.com
sales#mydomain.com
will be handled normally with your email client.
Please do not hesitate in asking more details!
You need to configure your MX record settings for your subdomains in your DNS control panel.