Phil: Thanks for the most helpful response!
With this client, we began by sending them the file pgp encrypted with the shared public key. This was fine except that on their end, the automated process (of which I know nothing) is two fold when they get a .pgp encrypted file, first is decrypts the file, then it appears to look for a signature. The decryption part worked fine, but the absence of a signature caused the process to fail. They then explained that raw encryption wasn't necessary required, but that all files coming to them had to be signed. So, using pgp desktop, I did the following:
Right clicked on the file to be signed, selected "Sign as <imported key here>". "Save detached key(s)" was left checked. And, as you indicated, this generated a detached signature file (.SIG).
This method was unacceptable to them, as they "do not support detached signatures."
Back to the drawing board, I then performed the same aforementioned step, but this time, unchecked the "Save detached keys(s)" box. The file was then signed, but had the .PGP extension. If you opened it in notepad, it looked like this:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
<DATA CONTENT HERE>
-----BEGIN PGP SIGNATURE-----
Version: PGP SDK 4.0.1
<SIGNATURE HERE>
-----END PGP SIGNATURE-----
This is your item #2 and was unacceptable to them and regarded as "clear signed" Which they do not support. As they indicated, they needed the signature to encapsulate or "wrap" the message.
And you're right, I may be misusing and/or mixing terms a bit.
With item #1 you mentioned that default signing is wrapped into the PGP message. It doesn't appear that this is doable simply by encrypting a file using your imported public key. At least not for me. Can you tell me how to achieve this?
I did notice the copy and past option you mentioned, but I wasn't sure how to arrange the information in the file. I'll give this a try as well and see if I make any headway.
Thanks so much for the help!