SquirrelMail error opening default_pref

[sneader]

I have a user that can use Horde and NeoMail, but he prefers SquirrelMail. However, when he logs in and clicks SquirrelMail, he gets:

ERROR
Error opening ../data/default_pref
Default preference file not found or not readable!
Please contact your system administrator and report this error.

This is only happening for one customer. I've deleted and recreated their mailbox, and run the fixmailbox thing and still no go. Any leads?

I am trying to find where the data/default_pref file is located, but not finding it where the SquirrelMail site suggests it should be (/etc).

Sorry for the newbie question! Thanks in advance for your help.

- Scott

 

[dholden]

For me the file is in smdata, you may need to a chmod 777 on the file.

- Dean

 

[sneader]

(embarrassed) -- where did you find smdata?

 

[Slav]

I noticed this in the edge reelase i think its not done right as i had thre same issue, i at the end went back to last stable reelase.

 

[rpmws]

same problem here on a couple boxes on edge builds

 

[Slav]

there is also a issue with horde too. where you seelctt he language andd then it logs you back to where you were and it just loops.

 

[Slav]

one thing i noticed that after you got o edge, some mailboxes get lost and reset to zero.

 

[groefie]

The same problem here with the edge build

I'm using the edge because it's the only build that has fixed the problem with terminating an account in whm on fedora.

 

[dgbaker]

Quick fix for this.

In SSH as root:

cd /usr/local/cpanel/base/3rdparty/squirrelmail
mkdir data
cd data
vi default_pref
#Add the following to the file
full_name=
reply_to=
show_html_default=0
sort=0
#Save and exit

The error should now be gone.

 

[groefie]

Thanks! That works fine :D

 

[GOT]

Edge had (IMO) a very important fix in that they eliminated the need for the data directory. It appears that they missed something along the way, as I had this problem on one of my servers today.

A simple /scripts/upcp --force resolved this issue for me, and might be better than creating a directory that cpanel intentionally got rid of.

 

[dgbaker]

That's a very good point. Which Edge level corrected it for you?

 

[GOT]

According to the change log, for build 51:

Eliminate the need for /usr/local/cpanel/base/3rdparty/squirrelmail/data

I just did the fix today, so that is the one that 'fixed' it.

 

[dgbaker]

That's wierd cause the reason I ask is that on Edge 78 this was an issue for us as well.

 

[GOT]

That is why I had to use the force flag.

 

[rpmws]

That's wierd cause the reason I ask is that on Edge 78 this was an issue for us as well.

hey dq ..i was bit by this as well so I made that data folder and pref file. Fixed my problem. Then I forced an upcp and the data folder is gone now ..but the problem is still fixed. So it must have been an incomplete edge build we got.

Force upcp and I think you will find you are ok.

 

[dgbaker]

Well, not with this one server. I'll have to look a little further. Thanks.

 

[dgbaker]

Just as an FYI, if the upcp --force does not work, just do the following

cd /usr/local/cpanel/base
rm -Rf sqmail* squirrelmail
cd /scripts/
upcp --force

That was the final way for one of our servers.

 

[GOT]

Gutsy call!

 

[sneader]

In SSH as root:

cd /usr/local/cpanel/base/3rdparty/squirrelmail
mkdir data
cd data
vi default_pref
#Add the following to the file
full_name=
reply_to=
show_html_default=0
sort=0
#Save and exit

The error should now be gone.

Thanks dgbaker -- worked for me !!!

- Scott