>Discussed in the past on this list has been using non-records management
applications such as Symantec, to identify emails as records and its
inability to work with Blackberries. I'm looking for anyone the list that
has had experience with the standard RMAs, i.e. those that are
DOD-certified, in handling email messages read by Blackberries and
identifying them as records
> 

Not an easy one to answer, because it depends on how the messages are
actually managed and how they are received/used on the BBerry or other device. 

If the messages exist on a server and are pushed out to the BBerry and
viewed there, then remain on the server... no problem.

If the user can "action" the messages from the BBerry- that is to say: view
and delete, removing it from the server in the process or create and not
store on the server, then it's an issue.

Also, if there is an application that is moving the messages on receipt from
the incoming server to an ERMS, and irrespective of what the user does on
the BBerry a copy (which by policy could be declared the record) remains
intact, then it would also not be a problem. 

I'm learning with an iPhone that you an read, then mark as unread and retain
messages or read and not delete them and they remain as-is... but if you
delete them, then naturally they're gone.  So one way around it would be to
set policy for users to not delete any messages on the BBerry which would
then require an action be taken on the desktop later. 

Not necessarily an answer, but a way to keep "records" from being improperly
managed by users remotely.

E-mail isn't an easy situation... a lot of it either requires direct human
intervention or the automated storage of everything until more functional
technology exists.  Both alternatives are costly, and they both have a
component of risk associated with them. 

BUT IT IS getting better... I think the answer is going to take a
combination of human intervention to help the systems learn the practices
and eventually automate some of the functional classification of messages,
but we're not quite there yet.  

There is the ability to take advantage of some 'rule and role based'
practices in organizations that are structured to utilize these, but it's
not one size fits all.

Larry

List archives at http://lists.ufl.edu/archives/recmgmt-l.html
Contact [log in to unmask] for assistance
To unsubscribe from this list, click the below link. If not already present, place UNSUBSCRIBE RECMGMT-L or UNSUB RECMGMT-L in the body of the message.
mailto:[log in to unmask]