A script that helps you understand why your E-Mail ended up in Spam

Edit Package decode-spam-headers
https://github.com/mgeeky/decode-spam-headers

Whether you are trying to understand why a specific e-mail ended up
in SPAM/Junk for your daily Administrative duties or for your
Red-Team Phishing simulation purposes, this script is there for you
to help!

Idea arose while delivering a commercial Phishing Simulation
exercises against MS Office365 E5 estate, equipped with
MS Defender for Office365. As one can imagine, pretty tough security
stack to work with from a phishing-simulation perspective.
After digging manually through all these Office365 SMTP headers and
trying to cherry-pick these SCL values, time come to write up a
proper parser for SMTP headers.

Time went by, I was adding support for more and more SMTP headers -
and here we have it. Tool that now comprehends tens of different headers.

Source Files
Filename Size Changed
_service 0000000510 510 Bytes
_servicedata 0000000247 247 Bytes
decode-spam-headers-0~git20250417.tar.xz 0000550680 538 KB
decode-spam-headers.changes 0000000194 194 Bytes
decode-spam-headers.spec 0000002286 2.23 KB
Comments 0
No comments available
openSUSE Build Service is sponsored by