Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
We value your experience with Plesk during 2025 Plesk strives to perform even better in 2026. To help us improve further, please answer a few questions about your experience with Plesk Obsidian 2025. Please take this short survey: https://survey.webpros.com/
On Plesk for Linux mod_status is disabled on upgrades to improve Apache security. This is a one-time operation that occurs during an upgrade. You can manually enable mod_status later if needed.
it is easier to setup and manage because it does not require patching. Also it does not require postgres/mysql. Basically you prepend it as a separate module in the tcpserver chain
Btw, do you know how to make the change in the tcpserver chain permanent, because every change on the Plesk Mailsettings Menu overwrite the smtp_psa again...
Originally posted by Brujo Btw, do you know how to make the change in the tcpserver chain permanent, because every change on the Plesk Mailsettings Menu overwrite the smtp_psa again...
since about three Days the Greylisting on one of our machines stopped working.
I can find any incoming E-Mail in the Database.
All Mails got a blocked_count of 1 and a passed_count of 0.
Normaly that means the Mail was not delivered.
In our case any Mail passed and was delivered to the useres Mailbox.
It seems like qmail insert an Entry for each mail but do not check them a second time but y?
Just re-read that and noticed your saying it is getting through. Have you recently updated plesk? If so you will need to recopy the qmail-smtpd from the compile directory to the qmail/bin directory.
also worth running a myisamchk on your greylist dbase - and if necessary repairing it
thanks for your fast reply.
Since I posted my help-request I search for further possible problems.
The funny part of the problem is the fact that qmail apperently signed any e-mail as new one and delivered them
to the mailbox instead of rejecting in case of first contact.
Also already saved entries in DB where not updated anymore.
While my Spy-Job on the affected machine I stumbled about the greylisting_dbg.txt which seemed not to be affected of any jounal cycle and had a filesize of 2GB.
A tail -f on the debugfile has shown me no more upcoming entrys at that time.
I backuped the regular file.
Directly after the backup a new one appeared and the problem disappeared.