Documentation for what exactly? Its 2 flat files with the list of domains to handle mail for. You don't even restart anything
Like I said, I've never seen anything that I don't need to maintain in some way or another. This is not making sense to me and I'd love to better understand it so that I can use it.
For example any spam server I've ever built, such as assp, while it runs on it's own for the most part, you still have to teach it and tweak it and work at it so that it will do the best job. Even Qmail-Toaster as another example, which is another email server I run, needs constant attention, tweaking, fine tuning, it's never that easy.
So I don't understand how your spam solution can be this simple. It's not clear to me how it gets updates, how I teach it, how I fine tune it, how it acts as a smarthost, etc.
That's why I'd love documentation because it would be a dream if it does all of these things so easily.
PS: For example, in the logs,
Sep 1 04:02:06 gam64 freshclam: Downloading daily-8131.cdiff [100%]
Sep 1 04:02:06 gam64 freshclam: daily.cld updated (version: 8131, sigs: 93955, f-level: 33, builder: mcichosz)
Sep 1 04:02:06 gam64 freshclam: Your ClamAV installation is OUTDATED!
Sep 1 04:02:06 gam64 freshclam: Current functionality level = 31, recommended = 33
Sep 1 04:02:06 gam64 freshclam: DON'T PANIC! Read http://www.clamav.net/support/faq
Sep 1 04:02:06 gam64 freshclam: Database updated (406259 signatures) from db.us.clamav.net (IP: 126.96.36.199)
Sep 1 04:02:06 gam64 freshclam: Clamd was NOT notified: Can't connect to clamd through /tmp/clamd.socket
So for example, right from the start, there is some maintenance which needs to be done. Someone trying this out and not linux aware enough to even look at the logs, would not even know about this based on what you're told me, that it's done once installed.
This is not arguing with you, I like the stuff you're putting out, and I'd love to put it to use, let others know about it, etc. Just need to better understand it