What does Email Classification mean to you?

Grant Lindsay  July 1 2009 10:00:00 AM

E-mail classification can be done in two ways, either by the user or by the computer. Ideally, the method with perfect results would be selected. Unfortunately, neither of these does. Users will forget to classify or do so incorrectly and computers, while less likely to forget, are limited to binary thinking. There are ways to make these methods more effective, tweaking them. One example might be to use a hybrid approach.
What do you think?

Feel free to chime in on any of these questions:

• What does it mean to classify e-mail messages?
• Why classify messages?
• What business need would this address?
• Is classification meant to assist users in processing their in-boxes or to facilitate later e-discovery?
• What would a successful classification system look like?

• Comments [0]

Fix for Quickr ’Attachment size exceeds the amount allowed’ Error

Denny Russell  June 12 2009 07:59:05 AM

I started receiving an error on my Quickr site that read "Attachment size exceeds the amount allowed. Try again"  It didn't matter if I was trying to add a wiki document or add a post to a discussion, I received the error.  I didn't notice it prior to my 8.2 upgrade, but I can't be sure, as it's been slow going getting this rolled out (not at all because of the product, but other priorities in new product releases).

Inside the 'Site Administration - Other Options' there is a setting 'Maximum Attachment Size'.  I tried resetting this but again, same error. So I was stumped.

So I tried two methods of finding an answer.  First, I Tweeted my dilemma and then after no response, I opened an incident with IBM.

From Lotus Support, I was presented with the following options:

Suggestions:
Solution 1: You might have increased the Maximum Post data size to a number too high for Domino to handle, please change the following setting to "50,000"
Change the Server document => Internet Protocols => Domino Web Engine => Maximum POST data to 50,000

Solution 2: Add the following notes.ini parameters
QuickPlaceLargeRequestOnFile=1
QuickPlaceLargeRequestDir={directory where temporary files should be written}

These parameters are added to allow Domino to handle larger files more efficiently.  Domino does not automatically create the temp directory for Chunk buffering, therefore if you have set the temp directory to "c:\temp", then you will have to create that directory on the hard drive yourself

QuickPlaceLargeRequestDir=C:\temp

After making the above changes please make sure to restart your server and delete the browser cache.

I decided on updating both solutions in an attempt to make it work better all around.  All is working now and I'm back in business.  Now I've got to work on testing out a few templates from the great guys over at Snapps.com and get my co-workers trained and using it.

This morning on Twitter, I received a reply and a good reference from @m0urs, I was provided this link. Thanks for the great Wiki to a lot of awesome Lotus related info.

• Comments [0]

Blackberry Server Vulnerability & .pdf files

Denny Russell  May 29 2009 12:41:23 PM

Just a heads up out there to anyone using a BES, there was a statement released this week about a Vulnerabilities in the PDF distiller of the BlackBerry Attachment Service for the BlackBerry Enterprise Server.

Overview
This advisory describes security issues that the BlackBerry Attachment Service component of the BlackBerry Enterprise Server is susceptible to. The issues relate to the handling of malformed and possibly malicious PDF files.

The complete information along with fixes and workarounds can be found here.
http://www.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB18327

• Comments [0]

Beware of Purge setting in the Domino Journal

Denny Russell  May 27 2009 02:57:54 PM

In working with a customer, I stumbled across how the purge setting works in the Domino Journal.  When setting up Journaling, you've got options for what should be done with the journal documents over time.    As you can see, there is a 'Method' field in the Database Management section that allows you to set this to 'Purge/Compact' with a specified number of days.



All sounds great, right?  And it works exactly as designed.  So where's the problem you ask? Glad you asked.

One of our customer's had called believing Mail Attender must be deleting items out of their Archived Journals.  Knowing we couldn't be deleting these documents based on their configuration, I started to dig.  To be compliant with their policy, they were archiving journals and placing a copy of the Domino Journal off to another storage device outside of Domino.  Again, no issues yet.  However, they wanted to search these Journals and used Domino Dirlinks to allow Domino to have access to this stored data.  Herein lies the problem I've eluded too.  To purge the data from the Journal, they've enabled the "Remove documents not modified..." setting in the Replication Settings field.



So now, the 'archived' data, because of the Dirlinks AND the Purge/Compact settings being enabled, Domino started removing old data that was older than 7 days as specified in the Configuration document.

So my warning to anyone using Domino Journaling is beware of this Purge/Compact setting especially if you are making copies of the Old Journals and placing them to another location as part of your Retention Policy.  Make sure of this setting as you may not know this data is gone until the time you need it.

• Comments [0]

Best of Tech Ed

Srinivasan Balaji  May 19 2009 11:23:27 AM

As we had blogged about earlier here, Sherpa Software's Mail Attender for Exchange was voted the Best of Tech Ed in the  Messaging category. Here is a picture of Tom Hand, VP of our Exchange practice, receiving the award.



Tom was the first technical resource in Sherpa's Exchange practice and was the original creator of Mail Attender for Exchange. So it was indeed very fitting that he was on hand to receive the award.

• Comments [0]