On Mon, 2004-06-07 at 20:08 -0400, David Malcolm wrote:
On Mon, 2004-06-07 at 18:53 -0500, Mike Chambers wrote:
> On Mon, 2004-06-07 at 18:10 -0500, Mike Chambers wrote:
>
> > Seems since installing this version (along with updates from rawhide),
> > while retreiving emails via POP on my local network, they are EXTREMELY
> > slowwwwwwwwwwwwwwwwwwwwwwwwww, and this is a 100M network, as they were
> > fast before this version.
>
> Well, first I watched the emails come through and saw in the bottom left
> corner that junk was being checked and that seemed to go real slow,
> possibly holding up the emails. So I turned the checking for junk
> emails off and, voila, that solved the problem. I am not sure how it
> determines junk to begin with as it seemed to let some of the emails to
(It's running spamassassin on your client machine)
> keep coming through (although a few were being sent to the junk folder),
> so no biggie to turning it off (I run spamassassin on my server anyway).
Wondered why it was installed as a dependency when upgrading to
evolution-1.5.9.1-2...
[root@radar0 root]# rpm -q --redhatrequires spamassassin
no package requires spamassassin
[root@radar0 root]# yum remove spamassassin
Gathering header information file(s) from server(s)
Server: Evolution Devel Snaps
Server:
macromedia.mplug.org - Flash Plugin
Server: Fedora Core 2 - i386 - Base OS
Server: Fedora Core 2 updates
Finding updated packages
Downloading needed headers
Resolving dependencies
..Dependencies resolved
I will do the following:
[erase: spamassassin 2.63-8.i386]
I will erase these to satisfy the dependencies:
[deps: evolution-devel 1.5.9.1-2.i386]
[deps: evolution 1.5.9.1-2.i386]
Is this ok [y/N]: n
Exiting on user command.
[root@radar0 root]# service spamassassin status
spamd (pid 25404) is running...
[root@radar0 root]# chkconfig --list spamassassin
spamassassin 0:off 1:off 2:on 3:on 4:on 5:on 6:off
[root@radar0 root]# grep -E "(evolution|spamassassin)" /var/log/yum.log*
/var/log/yum.log:04/02/04 09:12:41 Erased: evolution-devel 1.4.5-7.i386
/var/log/yum.log:05/27/04 14:52:45 Erased: evolution 1.4.5-7.i386
/var/log/yum.log:05/27/04 14:52:45 Erased: evolution-devel 1.4.5-7.i386
/var/log/yum.log:05/27/04 16:33:38 Installed: evolution 1.5.8-2.i386
/var/log/yum.log:05/27/04 16:33:38 Installed: evolution-devel 1.5.8-2.i386
/var/log/yum.log:05/27/04 16:33:38 Dep Installed: evolution-data-server 0.0.93-3.i386
/var/log/yum.log:06/04/04 09:25:20 Installed: evolution-data-server-debuginfo
0.0.93-3.i386
/var/log/yum.log:06/04/04 09:25:20 Installed: evolution-debuginfo 1.5.8-2.i386
/var/log/yum.log:06/08/04 08:34:10 Dep Installed: spamassassin 2.63-8.i386
/var/log/yum.log:06/08/04 08:34:10 Updated: evolution-data-server-debuginfo 0.0.94-2.i386
/var/log/yum.log:06/08/04 08:34:10 Updated: evolution 1.5.9.1-2.i386
/var/log/yum.log:06/08/04 08:34:10 Updated: evolution-data-server 0.0.94-2.i386
/var/log/yum.log:06/08/04 08:34:10 Updated: evolution-devel 1.5.9.1-2.i386
/var/log/yum.log:06/08/04 08:34:10 Updated: evolution-debuginfo 1.5.9.1-2.i386
[root@radar0 root]#
So, why does evolution now require (and apparently start/run)
spamassassin on the client machine?
Phil