Search results

Hey! I'm the developer of the extension. Please do not spread untruths. The integration of Amavis in cooperation with SpamAssassin and ClamAV is a standard procedure, which many other operators also do. We only use open-source software in Plesk Email Security to fight spam, with optimised rules...

Hey Klaus, I finished the work on the new version last week, and it has already passed the certification process. It's scheduled for publication and will be released soon! Cheers Viktor

Hello Klaus, Thank you for your entry. I'm currently working on the Joomla! 4 support in our Joomla Toolkit. I will finish it by the end of this week, and most likely latest next week, the new version will officially be released. So, stay tuned! Cheers Viktor

Hey Brock, First of all, thank you for your praise. I'm happy that you like the Joomla! Toolkit! Everything that you've described is expected behaviour. The toolkit only displays extensions with extension IDs higher than 10.000. So, the IDs in the database have been set "incorrectly" in your...

Thanks for the feedback. Yes, I will discuss it internally, could be quite useful. Thanks for the feature request!

You are welcome, no problem! :)

Hi! This issue does not occur in the latest version of the extension. I'd be happy if you could test it again! Cheers Viktor

Hey! The spam settings can be set directly from the Mail overview page (as an admin also for all client accounts by using the customer panel login): Cheers Viktor

Hey TomBoB! Not sure I understood you correctly, but this is fully integrated already (with normal user accounts and with email accounts only). Example for email accounts only with access to the Plesk interface: Settings can only be adjusted server-wide or on email level for now. I like...

Hey Achim, What do you mean? I've implemented this feature already almost half a year ago in version 1.1.0 (released on 16th July 2020). Excerpt from the changelog: Merry Christmas!

Yes, I already informed my colleagues about it! ;-) Thanks! Edit: Description has been updated.

Hello @obendev, we've released version 1.1.1 of Plesk Email Security with your proposed Postfix security rules: Plesk Email Security - Plesk Extensions Thank you once again for helping us to improve our solution! Cheers

Thank you once again @obendev for your detailed post. I've applied all recommended rules and will prepare the release of version 1.1.1. We plan to release it in the first half of next week. Cheers

Hi! SPF spam protection is a separate handler in Plesk. Please make sure to set the "Reject" option in "Tools & Settings" -> "Mail Server Settings" -> "SPF spam protection" -> "SPF checking mode": We're working on improving the restrictions to stop such spam emails completely also directly...

Hi Oliver, do not use * (asterisk) in Plesk Email Security. Use this for your case: Vulkan@.com The . (dot) stays for any character (as in regular expressions). Cheers

Hi! The extension executes the following command (you can try to run it manually in the terminal to see the full response of the query): host -tTXT 2.0.0.127.multi.uribl.com Please see here why and what you can do if the query is refused: URIBL.COM - Realtime URI Blacklist Cheers

Hallo Moswak, ich gebe dir Recht, ich finde die Beschriftung generell nicht korrekt, da man damit tatsächlich die Domain löscht und nicht die Websites (Daten der Domain)! @Katya I think we should change the label to "Delete domain" also in English since this action does not only remove the...

Hi! Did you run the following command? plesk repair web -y Cheers

Hi Trialotto, thank you for your opinion and constructive criticism! I will discuss your proposal how to improve the extension internally. Cheers

Okay, please contact me via PM.