SME Server talk:Documentation:Administration Manual:Chapter9

I suppose it will be great to have also one note into Practical usage guidelines about removing the default SME server behaviour to auto create pseudonyms

I propose:

In this scenario (multiple domains) You probably will not need any more the auto creation of pseudonyms 
To achieve this comment with an # at beginning the line 793 into /usr/lib/perl5/site_perl/esmith/FormMagick/Panel/useraccounts.pm

the line should be like

#    $accountdb->create_user_auto_pseudonyms($acctName);

--Stephdl (talk) 01:41, 12 July 2013 (MDT) we ought to add this mentions The following settings are available to specify the password strength on SME Server:

Changing User Passwords

Once they have an active account, your users can set their own passwords by accessing the user-password URL which is only accessible from Local Networks. They do this through their web browsers by visiting the URL www.yourdomain.xxx/user-password (where "www.yourdomain.xxx" is the web server name you entered into the server console). The staff at The Pagan Vegan would visit the URL www.yourdomain.xxx/user-password .

To make the change, a user would enter his or her account name (the characters before "@"), the old password and the new password (to ensure accuracy, the screen asks for the new password twice). Note that changing the password for a user in the server-manager overrides any previous password entered by your user. Therefore, when a user forgets his password, simply reset it in the server- manager.

 

	Note:
	There is no way for the administrator to recover a forgotten password for a user. All they can do is set a new password for the user.

 

Note:

Password strength checking is too strong. How do I change it? First a warning - Far too many systems out there have weak passwords and they will be broken into. Educating your users on the necessity of strong passwords is the best option. If that fails, here is how you change the password strength checking from 'strong' to 'normal', which was the setting in previous versions of SME. Be careful to use the exact capitalization. config setprop passwordstrength Users normal config setprop passwordstrength Ibays normal It is also possible, but strongly discouraged, to disable password strength checking by setting to 'none'

setting explanation
strong	The password is passed through Cracklib for dictionary type word checking as well as requiring upper case, lower case, number, non alpha and a mimimum length of 7 characters.
normal	The password requires upper case, lower case, number, non alpha and a minimum length of 7 characters.
none	The password can be anything as no checking is done. Please note that "none" does not mean no password, it just means no password strength checking, so you can enter any (weak) password you want as long as it is at least 7 characters long.

--Stephdl (talk) 11:32, 29 July 2013 (MDT) bugzilla:7738

Quotas

By default, there is no size limit on the files a user may store on the server nor the amount of email that can be received. However, if you wish to limit the disk space a particular user account can use, you may do so on the " Quotas " panel in the server-manager. As shown in the image below, you will see a list of user accounts, the actual disk space they are using and the quotas, if any, set for that user account.

	Warning:
	Note that the quotas apply to all files that a user stores on the server. This includes not just their home directory, but also all files that they may put into any of the i-bays.

There are two quotas that can be applied to each user account:

• Limit with grace period - when a user's disk usage exceeds this limit, an email warning message will be sent to the user account each night until the disk usage is brought back under the limit.
• Absolute limit - when a user's disk usage hits this limit, the user will no longer be able to save files to the server or receive email.

Note that if the user account exceeds the "Limit with grace period" for seven consecutive days, the account will be treated as if it exceeded the absolute limit and will no longer be able to save files or receive email.

	Warning:
	Email for the user account is not lost! It is held in the delivery queue and will be delivered to the user when their disk usage drops back below their absolute limit (or the "limit with grace period" if they were locked out due to seven days above that limit).

	Note:
	In certains cases you have some mailboxes which can't delivery messages and the qmail log say: deferral: Temporary_error_on_maildir_delivery._(#4.3.0)/ It is probably that your users want to go beyond the upper limit of their quota, so you have to increase it. This could solve their problems.

By selecting " Modify " you are able to set a quota (in Megabytes) for a particular user account. Note that you do not have to set both limits for a user account and can choose to set only one of the limits.

If you set a limit and later wish to disable the quota for a given user account, all you need to do is set the limit to "0".