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

# sk185080 - Emails stuck in Postfix queue after R82 installation

| Property | Value |
|----------|-------|
| Solution ID | sk185080 |
| Date Created | 2026-06-23 |
| Last Modified | 2026-07-01 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82 |
| OS | Gaia |

## Symptoms

- * After a clean installation of the on-premises Mail Transfer Agent on Gaia R82, emails stay in the gateway Postfix queue and are not delivered.
* Mail delivery does not continue. Queued emails stay pending, even after a failover in a High Availability cluster and after policy changes.
* The issue occurs when SMTP relay authentication is enabled in the Data Loss Prevention settings or the mail server authentication settings.
* The mail log shows that the Postfix SMTP process does not start. The error is similar to this:  
  `Error:- postfix/master: warning: process /opt/postfix/usr/libexec/postfix/smtp pid XXXX exit status 127`  
  `
  warning: /opt/postfix/usr/libexec/postfix/smtp: bad command startup -- throttling`

## Cause

A dynamic library resolution conflict on Gaia R82 causes this issue.  

When you enable SMTP relay authentication, Postfix uses Cyrus Simple Authentication and Security Layer (SASL) for the authenticated relay. On the affected systems, the dynamic linker cache gives priority to the Check Point `libsasl2.so.2` library in the path `/opt/CPsuite-R82/fw1/lib`. It does not give priority to the standard system library path.  

As a result, the Postfix SMTP daemon loads the Check Point `libsasl2.so.2` library first when it starts. This library is not compatible with the standard Cyrus SASL plug-ins that Postfix uses, such as the plug-ins in `/usr/lib/sasl2`.  

Because of this incompatibility, the Postfix SMTP process fails when it starts. It exits with status 127 before it can deliver mail. As a result, the emails stay in the Postfix queue.

## Solution

This solution requires authentication. Please log in to view the full solution.

---

# 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