Webmail Stopped Working

[MannyRSilva]

Hi everybody. Just joined this forum!
Just recently switched to our own server inhouse for email. Using a Mac G5 with 1GB RAM, OS X Server 10.4.3. POP mail and webmail was working well, except that now, the webmail interface is not working as it was at the beginning a few weeks ago.
When logging in via the web, users now get an error: unknown user or password incorrect.
The funny thing is, users can access the account using mail2web.com no problem.
I have tried stopping services, reconfiguring, restarting the Mac, and then starting services again but so far no luck.
Any suggestions?

Manny

 

[sourcehound]

Chaging authentication methods in the mail service settings in Server Admin can affect SquirrelMail. Double check to make sure you haven't disabled any.

Hi everybody. Just joined this forum!
Just recently switched to our own server inhouse for email. Using a Mac G5 with 1GB RAM, OS X Server 10.4.3. POP mail and webmail was working well, except that now, the webmail interface is not working as it was at the beginning a few weeks ago.
When logging in via the web, users now get an error: unknown user or password incorrect.
The funny thing is, users can access the account using mail2web.com no problem.
I have tried stopping services, reconfiguring, restarting the Mac, and then starting services again but so far no luck.
Any suggestions?

Manny

 

[Kees Buijs]

When logging in via the web, users now get an error: unknown user or password incorrect.


Any suggestions?

I also have this problem and took some time to try to fix it. Actually i got the message /data/default_pref wrong, but when that one was fixed, the username or password incorrect error occured.

The first error was solved by changing the owner / group of the data map to nobody:nobody.

The second problem was partially fixed by setting all files in the squirelmail map to nobody:nobody.

command: chown -R nobody:nobody /usr/share/squirrelmail

Also i had a bad config.php file. I copied config_default_apple.php to config.php also (and reconfigured it with ./configure).

This looks like a brute force solution, which (as i already said) solved my problem.

Now on the mailserver itself i do not get the error anymore, but on another mac in our local network we still do get the same error with safari. This problem has been there before. Users from the outside world (url/webmail) can obtain their mail (even with safari). Using mozilla firefox for OS-X works fine, even on the internal network as does PC's do.


Good Luck, Kees