|
80.
|
|
|
**Advanced**: Performs additional checks to determine whether email addresses are real or contain URLs that are blacklisted. This requires an Internet connection.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:392
|
|
81.
|
|
|
**Spamhaus URL blacklist**: If set to "Yes", URLs will be checked against the Spamhaus DNSBL. The `Spamhaus Project <http://www.spamhaus.org>`_ provides a URL blacklist that is free for non-commercial, low-traffic use. A professional use datafeed service is also available but not supported in Mahara. Please read the `Spamhaus DNSBL usage terms <http://www.spamhaus.org/organization/dnsblusage.html>`_ before enabling this option.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:252
|
|
82.
|
|
|
**SURBL URL blacklist**: If set to "Yes", URLs will be checked against the SURBL DNSBL. `SURBL <http://www.surbl.org>`_ provides a URL blacklist that is free for organizations with fewer than 1000 users. A professional use datafeed service is also available, but not supported in Mahara. Please read the `SURBL usage terms <http://www.surbl.org/usage-policy.html>`_ before enabling this option.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:286
|
|
83.
|
|
|
**Disable external resources in user HTML**: Turning this option on will prevent users from embedding external resources such as images from remote sites into their forum posts and other HTML content. YouTube videos and other media can also not be embedded. It is however a good thing to do from a security standpoint since it does neutralise a few clever phishing attacks. See the `HTML Purifier documentation <http://htmlpurifier.org/live/configdoc/plain.html#URI.DisableExternalResources>`_ for more details.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:287
|
|
84.
|
|
|
This setting also disables the inserting of images that you have uploaded to Mahara into regular text. An upgrade to Mahara 16.04 or later fixes this problem. If you want to backport the fix, you can find it on the `bug report <https://bugs.launchpad.net/mahara/+bug/1550519>`_.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:257
|
|
85.
|
|
|
**reCAPTCHA on user registration form**: If set to "Yes", :index:`people who register themselves on the site <single: reCAPTCHA>` are required to fill in a `reCAPTCHA <http://recaptcha.org/>`_ test. This is a spam protection instrument.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:259
|
|
86.
|
|
|
**reCAPTCHA site key**: Enter the site key for your site's reCAPTCHA account.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:398
|
|
87.
|
|
|
**reCAPTCHA secret key**: Enter the secret key for your site's reCAPTCHA account.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:399
|
|
88.
|
|
|
Proxy settings
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:409
../source/administration/config_site.rst:414
|
|
89.
|
|
|
**Proxy address**: If your site uses a proxy server to access the Internet, specify the proxy in ``hostname:portnumber`` notation.
|
|
|
|
(no translation yet)
|
|
|
|
Located in
../source/administration/config_site.rst:416
|