If you try to receive big e-mails with attachements you can get a timeout like:

Fatal error: Maximum execution time of 60 seconds exceeded in  c:\web\moregroupware\modules\webmail2\inc\class.pop3.inc on line 418
Fatal error: Maximum execution time of 60 seconds exceeded in c:\web\moregroupware\modules\webmail2\inc\pear.php on line 498

One dirty way to fix it is to edit /modules/webmail2/inc/class.pop3.inc. Around line 14 you should find

var $TIMEOUT    = 60; // Default timeout before giving up on a network operation.

If you change from e. g. 60 to 260 you should not so easily get the timeout.

if you see memory error messages like:

Fatal error: Allowed memory size of 8388608 bytes exhauste (tried to allocate 8192 bytes) in ...

This happens because the webmail2 module downloads email from the mail server. These email can only be downloaded in one step, that means the whole email is copied to the memory and then stored on your harddisk. e.g. an email with the size of 5 MB needs about 10-15 MB in the memory.

To fix it you have to increase the memory limit in php.ini:

memory_limit = 8M ; Maximum amount of memory a script may consume (8MB)

Increase this value to '16M' (16 MB) or more (depends on the size of the emails you get, often there is a limit on the mail server [e.g 10 MB for gmx]).

If you have problems with sending and/or receiving emails with large attachments you should try to increase the values for 'post_max_size' and 'upload_max_filesize' in php.ini. Set them to a value high enough, e.g. '20M'.

Check php.ini and the parameters below as mentioned earlier in this guide:

include_path = "."
register_globals = Off
session.auto_start = Off

While you are editing php.ini anyway, you might want to change some more things:

display_errors = Off
error_reporting = E_ALL ~ E_NOTICE
log_errors = On
error_log = /var/log/php.log

(make sure Apache has the rights to write to this file). This will make all erros and warnings go to a log file instead of to the screen, which solves a lot of problems already, and makes it easier to work on the remaining ones.

Login screen in stead of the data you expected: Internet Explorer 6 can behave strange together with more.groupware. Some times I have had good results with erasing temporary files from my computer. After such a clean up everything often works fine for a while.

If you get problems with the graphics, login screen in stead of that you expected etc. a solution can be to change the following line in config.inc.php:

$appconf["rooturl"] = "http://localhost/moregroupware"; 

to look like this:

$appconf["rooturl"]="http://".$HTTP_SERVER_VARS["HTTP_HOST"]."/moregroupware"; 

Wrong URL in config.inc.php: You install more.groupware, log in and everything is ok. Another person on your network tries to login and doesn't see the right layout at the login screen (and login fails).

Solution: Go to the home directory of mgw, take a look at config.inc.php. Look for the variables:

$appconf["rooturl"] = ...
$appconf["rootpath"] = ...

If $appconf["rooturl"] is something like http://localhost/moregroupware/ or http://127.0.0.1/moregroupware/ you have to replace localhost or 127.0.0.1 with your real IP address that is reachable from other computers in the net.

A solution can also be to change from:

$appconf["rooturl"] = "http://localhost/moregroupware";

to

$appconf["rooturl"]="http://".$_SERVER["HTTP_HOST"]."/moregroupware";