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

Users password compromised - How do I find out which one?

B

buster@

Guest
Someone is sending spam through my plesk server.

They are authenticating to the server:

Apr 5 06:34:37 plesk relaylock: /var/qmail/bin/relaylock: mail from 2xx.xxx.xxx.xxx:4056 (bb2xx-xxx-xxx-xxx.xxxxxxx.xxx.xx)

But for the life of me, I cannot find a way to find the user that authenticated.

Any tips or hints? If there isn't any way to look through the logs now, is there something I can setup to log what relaylock does. Just user and ip?


Thanks...
 
Apr 6 07:22:26 plesk smtp_auth: smtp_auth: SMTP user sales : /var/qmail/mailnames/domain.com/sales logged in from (bb2xx-xxx-xxx-xxx.xxxxxxx.xxx.xx) [2xx.xxx.xxx.xxx]

I just had to look for the lines like that.

So [email protected] was the culprit.

I was in a rush and looked right over them.
 
I'm curious where you found that log.

I'm curious where you found that log file, I would like to look for the same thing.

Thanks.
 
Plesk keeps the log file here: /usr/local/psa/var/log/maillog
 
Thanks, I found it after looking a little deeper.

That's an interesting log, I'm curious as to why it's not simply in /var/log, but the reasoning behind some of this is a little confusing anyway.
 
Thank ART,
I was pretty sure it would. It's just odd that the "out of the box" solution doesn't put all the logs in a central location.

But then again "logic" is something many developers lack. ;-)
 
Back
Top