Configuration is just a short artifact. It's not a creative work and is therefore not copyrightable at all, whether by AGPL or otherwise.
> if there is a security issue and it has an emergency patch but there is some coordinated disclosure going on so its not public yet, is this an agpl violation?
No because:
- if you are coordinating with the developers, then you have their explicit permission to temporarily withhold those changes (AGPL copyright holders can still grant exceptions to the license)
- AGPL does not mean you must provide up-to-date source code in an automated matter; you have to be able to provide the source code upon request, and there's nothing in the license preventing any forms of delays (much less so for ensuring security of users)
> antispam stuff tends to benefit from security through obscurity. Can i embed antispam checks directly in the agpl source without revealing
I'm not convinced obscurity helps against spam at all. DKIM and blocklists have done much more against email spam than any form of "security by obscurity" corporate scheme has.
However, if the logic is separate from the configuration, you would have to publish the edited source code (the logic), but could retain the actual configuration (because once again, configuration is not copyrightable).