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

# sk123932 - Mobile Access Dynamic ID parameters cannot be explicitly entered

| Property | Value |
|----------|-------|
| Solution ID | sk123932 |
| Date Created | 2018-05-27 |
| Last Modified | 2018-12-29 |
| Technical Level | Advanced |
| Products | Security Gateway |
| Versions | R82.10, R82, R81.20 |
| OS | Gaia |

## Symptoms

- * At Mobile Access DynamicID Setting,the BODY section does not take any parameters, and cannot be set explicitly.   
  Example for a test case:  

  ```
  
  1.mail:TO=ticket@emailServer.com;SMTPSERVER=1.1.1.1;FROM=sslvpn@domain.com;BODY=$RAWMESSAGE
  2.mail:TO=ticket@emailServer.com;SMTPSERVER=1.1.1.1;FROM=sslvpn@domain.com;BODY=$RAWMESSAGE $USERNAME $PHONE
  3.mail:TO=ticket@emailServer.com;SMTPSERVER=1.1.1.1;FROM=sslvpn@domain.com;BODY=TEST
  ```

  <br />

  The first test works as expected. The email body shows the message defined at $RAWMESSAGE.   
  The second one failed the progress, portal shows the error "Dynamic Id authentication failed" and there is no traffic to email server at all.   
  The third one is supposed to have email body message as "TEST" but it ends up with the same message that is defined in $RAWMESSAGE, which is not correct.
* From traffic captures, the SMTP traffic to email server is not changing the body section, it is always just using $RAWMESSAGE.

## 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