We want to extend our support licences for our fortiweb 400d device with
a 24x7 FortiCare plus AV, FortiWeb Security Service and IP Reputation
support licence. When we contacted our distributor he told us they could
only extend it up to 2026-01-14 wh...
Related to this question that was never answered: Clarification about
Local Spam by Sender report - Fortinet CommunityWhat does the Spam by
Sender report signify?Are the listed accounts sending spam or recieving
it? The report says that in the last 2...
Hi All, I have a fortimail 900f and we've noticed that when users emails
are compromised the malicious actors use said email accounts to send
mass spam between 1 am and 5 am. From what we can see no users are
sending emails during that period so we'd...
Hi All, I've got a user recieving sensitive encrypted attachments that
are being blocked by the attachment filter. As a solution Ive created a
new content filter + a new inbound policy for the specific domain and
address that share these attachments....
Hi all, I'm wondering if there is a better way to deal with the issue we
are facing. Currently we have around 3500 emails on our exchange which
is protected by fortimail and fortiweb-400D. About 50% of our users use
the webmail to login to their emai...
Sure we're more curious what happens with the software support since its
EoS date is a year and a half after the HW support date. The offer we
got from our distributor was up to the EoS date of the HW and not the SW
so while the SW is still not EoS w...
All of them are marketing for different things so I can understand if
that qualifies as spam. But these are emails that arrived TO that users
address so its users that GET the most spam?
Sorry I accedentaly accepted this. We do have spam filtering enabled and
it blocks a lot but our users are generally older and fall prey to spam
emails asking for passwords which causes most of our headaches. Thats
why I'm looking for additional rest...
Yeah thats what I planned as option b, I didn't create the original one
but I wanted to see if I could skip disabling that one and creating a
new one. I'll try that and see if I can make it work.
Thats correct its the default system level recipient policy which takes
precedent over all the others. How would I create the IP based policy to
work between an email and domain? Also I don't see this option you
mentioned when creating a new IP based...