I’m not sure what that middle option means but it sure seems scary…
This is an excellent video introduction to the concepts of WordPress. Pay close attention to the open source principles and references that Matt makes. Those same ideas drive everything I do at work and online.
Two of my favorite Linux projects are forking!
Mandriva -> Mageia
Mandriva is becoming Mageia. My first successful foray into the world of open source software (way back in 2002!) was made using Mandriva (called Mandrake way back then) as the operating system. At that time I was running the current version (Mandrake 9.2). I started building linux servers using MandrakeLinux 10.0. There were some rough spots in the road for those of us hosting servers with this product. Things had a nasty way of changing on us during upgrades that would bring down mission critical systems until I could figure out where the configuration files had moved to without warning. Once they changed the name to Mandriva and created a subscription based Club membership I knew that my days were numbered. I hated the thought of having to pay for the club repository so that I could install the software that I wanted. I switched to Ubuntu about three years ago and never looked back.
After following Mandriva’s various staffing decisions and financial woes it would appear that a large part of the development team has decided to fork the project. Many of the management decisions that Mandriva (the company) made over the last several years have been disastrous for the end users of Mandriva (the linux distribution). I for one am glad to see the community taking back control of this project. I am watching this project very closely, having signed up for the mailing lists and spending a good bit of time in the IRC chatroom. If this project gets off the ground I will strongly consider switching back! You can start following the project at http://mageia.org.
OpenOffice -> LibreOffice
I must admit this announcement caught me a bit by surprise:
On the morning of September 28th, a community of developers and other volunteers announced that they were forming The Document Foundation to fulfil the promise of independence written in the original OpenOffice charter. According to the group, “The Foundation will be the cornerstone of a new ecosystem where individuals and organizations can contribute to and benefit from the availability of a truly free office suite. It will generate increased competition and choice for the benefit of customers and drive innovation in the office suite market. From now on, the OpenOffice.org community will be known as ‘The Document Foundation.’”
After OpenOffice.org was organized by Sun the project got off to a good start but then stagnated. Now there is not much development and the product is falling further and further behind. After Sun was purchased by Oracle, it would appear to be falling behind even faster. All of that changes with this announcement. I hope that Oracle steps up and does the right thing by donating the name (OpenOffice.org) to the community (The Document Foundation). This would put the project in a similar arrangement to the one between The Mozilla Foundation and Firefox. I will be paying close attention to the developments of this project as well. You can follow along as well at http://www.documentfoundation.org/.
It’s a great day for freedom!
Since I had to figure out how to limit outbound traffic by domain today I thought I would post the procedure for everyone to enjoy. Listed below are the configuration changes that I made to our main postfix gateway server.
Add the following lines to /etc/postfix/master.cf. You could also copy the smtp line and rename it to something else. I use the term slow in this example.
# Outbound rate limiting
slow unix - - n - 1 smtp
Now add the following line to /etc/postfix/transport. You can rate limit as many individual domains as you wish using the transport file. Don’t forget to postmap transport when you are finished. You should also have transport_maps set in /etc/postfix/main.cf.
The last step is to add the following block of code to /etc/postfix/main.cf:
# Outbound rate limiting
slow_destination_rate_delay = 120
slow_destination_concurrency_limit = 5
slow_destination_recipient_limit = 100
slow_connection_cache_time_limit = 0
slow_never_send_ehlo = yes
slow_connect_timeout = 5
This code forces a delay of 120 seconds between connection attempts. It also forces five concurrent connections at any one time. The current postfix default is 10. I’m not sure I would go lower than three for an organization of our size. It also limits recipients to 100 per connection attempt. Don’t forget to restart the postfix daemon after making these changes!
I have been spending a good deal of time in our mailing list server archives trying to run down several permissions related problems. After doing a great deal of searching online I realized that there was no place online that listed the comprehensive required permissions for the /var/lib/mailman/archives and /var/lib/mailman/lists folders. I spent a few hours today blindly stumbling through the permissions before I got them right so I thought I would print them here for reference. This is by no means a comprehensive list of the official permissions. It is however, what is working for me.
drwxrwsr-x 50 root mailman 4.0K Jul 26 13:17 . drwxrwx--- 312 root mailman 20K Jul 29 14:04 .. drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-April -rw-rw-r-- 1 root mailman 13K Jul 29 13:35 2010-April.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-February -rw-rw-r-- 1 root mailman 8.7K Jul 29 13:35 2010-February.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-January -rw-rw-r-- 1 root mailman 21K Jul 29 13:35 2010-January.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-July -rw-rw-r-- 1 root mailman 34K Jul 29 13:35 2010-July.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-June -rw-rw-r-- 1 root mailman 25K Jul 29 13:35 2010-June.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-March -rw-rw-r-- 1 root mailman 24K Jul 29 13:35 2010-March.txt drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 2010-May -rw-rw-r-- 1 root mailman 22K Jul 29 13:35 2010-May.txt drwxrwxr-x 569 root mailman 20K Jul 29 13:35 attachments drwxrwx--- 2 root mailman 24K Jul 29 13:36 database -rw-rw-r-- 1 root mailman 38K Jul 29 13:36 index.html -rw-rw---- 1 root mailman 2.7K Jul 29 13:36 pipermail.pck
drwxrwxr-x 2 root mailman 4.0K Jul 29 13:36 . drwxrwxr-x 94 root mailman 12K Jul 29 13:36 .. -rw-rw-r-- 1 root mailman 2.5K Jul 29 13:36 002505.html -rw-rw-r-- 1 root mailman 2.2K Jul 29 13:36 002506.html -rw-rw-r-- 1 root mailman 2.5K Jul 29 13:36 002507.html -rw-rw-r-- 1 root mailman 4.4K Jul 29 13:36 author.html -rw-rw-r-- 1 root mailman 4.4K Jul 29 13:36 date.html lrwxrwxrwx 1 root mailman 11 Jul 29 13:35 index.html -> thread.html -rw-rw-r-- 1 root mailman 4.4K Jul 29 13:36 subject.html -rw-rw-r-- 1 root mailman 5.1K Jul 29 13:36 thread.html
drwxrwx--- 2 root mailman 24K Jul 29 13:36 . drwxrwxr-x 94 root mailman 12K Jul 29 13:36 .. -rw-rw---- 1 root mailman 31K Jul 29 13:36 2010-July-article -rw-rw---- 1 root mailman 4.4K Jul 29 13:36 2010-July-author -rw-rw---- 1 root mailman 3.9K Jul 29 13:36 2010-July-date -rw-rw---- 1 root mailman 4.6K Jul 29 13:36 2010-July-subject -rw-rw---- 1 root mailman 3.9K Jul 29 13:36 2010-July-thread
drwxrwsr-x 2 root mailman 4.0K Jul 29 13:17 . drwxrwsr-x 194 root mailman 12K Jul 6 21:51 .. -rw-rw---- 1 root mailman 1.7K Jul 6 21:51 admindbpreamble.html -rw-rw---- 1 root mailman 8.9K Jul 6 21:51 config.db -rw-rw---- 1 root mailman 8.9K Jul 6 21:51 config.db.last -rw-rw---- 1 apache mailman 14K Jul 29 13:17 config.pck -rw-rw---- 1 mailman mailman 14K Jul 29 00:54 config.pck.last -rw-rw---- 1 root mailman 12K Jul 27 18:42 digest.mbox -rw-rw---- 1 root mailman 189 Jul 6 21:51 handle_opts.html -rw-rw---- 1 root mailman 1.1K Jul 6 21:51 headfoot.html -rw-rw---- 1 root mailman 3.1K Jul 6 21:51 listinfo.html -rw-rw---- 1 root mailman 4.1K Jul 6 21:51 options.html -rw-rw---- 1 mailman mailman 46 Jul 29 00:54 pending.pck -rw-rw---- 1 root mailman 2 Jul 6 21:51 request.db -rw-rw---- 1 mailman mailman 13K Jul 6 21:51 request.pck -rw-rw---- 1 root mailman 1.2K Jul 6 21:51 roster.html -rw-rw---- 1 root mailman 198 Jul 6 21:51 subscribe.html
After setting these permissions the mailman server resumed normal operations. It looks like apache will take over the files that are edited directly from the web interface. That should be ok. The main problem is giving mailman read/write access to the files that it needs to update and maintain the mailing list archives. Trust me, if mailman can’t access any of these files it will move the message quietly over to the /var/spool/mailman/shunt directory. Nobody wants that. Once you resolve any permissions issues be sure to restart the mailman daemon. To remove e-mail from the shunt directory run /usr/lib/mailman/bin/unshunt.