• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

Recent content by bork

  1. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    I have Wordfence installed on all of the sites, and check them regularly. In any case I checked the files/folders and since I've had several malware clean-ups done so far(not on these sites), I can confirm that they are clean. Only thing that could possibly mess things up is that couple of the...
  2. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    Thank you for the clarification, I though if maybe that mail event initiated the deceptive site issue. In any case, I scan with Imunify daily, it reports that everything is okay. I have the standard WordPress vulnerabilities(WordPress <= 6.2 - Unauth. Blind SSRF vulnerability/WordPress tagDiv...
  3. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    Sorry, you might meant transparencyreport.google.com. This is from domain1.com. plesk.domain1.com is safe according to this.
  4. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    You mean from the deceptive warning? Here is the url: https://plesk.domain1.com/modules/email-security/index.php?email=user%40domain1.com
  5. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    I forgot to add part of the log from the time of the incident. 2023-10-14 19:21:14 INFO postfix/qmgr [1179220] 97A991960717: removed 2023-10-14 19:21:14 INFO postfix/smtp [1232627] 97A991960717: to=<[email protected]>, relay=gmail-smtp-in.l.google.com[64.233.165.26]:25, delay=1.4...
  6. B

    Issue Email Spoofing subsequent subsequent plesk.domain.com deceptive site ahead

    Hi, Couple of days ago there was an email spoofing accident where someone sent some sort of threatening email that was sent to [email protected] to [email protected], [email protected] to [email protected] and then to a Gmail address. Firewall is enabled, fail2ban, SPF checking mode is set to...
  7. B

    Resolved no SASL authentication mechanisms

    This thread can be marked as resolved.
  8. B

    Resolved no SASL authentication mechanisms

    I want to thank you all for the support so far. This is a summary what I've done and everything seems to function properly for now at least, except for the BIND issue... I made a backup, removed and reinstalled only Postfix, since the only change I made to Dovecot I have reverted it and did not...
  9. B

    Resolved no SASL authentication mechanisms

    These errors also persist, but if they are not a potential culprit, I will open a separate thread for them. Execution status has failed with exit code 3, stdout: × named.service - Berkeley Internet Name Domain (DNS) Loaded: loaded (/usr/lib/systemd/system/named.service; disabled; preset...
  10. B

    Resolved no SASL authentication mechanisms

    These are the errors prompted that I found in the Plesk update log, other then that there is nothing out of the ordinary: 2023-10-13 01:27:23 INFO: pum is called with arguments: ['--check'] 2023-10-13 01:27:23 ERROR: Update operation was locked by another update process (Plesk installer or...
  11. B

    Resolved no SASL authentication mechanisms

    Sorry I wasn't certain before, since I was out for the moment, however I do not have any type of Email extension installed. I added the Postfix parameters myself just trying to find a solution to the issue. I used Certbot, since while searching how to create a wildcard SSL for the no host...
  12. B

    Resolved no SASL authentication mechanisms

    I am using the free mail extension. I suspect maybe the issue was caused by the issuing of the wilcdcard certificate for the no host domain using the digitalocean tutorial, which worked, but maybe caused all this. Should I reinstall postfix and dovecot to revert the change? Any assistance...
  13. B

    Resolved no SASL authentication mechanisms

    The snippet you provided was the default configuration, yes. I provided the initial configuration in my first post. However, I was constantly getting the error, whatever I tried to fix the issue. The plesk update was performed around 1:30am, the errors begun in 2:30am. It resolved half an hour...
  14. B

    Resolved no SASL authentication mechanisms

    Okay so adding this code snippet in the dovecot.conf in the service auth part seems to have solved the issue for the time being, I will still be monitoring this. I mean I tried several other solutions that I found from plesk support googling, however since they didn't work and I reverted those...
  15. B

    Resolved no SASL authentication mechanisms

    Thanks for the assistance skibidi, I am still not able to solve this issue unfortunately. No incoming/outgoing mail still...
Back
Top