1. ZanderMail Agent And wireless software development - Introduction -WAP Architecture - Architechture (basis) - Security - Implememtation ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

2. Introduction n Http://zandermail.sourceforge.net n Email Agent, which makes possible to receive and send emails with any terminal equipment. n Makes possible to receive and send emails from different mailboxes in the same GUI. Example: You could read your schools INBOX,works INBOX and ISP’s INBOX at the ’same time’ n Very flexible and easy to change interface, so user can basicly determine what kind of user interface he/she wants... ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

3. Introduction (cont.) n Open Source, so you can create own modules or examine the implementation. n Is implemened with Object-Oriented paradigm, eventhough PHP is a scripting language n ServerSide program, so you dont need to install any extra software on your terminal equipments. n Requirements: n mySql - database n Apache (or another) web server n PHP 4.0.6 Module, or newer. n Linux Send mail n (will change so that is possible to run on top of Windows) ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

4. Introduction (cont) Zander Mail view of the one mailbox, with MSIE profile. Note that you can build your unique view for every browser.

5. Introduction (cont.) Here is the default profile view with wap7110. Note that 8ball.wbmp is an attachment, which you can view.

6. WAP Architechture n Overview of the architecture Kannel Wap/SMS Gateway Server running ZanderMail Agent Server Cluster With Modems TE WSP HTTP HTTP Request/Response Note that the modem, Kannel Gateway and Server running ZanderMail, can all be physically in the same machine if so wanted. BS/NET Over the air ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

7. WAP Architecture (cont.) n When wanted to use ZanderMail, you must call to the Dial-in server, your ISP or phone company has provided. That server then connects to the Gateway you’ve chosen (basically the IP of the gateway and the number of the dial-in server, comes with in the WAP-properties of your wap- phone). The gateway then connects to the server running zandermail with normal http request. The zandermail agent returns a http response to the gateway, which converts it to wsp (wireless session protocol ) response. The data itself is coded to binary strings either by the server or the gateway. The terminal equipment (TE) the interpretes the binaryXML (wml decks and cards) as implemented by the browser vendor. ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

8. Architechture n User- and TE-identification are the basis of the ZanderMail Architechture, which allows the user to read/send emails with different Terminal equipments NOKIA7110 MSIE 5.5 Some other TE ProfileMapper UserAgent String MappedNames DB ZanderMailAgent system Example Nokia WML... … ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

9. Architechture (cont.) n The login page is the entering point to the system. When user enters to the login page a temporary profile is created, from the xml formed default profiles(library.xml). The profileMapper assignes a certain profile to a certain user, based on the user-agent environment variable. If the user-agent string says nokia and a certain profiles mappedName attribute is nokia, this profile is assigned to the user. n Profiles also determine what language is outputted, (output- attribute). In this case it would be WML. Profiles also include many other usefull attributes. When a profile is assigned by the system, it is saved to the user when logging in. The system produses a collection of different profiles to each user, whenever user enters to the system with different TE. User can also make its own profiles if suitable is not provided. The profile is used outputting trought out the session.

10. Architechture (cont) n MailBox context is not a similar than usual mailbox. ZanderMailbox is global, so you can add any mailbox from any server to your mailPool, which contains all you mailboxes. MAILPOOL Commercial School ISP Work Page- Formatter uses Profile assigned Example ->Server: jasu.ath.cx; userName: imap_testi; passwd: imap; port: 143 TE

11. Architechture (cont) n User can define number of mailboxes to use, These all are saved to the mailPool. ZanderMail uses IMAP protocol to access these boxes, which are physically located in different servers trough out the world (also local mailboxes can be added) n Modifying the profiles user can define the view he/she wants. All boxes can be seen at the same time, or a generic menu is created if wanting to view boxes one at a time. n Password of the remote boxes are encrypted to the database, so you are the only one who knows the key (your system password) needed to decrypt the passwords... ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

12. Security Security of the system As mentioned earlier the password of the remote boxes are encrypted to database. The data in session is saved to a table, so the default save.session handler have been replaced to quarantee to safeness of the session variables. IMAP over SSL is supported ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

13. Implementation The development is continuing in http://zandermail.sourceforge.net, please feel free to join the crew… The online demo of the development version is available there also, and the instructions how to install and use the zandermail agent. There is also one version at: http://jasu.ath.cx:8000/~zander/ ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen

14. Thank You! Thank you for your attention and feel free to contact us. mikhel at batman dot jypoly dot fi jarjar at batman dot jypoly dot fi jankal at batman dot jypoly dot fi jarkol at batman dot jypoly dot fi ZanderMail Development Group ; Mikko Helin, Jari Järvinen, Janne Kalliokorpi, Jari Kolehmainen