How to fix BAD FILE MODE Cron errors

Inside Logwatch, its common to see errors such as "BAD FILE MODE" appear at the end of the crontab section. it should also be kind enough to display which files it didn't like and errored on.
You may see something similar to BAD FILE MODE (/etc/cron.d/filename)

The problem is file permissions - a lot of times when a program installs it will then install the cron file as 755 - which is no good, however the good news is that the fix for this is very easy

Instructions

1. First login as root in SSH and then change the permissions to 644 on the affected files.
   chmod 644 /etc/cron.d/filename

2. Now sit back and drink a beer - you earned it!

3. Next time Cron tries to run these files it should work, and the error messages should also disappear