This is a line from the log

------------------------------

 [498] Protocol error - Message Id: U33Y6MQ4H8VJ Offset: -1 Failure to encode B2 format...
2013-09-30 08:43:10 *** Paclink 4.3.4.0 ready..

-----------------------------------------------------------

I try to send a with attachments, and then i get this. I am in the list of people with up-to-date software.

my winlink email adress is pa3bas@winlink.org or other email pa3bas@xs4all.nl

Please contact me if you need more information

Thank you,

Bastiaan PA3BAS

First of all, great work Lee on the Google Map, it loads much much faster than SilverLight did. :)

Suggest a project for next year, to display Digi locations on the map (maybe a blue balloon) with callsign information. It would require the operator to register the digi with frequency and location information either in a web page interface to the database, or some other means. (self registration would make it easier for the operator to keep it up to date without need for emails to the WDT)
Last heard status of the digi can be monitored when the RMS Packet application detects a connection through the digi. I'm assuming RMS Packet knows the route back to the original station.

Timeout or dropping the digi off the map could be done if it has been detected that it hasn't been used to make a connect to an RMSP gateway after 3 months or sooner, at which point the operator would need to log in and reset the active status of the Digi. 

For simplicity, I run a simple digi, not a node. I also advise local packet users to use only one hop to an RMSP gateway. I know it's slow, but in most cases in our terrain for packet users, individual gateways are not always reachable direct and the digi makes the difference of connect or no connect for Technician class operators.

The above is just an initial suggestion and there are several ways to implement it if the interest is there.

Tom
KG4VUB