error in installing psa-atmail

[zeki]

hello
when i install psa-atmail i get this:

PHP Warning: fopen(): Unable to access /etc/psa/webmail/atmail/.atmail.shadow in /var/www/atmail/libs/Atmail/Config.php on line 4
PHP Warning: fopen(/etc/psa/webmail/atmail/.atmail.shadow): failed to open stream: No such file or directory in /var/www/atmail/libs/Atmail/Config.php on line 4


i have plesk 9.01 on c4.7
on plesk i only can choose horde.

anyone other have the problem, too?

thanks
zek

[scott]

Oh wow, yeah thanks for the report on that! I'll check it out, that might be something that is created by the older psa-atmail rpm.

[freethought]

Scott, sorry to drag up an old thread, but I've just installed psa-atmail 1.03 from the ART repo on CentOS 5.3 x86_64 and I'm getting the same error

There is no atmail database or user created in MySQL and creating a blank /etc/psa/webmail/atmail/.atmail.shadow file before installing the RPM doesn't help.

Downloading Packages:
psa-atmail-1.03-2.el5.art.noarch.rpm | 1.9 MB 00:02
Running rpm_check_debug
Running Transaction Test
Finished Transaction Test
Transaction Test Succeeded
Running Transaction
Installing : psa-atmail [1/1]
PHP Warning: fopen(): Unable to access /etc/psa/webmail/atmail/.atmail.shadow in /var/www/atmail/libs/Atmail/Config.php on line 4
PHP Warning: fopen(/etc/psa/webmail/atmail/.atmail.shadow): failed to open stream: No such file or directory in /var/www/atmail/libs/Atmail/Config.php on line 4

Installed: psa-atmail.noarch 1:1.03-2.el5.art
Complete!

[freethought]

Just thought I'd let everyone know how I fixed this.

It seems that the ART RPM expects the @mail database to already exist in MySQL. However, if (like me) you install Plesk 9 from the ART PSA yum repository, it uses the newer 1.03 RPM in the ART channel for the initial installation.

The solution to this was to manually install the 1.02 RPM from the PSA channel (http://www4.atomicorp.com/channels/ples ... noarch.rpm in my case) and then update to 1.03 normally via yum. This way, the database already exists in MySQL and the shadow file has been created with the login details.