as will be described is more detail below , a system and method for distributing an attachment by email is described . in one embodiment , the attachment is automatically converted to reduce the file size of the attachment . in another embodiment , the attachment is converted to a predetermined format according to an addressee &# 39 ; s preferences . in another embodiment , the original attachment is automatically attached to the email when the email is forwarded to another addressee . fig3 shows one embodiment of a process of converting the attachment . first , the email is received in block 305 . the email includes an attachment . then the attachment is converted in block 315 . various embodiments of converting the attachment will be described in more detail below . in block 320 , the converted attachment replaces the original attachment in the email and the email is sent onto the addressees in block 325 . in one embodiment , the attachment is detached from the email so that the attachment can be manipulated separately from the email . in another embodiment the original , unconverted attachment is stored in the server . in yet another embodiment , the converted attachment includes a representation of the attachment such as an attachment id and the attachment id is also recorded to correspond to the correct original , unconverted attachment and the correct converted attachment . fig3 a shows one embodiment of a process of converting the attachment in a client - server system . first , the email is received in an email server for an addressee of the email in block 340 . the email includes an attachment . the attachment is converted in block 342 . in block 344 , the converted attachment replaces the original attachment in the email and the email is sent onto the addressee in block 346 . in another embodiment , the email is received by a recipient ( i . e . an addressee of the received email ). then the recipient forwards the email to a new addressee . then the attachment is automatically converted and attached to the forwarded email . then the forwarded email with converted attachment is sent on to the new addressee . in one embodiment the attachment is converted to reduce the file size of the attachment . converting the attachment to reduce the file size reduces the bandwidth required to distribute the email . for example , if the attachment is a microsoft word ( msword ). doc file format that has a size of 200 k , the file may be converted to any one or more or combinations thereof , of other file formats such as ascii text , rich text format , html , xml and many other file formats . the converted attachment can be substantially smaller than the original attachment . another example of reducing a file size is converting a 16 - bit color , high resolution jpeg (. jpg ) graphic attachment to a low resolution , 4 - bit gray scale graphic . determining the correct conversion process to use to convert the attachment can include many factors . in one embodiment , the attachment is converted to a file format according to the preferences of the addressee of the email . in another embodiment , the attachment is converted to a predetermined file format . for example , if the attachment is a proprietary file format such as a proprietary database report format , then the converting process could convert the report from the proprietary format to a more common format such as the adobe acrobat . pdf file type format or an html format . other conversion processes can also be used so that the converted attachment is more easily useable by the addressee . there are many attachment conversion applications that are commercially available . proprietary or specialized conversion applications can also be used to convert the attachment to meet the requirements of the viewer of the attachment . fig4 shows one embodiment of a process of receiving an email with the converted attachment in an email client . an email client can include a client computer that accesses the email server for email services . the email client can also include an email client application operating on the same computer as the email server . the email is received in the email client ( client ) of the email addressee in block 405 . the received email includes a converted attachment . in block 410 , the email is forwarded from the client to one or more addressees ( forward addressees ). in one embodiment , the forwarded email also includes the converted attachment . alternatively , the forwarded email can also include a representation of the received email . a representation of the received email can include an unique email id or other reference that identifies the received email . the forwarded email is sent to the server in block 415 . the server is the same server such as the email server that converted the attachment and also stored the original , unconverted attachment as part of the conversion process . the server receives the forwarded email in block 420 and determines the correct , original , unconverted attachment from the received email . the server automatically replaces the converted attachment with the corresponding original , unconverted attachment in the forwarded email in block 425 . then the server sends the forwarded email with the original attachment to the forward addressee ( s ) in block 430 . in one embodiment , the server determines the correct , original , unconverted attachment by comparing the converted attachment or a representation of the converted attachment to several stored attachments . in another embodiment , the correct , original , unconverted attachment is determined by comparing the representation of the received email to the email received for the client or otherwise stored in the server . as described above , the server converted the attachment to reduce bandwidth requirements to the client and / or according to the preferences of the email client . however , the forward addressees of the forwarded email may or may not have the same preferences or limitations of bandwidth or format . further , the converted format is often a pared down version that includes fewer details ( i . e . less formatting , lower resolution , etc ) and other aspects than the original attachment . therefore , the original attachment may be a preferable format for the forwarded email . for example , a high resolution , color . jpg attachment is received in the server . the server converts the high resolution , color . jpg to a low - resolution , 4 - bit gray - scale . jpg or other graphic format because the server knows preferences of the addressee . in this example the addressee is a wireless pda client of the server . because the wireless pda has a small , low - resolution monochrome display , then the addressee does not need the high resolution color jpg . the addressee receives and views the email and attachment . the addressee then forwards the email on to a group of forward addressees . the email with the converted attachment is returned to the server . the server determines the original attachment and replaces the converted attachment with the original high - resolution , 16 - bit color . jpg graphic attachment and sends the forwarded email to the forward addressees . in one embodiment , the attachments are identified by an attachment id in the server that performs the attachment conversion . the server stores the original attachment and the attachment id and the converted attachment . the server can then more easily identify the original and converted attachments that are received by the server . the attachment id can be in the file name or can be part of a file header in the converted attachment or elsewhere in the converted attachment so that the server is able to identify the converted attachment . in one alternative embodiment of the process of fig4 , forwarding the email from the client to a forward addressee , the converted attachment is replaced by an attachment id in the forwarded email . when the forwarded email is received in the server , the server identifies the original attachment by comparing the attachment id from the forwarded email to the attachment ids of the stored attachments . then the attachment id in the forwarded email is replaced by the corresponding original attachment . then the forwarded email is sent to the forward addressee ( s ) specified by the email . including only the attachment id in the forwarded email from the client to the server can further reduce the bandwidth required to distribute an attachment by email . fig5 illustrates one embodiment of a process where the converted attachment is edited in the email client . the email with the converted attachment is received in the client in block 505 . the client then views the attachment and edits the attachment in block 510 . in block 515 , the email is forwarded . the forwarded email includes the edited , converted attachment and one or more forward addressees . in block 520 , the forwarded email is sent to the server that converted the attachment as described above . the server then as descried above , detects the edited , converted attachment and identifies the corresponding converted attachment stored in the server . the server then compares the edited , converted attachment to the original converted attachment in block 525 . there are many known methods in the art of comparing two similar files to identify differences ( i . e . edits in this instance ). in block 530 , the server automatically edits the original , unconverted attachment in accordance with the edits that were applied to the edited , converted attachment in the client . in block 535 , the server replaces the converted , edited attachment in the forwarded email with the edited , unconverted attachment . in block 540 , the server sends the forwarded email to the forward addressees . as described above in fig5 , the server can receive an edited converted attachment and then forward a correspondingly edited original attachment . for example , if the original attachment is a msword document , the server converts the msword document to an ascii text file . the ascii text file then sent to the client . the client views the ascii text file and edits the ascii text file , ( e . g . changing a sentence , or a letter , etc .). then the client forwards the email with the edited ascii text file to one or more forward addressees . the server receives the edited ascii text attachment . the server determines the corresponding converted ascii text attachment and compares the edited ascii text attachment edited to the corresponding ascii text attachment . the server identifies the differences / edits that were made in the client . the server then applies the identified edits to the original , unconverted msword document attachment to create an edited , msword document . the server then attaches the edited msword document to the forwarded email and sends the forwarded email on to the forward addressees . the process of fig5 allows a client to virtually view and edit the original format attachments without being burdened by having to actually manipulate the large original attachment . the process of fig5 also allows the client to forward the client &# 39 ; s proposed changes to other addressees . fig6 is a high - level block diagram of a computer system representative of any or all of the client 701 or the servers , i . e ., network servers 716 , 720 and gateway server 708 , shown in fig7 . as shown , the computer system includes a processor 602 , rom 604 , and ram 606 , each connected to a bus system 608 . the bus system 608 may include one or more buses connected to each other through various bridges , controllers and / or adapters , such as are well known in the art . for example , the bus system 608 may include a “ system bus ” that is connected through an adapter to one or more expansion buses , such as a peripheral component interconnect ( pci ) bus . also coupled to the bus system 608 are a mass storage device 610 , a network interface 612 , and a number ( n ) of input / output ( i / o ) devices 616 - 1 through 616 - n . i / o devices 616 - 1 through 616 - n may include , for example , a keyboard , a pointing device , a display device and / or other conventional i / o devices . mass storage device 610 may include any suitable device for storing large volumes of data , such as a magnetic disk or tape , magneto - optical ( mo ) storage device , or any of various types of digital versatile disk ( dvd ) or compact disk ( cd ) based storage . network interface 612 provides data communication between the computer system and other computer systems such as via the networks 704 , 712 of fig7 . hence , network interface 612 may be any device suitable for or enabling the computer system 600 to communicate data with a remote processing system over a data communication link , such as a conventional telephone modem , an integrated services digital network ( isdn ) adapter , a digital subscriber line ( dsl ) adapter , a cable modem , a satellite transceiver , an ethernet adapter , or the like . of course , many variations upon the architecture shown in fig6 can be made to suit the particular needs of a given system . thus , certain components may be added to those shown in fig6 for given system , or certain components shown in fig6 may be omitted from the given system . fig7 describes one embodiment of a network server system . the network server system includes a gateway server 708 that provides a gateway to a wireless network 704 , and the wireless network has a wireless client 701 . as shown the wireless client 701 is a cellular telephone , but other types of wireless clients such as a wireless pda , and other devices could also be used . in addition , the gateway server is attached to a network 712 , also attached to the network 712 are two network servers 716 , 720 . the gateway server 708 can also be part of one of the network servers 716 , 720 . one of the servers 708 , 712 , 720 is an email server for the wireless client 701 . because the bandwidth across the wireless network 704 , tends to be more limited than across the wired network 712 , then it is advantageous to have reduced sized the email . in addition , the wireless client 701 does not have the viewing capabilities and the processing capabilities of larger computer system such as a lap top and desk top pcs and other computing platforms . therefore , a reduced sized and / or converted format attachment might also be required to allow that wireless client 701 to use the attachment . the wireless network 704 is typically limited to narrow bandwidths of approximately 14 . 4 kbps or less and sometimes slightly higher bandwidths such as like 19 . 2 or 28 . 8 kbps . the wireless network 704 is typically substantially narrower bandwidth when compared to the large bandwidth capabilities of a wired network 712 . often wired network 712 includes a 1 . 4 megabit of a t1 connection , the approximately 1 megabit connection of a dsl connection , a 10 megabit ethernet connection or other types of broad bandwidth ( i . e . approximately 300 kbps or greater ) connections that are capable in a wired network 712 . fig8 illustrates one embodiment of a client computing device . the client computing device 800 includes a microcontroller 805 , an external memory 865 , a display 875 , various i / o devices 880 such as a keyboard , and a battery 860 . the external memory 865 may be used to store programs and / or portal data transmitted to the client computing device 800 from the portal server 708 . in one embodiment , the external memory 865 is non - volatile memory ( e . g ., an electrically erasable programmable read only memory (“ eeprom ”); a programmable read only memory (“ prom ”), etc ). alternatively , the memory 865 may be a volatile memory ( e . g ., random access memory or “ ram ”) but the data stored therein may be continually maintained via the battery 860 . the battery 860 in one embodiment is a coin cell battery ( e . g ., of the same type used in portable electronic devices such as calculators and watches ). in one embodiment , when the battery power decreases below a threshold level , the client computing device 850 will notify the user and / or the portal server 708 . the portal server 708 in one embodiment will then automatically send the user a new battery . the microcontroller 805 of one embodiment is comprised of a central processing unit (“ cpu ”), a read only memory (“ rom ”), and a scratchpad ram . the rom is further comprised of an interpreter module and a toolbox module . the toolbox module of the rom contains a set of toolbox routines for processing data , text and graphics on the client computing device 800 . these routines include drawing text and graphics on the client computing device &# 39 ; s display 875 , decompressing data transmitted from the portal server 708 , reproducing audio on the client computing device 800 , and performing various input / output and communication functions ( e . g ., transmitting / receiving data over the client link ). a variety of additional client computing device functions may be included within the toolbox while still complying with the underlying principles of the invention . in one embodiment , microprograms and portal data are transmitted from the portal server 708 to the external memory 865 of the client computing device via a communication interface under control of the microcontroller 805 . various communication interfaces may be employed without departing from the underlying principles of the invention including , for example , a universal serial bus (“ usb ”) interface or a serial communication (“ serial ”) interface . the microprograms in one embodiment are comprised of compact , interpreted instructions known as “ bytecodes ,” which are converted into native code by the interpreter module before being executed by the microcontroller 805 . one of the benefits of this configuration is that when the microcontroller portion of the client computing device 800 is upgraded ( e . g ., to a faster and / or less expensive model ), only the interpreter module and toolbox of the rom needs to be rewritten to interpret the currently existing bytecodes for the new microcontroller 805 . in addition , this configuration allows client computing devices 800 with different cpus to coexist and execute the same microprograms . moreover , programming frequently - used routines in the rom toolbox module reduces the size of microprograms stored in the external memory 865 , thereby conserving memory and bandwidth over the client link . in one embodiment , new interpreter modules and / or toolbox routines may be developed to execute the same microprograms on cellular phones , personal information managers (“ pims ”), or any other device with a cpu and memory . one embodiment of the rom may be comprised of interpreted code as well as native code written specifically for the microcontroller cpu . more particularly , some toolbox routines may be written as interpreted code ( as indicated by the arrow between the toolbox and the interpreter module ) to conserve memory and bandwidth for the same reasons described above with respect to microprograms . moreover , in one embodiment , data and microprograms stored in external memory 865 may be configured to override older versions of data / microprograms stored in the rom ( e . g ., in the rom toolbox ). the client computing device 800 may communicate with the portal server 708 ( discussed above ) using various rf communication techniques . in one embodiment , the rf communication is established through the communication device 880 . in one embodiment , the communication device 880 includes a cellular telephone module that includes a full function cellular telephone that the microcontroller 805 may access for establishing a wireless link to the portal server 708 . the communication device 880 can also include any other similar rf receiver / transmitter combination that will allow the microcontroller 805 to establish a link to the portal server 708 or other network server such as network server 716 , 720 . for example , in one particular embodiment , the client computing device 800 transmits and receives data to / from a cellular network via the cellular digital packet data (“ cdpd ”) standard . as it is known in the art , the cdpd standard is a digital wireless standard that is deployed as an enhancement to the existing analog cellular network . it provides a packet overlay onto the amps network and moves data at 19 . 2 kbps over continuously - changing unused intervals in standard voice channels . accordingly , this embodiment of the client computing device is capable of exploiting normally unused bandwidth on a nation - wide , analog cellular network . embodiments of the client computing device may also be configured to transmit / receive data using a variety of other communication standards including 2 - way paging standards and third generation (“ 3g ”) wireless standards ( e . g ., utms , cdma 2000 , ntt docomo , . . . etc ). as indicated in fig8 , one embodiment of the client computing device 800 , the cpu employs a 32 - bit risc - based microprocessor such as an arm processor . as is known in the art , arm processors are widely used in pdas , cell phones and a variety of other wireless devices . it should be noted , however , that various other hardware and software ( and / or firmware ) architectures may be used for the client computing device 800 while still complying with the underlying principles of the invention . embodiments of the invention may include various steps as set forth above . the steps may be embodied in machine - executable instructions . the instructions can be used to cause a general - purpose or special - purpose processor to perform certain steps . alternatively , these steps may be performed by specific hardware components that contain hardwired logic for performing the steps , or by any combination of programmed computer components and custom hardware components . elements of the present invention may also be provided as a machine - readable medium for storing the machine - executable instructions . the machine - readable medium may include , but is not limited to , floppy diskettes , optical disks , cd - roms , and magneto - optical disks , roms , rams , eproms , eeproms , magnetic or optical cards , propagation media or other type of media / machine - readable medium suitable for storing electronic instructions . for example , the present invention may be downloaded as a computer program which may be transferred from a remote computer ( e . g ., a server ) to a requesting computer ( e . g ., a client ) by way of data signals embodied in a carrier wave or other propagation medium via a communication link ( e . g ., a modem or network connection ). fig9 illustrates an embodiment of a handheld keyboard and display device such as may be used as the client computing device of fig8 . the handheld keyboard and display device 900 can also include additional user interface devices such as a pointing device , selection buttons 904 , 906 , 908 and other user interface devices such as joysticks , mice , trackballs , or trackpoint 909 . in one embodiment , the display 902 rotates about a pivot . for example , fig9 shows one embodiment of the keyboard and display device in the open position so that the keyboard 904 is accessible . when the display 902 is rotated 180 degrees about the pivot , to the closed position , the keyboard 914 is substantially covered . in one embodiment , the display 902 is a liquid crystal display , or other similar monochrome or color display devices . the display 902 can also include a scratch resistant display surface such as glass or polycarbonate or other scratch resistant coating or outer layers as are known in the art . in one embodiment , the display also includes a removable transparent cover to protect the display screen . the transparent cover can also be a disposable cover . in one embodiment , the display 902 can also include a touch screen . throughout the foregoing description , for the purposes of explanation , numerous specific details were set forth in order to provide a thorough understanding of the invention . it will be apparent , however , to one skilled in the art that the invention may be practiced without some of these specific details . for example , while the system described above in fig7 employs a single gateway server 708 , alternative embodiments of the invention may include numerous different servers ( e . g ., database servers , web servers , etc ), and / or mirrored servers distributed across a network . moreover , while the embodiments described above focus on a client computing device , which executes interpreted code ( e . g ., java byte codes ), the principles of the invention may also be implemented on devices , which execute non - interpreted code . accordingly , the scope and spirit of the invention should be judged in terms of the claims that follow . one skilled in the art will immediately appreciate that the invention can be practiced with other computer system configurations , including multi - processor systems , minicomputers , mainframe computers , and the like . the invention can also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network . it will be further appreciated that the instructions represented by the blocks in fig3 – 5 are not required to be performed in the order illustrated , and that all the processing represented by the blocks may not be necessary to practice the invention in the foregoing specification , the invention has been described with reference to specific exemplary embodiments thereof . it will be evident that various modifications may be made thereto without departing from the broader spirit and scope of the invention as set forth in the following claims . the specification and drawings are , accordingly , to be regarded in an illustrative sense rather than a restrictive sense .