Skip to main content
NeoRant
NeoRant
Explorer III
March 12, 2025
Solved

Forti Mail "No license" error on Dashboard for Virus Outbreak & Antispam

  • March 12, 2025
  • 5 replies
  • 2983 views

Good day,

 

This is URGENT.

I am seeing “No license” for features Virus Outbreak & Antispam. These features were always in the green during my 2024 subscription and even after renewal license in January 2025. Last time I checked, even last week, these 2 features were in the green/licensed. I Logged on this morning and now realizing this.

 

What is the cause for this change?

 

Contact Fortinet support or something i can do from cli etc.?

 

This is very strange. HELP!

 

 

FM license error.jpg

Best answer by NeoRant

Issue resolved.

 

Solution:

Using the GUI console, go to "System > FortiGuard", select the tab "AntiSpam". Now, change "FortiGuard server port" value form 53 to 8888 and click on "Apply". Now click on "Update Now" and wait for 5 minutes

5 replies

AEK
SuperUser
AEK
SuperUser
March 12, 2025

Hi NeoRant

What do you see as active subscription on the support portal?

AEK
    NeoRant
    NeoRantAuthor
    Explorer III
    March 12, 2025

    All is active. I am just noticing the change today.

    FMentitlement.jpgFM licenseExpiration.jpg

    AEK
    SuperUser
    AEK
    SuperUser
    March 12, 2025

    Which FML version?

    Does your FortiGuard's Antispam actually works? You can check in the logs if the signature is sent to FortiGuard and if the response is received.

    AEK
    NeoRant
    NeoRantAuthor
    Explorer III
    March 12, 2025

    Version: FML VM01

     

    All seemed well last week up to yesterday.

    AEK
    SuperUser
    AEK
    SuperUser
    March 12, 2025

    I mean which firmware version?

    Do you mean FortiGuard antispam is not working anymore? Do you see it in the logs.

    AEK
    AEK
    SuperUser
    AEK
    SuperUser
    March 12, 2025

    It seems the screenshot confirms that FortiGuard antispam is not working. This also confirm that the "no license" message on the dashboord is not a cosmetic bug.

    First thing I'd do is to update to 7.4.4, which is quite more mature than 7.4.1. You may have a chance to fix your issue with this update.

    In case it doesn't help than I'd ask to escalate the ticket  to L2 (significant impact on business), and in the meantime I'd prepare a new VM 7.4.4 from scratch and then open a CS ticket to move the license to the new VM.

    Hope it helps.

    AEK
    NeoRant
    NeoRantAuthor
    Explorer III
    March 12, 2025

    AEK,

     

    Wow, that update may not be possible right now. You know how workplace politics, awaiting approval from managers all that **bleep** goes. I sent a ticket, waiting for reply. Will update you if anything changes.

    NeoRant
    NeoRantAuthorAnswer
    Explorer III
    March 14, 2025

    Issue resolved.

     

    Solution:

    Using the GUI console, go to "System > FortiGuard", select the tab "AntiSpam". Now, change "FortiGuard server port" value form 53 to 8888 and click on "Apply". Now click on "Update Now" and wait for 5 minutes

      AEK
      SuperUser
      AEK
      SuperUser
      March 15, 2025

      Hi NeoRant

      Happy to see your issue is resolved.

      But what I find strange is that ports 53 & 8888 should not be involved in license validation, while 443 & 8890 are.

      Below port ref from admin guide.

      https://docs.fortinet.com/document/fortimail/7.4.1/administration-guide/122044

       

      443 or 8890

      TCP

      • Fortinet

      53 or 8888

      UDP or TCP

      FortiGuard Antispam rating query

      AEK
      NeoRant
      NeoRantAuthor
      Explorer III
      March 16, 2025

      Hi AEK,

       

      I fully understand. However, that is what was instructed to be used by Fortinet when setting up the Fortimail.

       

      Kindly see below final response from Fortinet to the ticket I created related to this problem:

       

      Hello,

       

       

      Thanks for the feedback.

       

       

      We cannot explain exactly what happened with port 53 due to factors beyond our control, such as the ISP or border/edge devices. We've observed that sometimes the used port (53, 8888, etc) is inhibited and we only change it and FML connects again with FortiGuard. In fact, if you return the port 53 again, the connection won't be affected and will work again using that port 53.

       

       

      We proceed to close the ticket, and we would appreciate if you could take a moment to answer the "customer satisfaction" survey that will be sent to your email once the ticket is closed. The information provided will help to improve the support offered. The next link can help you to know how to evaluate the TAC service:

       

       

      https://community.fortinet.com/t5/Customer-Service/Technical-Tip-How-to-Rate-Fortinet-TAC-Service/ta-p/243789

       

       

      Thank you again for contacting us.

       

       

      Greetings,

       

       

       


      FORTINET | LATAM TAC


      ☏ Support Center:+1 408-542-7780


      https://support.fortinet.com


      https://community.fortinet.com

        AEK
        SuperUser
        AEK
        SuperUser
        March 16, 2025

        Thanks for sharing.

        Sometimes I want to say:

        Theory is when you know everything but nothing works. Practice is when everything works but no one knows why. In our lab, theory and practice are combined: nothing works and nobody knows why.

        AEK
        Terms & ConditionsAccessibility statement