Mail scanning and incoming mail.

[akots]

Hi!

You mention configuration, but I can’t find any. Do you mean if the user has a spam folder or not? And that’s there's no actual configuration for Imunify Email yet?

Sorry for the confusion (: The phrase “depending on configuration” in the refers not to ImunifyEmail settings, but to the recipient mail environment’s (Exim/cPanel) spam handling rules, typically SpamAssassin or account-level mail filters managed via cPanel.

https://docs.imunify360.com/email/#enabling-disabling-incoming-filtration

is it fair to say that Imunify Email is in early development and that more features are expected?

ImunifyEmail as a product (outgoing protection, rate limiting, quarantine, etc.) has been in production use since June 2024. What you are referring to now is specifically the incoming email filtration feature, which is a new addition introduced earlier this year and is currently in beta.

We cannot guarantee specific future changes, but its status indicates that this component is still being refined, and user feedback plays an important role in shaping its development (:

[verdonv]

akots thank you for replying. Sorry if I’m tardy now, I didn’t get a notification and just came back to have a look. I appreciate your insight.

Inbound filtering in ImunifyEmail is focused on detection and classification, not full message management yet. No quarantine or manual actions are currently available; ImunifyEmail only detects and classifies messages, then delivers them to the user’s Spam or Trash folder, depending on configuration.

I'm used to a system where messages are scanned and then scored on their likelihood of being spam, and viruses are detected. Depending on what I have configured, infected emails are deleted, emails ranked as low scoring spam are delivered to a spam folder, emails ranked as high scoring spam are deleted. These are all configurable actions. You mention configuration, but I can’t find any. Do you mean if the user has a spam folder or not? And that’s there's no actual configuration for Imunify Email yet?

If you’d like to see more granular control or real-time inbound stats in future versions, I encourage submitting feedback through the Imunify feature request form: https://cloudlinux.zendesk.com/hc/en...st

Thanks for that.

is it fair to say that Imunify Email is in early development and that more features are expected?

thanks again and best regards,
v

[akots]

Hi,

No actions can be taken with those stats, there's not settings for anything in regards to inbound scanning, is that all I should be seeing?

Would you please clarify what settings you are looking for?

Inbound filtering in ImunifyEmail is focused on detection and classification, not full message management yet. No quarantine or manual actions are currently available; ImunifyEmail only detects and classifies messages, then delivers them to the user’s Spam or Trash folder, depending on configuration.

I can see some incoming stats in the Statistics tabs, but they're a day late and don’t seem to be enough.

The statistics update once the incoming messages are processed and aggregated, so it’s normal to see a short delay (up to 24 hours). At the moment, the UI only provides aggregated statistics without real-time interaction or filtering rules.

I should say, I still have Mailscanner running, so it’s my understanding it will have run before Imunify360 looks at the mail, and that is likely why the statistic look low. I'm a little reluctant to disable Mailscanner and deluge my clients with spam that currently gets deleted, but i'm not convinced Imunify360 can replace that, or how. Has anyone else gone down this road yet?

ImunifyEmail can safely work alongside MailScanner. Our internal investigation confirms they are compatible and can operate concurrently:

• MailScanner intercepts messages first, placing them in a queue and scanning them for spam and viruses before delivery.
• ImunifyEmail performs its scanning after MailScanner, during the delivery stage.

So, if MailScanner already processes and removes some spam, ImunifyEmail will naturally see fewer incoming samples, which explains the lower inbound stats you observed.

If you’d like to see more granular control or real-time inbound stats in future versions, I encourage submitting feedback through the Imunify feature request form: https://cloudlinux.zendesk.com/hc/en...st

[verdonv]

I'm a new user of Imunify360 on an Alamalinux 8 cPanel server. I'm coming from a full suite of CSF products.

The default outbound mail scanning seemed simple but working. I enabled the new beta inbound mail scanning. I'm not sure that I’m not missing something, but it doesn’t seem to have made much difference, at least in the UI. I can see some incoming stats in the Statistics tabs, but they're a day late and don’t seem to be enough. There doesn’t seem to be anything else. No actions can be taken with those stats, there's not settings for anything in regards to inbound scanning, is that all I should be seeing?

I should say, I still have Mailscanner running, so it’s my understanding it will have run before Imunify360 looks at the mail, and that is likely why the statistic look low. I'm a little reluctant to disable Mailscanner and deluge my clients with spam that currently gets deleted, but i'm not convinced Imunify360 can replace that, or how. Has anyone else gone down this road yet?