Translations by Mitsuhiro Yoshida

**Warning time for institution expiry**: If set, a notification will be sent to site and institution admins this amount of time before an institution is due to expire and be suspended. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, institutions will not expire by default.

**Auto-suspend expired institutions**: If set, this option will allow Mahara to automatically suspend an institution that has expired automatically. This means that users of that institution will not be able to log in until the institution has been unsuspended.

Account settings

**Session lifetime**: For security reasons, after a specified period of inactivity, a user will be logged off the site automatically. This field specifies this time in minutes. The default value is 1440 minutes (24 hours).

**Default account lifetime**: If set, user accounts will expire after this amount of time from when they were created. When a user account is expired, the user cannot log in. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, accounts will not expire by default.

**Default account inactivity time**: If set, users who do not log in for this amount of time will be considered "inactive" and will not be able to log in anymore. This time may be specified in days, weeks, months, years or "No end date". If the latter option is chosen, users are not set to "inactive" by default.

**Warning time for inactivity / expiry**: If set, a warning message will be sent to users this amount of time before their accounts are due to expire or become inactive. This time may be specified in days, weeks, months, years or "No end date". If the latter is chosen, users do not receive a warning before their account expires or they are flagged as having an inactive account.

Security settings

**Anti-spam**: There are three levels of anti-spam protection available for publicly visible forms, such as the contact and registration forms. A form submission is never silently rejected. Rather, an error message is displayed asking the user to try again if the submission is classified as spam. The three choices are:

**None**: No anti-spam checks are performed on form submissions.

**Simple**: Some basic checks are performed. Form submissions with email addresses that are not well-formed or that have an excessive number of URLs are rejected.

**Enable Spamhaus URL blacklist**: If enabled, 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.

**Enable SURBL URL blacklist**: If enabled, 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.

**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. 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.

Proxy settings

**Proxy authentication model**: Select your proxy's authentication model (none or basic [NCSA]), if appropriate.

**Proxy credentials**: Enter the credentials required for your proxy to authenticate your web server in ``username:password`` format.

Email settings

**SMTP host**: If you want to force Mahara to use a specific SMTP server instead of the system one, enter its hostname here, e.g. ``smtp.example.com``. It is possible to specify more than one host by separating them with semicolons, e.g. ``smtp1.example.com;smtp2.example.com``, but keep in mind that all other settings, e.g. authentication credentials and port numbers, will apply to all listed servers. It is not possible to specify different credentials for each server in this list. This feature is useful when SMTP host authentication is not required or you list different frontends for the same mail server in which case other settings will work.

**SMTP port**: If your SMTP server uses a port number different from 25, you may specify it here. When encryption is enabled, the default ports are 465 for SSL and 587 for TLS. You only need to specify a port number if it is different from these. Check the correct settings with your mail service provider.

**User**: If your SMTP server requires authentication, enter your username here.

**Password**: If your SMTP server requires authentication, enter your password here.

**SMTP encryption**: If your SMTP server supports encryption, enable it here.

General settings

**Allow public pages**: If checked, users can create portfolio pages that are accessible to the public rather than only to logged-in users.

**Maximum tags in cloud**: Enter the default number of tags to display in user tag clouds. Users can change this number in their :ref:`account settings <general_account_options>`.

**Show online users**: If checked, users see a side block with a list of the users who have been logged-in in the last 10 minutes (cf. the :ref:`dashboard <dashboard>`).

**Registration agreement**: If checked, you force users to agree to the "Terms and Conditions" before registration. You should edit your site's "Terms and Conditions" page before enabling this option. You can do so under :ref:`Edit site pages <edit_site_pages>`.

**Allow mobile uploads**: If checked, users have the option of setting an authentication token in their :ref:`account settings <general_account_options>`. That allows them to upload content from their :ref:`mobile devices <mobile_mahara>`.

Edit site pages

Here you can edit the content of some pages around the site and the pages linked to in the footer:

About

Home (Dashboard)

Logged-out home

Privacy statement

Terms and conditions

All pages come with default text that you can change entirely. Every page must contain some text. You can use the visual editor to style your page.

Click the *Save changes* button.

Menus

There are two menus in Mahara:

Links and resources

Footer

Add external links to the *Links and resources* menu

Choose which *Links and resources* menu you want to edit: the public or the logged-in users one.

Choose the type *External link*.