I think I know where the confusion came from - MASE is an acronym that refers to an old product called McAfee AntiSpyware Enterprise, which has nothing to do with spam
The packages you refer to are the anti-spam engine and rule updates used by products with anti-spam capabilities, like GroupShield. If you need to put them back into the repository, all you need to do is make sure you have the extension for Groupshield checked in to ePO, and then run a pull task - they will be downloaded automatically.
Thank you Joe! I just want to add a little clarification in the rare case that anyone else out there would care about this :-) The Anti-Spam modules are somehow still a part of that old McAfee Anti Spyware Enterprise (MASE). Assuming that someone has customized their daily pull task so that they do not constantly download modules they don't use, then in order to ensure the Anti-Spam returns you would need to edit the details of that "Server Task" to check the Site Package "Anti-Spam Engine for Windows" again. When the update process is run, you will see the following:
Checking in package Current\MASECORE2000\188.8.131.5286\SpamEngine\0000 complete
At this point the Anti-Spam information has automatically been installed into the Repository.
Obviously - to remove Anti-Spam completely (for those of us who don't use it and want to clean-up the console and pull process) - remove the modules from the Repository and then edit the daily repository pull task to uncheck the Site Package "Anti-Spam Engine for Windows".
I think I may have not been clear though - there is no link between the anti-spam packages and the old MASE product. Just to clarify, they're completely unrelated - they just happen to share an acronym.