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

Bounce versus Reject

breun

Golden Pleskian
Sometimes a mail queue can get rather filled with bounces to non-existent mailnames (a.k.a. bounces to spam messages). I'd like to change all domains that are currently set to bounce mail to reject mail to non-existent mailnames. However, I don't want to change domains that have catch-all setup to reject, so I can't use Group Operations to accomplish this.

How should I go about this? I obviously don't want to check all domains manually. Should I just write an SQL query against the psa database that sets a domain to reject if it is currently set to bounce? And then run mchk -v afterwards? I'm guessing that would work. Any ideas?
 
Back
Top