• 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. TorbHo

    Question Backscatter

    Hello, I had a similar problem and I found out that the problem are the bounce mails from MAILER-DAEMON. So, spam was sent to not existing mail boxes and the MAILER-DAEMON tries to return a bounce message. As the sending mail address is forged, this bounce can't be sent, so the mail stays in...
  2. TorbHo

    Resolved DirectoryIndex not working after migration

    I don't know why, but after I changed settings->server settings->preferred domains for website from "www.domain.tld" to "none" it worked The old server was set to "www.domain.tld", too. Does this make any sense to you?
  3. TorbHo

    Resolved DirectoryIndex not working after migration

    Update: some mod_rewrite rules don't work anymore, too. Could there be some kind of connection?
  4. TorbHo

    Resolved DirectoryIndex not working after migration

    Plesk 17.8.11 Update #54 ‪Ubuntu 18.04.2 LTS‬ After migrating a Plesk server to a new Plesk server, the websites with custom DirectoryIndex in htaccess do not work anymore. They show a "403 Forbidden" error. The sites without custom DirectoryIndex work as expected. Anything in the...
  5. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    The problem is not solved yet. But, I use a cron-job to flush the messages and so the symptoms don't bother me anymore. But I still would like to know, why the messages appear in 17.8, when they didn't appear in 17.0. The cron looks like this: #mailq |awk...
  6. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    Remarked as unresolved. Now, after the weekend, again we have a lot of these bounce messages. What can we do?
  7. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    We use spamhaus. Maybe the domain was not in the list as the mail arrived. Although i don't like SPF protection that much, I activated it now. As far as I know, Plesk now supports SRS for forwarded mails, so I gave it a try. Up to now: no more error mails in the queue for some hours. Maybe...
  8. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    No, these mails are no outgoing spam. I checked the mail body via ssh. A mail doesn't need a valid mx record to be sent. The "from" address can of course be spoofed. For example: the message from spammail@spamdomain.com is sent to our client customer@domain.com. This mailadress is forwarded to...
  9. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    The same today. A lot of MAILER-DAEMON@ messages. None of them are outgoing spam, but error messages to the sender which can not be reached of course. Why didn't we have these messages with Plesk 17.0? Is there anything different in the mail configuration?
  10. TorbHo

    Resolved Inbound Mail Stays in Queue

    Next time, try to disable apparmor and than flush mailqueue (postqueue -f): How to disable AppArmor on Plesk 12.x That solved the problem for me. Please keep in mind, that apparmor is part of Plesk Onyx since 17.0 and should not be uninstalled completely.
  11. TorbHo

    Issue Lot of MAILER-DAEMON@ messages in mail queue

    After upgrading from Plesk 17.0 to 17.8 (Ubuntu 14.4 lts) we have a lot of bounce messages in our mail queue. After a look in the mail header, these mails don't seem to be outgoing spam-mails, but they are bounce messages from spam which was sent to our customers. They are just the error...
  12. TorbHo

    Resolved Mails: No such user in mail authorization database

    Maybe there should be a simple javascript warning message, so that the user can not send the form without a password. How about that?
  13. TorbHo

    Resolved Mails: No such user in mail authorization database

    Plesk Onyx Version 17.5.3 Ubuntu 16.04.3 LTS‬ We had the problem, that some Mails could not be delivered to the local mailbox. The Maillog showed "No such user in mail authorization database" After some searching, we found the solution at: Email cannot be delivered: No such user in mail...
  14. TorbHo

    Resolved bind does not start

    Now it works. Instead of uninstalling bind via Plesk interface I used # apt-get purge bind9 then I reinstalled it via # /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component bind Thank you
  15. TorbHo

    Resolved bind does not start

    I uninstalled it via Plesk interface and then used: /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component bind
  16. TorbHo

    Resolved bind does not start

    Of course. I made a screenshot for you where I tried the command with # and without. Just nothing happens.
  17. TorbHo

    Resolved bind does not start

    No, we don't get anything. No error and no success message. Syslog doesn't show anything, too.
  18. TorbHo

    Resolved bind does not start

    Yes, the hostname is correct and the same hostname is in the hosts file under the matching ip address.
  19. TorbHo

    Resolved bind does not start

    The bind service does not start. If we try # service bind9 restart nothing happens. No error message, just nothing. We already tried to reinstall bind via plesk. It does not work. Syslog shows nothing about named service. We tried to remove apparmor, too. What else can we do? Ubuntu...
  20. TorbHo

    Resolved fail2ban cannot be started

    Now it works. I uninstalled the fail2ban extension AND removed the /etc/fail2ban directory via ssh. After that, I reinstalled the extension via: # /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component fail2ban
Back
Top