1,574
edits
Changes
Jump to navigation
Jump to search
Line 44:
Line 44: + + + + + + + + + + + + + + + + Line 81:
Line 97: − + Line 96:
Line 112: + + + + + Line 120:
Line 141: + − '''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. + − + − + − − − − Line 139:
Line 157: − eg create your domains eg domain1, domain2, domain3, domain4 and configure those domains to use different ibays for the web content. + − − − create user accounts user1, user2, user3, user4 as needed for users who want to use the email address "sales", but keep in mind they will use the login name user1 rather than sales (the login names could be johnb, johnb2, johnw, johnm etc) − − create user accounts user5, user6, user7, user8 as needed for users who want to use the email address "info", but keep in mind they will use the login name user5 etc rather than info − + − + − sales@domain1 which forwards to user1 − sales@domain2 which forwards to user2 − sales@domain3 which forwards to user3 − sales@domain4 which forwards to user4 − info@domain1 which forwards to user5 + − info@domain2 which forwards to user6 − info@domain3 which forwards to user7 − info@domain4 which forwards to user8 − + − + − + − + + + + + + + + + + Line 175:
Line 190: − + − − − Line 224:
Line 236: − + + + + + + + + + + +
SME Server:Documentation:Administration Manual:Chapter9 (view source)
Revision as of 06:40, 21 July 2017
, 06:40, 21 July 2017Broken link
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====
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====
{{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.
[[Image:Create-a-pseudonym.png]]
[[Image:Create-a-pseudonym.png]]
=====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.
So the user account "sales" will receive email for:
*sales@domain1
*sales@domain2
*sales@domain3
So the user account "sales" will receive email for
*sales@domain4
sales@domain1
sales@domain2
sales@domain3
sales@domain4
The problem with this is that you cannot have different people using the same user account name to collect email.
The problem with this is that you cannot have different people using the same user account name to collect email.
The golden rule is never allocate unique user names to end users accounts as these will no longer be available for globalname@domain type email address usage.
The golden rule is never allocate unique user names to end users accounts as these will no longer be available for globalname@domain type email address usage.
*create your domains eg domain1, domain2, domain3, domain4 and configure those domains to use different ibays for the web content. You can even setup different groups to allow only different users to access each ibay to update web content etc.
You can even setup different groups to allow only different users to access each ibay to update web content etc.
create user accounts user9, user10, user11, user12 as needed for users who want to use the email address "accounts", but keep in mind they will use the login name user9 etc rather than accounts
*create user accounts user1, user2, user3, user4 as needed for users who want to use the email address "sales", but keep in mind they will use the login name user1 rather than sales (the login names could be johnb, johnb2, johnw, johnm etc)
create pseudonyms eg
*create user accounts user5, user6, user7, user8 as needed for users who want to use the email address "info", but keep in mind they will use the login name user5 etc rather than info
*create user accounts user9, user10, user11, user12 as needed for users who want to use the email address "accounts", but keep in mind they will use the login name user9 etc rather than accounts
accounts@domain1 which forwards to user9
*create pseudonyms eg
accounts@domain2 which forwards to user10
**sales@domain1 which forwards to user1
accounts@domain3 which forwards to user11
**sales@domain2 which forwards to user2
accounts@domain4 which forwards to user12
**sales@domain3 which forwards to user3
**sales@domain4 which forwards to user4
**info@domain1 which forwards to user5
**info@domain2 which forwards to user6
**info@domain3 which forwards to user7
**info@domain4 which forwards to user8
**accounts@domain1 which forwards to user9
**accounts@domain2 which forwards to user10
**accounts@domain3 which forwards to user11
**accounts@domain4 which forwards to user12
ie. in the pseudonyms field type the whole pseudonym name as sales@domain1
ie. in the pseudonyms field type the whole pseudonym name as sales@domain1
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'''
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.