Nuagerie has completed the activation of an additional filtering layer for incoming and outgoing email on the managed hosting platform. The deployment integrates Imunify Email with the existing mail services and retains the established spam and malware controls. Initial verification included real message flows, service health and encrypted SMTP connectivity.
Protection in both directions
Incoming filtering adds another stage of examination before messages reach their destination. Outgoing filtering also examines mail leaving the hosting environment. Addressing both directions is important for a shared mail platform: incoming protection helps manage unwanted messages, while outgoing checks contribute to controlling abusive sending from hosted applications or accounts.
We also enabled the native restriction on Windows executable attachments on the affected mail services, including executable and batch files. This reduces a common route for delivering unwanted programs through email. Existing sending limits, spam-scanning settings and quarantine controls remain part of the overall configuration.
Integration checked against actual mail delivery
Our team activated the protection in stages and checked that filtering and mail services were operating together. An independent connection check confirmed that the encrypted SMTP service remained accessible after deployment.
We then followed a sample of real incoming and outgoing messages through the filtering process. It included incoming messages delivered to the spam folder and outgoing messages delivered successfully to remote recipients. The related services remained stable during these checks, confirming that the additional protection was operating within the delivery process.
What customers should expect
The platform changes are handled by Nuagerie. Customers do not need to change their mail server address, rebuild their mailbox or reconfigure their email application for this filtering rollout. Existing mailbox and sending policies continue to apply.
As with any filtering system, classification depends on the message and its context. Customers should continue to review their spam folder when an expected message is missing. A legitimate message incorrectly classified as spam should be reported with enough information to identify the delivery, such as the sender, recipient and approximate sending time.
Executable files should not be sent as ordinary attachments when they fall under the attachment restriction. If you need to share software or another file that requires special handling, contact support for guidance on an appropriate transfer method.
For a business, a delivery question may concern a quotation, an order or a time-sensitive reply. The useful outcome is a clear explanation of what happened to the message and what to do next. Our team can compare the delivery path with the filtering result, then identify whether follow-up belongs with the mailbox settings, the sending application or another provider.
Existing customers can send the relevant delivery details through the client area so the request stays associated with their service. Avoid posting message contents or account credentials publicly. If your business needs coordinated oversight of mailboxes, applications and staff devices, our IT management services provide a way to discuss those responsibilities together.
