Antivirus Gateway Problems III

All attempts to get the antivirus gateway to process messages faster have failed. Network Associates, the maker of the product, stated that the theoretical limit of throughput for the software was 5-10000 messages per hour, if no messages are infected, and if no other filtering was being done. They were unable to say exactly what was causing what we’re seeing.
Continue reading

MX record change

The MX record on DNS zones was changed to and in an effort to normalize the naming convention for our mail exchange servers. This change resulted in some mail delivery problems since not also external mail servers picked up the change in a timely manner. A workaround was implemented to allow mail delivery to continue. Mail messages sent between 10:00am and 11:45am (-8:00 PST) seem to have been effected.

Internet Connection Down April 27 – entry I

Most of the campus is experiencing internet connection failure. This is due to a major outage in Seattle (information from Electric Lightwave, the University’s Internet Service Provider). Some areas of campus apparently have an internet connection, so the problem is due to improper routing information across our section of the internet.

No ETA as to the return of service as yet.

Possible WebMail problem identified

In our efforts to identify the cause of recent problems with the WebMail server, we have been at a loss for information. We have tried to discover what has been causing the delays and unresponsiveness in WebMail as of late. We have looked at possible memory leaks in daemons, possible attacks, possible miss configurations. All of these have not lead to a clear answer.

It is believed at this point in time that if Ockham’s Razor holds true we may have found the source of the problem. It was discovered late yesterday that the available disk space of the WebMail server was extremely low. Since WebMail serves as an imap gateway temporarily caching and displaying mail messages via a http server, disk space for temporary files is necessary. This has been the best possible explanation for the problems we have seen thus far.

We have increased available disk space on the server. We have also contacted server individuals who reported problems to determine if the issue still persists.