Changes

==Frequently Asked Questions==

==Frequently Asked Questions==

Some FAQ's have separate howto's or manual entries

Some FAQ's have separate howto's or manual entries

How to Upgrade from SME 5.x and 6.x [[/sme70/sme70/Manual/UpgradeTo7 howto/UpgradeTo7]]

* How to Upgrade from SME 5.x and 6.x [[/sme70/sme70/Manual/UpgradeTo7 howto/UpgradeTo7]]

Changing password strength [[/sme70/sme70/Manual/Chapter9#h77-4 Chapter 9.1.2]]

* Changing password strength [[/sme70/sme70/Manual/Chapter9#h77-4 Chapter 9.1.2]]

Setting admin rights for users's on windows domains   [[http://smeserver.sourceforge.net/sme70/sme70/Manual/Chapter7#h75-9 Chapter 7.2.4.2]]  

* Setting admin rights for users's on windows domains [[http://smeserver.sourceforge.net/sme70/sme70/Manual/Chapter7#h75-9 Chapter 7.2.4.2]]  

   

   

1. A package that is not specific to SME Server won't have any actions to run

1. A package that is not specific to SME Server won't have any actions to run

*Note*

||??**Note**??

An upgrade for an application that has templated configuration files will likely overwrite SME Servers altered configuration files, so you need to regenerate them

An upgrade for an application that has templated configuration files will likely overwrite SME Servers altered configuration files, so you need to regenerate them||

 

2. A smeserver-application rpm may or may not use the post-upgrade and reboot twin-step.

2. A smeserver-application rpm may or may not use the post-upgrade and reboot twin-step.

Newer packages may assume you will run yum (local)install and post-upgrade

Newer packages may assume you will run yum (local)install and post-upgrade

*Note*

||??**Note**??

Contribs that are being considered for the SME Extras repository will likely not have post install scripts, and will use the post-upgrade event

Contribs that are being considered for the SME Extras repository will likely not have post install scripts, and will use the post-upgrade event||

===Email===

===Email===

**How can I add the admin user as an administrator for Horde?**

*How can I add the admin user as an administrator for Horde?*

You can set up the admin user as an administrator for Horde. This gives you the ability to view the Horde configuration via the web interface. The web interface explains what the settings are actually for. This is helpful if you are developing any of the additional horde addon modules as you can see what the configuration should look like. After figuring out the layout you can build the default templates based on that output.  

You can set up the admin user as an administrator for Horde. This gives you the ability to view the Horde configuration via the web interface. The web interface explains what the settings are actually for. This is helpful if you are developing any of the additional horde addon modules as you can see what the configuration should look like. After figuring out the layout you can build the default templates based on that output.  

By default, no user has the ability to update the default configuration files from the web interface. If you want to make a change, you can change it from the web interface, when done click on generate configuration. You will get an error stating that you could not save the backup configuration file, but the output is still displayed so you can see what the settings should be. To add this function, you will need to create a custom template. Here are the steps to take:   

By default, no user has the ability to update the default configuration files from the web interface. If you want to make a change, you can change it from the web interface, when done click on generate configuration. You will get an error stating that you could not save the backup configuration file, but the output is still displayed so you can see what the settings should be. To add this function, you will need to create a custom template. Here are the steps to take:   

This item was originally posted as [[http://bugs.contribs.org/show_bug.cgi?id=831 SME Server bug 831]]

This item was originally posted as [[http://bugs.contribs.org/show_bug.cgi?id=831 SME Server bug 831]]

   

   

*Warning*

||??**Warning**??

Do not use any other feature other than setup as you could cause damage to your installation!

Do not use any other feature other than setup as you could cause damage to your installation!||

    

    

===Client Computers===

===Client Computers===

**Samba trust relationships lost?**

*Samba trust relationships lost?*

This is a possible bug with an upgrade from SME6. After an upgrade, local workstations cannot log in. If you are experiencing this problem, please have a look at this bug for a fix, and provide followup:  

This is a possible bug with an upgrade from SME6. After an upgrade, local workstations cannot log in. If you are experiencing this problem, please have a look at this bug for a fix, and provide followup:  

[[https://sourceforge.net/tracker/index.php?func=detail&aid=1234009&group_id=96750&atid=615772]]

[[https://sourceforge.net/tracker/index.php?func=detail&aid=1234009&group_id=96750&atid=615772]]

    

    

**Windows XP Clients - Patch to logon to SME domain**

*Windows XP Clients - Patch to logon to SME domain*

This patch can be used when Windows XP clients won't be able to log on to the SME Server domain. The registry patch is located here:  

This patch can be used when Windows XP clients won't be able to log on to the SME Server domain. The registry patch is located here:  

http://servername/server-resources/regedit/winxplogon.reg

http://servername/server-resources/regedit/winxplogon.reg

Just double click on the win98pwdcache.reg file and the settings will be added to the Windows Registry.  

Just double click on the win98pwdcache.reg file and the settings will be added to the Windows Registry.  

*Note*

||??**Note**??

Although the filename seems to indicate that this patch will only work for Windows 98, but it also works in Windows 95, Windows ME and Windows 2000.

Although the filename seems to indicate that this patch will only work for Windows 98, but it also works in Windows 95, Windows ME and Windows 2000.||

   

   

**LDAP Directory Gives Errors on Outlook 2002 or Outlook 2003**

*LDAP Directory Gives Errors on Outlook 2002 or Outlook 2003*

In Outlook 2002 or 2003 when someone tries to find a contact using the LDAP server, a message stating that "Unavailable critical extension" and then a second message saying "The search could not be completed. MAPI_E_CALL_FAIL" shows up and nothing shows up from the search. The directory works beautifully in Thunderbird 1.5 as well as Outlook 2000, but not 2002 or 2003.  More information can be found here:[[http://support.microsoft.com/default.aspx?scid=kb;en-us;555536&sd=rss&spid=2559]] [[http://bugs.contribs.org/show_bug.cgi?id=1406]]

In Outlook 2002 or 2003 when someone tries to find a contact using the LDAP server, a message stating that "Unavailable critical extension" and then a second message saying "The search could not be completed. MAPI_E_CALL_FAIL" shows up and nothing shows up from the search. The directory works beautifully in Thunderbird 1.5 as well as Outlook 2000, but not 2002 or 2003.  More information can be found here:[[http://support.microsoft.com/default.aspx?scid=kb;en-us;555536&sd=rss&spid=2559]] [[http://bugs.contribs.org/show_bug.cgi?id=1406]]

  ===Firewall/Port Forwarding,Opening,Blocking===

  ===Firewall/Port Forwarding,Opening,Blocking===

   

   

**How do I configure the firewall?**

*How do I configure the firewall?*

The server manager is the GUI front end for the firewall. The firewall is modified automatically in response to changes you make in the configuration, such as enabling/disabling services, marking them public/private, forwarding ports, etc. If you wish to make changes beyond those provided for by the server manager, you can do so by providing custom templates

The server manager is the GUI front end for the firewall. The firewall is modified automatically in response to changes you make in the configuration, such as enabling/disabling services, marking them public/private, forwarding ports, etc. If you wish to make changes beyond those provided for by the server manager, you can do so by providing custom templates

**How do I allow public access to a service I've added to SME Server 7?**

*How do I allow public access to a service I've added to SME Server 7?*

The procedure has changed and is now much simpler in SME Server 7. For this example the service you have installed is called 'manta' and 'nnn' is the TCP port number that needs to be opened. Watch your capitalization with the command below:

The procedure has changed and is now much simpler in SME Server 7. For this example the service you have installed is called 'manta' and 'nnn' is the TCP port number that needs to be opened. Watch your capitalization with the command below:

    

    

It may have been, but it was not used so it is no longer included. If you do want to install it do the following:

It may have been, but it was not used so it is no longer included. If you do want to install it do the following:

*Note*

||??**Note**??

The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.

The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.||

   ##yum install mod_perl##

   ##yum install mod_perl##

To disable indexes for an ibay in SME Server 7.0 do the following:

To disable indexes for an ibay in SME Server 7.0 do the following:

*Note*

||??**Note**??

The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.

The commands on a linux shell are case-sensitive, this means that Capital is not the same as capital.||

   

   

   ##db accounts setprop //ibayname// Indexes disabled ##

   ##db accounts setprop //ibayname// Indexes disabled ##

===Log Messages===

===Log Messages===

   

   

**Log message regarding permissions on /var/spool/qpsmtpd/**

*Log message regarding permissions on /var/spool/qpsmtpd/*

You may see messages similar to this in your log file:  

You may see messages similar to this in your log file:  

   

   

    

    

They can be safely ignored. Clamav runs under a different user and needs read access to the spool area to avoid copying the file.  

They can be safely ignored. Clamav runs under a different user and needs read access to the spool area to avoid copying the file.  

[[https://sourceforge.net/tracker/index.php?func=detail&aid=1314168&group_id=96750&atid=615772]]

[[https://sourceforge.net/tracker/index.php?func=detail&aid=1314168&group_id=96750&atid=615772]]

==Known Problems==

==Known Problems==