• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Recent content by Michael Gabriel

  1. M

    Issue email blacklist not working

    yeah, i understood that, im just say the interface doesnt make that very clear. nor is that what i would expect that feature to do.
  2. M

    Issue email blacklist not working

    dont know how its in english, but in german the interface just asks for a "domainname". so its not quite clear whether thats as part of an email address or as part of a host name.
  3. M

    Issue email blacklist not working

    oh, yeah, got those. i was expecting a check_client_access of course. sounds more like a bug than a feature
  4. M

    Issue email blacklist not working

    i havent used that feature before and all i can find are threads with no answers or solutions. using postfix on centos 7.9 ive added 3 entries under tools & settings -> mailserver -> blacklist nothing seems to get blocked. checked the /etc/postfix/master and main.cf and there is no reject file...
  5. M

    Issue Plesk visit Statistics are wrong

    for that one would have to know wether you are using awstats or webalizer. beside that, they are log analyzers. statcounter i guess uses some js or something to track. so it probably doesnt count bots and people that dont have js activated.
  6. M

    Issue Mail from non-existant user of a local domain

    strict spf ? but then again you will not receive many others
  7. M

    Issue Plesk visit Statistics are wrong

    pleks doesnt calculate anything. awstats or webalizer do.
  8. M

    Backups to remote storage fail with "expected str, bytes or os.PathLike object, not int"

    same problem, LOCAL backup tho, NO exlcuded files ! update didnt fix. manual backup works
  9. M

    [Bug is confirmed: ID PPPM-13733] Scheduled Backups Fail in Plesk Obsidian 18.0.47

    manual run over the gui worked
  10. M

    [Bug is confirmed: ID PPPM-13733] Scheduled Backups Fail in Plesk Obsidian 18.0.47

    im not excluding any files it seems exlcude files and exclude logs are both not checked
  11. M

    [Bug is confirmed: ID PPPM-13733] Scheduled Backups Fail in Plesk Obsidian 18.0.47

    failing here as well, but with expected str, bytes or os.PathLike object, not int
  12. M

    Question reject emails based on ip address

    im already using two lists, but many are too strict or too weak for my taste and there are still spam wave spikes from certrain ips that dont appear in those list at all or only weeks later.
  13. M

    Question reject emails based on ip address

    is there any semi-official way to reject mail per ip address ? the blacklist under mail settings only accepts domain names and not ip addresses. and i cant use check_sender_access cause plesk recreates that file. can i write to the db table with the mail blacklist and thus skip the domain name...
  14. M

    Resolved Errors in german Translation of 18.0.20

    - the notification Popup buttons are both not translated. - in the wordpress security page the button should be "sichern" aka "to secure", not "gesichert" aka "secured"
See more
Back
Top