• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Search results

  1. D

    Forwarded to devs SPF_FAIL for internally forwarded emails

    Have the same issue: see https://talk.plesk.com/threads/421-ehlo-mxin201-your-helo-ehlo-example-com-is-not-matching-your-dns-configuration-s2-myserver-com.363932/
  2. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    No still have this issue, i recommen that users from this server dont use the forward function for now
  3. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    My host file: 127.0.0.1 localhost.localdomain localhost # The following lines are desirable for IPv6 capable hosts ::1 localhost.localdomain localhost ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3...
  4. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    First i see: Received: from s2.example.com (s2.example.com [80.200.100.100]) Then Received: from s2.example.com (localhost.localdomain [127.0.0.1]) Then: Received: from s2.example.com ([127.0.0.1]) by s2.example.com (s2.example.com [127.0.0.1]) I checked everything, i can't figure out why...
  5. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    We use Send from domain IP addresses because of other issues. Here are the headers: I masked some domainnames and ip addresses you can still see the 127 address: Received: from pv33p00im-smtpin032.me.com ([17.142.180.58]) by ms62004.mac.com (Oracle Communications Messaging Server...
  6. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    Ok but i know for sure i sended this test with apple mail client Also my myhostname = s2.example.com I found: mydestination = localhost, localhost.localdomain, localhost smtpd_authorized_xforward_hosts = 127.0.0.0/8 [::1]/128
  7. D

    Resolved Let's Encrypt and IOS problem

    is this bug still a thing?
  8. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    I found something is wrong with the SPF. Looks like postfix uses a local ip 127.0.0.1 instead of the public ip. How can i set the public ip adres here? ____________ MXTools report: _____________ spf:example.com:127.0.0.1 v=spf1 +a +mx +a:s2.example.com +a:mail.example.com +a:example.com...
  9. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    Yes it does! My hostname is s2.myserver.com Reverse dns is s2.myserver.com
  10. D

    Issue 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com

    hi Guys, I have problems setting up the mail servers and the DNS settings. I try to mail to ziggo.nl but i keep getting the following error: 421 EHLO MXIN201 Your HELO/EHLO example.com is not matching your DNS configuration s2.myserver.com i should expect that example.com should be...
  11. D

    Resolved Server unreachable, 24 hours after reboot

    HI, I think it is fixed. It had to do something with the DHCP release of the service provider of my VPS. After setting a static ip, and we aint relying on the DHCP the symptoms disapeared. Thanks for the help!
  12. D

    Toolkit sending notifications about deleted installation

    After looking in the mysql databases, i found old databases and removed Then i followed the link...
  13. D

    Resolved Server blocking all ports, can only connect to server directly

    New thread: https://talk.plesk.com/threads/server-unreachable-24-hours-after-reboot.363685/ new findings
  14. D

    Resolved Server unreachable, 24 hours after reboot

    Hi Guys, My plesk server suddently unreachable on all ports. The server is up to date. It happened after a licence renewal. Looks like it happends 24 hours after a reboot. What i tried: # plesk repair all -v After restart everything runs but no website or mail can be reached. After a new...
  15. D

    Resolved Server blocking all ports, can only connect to server directly

    I found in the kern.log Jan 21 02:34:12 s2 named[720]: no longer listening on <Server IP>#53 and Jan 21 02:35:01 s2 CRON[129292]: (root) CMD (/opt/psa/bin/sw-engine-pleskrun /opt/psa/admin/plib/DailyMaintainance/task-script.php StoreOutgoingMessagesStatistics >/dev/null 2>&1) Around the time...
Back
Top