• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Input PES - make it useful to track reason for spam listing

TomBoB

Silver Pleskian
Currently PES does work to whatever degree and lists in the stats how many mails were encountered / dealt with per email address, separated into incoming and outgoing. That in itself is only useful for statistics people. Not for us hosters who need to know the reason behind the spam listing.
PES just works quietly in the background without giving us any insight WHY a mail is treated the way it was treated. [Yeah, we can dig through log files. Takes forever].

I'd like to suggest a major improvement, where you can click in the column for spam / outgoing, and same for spam / incoming for [email protected] , and see all the listed mails that were detected as spam, together with date, time, ips, and the exact reason WHY the mail is being detected as spam.

Practical: we have very tight controls. None of our clients is sending spam. Haven't had a compromised email account for long while either. Yet there is email addresses where PES detects 120 sent spam mails.
[Another improvement: specify the time period for the whole statistic display columns! Is it days? month? weeks? server restarts?...]

Currently we just have to "trust" that PES is doing its job. And I'm starting - with above example - to loose trust in it... Above improvement might help restore that.
 
Back
Top