|
Problem description: Setup a Cenos 7 based postfix/dovecot e-mail server. It appears to work fine, I can connect to it alright. If I try to send an outgoing e-mail to external recipient, /var/log/maillog shows:code:There's no filtering Attempted fixes: Restarted postfix/dovecot. No firewall is running. IP and domain are all green for blocklists. Can't think of anything else. Recent changes: Just installed this, it's never worked. I DID have a similar setup working not long ago, but I reloaded the server to do some different stuff. -- Operating system: CentOS 7 64-bit System specs: Simple VPS Location: What country are you in? I have Googled and read the FAQ: Yes
|
#
?
Apr 19, 2016 17:36
|
|
|
|
| # ? Apr 23, 2024 15:39 |
|
|
Who is your ISP? A lot of them block port 25 and others in order to prevent people from running email servers on individual accounts. The log you posted appears to show success on port 25, but I'm not sure how a block at the ISP level would look there.
|
|
#
?
Apr 20, 2016 04:15
|
|
|
CaptainSarcastic posted:Who is your ISP? A lot of them block port 25 and others in order to prevent people from running email servers on individual accounts. The log you posted appears to show success on port 25, but I'm not sure how a block at the ISP level would look there. It did successfully send messages during a previous installation and I have confirmed with the hoster that no filtering is present. I bulldozed the whole box and started over, and now I can RECEIVE messages, but sending still gives success messages to multiple different domains but no actual delivery. I assume receiving messages means both postfix and dovecot are working properly, so I am fully confused at this point.
|
|
#
?
Apr 20, 2016 15:36
|
|
|
AlternateAccount posted:
Does your domain have SPF records in the DNS? If you're unsure, run (replace example.net with the name of your actual DNS domain): code:It might specify IP addresses explicitly, and/or it might include "+mx" indicating that the servers within your domain with MX records associated with them are also valid email senders. In that case, check the MX records too: code:You said you've already checked your IP and domain against blocklists, but have you checked that your server has a valid _reverse_ DNS mapping? code:code:Failing this old test (at least 20 years old at this point!) gets your email treated as "coming from some spammer server that doesn't even have a proper domain registration" - and today, that means your outgoing emails will very likely go to /dev/null without any error reply. Note that all the "dig" commands I showed here have a "@8.8.8.8" at the end. That tells the "dig" command to contact Google's public DNS server and have it query your domain - this way, you'll get an idea of how your domain actually looks "from the outside". If some of the answers are not what you expect, try the commands again without the "@8.8.8.8" at the end - if the answers change when omitting the "@8.8.8.8", you have found a DNS data propagation problem.
|
|
#
?
Apr 28, 2016 20:16
|
|