Pritty pics
Dec. 22nd, 2006 12:17 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
trixtahMy mail server is chugging along v. happily, and is rejecting 67% of attempted connections, now that I've added a rule to stop it from sending from people who purport to be from our domain. We can do this because it's a gateway server and doesn't have any mailboxes on it. If people are sending from user@local_domain to user@local_domain, they will be on our local network, and Postfix knows which networks they are. For the rare occasions that messages will be coming from an external network, but from a $local_domain sender, they will be forced to authenticate first.
Isn't it pretty? I hope to be able to get the bottom graph a bit more informative, once I figure out how to integrate the IMSS virus/spam log into this Mailgraph tool.
Also, let me tell you, getting Mailgraph to work on RedHat Linux is a pain in the butt, due to SELinux. While I have a procedure, it's pretty hit-and miss, and requires reapplying security contexts and restarting services virtually at random until it just suddenly springs into action. I'd like to get it installed consistently. The new version of RedHat coming up is supposed to be much better in terms of SELinux configuration. It could hardly be worse.
ETA: By the way, this server has a ways to catch up before it hits the processing level that our current primary and secondary servers are handling. Between them, they're processing about a million messages a month. This one, if we count the rejected messages as well, will only get up to around 200,000 a month, at the current rate.
Isn't it pretty? I hope to be able to get the bottom graph a bit more informative, once I figure out how to integrate the IMSS virus/spam log into this Mailgraph tool.
Also, let me tell you, getting Mailgraph to work on RedHat Linux is a pain in the butt, due to SELinux. While I have a procedure, it's pretty hit-and miss, and requires reapplying security contexts and restarting services virtually at random until it just suddenly springs into action. I'd like to get it installed consistently. The new version of RedHat coming up is supposed to be much better in terms of SELinux configuration. It could hardly be worse.
ETA: By the way, this server has a ways to catch up before it hits the processing level that our current primary and secondary servers are handling. Between them, they're processing about a million messages a month. This one, if we count the rejected messages as well, will only get up to around 200,000 a month, at the current rate.
