2 Replies Latest reply on Feb 1, 2018 12:56 PM by MarkWalsh

    Form flagged as virus in email server

    MarkWalsh Level 4

      I had an issue today where I couldn't send a PDF form I had been working on to a coworker, and found out that the form was being flagged by our server as a virus (MAL/PdfEx-C). I traced back through the changes I made (a previous version had no problems posting) and was finally able to track it down to a function I had added to a field's Custom Format event. In that event, I needed to sort an array of checkboxes to keep them in the proper order and concatenate their values. I added a function to do the sorting, and this was what was being flagged by our server. I moved the sort function out of the Custom Format event into a standard JavaScript code module, and had no problems then emailing the file. This is the function:


      // Custom sort order for checkbox field array

      function customSort(a,b) {

          return( a.name.toString() < b.name.toString());



      Can anyone say why the email server would flag a file for having a function defined within the field's events? I usually don't do this, (I put all code into a code module for reusability across all fields), but in this instance I knew it would only be used within that event. I will remember to avoid this situation in the future, but was wondering if there was an explanation for why this happened in the first place. It took me an hour or two to track down this issue, and I would like to know a little more about this in case something like this happens in the future.



        • 1. Re: Form flagged as virus in email server
          Joel_Geraci Adobe Community Professional

          I had a desktop virus scanner that decided that every PDF with a document level script had a virus. They get a bit too aggressive at times. You can probably have a setting changed on the server.

          • 2. Re: Form flagged as virus in email server
            MarkWalsh Level 4

            Thanks. Luckily, haven't had anything that aggressive happen here.


            I'd rather not change the settings on our server (we may not even be able to), and besides, I'd rather have these issues come to light before we send the files to our client, whose settings we definitely cannot change or even be aware of. Hence the reason I'd like to know more about what can cause problems/why this instance was flagged. I'd like to be aware of anything that could potentially happen when we send a form to our client, or if they need to send one out. It would not be good if we sent a file to our client, and they needed to distribute it and started seeing these issues.