Changes

Jump to navigation Jump to search
Broken link
Line 44: Line 44:  
It is also possible, but strongly discouraged, to disable password strength checking by setting to 'none'
 
It is also possible, but strongly discouraged, to disable password strength checking by setting to 'none'
 
}}
 
}}
 +
 +
The following settings are available to specify the password strength on SME Server:
 +
{|
 +
! 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.
 +
|}
    
====Groups====
 
====Groups====
Line 81: Line 97:     
You can also create a less privileged group "Power Users"<br>
 
You can also create a less privileged group "Power Users"<br>
see http://www.kellys-korner-xp.com/xp_groups.htm for the rights granted to the different groups.
+
see https://ss64.com/nt/syntax-security_groups.html and https://www.howtogeek.com/school/windows-network-sharing/lesson1/all/ for the rights granted to the different groups.
    
====Quotas====
 
====Quotas====
Line 96: Line 112:     
{{Warning box|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).}}
 
{{Warning box|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 box|msg=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, [[SME_Server:Documentation:Administration_Manual:Chapter9#Quotas|so you have to increase it]]. This could solve their problems. see [[bugzilla:7738]]}}
    
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.
 
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.
Line 120: Line 141:  
[[Image:Create-a-pseudonym.png]]
 
[[Image:Create-a-pseudonym.png]]
   −
 
+
=====Practical usage guidelines=====
'''Practical usage guidelines'''
      
An SME Server has only one name set, meaning only one occurrence of a name can be in the system, whether it be a user, a group, a pseudonym or an ibay. Therefore whenever you create a user account and you have multiple domains, then that user will apply to all domains automatically.  
 
An SME Server has only one name set, meaning only one occurrence of a name can be in the system, whether it be a user, a group, a pseudonym or an ibay. Therefore whenever you create a user account and you have multiple domains, then that user will apply to all domains automatically.  
Line 154: Line 174:  
**info@domain3 which forwards to user7  
 
**info@domain3 which forwards to user7  
 
**info@domain4 which forwards to user8
 
**info@domain4 which forwards to user8
sddkdjas
   
**accounts@domain1 which forwards to user9  
 
**accounts@domain1 which forwards to user9  
 
**accounts@domain2 which forwards to user10  
 
**accounts@domain2 which forwards to user10  
Line 171: Line 190:     
If you want webmail to be configured for the correct domain for the correct end user the first time they use it, then you will need to do that manually yourself before issuing the login details to the user, eg
 
If you want webmail to be configured for the correct domain for the correct end user the first time they use it, then you will need to do that manually yourself before issuing the login details to the user, eg
login to webmail as the end user eg user1 (for domain1) and setup the profile for that user to show the return email address of sales@domain1  
+
login to webmail as the end user eg user1 (for domain1) and setup the profile for that user to show the return email address of sales@domain1 login to webmail as the end user eg user2 (for domain2) and setup the profile for that user to show the return email address of sales@domain2  
 
  −
login to webmail as the end user eg user2 (for domain2) and setup the profile for that user to show the return email address of sales@domain2  
      
Do the same for all other webmail accounts that will be issued configuring the profile and return address as applicable.  
 
Do the same for all other webmail accounts that will be issued configuring the profile and return address as applicable.  
    
If you don't configure webmail profiles manually then they will have the default return address of loginusername@domain1 (or the main domain name of the server if different).  
 
If you don't configure webmail profiles manually then they will have the default return address of loginusername@domain1 (or the main domain name of the server if different).  
      
'''Summary'''
 
'''Summary'''
Line 221: Line 237:  
See this thread for details  
 
See this thread for details  
 
http://forums.contribs.org/index.php?topic=30953.0
 
http://forums.contribs.org/index.php?topic=30953.0
 +
 +
Removing the default SME server behaviour to '''auto create pseudonyms'''.  In this scenario (multiple domains) you may not require or desire the need of the default behaviour of 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
 +
 +
{{Note box|Please not that the path to esmith perl libraries has changed as of SME Server 9.x to '''/usr/share/perl5/vendor_perl/esmith'''.}}
 +
 +
the line should be like
 +
 +
#    $accountdb->create_user_auto_pseudonyms($acctName);
    
====Information Bays====
 
====Information Bays====
 
The i-bay (information bay) feature of the SME Server is a simple, very flexible and powerful way for you to share information with others. It is such a rich and important feature that we've devoted [http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter14 Chapter 14] entirely to dealing with Information Bays.
 
The i-bay (information bay) feature of the SME Server is a simple, very flexible and powerful way for you to share information with others. It is such a rich and important feature that we've devoted [http://wiki.contribs.org/SME_Server:Documentation:Administration_Manual:Chapter14 Chapter 14] entirely to dealing with Information Bays.

Navigation menu