In order for Crypt_GPG to be able to read an encrypted message properly and decrypt it, it is required that the message be formatted like so:

-----BEGIN PGP MESSAGE-----
Version: Cryptocx v5.3.2

qANQR1DBwE4D70rFP5ieVJcQA/40BNu3/6coJRtDQdokjfD4em2/8kQyoe8LS/gj btOuDPxHediY7XmIA4TTXf3z8YU3/G2NRaEZ1sPxHuwcZ7zHQQmkZuSJetkPVg/6 9YoDsQtTKoH7YQG99m3MKCP8BzF9beO8luWqYm6T+sdmBWWtcOQ1H5Sdxud4aBY4 /YGZGwP9H8g5MLJHgbJoshO7gqEMK4uQLpiLVxFDn/tpVqISi1rh3fB5luEPi+Qs viPE9pCM9LhLW2KAUyMSo3osaJqTfmwtxhJQ2CGlqc/J98YzN5m1TQlzpcVJDCwQ 5MLp3H6lu2gdce4S7aWEIyE+lMSUuAAQwHGnXAer7ecizG5yfS3JXQrlZJyB9Y+C cBOV00atxsvXpYMjXvXyMpkzKhYZ5TLgPTSZHr8jIusIP3nZT0bmT/dnc+j0oD7p t+iQWgeAiz58LULUqfpZOP2d0I5SBzGZmG90EhXyPk2mRkd9JA== =n+RF
-----END PGP MESSAGE-----

When the message is being passed via POST as a string like so:

-----BEGIN PGP MESSAGE----- Version: Cryptocx v5.3.2 qANQR1DBwE4D70rFP5ieVJcQA/40BNu3/6coJRtDQdokjfD4em2/8kQyoe8LS/gj btOuDPxHediY7XmIA4TTXf3z8YU3/G2NRaEZ1sPxHuwcZ7zHQQmkZuSJetkPVg/6 9YoDsQtTKoH7YQG99m3MKCP8BzF9beO8luWqYm6T+sdmBWWtcOQ1H5Sdxud4aBY4 /YGZGwP9H8g5MLJHgbJoshO7gqEMK4uQLpiLVxFDn/tpVqISi1rh3fB5luEPi+Qs viPE9pCM9LhLW2KAUyMSo3osaJqTfmwtxhJQ2CGlqc/J98YzN5m1TQlzpcVJDCwQ 5MLp3H6lu2gdce4S7aWEIyE+lMSUuAAQwHGnXAer7ecizG5yfS3JXQrlZJyB9Y+C cBOV00atxsvXpYMjXvXyMpkzKhYZ5TLgPTSZHr8jIusIP3nZT0bmT/dnc+j0oD7p t+iQWgeAiz58LULUqfpZOP2d0I5SBzGZmG90EhXyPk2mRkd9JA== =n+RF -----END PGP MESSAGE-----

It is not readable by Crypt_GPG. Anyone have any recommendations on how to remedy this? I'm checking to see if it can be passed properly, if not I'm guessing some regex is going to be needed.