I am a huge fan of Gmail which I use to consolidate multiple email addresses in one location so I can easily search, store, and manage tens of thousands of emails dating years back. One of the issues I run into is archiving email messages or managing more than the default screen of 25 email conversations at a time. There are two tricks that can assist you managing more than 25 messages at a time using the Gmail web interface which I explain in more detail below. It is also possible to use an email client such as Microsoft Outlook to drag and drop email messages between folders or labels as they are known within Gmail.
Earlier this evening I ran into a unique issue where a PostgreSQL table had been created with no primary key this allowing duplicate rows to exist in the database table. You are unable to delete such rows in a SQL table because there is no primary key. After not being able to delete the rows via the PSQL CLI I opened pgAdmin III to see if I could delete the rows using the GUI interface provided by pgAdmin III however the delete was grey in the menu as shown in the below image.
I use Outlook 2007 to manage email and to schedule appointments or meeting requests. Recently Outlook crashed and required a scan of the PST file before it would operate properly again. All seemed to be working without issue and then one of my recurring meetings continued to alert me that it was time for the meeting which was incorrect. After dismissing the item it would continue to warn of the issue which lead me to believe that the recurring meeting entry had become corrupted. After poking around some more I was able to verify that the meeting was in fact corrupted and read about all sorts of various steps that could be taken to resolve the issue. After attempting many of those steps including the /cleanreminders switch the meeting still existed and was still corrupted. Below I describe the error in more detail and a simple way to resolve a corrupted recurring meeting entry in the Outlook 2007 calendar.
A company I work with uses Gmail to log exception emails from our Ruby on Rails application. This allows us to always capture issues with the application and keep a lengthy history of all the issues without using up disk space on the server itself. Sometimes if there is an issues on a development server that is not fixed right away we may get thousands of emails into the Gmail account that are all the same and it benefits us to clear these out from time to time since they can number over 50,000 at times. The example image below shows our Ruby on Rails application exception inbox from Gmail.
I recently had some issues with my printer not working on my home network and during the troubleshooting process I wanted to remove the printer port so I could reinstall the printer all together. The issues ended up being stupidity on my part for adding a temporary device on my network that had the same…