I am running Postfix MTA on my home server to send bulk emails.I have setup MX records and DNS but rDNS still needs to be configured as gmail etc. won't accept email from my IP. I don't have a VPS so I can't use cPanel or WHM. Is there any other alternative.
NOTE: I can't use a mail provider like gmail as I need to send more than 500 emails daily.
Thanks a lot!
Reverse IP address is linked with the PTR record set by the owner of the IP address which is mostly your ISP. You need to check with your ISP (Internet Service Provider) on updating the PTR record for the IP address assigned to you.
Related
I created a web app to do some basic content management for just myself. I want to mail some docs to the server instead of downloading then uploading them. Ive been looking at postfix but everything assumes you have a domain. Is it possible to receive email at a server with a fixed ip and no domain?
if you want anybody and any app to be able to send mail you need MX records in DNS. And MX records point at dns server names, not IP addresses.
https://serverfault.com/questions/663112/why-cant-mx-records-point-to-an-ip-address
If its just you then you can telnet to the SMTP port to send mail
I have an Ubuntu 16.04 server with ISPConfig 3.1.
I set up many websites and emails, but when I send an email to a certain email address I have the following error:
Your server IP address [186.156.31.17] does not have a valid reverse
550-DNS entry [pc-17-31-156-186.cm.vtr.net]. see
550-http://spamauditor.org/best-practices/check_dynamic_reverse_dns/
for
more 550-information. Protection provided by MagicSpam 2.1-8.3 550
http://www.magicspam.com (in reply to RCPT TO command)
How can I set up reverse DNS in ISPConfig? I learned that I need a PTR record but I'm not sure how to do it correctly.
This isn't something you can configure from your end unless your ISP has specifically given you the ability to do it.
Linode, for example has a button for it, but if you don't, you would need to contact your ISP.
Normally individuals don't have access to the rDNS records
I currently have a domain name which is set to point to Amazon Cloudfront's nameservers. I also have a dedicated server which uses WHM/cPanel that I want to use for all mail.
On Amazon:
The A record for the domain is set to point to the server IP
The MX record is set up as well
On Server:
I have an A record for "mail" that points to the server IP
However, when I log into cPanel webmail, I can send mail but cannot receive it.
Any help would be greatly appreciated. Some type of routing issue I am assuming? When I send an email via Gmail to myemail#mydomain.com, it does not bounce back.
I fixed it by changing the MX record from mydomain.com. to mail.mydomain.com. and then having the A record for mail point to the server IP.
Our email server was blocked, I need find a way to solve this.
About the outbound SMTP IP, when I send emails from my email server, if I send them to a SMTP relay on my other server, which IP the receive side will check for the reverse DNS? the email server IP or the relay server IP?
The receiving mail server will do a reverse dns check on the mail server that it received the message from. So, if your mail server sends a message through a relaying mail server, which then sends the message to the receiving mail server, the receiving mail server will do a reverse dns check on the relaying mail server.
The reverse DNS check works like so: Say the receiving mail server receives an incoming connection from 209.85.160.179. The receiving mail server will do a reverse DNS lookup on this IP, which (in this case) will resolve to mail-yk0-f179.google.com. To confirm that the sending mail server is in fact in the google.com domain (and 209.85.160.179 is not run by a spammer or spoofer who simply setup a PTR record for 209.85.160.179 that points to mail-yk0-f179.google.com), the receiving mail server then does a forward DNS lookup on mail-yk0-f179.google.com, to make sure that this FQDN does in fact resolve to 209.85.160.179 (a spammer would not be able to setup a DNS record for a FQDN in google.com's domain).
So, legitimate senders should have a PTR record setup for the IP address that their mail server sends from, and the FQDN that the PTR record points to should resolve back to this same IP. This is how spam filters identify mail from home computers that have been taken over by bots or zombies for sending spam - as most IPs used for home internet connections will not pass a reverse DNS check.
We send out mail via Microsoft Exchange 2010 running on a Windows Server set up as server.organization.local.
When error messages are generated it shows:
Generating server: server.organization.local
I am confused as to what our SPF records should look like based on this. Should it simply contain the external IP address that this server uses to send out mail, or both this .local address and external IP address?
Currently it is set as:
# 10800 IN SPF "v=spf1 mx a:server.organization.local ip4:10.10.10.10 -all"
The mx is included to be safe but I'm not sure if it needs to be? The MX records on the domain name is set to a third-party filtering service, no mail is sent via it.
You need to specify the public IPs if you want to send emails to the internet.
If you are sending emails to another mail server on the LAN then you might have to add the private IPs as well.
I suggest to use a testing utility to check your SPF records.