I am using subdomain for sending email. for example test.example.com. I have configured DMARC,SPF,MX record, Reverse DNS. Checked with mxtoolbox.com and seems perfect.Also checked the IP for blacklist and non of them blacklisted My IP but when I send mail it recieves in Spam folder in my Gmail account. My server is hosted with Digital ocean ubuntu server. It will be helpful if some one give their suggestion
Related
I have a mac osx server at my office. I have only one email address configured on it because it's an email address outside my GSuite account. That email address was created for sending mails from a php script (I don't want to pay to Google for that email address because I don't need all of the Google Services on it). I configured PHP Mailer for sending mails using that email account.
It's connecting perfectly fine, authentication is correct, etc., but there is one problem: if I send mails to #mydomain.com it says that account doesn't exist, but it does exist, only that it is hosted on GSuite. If I send mails outside mydomain, it works fine.
Question is: how do I route those mails to look up for the correct MX récords? I mean, how to make those #mydomain.com emails reach the GSuite host?
You can have multiple MX records per domain. It is possible. They will use priorities. You can even have multiple email servers checking emails from each other.
However, you case with hosted emails this won't work. Google is not going to let you do this.
You will have to pay.
I am hosting my email address, for example, arvind#mydomain.com on Gsuite.
How do I add more addresses in my server such as abc#mydomain.com and use my own server, such as my website to send emails to this user. I created abc#mydomain.com using WHM/cpanel for the domain. I am able to send email from this address but they end in spam folder. Also I am not able to send emails to this address.
I have added Google's server to MX entries and my own server such as mail.mydomain.com. However if I try to send email to abc#mydomain.com it fails with "Address not found".
How can I fix it? I am able to edit DNS entries if required to.
I have a scenario that gives me headache for a while now. I bought a domain on Namecheap, hosting on Godaddy cpanel, but later decided to host on Aws ec2 instance, but I don't want to use the SES service from Amazon. Now that was successful.On trying to setup the email account on the Godaddy cpanel, I can only send emails , but not receive. I tried several mx record settings, but none worked.
Domain from Namecheap --- works
Email service - Godaddy Cpanel email -- can only send, no receipts.
Website hosting - Aws ec2 ----works
I would like to know the correct setup for this. Any help would be appreciated.
What is that you are trying to host on EC2? Is it an application?
Where is your Email Hosting done? Is it in GoDaddy?
In order to do that you have to change your MX Record entries in your DNS.
You have to add the MX entry provided by the cpanel for that particular domain in your dns to get your incoming emails service working.
You are able to send emails because there is no need of MX when you are sending mails. You are using SMTP for sending mails out from your server.
Your website should be working if you have added your amazon ec2 instance public ip in your DNS.
You can make things simpler by moving your dns to cpanel i.e. on godaddy server by changing nameservers in your name cheap panel which is given by godaddy guys. You then have to add A record which must be pointing to your AWS ec2 instance public IP and your MX must be set bydefault in your cpanel server.
I have just installed VestaCP on a fresh CentOS VPS.
I have set up email for one domain. All mail sent to that domain bounces with the error 550 smtp auth requried
I have commented out the following;
deny message = smtp auth requried
from exim.conf
I have turned off anti-spam.
I still get the bounce with this message.
Specifically, if I send an email from a gmail account google responds:
Technical details of permanent failure:
Google tried to deliver your message, but it was rejected by the server for the recipient domain foobar.tld by mail.foobar.tld. [x.x.x.x].
The error that the other server returned was:
550 smtp auth requried
Any experience with this? I have seen the problem on a number of threads but have not found a solution.
I partially solved the problem. It only occurred when sending mail to the smtp server from a domain that was hosted on the same server for web but not for email. When I sent email from a domain that had nothing to do with any domains hosted on the same server as the exim instance, then it got through. I still can't send email from the domain that was causing the problem and I would like to, but I can work around it.
So to be clear in case anyone reads this:
domain1 web is hosted on server1
domain1 email is hosted on google's servers
domain2 is hosted on server1 for web and email
exim is running on server1
when I send email from thunderbird via google's server from email#domain1 to and email#domain2 the exim instance asks google's smtp server for authentication even though the mail is being delivered to a mailbox in its list of domains it can deliver to on the same physical server where it is running.
I suspect that it is suspicious of the from address, which it shouldn't be since the mx records indicate that it does not host mail for that domain.
I have configured my DNN mail server to send out mail using our companies Email service provider. I cannot send any emails to external email server.
For ex. My email provider is testx#ttt.com. I can send emails to testy#ttt.com and textz#ttt.com. However i cannot send to testy#gmail.com or testy#hotmail.com
The error i see in the DNN event viewer is as below
System.Net.Mail.SmtpFailedRecipientsException: Unable to send to all recipients.
System.Net.Mail.SmtpFailedRecipientException: Mailbox unavailable.
The server response was: This domain is not hosted here
I have the same email address configured in my outlook and i can send/recieve to any emails like gmail or hotmail. Following are my DNN email settings
It sounds like one or two things might be happening here:
Your SMTP server isn't set up to allow relaying from the IP address of your web server.
You may need to create an SPF (Sender Policy Framework) or TXT record in DNS for your SMTP server's primary domain that allows SMTP traffic from the IP address of the server where your DNN website is hosted. An SPF record may already be in use for your email domain, but generally you'd add something like this to it: v=spf1 a ip4:1.2.3.4 -all, where 1.2.3.4 is the IP address of your web server.