Category: GAC IT
-
Spamassassin server died
—
by
One of our two spamassassin servers stopped working Saturday at about 9:00am and was not fixed until 8:00am Sunday morning. During that time about half of all email being sent to spamassassin was not being checked and was just delivered instead. So you probably saw a big rise in spam in the past 24 hours.…
-
Internet Bandwith Increase
—
by
As of about 6:00pm tonight, our internet bandwith has doubled from 10M to 20M. It’s probably maxed out by the time I finish typing this, but oh well. Was good while it lasted 🙂
-
Solen rebooted
—
by
In case you noticed everything screetching to a halt tonight around 7pm, solen had a kernel panic and had to be rebooted. About 20 minutes later, it was back up and running again.
-
International Building now at a gig
—
by
The network connection for the International center bas been bumped up from 100Mbit/s to 1000Mbit/s as of about 11:30am this morning. Hope that makes some things a little bit faster.
-
SpamAssassin and Horde’s IMP
—
by
Unfortunately due to the way that Horde’s IMP webmail system inserts the IP address that was used to connect to the it in the email headers it sends, SpamAssassin thinks those messages are coming from dynamic ip addresses. To help work around this issue, I modified our SpamAssassin rules such that any email sent via…
-
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.
-
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.
-
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…
-
Spamassassin
—
by
For some reason early this morning an email that was passed to spamassassin appears to have caused all of our spamd processes to lock up. Therefore email was not being checked for spam. This means you probably all got way more spam today that normal. Sorry about that. I have never seen spamassassin lock up…