{'fraction_non_alphanumeric': 0.021464646464646464, 'fraction_numerical': 0.005050505050505051, 'mean_word_length': 4.914179104477612, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
Implementing LIES: (location independent email service)

This paper will provide a useful guide to those schools that have not yet implemented IMAP and are considering doing so. With both the systems and user services perspectives, any schools considering implementing this service will get a full view of what is involved in putting out IMAP. The goal of the LIES (Location Independent Email Service) project was simple: add IMAP services to our existing POP services in a way that would allow people to work from anywhere with their settings, nicknames, and mailboxes intact. The team knew that even if all the goals were not met in the first stage of implementing the new service, it was critical to achieve the location independence capability quickly. Over 500 people were still using email on our mainframe, and the only way to migrate them off was to recreate the capability they had with their mainframe accounts, complete location independence, while giving them new services (such as the ability to read attachments). Furthermore, with a large number of the POP users making use of the “Leave mail on server” option, it was clear that even those users were looking for a better solution. The project team was able to start with a server that already provided IMAP service because the server software had been replaced late in 1999 for Y2K reasons. System support still was needed to implement SSL support, quota management, and backup procedures. Client selection (both desktop and web based), new documentation, and marketing strategies were also components of the project.