So it might not be the biggest milestone to pass, but considering I just wrote this up quickly to solve my own problems, I think it’s quite an accomplishment. Clearly there’s a need for software like KBudget on the marketplace.

What’s next for KBudget? Here’s a few of the things I have planned:

• UI Overhaul (working on some concepts but if any artists out there want to help, I’m sure I could use it)
• add weekly/bi-weekly budgeting support
• add some graphs (this one will be tougher given that the app is free so I’ll have to write this from scratch)
• a super secret feature that I’m sure you’ll all love

If you have an idea you’d like to suggest for KBudget, send me an email or use the contact page on this site.

In other news, KBudget 0.22 will be added to the marketplace soon. This is just a minor update which adds Chinese Locale Support (thanks to goapk.com).

An update to KBudget has been posted yesterday on the Android Marketplace. This is a small update that fixes various bug fixes including some annoying date bugs that caused transactions to appear in incorrect months. There is also some fixes to the status bar calculations so that the right column properly calculates based on transactions in the current year.

Hopefully there aren’t any other issues with this release. But let me know in the comments or through the contact page if you run into any problems!

Within a day or two, I’ll be pushing another update to KBudget, my Android application which allows you to track your daily spending.

Screen of the password prompt

Screenshot of the new Auto complete box for transaction descriptions. This allows you to quickly enter common transactions

This update brings some new features such as password protection, basic export/import functionality, auto completion box for transactions, and more!

Hopefully there won’t be any unexpected bugs, but let me know if you run into any!

So I just spent a couple of hours last night knocking my head wondering why my postfix configuration on my server stopped working. I currently use Google Apps email services (which are free btw) for the email on this server and I have postfix setup to relay any mail the server has through Google Apps.

It’s been running great for the past 2 months but suddenly I noticed it was acting up. I got several errors like this:

May 6 05:53:46 kwasik postfix/smtp[20753]: certificate verification failed for smtp.gmail.com[74.125.113.109]:587:
untrusted issuer /C=US/O=Equifax/OU=Equifax Secure Certificate Authority


May 6 05:53:46 kwasik postfix/smtp[20753]: 25CF63C05A: to=, relay=smtp.gmail.com[74.125.113.109]:587, delay=2509, delays=2509/0.16/0.26/0, dsn=4.7.5, status=deferred (Server certificate not trusted)


At first, I thought something went wrong with my SSL certificates, so I tried re-doing those. No luck. Several hours later, I stumbled upon this:

http://www.google.com/support/forum/p/gmail/thread?tid=7e4a679f5917149e&hl=en

Seems Google decided to change their Certificate Authority.. instead of using Thawte, they’re now using Equifax (no wonder Equifax kept popping up in my log).

Anyways the simple fix (run as root):

cat /etc/ssl/certs/Equifax_Secure_CA.pem >> /etc/postfix/cacert.pem

Mind you, the above applies to Debian 5.0, but it should at least help you on your way to fixing the problem.

This is just to note to transition from CuteNews to WordPress. I didn’t bother with transferring over the old news items, so it’ll be a fresh start!

The custom theme I made for WordPress so it would integrate with the rest of the site is still incomplete so let me know if you notice any bugs. Thanks!