On Mon, Jun 23, 2008 at 3:16 AM, Bernd Schreiber
<[EMAIL PROTECTED]> wrote:
>>> we have solved the problem!
>>> The history:
>>> Squirrelmail was running before a suse linux online update, but not
>>> after
>>> it.
>>> The message of the Squirrelmail configtest after the update was:
>>> ERROR: Data
>> we have solved the problem!
>> The history:
>> Squirrelmail was running before a suse linux online update, but not
>> after
>> it.
>> The message of the Squirrelmail configtest after the update was:
>> ERROR: Data dir (/var/spool/squirrelmail/data/) does not exist!
>>
>> This error message is wr
Hallo, Bernd,
Du (schreiber) meintest am 20.06.08:
> Squirrelmail was running before a suse linux online update, but not
> after it.
> The message of the Squirrelmail configtest after the update was:
> ERROR: Data dir (/var/spool/squirrelmail/data/) does not exist!
> This error message is wrong.
> we have solved the problem!
> The history:
> Squirrelmail was running before a suse linux online update, but not after
> it.
> The message of the Squirrelmail configtest after the update was:
> ERROR: Data dir (/var/spool/squirrelmail/data/) does not exist!
>
> This error message is wrong. The Da
Hello,
we have solved the problem!
The history:
Squirrelmail was running before a suse linux online update, but not after
it.
The message of the Squirrelmail configtest after the update was:
ERROR: Data dir (/var/spool/squirrelmail/data/) does not exist!
This error message is wrong. The Data di
On Thu, Jun 19, 2008 at 11:52 PM, Ivars Strazdiņš
<[EMAIL PROTECTED]> wrote:
> Paul Lesniewski wrote:
> of course, I have checked the permissions of
> /var/spool/squirrelmail/data/ directory.
> Yesterday I set the permissions from /var/spool/squirrelmail/data/
> to 777 to test it. T
Paul Lesniewski wrote:
of course, I have checked the permissions of
/var/spool/squirrelmail/data/ directory.
Yesterday I set the permissions from /var/spool/squirrelmail/data/
to 777 to test it. The same error.
This problem is not easy to solve.
>>> What are t
On Thu, Jun 19, 2008 at 4:44 AM, Fredrik Jervfors
<[EMAIL PROTECTED]> wrote:
> This thread is a mess and hard to follow. Please comply to the list rules
> and don't top-post. In-line (or bottom-posted) replies are much preferred.
> Also trim irrelevant things, such as footers, when replying.
>
> Po
>>> of course, I have checked the permissions of
>>> /var/spool/squirrelmail/data/ directory.
>>> Yesterday I set the permissions from /var/spool/squirrelmail/data/
>>> to 777 to test it. The same error.
>>> This problem is not easy to solve.
>>
>> What are the permissions on the files inside it?
On Thu, 2008-06-19 at 13:44 +0200, Fredrik Jervfors wrote:
> This thread is a mess and hard to follow. Please comply to the list rules
> and don't top-post. In-line (or bottom-posted) replies are much preferred.
> Also trim irrelevant things, such as footers, when replying.
>
I think , you too h
This thread is a mess and hard to follow. Please comply to the list rules
and don't top-post. In-line (or bottom-posted) replies are much preferred.
Also trim irrelevant things, such as footers, when replying.
Posting guidelines: http://squirrelmail.org/postingguidelines
I have just inst
Hallo, Bernd,
Du (schreiber) meintest am 19.06.08:
>>> Could not create initial preference file!
>>> /var/spool/squirrelmail/data/ should be writable by user httpd
>> "user httpd" seems to be wrong.
> I couldn't find in any configuration file a user httpd. I think the
> user httpd is the owner
Hello Paul,
I have now copied the file 'default_pref' from
/srv/www/htdocs/squirrelmail/data/default_pref to
/var/spool/squirrelmail/data .
ls -lisa /var/spool/squirrelmail/data/default_pref
82081 4 -rw-r--r-- 1 wwwrun www 48 Jun 19 10:57 default_pref
ls -lisa /srv/www/htdocs/squirrelmail/data/d
Hello Helmut,
you wrote
>> 2. Squirrelmail login:
>> Error opening ../data/default_pref
>> Could not create initial preference file!
>> /var/spool/squirrelmail/data/ should be writable by user httpd
>
> "user httpd" seems to be wrong.
>
I couldn't find in any configuration file a user httpd. I t
Bernd Schreiber wrote:
> Hello,
>
> The ownership of the Apache hasn't changed after Suse upgrade:
>
> s1:/var/spool # ps -ef|grep httpd
> root5514 1 0 Jun18 ? 00:00:00 /usr/sbin/httpd2-prefork -f
> /etc/apache2/httpd.conf
> wwwrun 5515 5514 0 Jun18 ? 00:00:00 /usr/sbin/httpd2-prefo
Hallo, Bernd,
Du (schreiber) meintest am 19.06.08:
> The ownership of the Apache hasn't changed after Suse upgrade:
> cat /etc/apache2/uid.conf
> User wwwrun
> Group www
> The permissions of the following directories are also the
> same as before:
> s1:/var/spool/squirrelmail # ls -lisa
> total
Hallo, Bernd,
Du (schreiber) meintest am 18.06.08:
> Checking paths...
> ERROR: Data dir (/var/spool/squirrelmail/data/) does not exist!
> 2. Squirrelmail login:
> Error opening ../data/default_pref
> Could not create initial preference file!
> /var/spool/squirrelmail/data/ should be writa
Hello,
The ownership of the Apache hasn't changed after Suse upgrade:
s1:/var/spool # ps -ef|grep httpd
root5514 1 0 Jun18 ? 00:00:00 /usr/sbin/httpd2-prefork -f
/etc/apache2/httpd.conf
wwwrun 5515 5514 0 Jun18 ? 00:00:00 /usr/sbin/httpd2-prefork -f
/etc/apache2/httpd.conf
wwwrun 5
Paul Lesniewski wrote:
I have just installed Squirrelmail 1.4.15.
The errors are the same.
1. Squirrelmail configtest said:
SquirrelMail version:1.4.15
Config file version: 1.4.0
Config file last modified: 18 June 2008 14:38:34
Checking PH
Don't top-post, thanks. Please read the mailing list posting
guidelines more carefully if you have any doubts.
>>> I have just installed Squirrelmail 1.4.15.
>>>
>>> The errors are the same.
>>>
>>> 1. Squirrelmail configtest said:
>>>
>>> SquirrelMail version:1.4.15
>>> Config file versi
Hi,
of course, I have checked the permissions of
/var/spool/squirrelmail/data/ directory.
Yesterday I set the permissions from /var/spool/squirrelmail/data/
to 777 to test it. The same error.
This problem is not easy to solve.
Bernd
> Hi Bernd,
>
>> I have just installed Squirrelmail 1.4.15.
>
Hello,
I have just upgraded to Squirrelmail 1.4.15.
The errors are the same.
1. Squirrelmail configtest:
SquirrelMail version: 1.4.15
Config file version:1.4.0
Config file last modified: 18 June 2008 14:38:34
Checking PHP configuration...
PHP version 5.2.5 OK.
display_errors:
Hi Bernd,
> I have just installed Squirrelmail 1.4.15.
>
> The errors are the same.
>
> 1. Squirrelmail configtest said:
>
> SquirrelMail version: 1.4.15
> Config file version: 1.4.0
> Config file last modified:18 June 2008 14:38:34
> Checking PHP configuration...
> PHP version 5.2.5 OK.
Hello Chris,
I have just installed Squirrelmail 1.4.15.
The errors are the same.
1. Squirrelmail configtest said:
SquirrelMail version: 1.4.15
Config file version:1.4.0
Config file last modified: 18 June 2008 14:38:34
Checking PHP configuration...
PHP version 5.2.5 OK.
displa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Bernd Schreiber wrote:
| Hello,
|
| my Squirrelmail worked fine with Suse Linux 9.3. PHP 4, Imap, Postfix
| and Appache. After an online update of Suse Linux 9.3 with upgrade
| from PHP 4 to PHP 5 I got the following errors:
|
| 1. Squirrelmail configt
Hi Bernd,
> my Squirrelmail worked fine with Suse Linux 9.3. PHP 4, Imap, Postfix
> and Appache. After an online update of Suse Linux 9.3 with upgrade
> from PHP 4 to PHP 5 I got the following errors:
>
> 1. Squirrelmail configtest said:
> SquirrelMail version: 1.4.10a
> Config file version: 1.4.
Hello,
my Squirrelmail worked fine with Suse Linux 9.3. PHP 4, Imap, Postfix
and Appache. After an online update of Suse Linux 9.3 with upgrade
from PHP 4 to PHP 5 I got the following errors:
1. Squirrelmail configtest said:
SquirrelMail version: 1.4.10a
Config file version:1.4.0
Config fil
27 matches
Mail list logo
