• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Spam Originating from VPS

N

nathacof@

Guest
I've got a VPS that's been reported by as an open relay by SpamCop.

I've attempted to follow the KB article here, http://kb.swsoft.com/en/1711, to determine if this customer is being subjected to a PHP mail() injection.

The only problem is that the files empty. So does that mean no one is sending mail with PHP or that it's not working?

How else would these messages be getting in? Is there anyway to track which account these malicious users are authenticating as?
 
While I understand that an open relay is the most likely cause of these problems, I've run those tests and they come back fine.

Does anyone know how to increase the verbosity of the mail logs? Is there anyway to see a complete SMTP log?

The Plesk maillog shows deliveries and all but aside from that there isn't much useful info in there.
 
I knew the UID was hiding in there somewhere. Sometimes I'm just slow.

Thanks!
 
Back
Top