semester 2 2012 week 11-12

web server

Web server can refer to either the hardware the computer or the software the computer application that helps to deliver Web content that can be accessed through the Internet. The most common use of web servers is to host websites, but there are other uses such as gaming data storage or running enterprise applications.

The primary function of a web server is to deliver web pages on the request to clients using the Hypertext Transfer Protocol (HTTP). This means delivery of HTML documents and any additional content that may be included by a document, such as images, style sheets and scripts.

A user agent, commonly a web browser or web crawler, initiates communication by making a request for a specific resource using HTTP and the server responds with the content of that resource or an error message if unable to do so. The resource is typically a real file on the server's secondary storage, but this is not necessarily the case and depends on how the web server is implemented. While the primary function is to serve content, a full implementation of HTTP also includes ways of receiving content from clients. This feature is used for submitting web forms, including uploading of files.

Many generic web servers also support server-side scripting using Active Server Pages (ASP), PHP, or other scripting languages. This means that the behavior of the web server can be scripted in separate files, while the actual server software remains unchanged. Usually, this function is used to create HTML documents dynamically "on-the-fly" as opposed to returning static documents. The former is primarily used for retrieving and/or modifying information from databases. The latter is typically much faster and more easily cached. Web servers are not always used for serving the World Wide Web. They can also be found embedded in devices such as printers, routers, webcams and serving only a local network. The web server may then be used as a part of a system for monitoring and/or administering the device in question

webmail setting

The webmail service is enabled in the same way as any other Zentyal service. However, the e-mail module must be configured to use either IMAP, IMAPS or both and the web server module must be enabled. Without this configuration, webmail will refuse to work. The user must be set in the server because when do the login in the web mail, it requested username and password.

roundcube

If the client wants to email to the other client in the office, the just simply put the “bmi.com/webmail” at the link. Then the webmail with username and password request will appear. Then the client can login using their own username and password and they can do emailing to the other client.

To be able to log into the webmail interface, HTTP traffic must be allowed by the firewall from the source address used. The webmail login screen is available at bmi.com/webmail the browser. Then the user has to enter their e-mail address and password. Only the real e-mail addresses are accepted for login, not aliases.

zarafa webmail

       In this scenario, any number of the existing virtual domains will be assign to the groupware module and, from that moment on, the mail of those domains will be stored in Zarafa and not in the server. The mail sent to the other virtual domains will continue to be stored in the same way. This groupware module integrates with the existing mail module so that the client can consider themselves associated with a quota and use a Zarafa account. Enable outlook access is to integrate the zarafa platform and all its groupware services such as calendar, task and contact with a Microsoft outlook client. To support ActiveSyns mobile devices for synchronization email, contact, calendar and task, the ActiveSyns should be enabled. To provide users with POP3, POP3 on SSL, IMAP or IMAP on SSL access to their mailboxes, the zarafa gateways will be select. The Zarafa Gateways can only authenticate users with a Zarafa account and not users with only an email account.

As mentioned earlier, besides an email account, each user should have a Zarafa account. Furthermore, the quota defined in the mail module for each user will be applied to Zarafa, this can be unlimited globally defined or specifically set per user. The client who wants to use zarafa, they just put the “bmi.com/webapp” in the top of the link. The zarafa will be appearing and they requested username and password to do login.

In the zarafa, the client can do a shared contact, calendar and can chat with the other client using jabber application. To create an event in the zarafa, the client can do it at the calendar tab and double clicking in the desired date and time. The client can invite other client from the invite attendees. The recipient which is others client will receive a custom mail with event specification including a submenu which allow the client to accept or decline the invitation.