Topic: Broken Webmail after yum update SME6.0.1

[edb]

I was previously running Horde 3 and since running the yum update to fix the DST issue my webmail no longer works after the update.

It now displays a blank page when going to https://www.xyz.com/webmail
no login box just blank page.

Here is a log of what was updated by yum:
03/09/07 10:56:33 Updated: cyrus-sasl-md5.i386
03/09/07 10:56:33 Updated: perl-CGI-FormMagick.noarch
03/09/07 10:56:33 Updated: cyrus-sasl.i386
03/09/07 10:56:33 Updated: squid.i386
03/09/07 10:56:33 Updated: glibc-common.i386
03/09/07 10:56:33 Updated: samba-client.i386
03/09/07 10:56:33 Updated: e-smith-dnscache.noarch
03/09/07 10:56:33 Updated: perl-DB_File.i386
03/09/07 10:56:33 Updated: imp.noarch
03/09/07 10:56:33 Updated: sudo.i386
03/09/07 10:56:33 Updated: e-smith-horde.noarch
03/09/07 10:56:33 Updated: cvs.i386
03/09/07 10:56:33 Updated: tar.i386
03/09/07 10:56:33 Updated: e-smith-apache.noarch
03/09/07 10:56:33 Updated: krb5-libs.i386
03/09/07 10:56:33 Updated: glibc.i386
03/09/07 10:56:33 Updated: libtool-libs.i386
03/09/07 10:56:33 Updated: e-smith-qmail.noarch
03/09/07 10:56:33 Updated: unzip.i386
03/09/07 10:56:33 Updated: rp-pppoe.i386
03/09/07 10:56:33 Updated: bzip2.i386
03/09/07 10:56:33 Updated: e-smith-base.noarch
03/09/07 10:56:33 Updated: gzip.i386
03/09/07 10:56:33 Updated: util-linux.i386
03/09/07 10:56:33 Updated: pcre.i386
03/09/07 10:56:33 Updated: e-smith-tinydns.noarch
03/09/07 10:56:33 Updated: samba-common.i386
03/09/07 10:56:33 Updated: e-smith-imap.noarch
03/09/07 10:56:33 Updated: mc.i386
03/09/07 10:56:33 Updated: perl-NDBM_File.i386
03/09/07 10:56:33 Updated: e-smith-lilo.noarch
03/09/07 10:56:33 Updated: e-smith-hosts.noarch
03/09/07 10:56:33 Updated: perl-CPAN.i386
03/09/07 10:56:33 Updated: e-smith-openssh.noarch
03/09/07 10:56:33 Updated: samba.i386
03/09/07 10:56:33 Updated: e-smith-proxy.noarch
03/09/07 10:56:33 Updated: shadow-utils.i386
03/09/07 10:56:33 Updated: e-smith-email.noarch
03/09/07 10:56:33 Updated: stunnel.i386
03/09/07 10:56:33 Updated: perl-DBI.i386
03/09/07 10:56:33 Updated: e-smith-mailfront.noarch
03/09/07 10:56:33 Updated: perl-suidperl.i386
03/09/07 10:56:33 Updated: e-smith-flexbackup.noarch
03/09/07 10:56:33 Updated: e-smith-backup.noarch
03/09/07 10:56:33 Updated: e-smith-proftpd.noarch
03/09/07 10:56:33 Updated: turba.noarch
03/09/07 10:56:33 Updated: mount.i386
03/09/07 10:56:33 Updated: e-smith-turba.noarch
03/09/07 10:56:33 Updated: yum.noarch
03/09/07 10:56:33 Updated: bzip2-libs.i386
03/09/07 10:56:33 Updated: e-smith-LPRng.noarch
03/09/07 10:56:33 Updated: e-smith-lib.noarch
03/09/07 10:56:33 Updated: lynx.i386
03/09/07 10:56:33 Updated: horde.noarch
03/09/07 10:56:33 Updated: losetup.i386
03/09/07 10:56:33 Updated: e-smith-packetfilter.noarch
03/09/07 10:56:33 Updated: perl.i386
03/09/07 10:56:33 Updated: e-smith-ldap.noarch
03/09/07 10:56:33 Updated: flexbackup.noarch
03/09/07 10:56:33 Updated: e-smith-samba.noarch

Any help appreciated.

[bpivk]

Bugtracker is your friend.
Please report this issue to the bugtracker.

[edb]

Bugtracker is your friend.
Please report this issue to the bugtracker.

Yes, I know it is, but I'm not sure that it's a bug.
I'm sure others that are still running SME 6x have run into this as well.

[bpivk]

Post it as a bug.

[edb]

I just restored the /home/httpd/html/horde directory from backup and it is working fine now.

As per http://forums.contribs.org/index.php?topic=34290.0 this post indicates that the main section of yum.conf should have this added "exclude=horde imp turba e-smith-horde e-smith-imp e-smith-turba" so that these are not updated.

But anyway, a restore of the "horde" directory also seems to work fine at least in my case.

Later ...

[byte]

I'm sure others that are still running SME 6x have run into this as well.

I would have thought many would have updated to SME 7 by now as SME 6x has been obsolete and no updates been made since end of dec 06.

[edb]

I guess I was wrong thinking all was well.

Turns out that the webmail appears to be fixed as far as logging in and seeing everything but my email does not appear to be going out of the remote queue. I can send and receive fine locally and I can receive external emails but cannot send external emails.

Don't know what happened with that update but has anyone seen this before? There maybe a simple fix which is what I'm hoping for.
Darn thing just won't send email externally.

I tried disabling SA but still no go.

__________________________

BTW

Yes, I'm slow in upgrading due to the fact that I wanted to see SME 7x become stable and to see if all the contribs from SME6x are available.

Nothing worse than switching only to find that some things are not available yet.

Anyway, it may be getting close to switching time but I have been reserved in doing so mainly because of my Ecommerce website.
I remember way back when it took a ot of fiddling to get it working on SME and I just can't aford to have the site down for more than a few hours.

[bpivk]

Next time use vmware and install a new version of SME on it and then you'll know exactly what you have to do to get it working on the new version.

[edb]

Thanks for the tip...

I don't know anything about VMware, although I hear it metioned here all the time. It sounded to me like you had to be a guru to use it.
Is it used in live production situations or just for testing?
Will it install on a Windows 2000 box? Enlighten me please.

[bpivk]

Go to vmware and check up on it.
It is used to emulate another computer on your existing OS. I use it to test different OS.

[edb]

Do you use the free server version?

[bpivk]

Well i didn't use vmware for a long time so i don't know what people use now.  
I had vmware workstation (or smething similar).

[edb]

Ok, I got it fixed finally.

Here is what I had to do:

1) mysql

2) use mysql

3) UPDATE user SET Password=OLD_PASSWORD('horde') WHERE User='horde';

4) FLUSH PRIVILEGES;

I thought I remembered having to do this once before so I did a search on my own previous contribs posts and low & behold I found one of my old posts which was my answer. It has something to do with the way the newer MySQL version handles passwords.