Concerns in mod_mam default values

[badlop]

Erik Grun reported several problems by email. I reproduce here the unresolved ones:

---

It says on the page "Modules Options" under the "mod_mam" section:

assume_mam_usage: true | false […] The default value is false.

but in the default configuration (which gets installed with the RPM package) it is set to "true".

---

I am wondering, why the default value in "mod_mam" for "default" is set to "never".

It is confusing, because I still get the points in Daniel Gulschs "Compliance Tester", but it disables the expected behaviour from the module. (I have the same issue with In-Band Registration. Although this should probably be handled differently.)

This default setting does also seem to break "mod_carboncopy".