Post History

It's impossible to know for certain without examining the precise rules used by the IT department's spam filtering system, but we can probably make some sensible guesses.

It is **unlikely** (although not impossible) that the IT system cares about the validity of the PGP signature, or is even bothering to check it, for a couple of reasons:

 * The use of PGP-signed email is extremely niche, and mostly limited to open-source crypto enthusiasts (the only time I've seen PGP-signed emails is on Linux User Group mailing lists, and even then it was only a handful of people on a list with dozens of members). Therefore there is little motivation to integrate PGP functionality into a spam-detection system.
 * It's an extra computational step the system has to perform while processing many thousands of messages every day (although most of those messages won't be signed, for the above reason).
 * The validity of a PGP signature establishes nothing about whether the email is spam. Any spammer can create their own PGP key, upload it to some key servers and start signing their emails.

What spam filters **do** often care about is attachments.

Assuming your PGP-enabled mail client is set up to send signed emails using the [modern PGP/Mime format](https://www.phildev.net/pgp/pgp_clear_vs_mime.html), rather than the largely deprecated inline format, then the signature will be attached as a separate part of a multi-part MIME message, using the content type `application/pgp-signature`. This is in addition to the attachment you explicitly sent, so your resulting message now has two attachments instead of one, which might be enough to push it above the threshold for being marked as spam.