Drew's Blog

I recently had the experience of setting up Postfix. It works really well, in my opinion; however, setting it up wasn’t the simplest for what I wanted. But, at least it was simpler than sendmail

Reading through several articles on the Internet, everyone was giving steps on how to setup postfix to handle e-mail for any FQDN (Fully-Qualified Domain Name). Well, we don’t want to be handling someone else’s e-mail, so we decided to set it up with authentication. All of the guides on setting up Postfix with SASL authentication are great and all; however, they don’t address the issue of, what if you want to receive mail as well. That’s a simple fix, but moreover, what if you have a service like mailman running? Mailman isn’t easily configured to authenticate against the SMTP server to send mail. So, the following are the configurations that I’ve come up with to solve all of these problems:

For the file /etc/postfix/main.cf

Now keep in mind, your values for some of the above WILL be different. This configuration is on a machine that’s running mailman as well (thus the /etc/mailman/aliases file).

And lastly, for SASL auth, edit the file: /usr/lib64/sasl2/smtpd.conf

Your lib64 directory may just be lib, depending on the architecture of your box. All of these edits were made a 64-bit Fedora 12 machine, but they should work for every machine.

And last note. After all of the edits have been made, make sure to restart postfix and restart saslauthd with the following:

/etc/init.d/postfix restart
/etc/init.d/saslauthd restart

For questions on what some of the postfix settings mean, you can check out one of the following:

postconf man-page by running “man postconf” or visit http://www.postfix.org/postconf.5.html

Postfix Documentation at: http://www.postfix.org/documentation.html

Postfix HowTo’s at: http://www.postfix.org/docs.html

Postfix is definition the easiest MTA I’ve ever had the pleasure of working with, as far as configuration goes. I hope this helps

Well, I’m working on installing Forefront Client Security at my work and after configuring all of the prerequisites, nobody could figure out why it wasn’t installing. So, I setup a test machine and started playing with it. After about an hour of searching google, it seems nobody really has an answer for why MOM fails to install… but, I just figured it out!

If you check the installation logs in C:\Program Files\Microsoft Forefront\Client Security\Logs\MOMDB.log, you should notice there’s a line in there about an error running a query that results in an ERROR 112. The error is something like “There is not enough space on disk.” Well, in my case I had 60GB free on the disk, so this can’t be right… The database to be created was only 1GB in size.

Well, turns out the Quota on the disk was preventing the file from being created. To change the Quota (or in my case, turn it off for the duration of the install) go to Computer -> Right click on the drive you’re installing on -> Select “Properties” -> Click on the “Quota” tab. Once here you can either uncheck “Enable Quota Management” to completely disable it, or just select the radio button that reads “Do not limit disk usage”.

This should hopefully solve the problem