• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

/tmp getting full very quick with bounced spam

H

hatristain

Guest
Hello Guys

I am a new upgraded from psa 6.0 to 7.5 reloaded since that upgrade for some reazon my /tmp directory gets full very quick with files with this names:

-rw------- 1 root root 10906 Jan 31 08:33 psa-autoresponder-AVPt3O
-rw------- 1 root root 2362 Jan 31 08:33 psa-autoresponder-BYMFX8
-rw------- 1 root root 2720 Jan 31 08:27 psa-autoresponder-gpg0xq
-rw------- 1 root root 1305 Jan 31 08:30 psa-autoresponder-rTGf57
-rw------- 1 root root 1326 Jan 31 08:23 psa-autoresponder-tauHvL
-rw------- 1 root root 3268 Jan 31 08:20 psa-autoresponder-Zjbpf2


I get lots of them and need to erase them by hand, most of this are bounced spam.

any help is this regard?


Best regards


Humberto A.
 
Those are the "unique emails" that the autoresponder keeps track of so that it knows who it has replied to and who it hasn't. If you don't want so many, lower the number in your active autoresponders.
 
sorry , but that autoresponder files are most of them inexisting accounts , most of those files are Bull sh.... emails to unexisting accounts, the most strange is that I have bunce emails to unexisting accounts , and that email I tried creating and erasing it and its the same thing.

for now my problem was fixed (rudimentary) with a cron job and rm -f psa-autoresponders*

and at least no problems with my users , but I think thats not the REAL solution.


Regards
 
Back
Top