I've created several subaccounts in Mandrill and I've bought a dedicated IP. Now I am wondering how to bind a given dedicated IP to a subaccount?
Actually I've created some rules to tell Mandrill that an email is sent from a given sender then what subaccount should be used and what IP pool should be used too. However I don't fully understand how emails will be sent and how reputation is determined for those subaccounts and dedicated IP. I've checked out Mandrill documentation but I couldn't find any clue.
Any help will be appreciated.
Related
I am using Google Cloud for running a website, accessible on mydomain.com (fake, for illustration). I am trying to figure out how to receive email at support#mydomain.com (and let it be accessible by a human like a normal email) and also be able to send custom emails from info#mydomain.com programmatically. I am not sure what technology I am missing to be able to do this.
I have a k8s cluster with an Ingress with a static IP exposed through Cloud DNS zone. The NS records for mydomain.com. match the NS records on Google Domains. This works and I can access my website as expected.
From a little bit of research, I think I need to use something like Sendinblue because using their service will likely make my emails more legitimate. I purchased a dedicated IP in Sendinblue. Following this guide, I added ns1.sendinblue.com and ns2.sendinblue.com NS records for mail.mydomain.com in my Cloud DNS zone. I have associated the domain in Sendinblue and picked matching NS records. Then I created a sender and I am trying to verify this sender, but I have no inbox. This is the most confusing part. So I found this question-answer and followed by adding MX records and setting up email forwarding to mydomain+support#gmail.com (a plain Gmail account).
So now I expect any emails sent to support#mydomain.com to be accessible from the plain Gmail account. When I send emails, I do not receive them but I also do not get back a delivery failure. I've waited 12+ hours to make there isn't a DNS delay.
I feel like I haven't wired up these pieces correctly together and I am missing something but I am not sure what.
This is the answer publish by John Hanley added as community wiki since #John Hanley did not add as answer:
"
Select a normal mail service (Google Workplace, Office 365, Zoho (which offers a free account) and set up mail on your primary domain. Use Sendinblue as your email marketing tool - as it is not a general purchase email system
"
I am running a shared hosting environment (web + email). Some of the domains being hosted have elected to use third-party spam filtering and some have not.
In order for the spam filtering on these domains to be effective, the server should reject any messages that did not originally go through the spam filter servers. I.e. they did not arrive from specific IP addresses, and don't contain specific headers.
How can I block incoming mail for these specific domains, unless the mail arrives from the spam filtering servers?
I obviously can't add firewall rule(s), because some of our hosted domains don't use the filtering service. Firewall rules blocking port 25 etc would stop their email arriving.
It needs to be a filter based on 1) the email recipient domain name, and 2) a specific list of IP addresses.
For example, if domain is in a list of filtered domains, then check IP address. If IP address is NOT in list of spam filtering servers, reject the message.
Can anyone point me in the right direction?
Thanks!
I'm looking at doing this right now. Does this suggestion help: use postfix restriction classes. Put mail domains that need restricting to your spam filter servers in a separate class, then handle it differently.
See
http://permalink.gmane.org/gmane.mail.postfix.user/148366
and
http://www.postfix.org/RESTRICTION_CLASS_README.html
Recently I moved my site to GCE and now emails are not being sent. I send them using gmail's smtp server, through the port 465.
A simple google search points to this article, in which they say that I must use a third party solution like SendGrid.
The weird thing is, I can send regular emails. I was testing my site and I am able to send a simple email with "Hello world" in the message body. But the moment I add a link (URL address) to the body message, the email is not sent.
Is this an expected behaviour? Is there a work around?
I think it's dumb for Google to not allow sending emails even though its own Gmail servers.
Perhaps there is some confusion here. "Despite" of what they say...
Look at their article on Sending Email from an Instance and I quote:
"Google Compute Engine does not allow outbound connections on ports
25, 465, and 587 but you can still set up your instances to send mail
through ports 587 and 465 using servers provided through partner
services, such as SendGrid."
They clearly state that you CAN do it.
Also, if you're authenticating with your Google Account to send via smtp.gmail.com, you're authenticating with a username and password just like any standard email client would. So why would that not be allowed? You're basically connecting as an email client.
On another note, your issues with links were related to the quality of the message therefore being marked as spam (GCE wasn't causing any problems.) by Gmail, as I suspected in my previous comment. You're mainly using Gmail here, and not really any issues directly related to GCE.
I hope this clarifies things a little.
Apparently Google Cloud (despite of what they claim) does allow smtp traffic. I added the firewall exception of the port tcp:465 for all IP addresses.
Additionally, emails containing links were being sent to the spam box, but just on my email account. I sent it to another account and it worked just fine.
[Edit]
GCE had nothing to do with the links problem. It was the poor design of my email content that caused it to go to the spam folder.
The solution was already there. Open the right firewall ports and you're good to go.
Let's say I have a couple of ec2 instances with an elastic load balancer, and I want to run an email server on them so I can send and receive emails from multiple addresses. What is the best practice to do that?
It's sort of a broad question, but I can give you a (hopefully) helpful, specific answer. Email is a topic that doesn't get talked about much with AWS. In fact, this is where the benefits of the cloud can get a little... cloudy.
In my view, the key issue is email deliverability -- making sure that the emails sent from the cloud are reliably received by the intended recipients. Because of anti-spam measures employed by email providers, that means using IP addresses that have a good reputation. Unfortunately, that's not a big benefit of AWS. In fact, many spam filters simply drop emails sent from AWS IP's, and this is true for other cloud service providers as well.
So whenever I send any email from AWS, I always use a forwarding service such as SendGrid. Such companies offer SMTP forwarding in a secure way, and give you all the tools you need to reliably deliver both bulk and transactional emails.
At entry level, you use shared IP's and get the benefit of DKIM, open- and click-tracking, and bounce/block reporting. SendGrid helps to take care of managing your domain's reputation with the big providers. At higher service levels, they can help you warm up and maintain your own dedicated email-sending IP address to ensure that you are not impacted negatively by other SendGrid customers.
Of course, Amazon also sells Simple Email Service, and there are also other options such as sending through Gmail. I am in no way affiliated with any of these companies, but my main piece of advice to people wanting to send any kind of email from a cloud provider is to always use a third party service to maximise deliverability.
As to receiving emails, an Elastic Load Balancer isn't helpful for SMTP, though if you are providing webmail then it can help balance your port 80 traffic. For SMTP, use multiple MX records with the same weight, pointing to a set of hosts that can receive the email.
For your Mail Transport Agent, I recommend Postfix, but that's a matter of preference. You will find many people also recommending Qmail and Sendmail.
I agree with most of #platforms' answer in regards to receiving email in the "cloud", i.e., AWS. Especially the note about balancing port 80 traffic and the inability to balance SMTP (using multiple MX records instead). Just to give a different view on this matter, I had always set up a single MS Exchange Edge Transport Server for those tasks. In a Microsoft TechNet post they mention that a farm of 6 of these servers is able to safely handle around 13 million messages a day (even under peak load).
On the sending email from the "cloud", i.e. AWS, matter, I must disagree, though. I highly recommend using Amazon Simple Email Service (SES). It is fully integrated with the rest of your infrastructure, and the AWS SDKs have all the bindings you need for the majority of programming languages/platforms. As long as you correctly set up your Domain Records, DKIM, etc, you will have no trouble with deliverability. You also have the same reports about bounces, blocks, complaints, etc. Source: I have been using SES for years with no single complaint in regards to deliverability.
How to find ip address of email sender of yahoo mail or gmail?
Just a thought - If you are looking for the IP in order to track down a spammer or something similar - better report the email address directly to yahoo or gmail.
One more issue is that if the IP used to send the mail is/was dynamic, it can possibly help you only aproximately geo-locate the sender, nothing more.
There is a technique that sometimes works, and it's a well-known trick used by spammers.
Reply to the email with an HTML email that includes an image hosted by a server you control, with a unique query string in the URL. If the person opens the email AND displays images, your image will load. You can see which IP address loaded the image, and match that with the email address where you sent the image. Of course, even if this works it will give you the IP address where they read your message, not the one from which they sent the first email. This trick is the main reason that email programs check before they load images now.
You could also sue them, get a subpeona and force Google or Yahoo to get the IP address from their logs.
Looking at the mail headers, you can see who sent it and the host IP, but sender IP addresses aren't included in the header.
You need to look into the mail header which is where you can find the ip address.
Edit: Funny that this was the correct answer but was the only one that got a negative vote. You can go to this link to find out more http://aruljohn.com/info/howtofindipaddress/#gmail and to use some scripts that will make it easier for you. But in short, the IP address can usually be found in the header. Reading the header is different for every email provider so you will have to read to find out how. Some email services such as Google will never share the sender IP. But I've heard that if a sender uses a mail client such as Thunderbird, that the IP can always be tracked, haven't tested it yet though. Good luck!
It's quite easy to track the IP address.
And to track address of sender first we need to retrieve IP address is the sender from the mail and then convert that IP address in location with help of no of websites which offer this feature.
It's a different process for both Yahoo and gmail and putting whole steps will take around 70 lines so I an just putting it's link I found on a website
http://www.rybersoft.com/2016/04/how-to-find-location-of-email-sender.html