On 06 Jul 2016, at 10:54, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
On Wed, Jul 6, 2016 at 10:36 AM, Vincent Massol <vincent(a)massol.net> wrote:
On 06 Jul 2016, at 10:31, Thomas Mortagne
<thomas.mortagne(a)xwiki.com> wrote:
IMO ideally we should have <current wiki> -> <main wiki> for each
configuration property, not all or nothing. Exactly like standard
XWikiPreference based configuration properties.
This is what we have, it’s already per-property.
As for the 1 vs 2 I really see no reason to
forbid overwriting part of
the configuration in his own wiki for use cases like
myxwiki.org for
example.
The question is: Do we really want local admins on
myxwiki.org to be able to use their
own SMTP servers? I guess with ours we could configure some anti-spamming techniques to
prevent myxwiki users from spamming people. At least we would have the mail logs in our
SMTP server when some third party decides to blacklist us.
1) The SMTP server is not the only thing you can setup there (for
example it's interesting to change the default from mail address for
you wiki). But you might still want to use your own SMTP server for
you wiki (becauseou have a SMTP server which provide some analysis of
the mails, storage, etc.).
So we could easily decide to use the local wiki only for some properties if we want.
2) I don't see the relationship with spam.
The only thing really
important for spam is who is allowed to send mail, not really who is
allowed to choose the SMTP server. Allowing someone to configure his
own SMTP server actually only decrease the load on the main SMTP
server and the chance of it being used for spam in case it's
overwritten.
I explained the relationship in the previous mail. In short: controlling the SMTP server
allows you take some actions/monitor mails.