Month: January 2005
-
SpamAssassin Upgrade
—
by
After testing the latest version of Spamassassin on my account for the past few days, I have upgraded all our Spamassassin servers from 3.0.0 to 3.0.2. 3.0.2 includes a few bug fixes and other small enhancements. If anyone notices a drastic change in spam checking effectiveness, please let me know.
-
Squid on Fedora Core 3
—
by
Due to the way SELINUX is setup on Fedora Core 3 ( FC3 ) I discovered that if you try to move squid’s cache directory, you must tell SELINUX that the new location is ok. To do that, use the following command: chcon -R system_u:object_r:squid_cache_t /directory/where/cache-is
-
Learned Something New
—
by
As anyone who as worked with Linux, iptables, and ftp knows, firewalls and ftp can cause issues. I already knew that if I was using iptables I should use the ip_conntrack_ftp kernel module. So I had added “insmod ip_conntrack_ftp” to the /etc/rc.local file so it was inserted at boot. However what I didn’t think about…
-
Spamassassin 3.02
—
by
Spamassassin 3.02 was released last month. Not much new in there but in an attempt to always run the latest and greatest stable spamassassin code, I have upgraded a test server and am using it on my account. If all goes well, I will upgrade the rest of the servers to the newest version soon.
-
Charter blocking port 25
—
by
This is only a rumor, but I heard that last week Charted started blocking port 25 for home users on their Cable internet service in Mankato. This will probably cause a few problems for our users but there are ways of working around it securely. So all in all, this is a good thing.
-
Campus Network Outage
—
by
FYI, in case you didn’t notice, at about 10:35am today our core network router rebooted. That caused all network traffic on our network to temporarily stop flowing.
-
Rebooting Solen
—
by
Although solen has been workin great for the past 180+ days, it looks like we have no choice but to reboot it. If you are wondering why, the reason is that netatalk has stoped working. Restarting the netatalk daemon does not appear to fix it. For some reason the afpd process just gets stuck. Hopefully…
-
Res-Hall Network Flakeyness
—
by
Last night our res-hall network was extremely slow and flakey. There appeared to be lots of broadcast traffic and pings were timing out 80% of the time. After disconecting one dorm at a time, I discoverd that one dorm was causing the problem. I eventually traced it back to one network jack. Still not sure…