Answers.Body: <p>I recommend giving anyone who creates mailings the &quot;Bypass IDS Check&quot; permission. That will prevent them triggering this error. Really everyone on your staff should get that permission, since you already trust them to use the system.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-08T17:48:53.230Z
Answers.Text: thank you, I don't trust any of them at all though.
Answers.UserDisplayName: yurg
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2024-05-08T15:23:58.243Z
Answers.LastActivityDate: 2024-05-08T15:23:58.243Z
Answers.UserDisplayName: Coleman
Body: <p>Have started getting the below messages in logs.
  Would this be because of someone playing with mailings Public View URL or there is a JS  code added by mailing creators/editors somewhere?</p>
  <pre><code>[info] $IDS Detector Details = Array
  (
  [0] =&gt; Array
      (
  [name] =&gt; x-javascript; charset
  [value] =&gt; utf-8;base64,...
          [page] =&gt; /civicrm/mailing/data:application/x-javascript;
  </code></pre>
  
Tags: <mailing>
Title: $IDS Detector: There is a validation error with your HTML input. Your activity is a bit suspicious, hence aborting
ThreadText: # $IDS Detector: There is a validation error with your HTML input. Your activity is a bit suspicious, hence aborting
  
  (Asked by: username_0 on 2024-05-08)
  
  Have started getting the below messages in logs.
  Would this be because of someone playing with mailings Public View URL or there is a JS code added by mailing creators/editors somewhere?
  
  ```
  [info] $IDS Detector Details = Array
  (
  [0] => Array
      (
  [name] => x-javascript; charset
  [value] => utf-8;base64,...
          [page] => /civicrm/mailing/data:application/x-javascript;
  
  ```
  
  **Tags:** mailing
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2024-05-08. Score: 2 | Accepted answer
  
  I recommend giving anyone who creates mailings the "Bypass IDS Check" permission. That will prevent them triggering this error. Really everyone on your staff should get that permission, since you already trust them to use the system.
  
  > **Comments:**
  > **username_0**: thank you, I don't trust any of them at all though.  
  
  ---
  
  