> Source: [sk148995](https://support.checkpoint.com/results/sk/sk148995)

# sk148995 - MTA Postfix not running and down after each reboot

| Property | Value |
|----------|-------|
| Solution ID | sk148995 |
| Date Created | 2019-03-12 |
| Last Modified | 2023-01-23 |
| Technical Level | General |
| Products | Security Gateway |
| Versions | R81.20, R81.10 (EOS), R81 (EOS) |
| OS | Gaia |

## Symptoms

- * MTA Postfix is not started after a reboot.  
  The only way to start it is manually by using:   
  *#/opt/postfix/usr/sbin/postfix -c /opt/postfix/etc/postfix start*
* Invalid output of this command:  
  \[Expert@fw-ifl-sec:0\]# fw tab -t mta_rule_number  
  localhost:  
  Table mta_rule_number not loaded: Invalid argument  
* If the above symptom does not apply, but the still occurs, this is because using SMTP over TLS.

## Cause

This issue can occur if you do not have an automatic rule for MTA in the threat prevention policy,  
or if you are using SMTP over TLS.

## Solution

To resolve this issue, perform:

1. Disable MTA and then enable MTA. See [sk109699](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk109699) for instructions.  

2. Verify that the automatic rule is generated automatically to be the First Rule, as below:  

   ![](https://sc1.checkpoint.com/sc//SolutionsStatics/sk148995/RULE_Automatic1903120646.PNG)
3. Install policy.  

4. On the Security Gateway, run this command in SSH:  

   *#fw tab -t mta_rule_number* --\> This should provide a value.  

   \*If Threat Prevention Layer is not showing verify Threat Prevention is selected in the Policy Layer.  

   Security Policy \> Edit Policy (right click Policy) \> Policy Types \> Threat Prevention  

   <br />

   If you are using SMTP over TLS, this problem was fixed. [Contact Check Point Support](https://www.checkpoint.com/support-services/contact-support/) to get a Hotfix for this issue.

   A Support Engineer will make sure the Hotfix is compatible with your environment before providing it.  
   For faster resolution and verification, collect these files:
   1. [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) file from the Management Server involved in the case.
   2. [CPinfo](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk92739) file from the Security Gateway / each Cluster Member involved in the case.

   **Hotfix installation instructions:**   
   Refer to [sk168597 - How to install a Hotfix](https://supportcenter.checkpoint.com/supportcenter/portal?eventSubmit_doGoviewsolutiondetails=&solutionid=sk168597).

   <br />

   <br />

   <br />

---

# Agent Instructions

This content is from the Check Point Support Center (https://support.checkpoint.com), the official knowledge base for Check Point cybersecurity products.

## Navigating This Knowledge Base

- **Complete index**: [llms.txt](https://support.checkpoint.com/llms.txt)
- **All SK articles**: [SecureKnowledge Sitemap](https://support.checkpoint.com/sitemaps/secureknowledge-sitemap-index.xml)
- **SK article URL pattern**: `https://support.checkpoint.com/results/sk/{skId}`
- **Markdown responses**: AI bot User-Agents automatically receive `text/markdown` content
