DOCSLIB.ORG

Migrationsleitfaden

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
Migrationsleitfaden Migrationsleitfaden Leitfaden für die Migration der Basissoftwarekomponenten auf Server- und Arbeitsplatz-Systemen Version 1.0 – Juli 2003 Schriftenreihe der KBSt ISSN 0179-7263 Band 57 Juli 2003 Schriftenreihe der KBSt Band 57 ISSN 0179 - 7263 Nachdruck, auch auszugsweise, ist genehmigungspflichtig Dieser Band wurde erstellt von der KBSt im Bundesministeri- um des Innern in Zusammenarbeit mit dem Bundesamt für Sicherheit in der Informationstechnik (BSI), dem Bundesver- waltungsamt (BVA) und der C_sar Consulting, solutions and results AG Redaktion: C_sar AG, Berlin Interessenten erhalten die derzeit lieferbaren Veröffentlichungen der KBSt und weiterführende Informationen zu den Dokumenten bei Bundesministerium des Innern Referat IT 2 (KBSt) 11014 Berlin Tel.: +49 (0) 1888 681 - 2312 Fax.: +49 (0) 1888 681 - 523121 Homepage der KBSt: http://www.kbst.bund.de 1Frau Monika Pfeiffer (mailto: monika.pfeiffer@bmi.bund.de) Migrationsleitfaden Leitfaden für die Migration der Basissoftwarekomponenten auf Server- und Arbeitsplatz-Systemen Version 1.0 Juli 2003 Herausgegeben vom Bundesministerium des Innern INHALTSVERZEICHNIS 1 Einleitung ........................................................................ 8 1.1 Über das Vorhaben 8 1.2 Über diesen Leitfaden 9 1.3 Hinweise zur Benutzung des Leitfadens 10 1.4 Hinweise an die Entscheider 12 1.4.1 Grundsätzliche Empfehlungen 12 1.4.2 Fortführende und ablösende Migration 13 1.4.3 Migrationswege 14 1.4.4 Vergleichbarkeit von Alternativen 14 1.4.5 Künftige Schwerpunte 15 1.4.6 Wirtschaftlichkeit 16 2 Schwerpunkte des Migrationsleitfadens.................... 18 2.1 Wichtige Definitionen 18 2.1.1 Open Source -, Free - , Freie Software 18 2.1.2 Proprietäre Software 18 2.1.3 Commercial Linux Software 18 2.1.4 Ablösende Migration 19 2.1.5 Fortführende Migration 19 2.2 Migrationspfade 19 2.2.1 Ausgangslage Microsoft Windows 20 2.2.2 Systemlandschaft bei ablösender Migration 23 2.2.3 Systemlandschaft bei fortführender Migration 24 2.2.4 Interne Abhängigkeiten in der Microsoft- Systemlandschaft 25 2.3 Linux-Distributionen 28 2.3.1 Einleitung 28 2.3.2 Debian GNU Linux 30 2.3.3 SuSE Linux Distribution 30 2.3.4 Red Hat-Distribution 31 2.3.5 Zertifizierungen 32 2.3.6 Fazit 34 Seite 1 INHALTSVERZEICHNIS 2.4 Lizenzmodelle 34 2.4.1 GPL 34 2.4.2 Lesser GPL 35 2.4.3 BSD Lizenz 36 2.5 Datenerhebung 36 2.5.1 Erfahrungen aus Migrationsprojekten 37 2.5.2 Einbindung von Experten 39 3 Technische Betrachtung der Migrationspfade .......... 41 3.1 Einleitung 41 3.2 Dateiablage 42 3.2.1 Überblick 42 3.2.2 Windows NT 4 43 3.2.3 Ablösende Migration 52 3.2.4 Fortführende Migration 63 3.3 Druckdienst 68 3.3.1 Überblick 68 3.3.2 Einleitung 69 3.3.3 Ausgangssituation – Drucken unter Windows NT 4 70 3.3.4 Ablösende Migration 78 3.3.5 Fortführende Migration 88 3.4 Authentisierungsdienste 89 3.4.1 Überblick 89 3.4.2 Ausgangslage – Windows NT 4 90 3.4.3 Ablösende Migration – Linux, Samba und OpenLDAP 98 3.4.4 Fortführende Migration 101 3.5 Netzwerkdienste 102 3.5.1 Überblick 102 3.5.2 Ausgangslage – Netzwerkdienste unter Windows NT 102 3.5.3 Ablösende Migration – Netzwerkdienste unter Linux 107 3.5.4 Fortführende Migration – Netzwerkdienste unter Windows 2000 110 3.6 System-Überwachungs- und –Management-Dienste 111 Seite 2 INHALTSVERZEICHNIS 3.6.1 Überblick 111 3.6.2 Ausgangslage – Systems Management Server unter Windows NT 4 112 3.6.3 Ablösende Migration – Linux 114 3.6.4 Fortführende Migration – Windows 2000 117 3.7 Verzeichnisdienst 118 3.7.1 Überblick 118 3.7.2 Grundlagen 119 3.7.3 Active Directory Service (ADS) 123 3.7.4 Ablösende Migration – Samba und OpenLDAP 138 3.7.5 Fortführende Migration – Einführung ADS 143 3.8 Middleware – COM,.NET, J2EE 150 3.8.1 Component Object Model (COM) 151 3.8.2 „.NET“ 152 3.8.3 Java 2 Enterprise Edition (J2EE) 153 3.9 Web Services 155 3.9.1 Überblick 155 3.9.2 Grundlagen 156 3.9.3 .Net Web-Services 157 3.9.4 J2EE 158 3.10 XML (Extensible Markup Language) 158 3.11 Webserver 160 3.11.1 Überblick 160 3.11.2 Einleitung 160 3.11.3 Internet Information Server 4.0 161 3.11.4 Ablösende Migration 164 3.11.5 Fortführende Migration 171 3.12 SharePoint Portal Server 173 3.12.1 Überblick 173 3.12.2 Einleitung 174 3.12.3 Dashboardsite 174 3.12.4 Dokumentenmanagementsystem (DMS) 176 3.12.5 Suchfunktionen 176 3.12.6 Fazit 176 Seite 3 INHALTSVERZEICHNIS 3.13 Datenbanken 177 3.13.1 Überblick 177 3.13.2 Einleitung 177 3.13.3 MS SQL Server 7.0 178 3.13.4 Ablösende Migration 183 3.13.5 Fortführende Migration 190 3.14 Groupware 191 3.14.1 Überblick 191 3.14.2 Einleitung 192 3.14.3 Ausgangslage – Microsoft Exchange 5.5 193 3.14.4 Ablösende Migration 198 3.14.5 Fortführende Migration 217 3.15 Office / Desktop 223 3.15.1 Überblick 223 3.15.2 Einleitung 223 3.15.3 Ausgangslage MS Office 224 3.15.4 Ablösende Migration 228 3.15.5 Fortführende Migration 247 3.15.6 Weitere Desktopanwendungen 251 3.15.7 Integration von Windows-Anwendungen beim Einsatz von Linux-Client 260 3.15.8 Bewertung 272 3.16 Terminal-Server und Thin Clients 274 3.16.1 Überblick 274 3.16.2 Einleitung 274 3.16.3 Linux-Terminal-Server-Projekt 279 3.16.4 Terminalservices NX 280 3.16.5 Windows Terminal Services und Citrix 281 3.17 Hochverfügbarkeit 284 3.17.1 Ziele 284 3.17.2 Die „fünf Neunen“ und die Realität 285 3.17.3 Vorgehensweise 285 3.17.4 Kategorien von HA-Systemen 287 3.17.5 Proprietäre HA-Software 288 Seite 4 INHALTSVERZEICHNIS 3.17.6 Open Source HA-Software 289 4 Wirtschaftlichkeitsbetrachtung................................. 293 4.1 Einleitung 293 4.2 Methodische Grundsätze 294 4.2.1 Monetäre Analyse 295 4.2.2 Nutzwert-Analyse 295 4.2.3 IT-WiBe 21 295 4.2.4 Migrations-Kosten-Matrix 296 4.2.5 TCO 297 4.2.6 Vergleichbarkeit 297 4.2.7 Neueinführung vs. Migration von Systemen 299 4.2.8 Vollkostenansatz 299 4.3 Monetäre (operative) Dimension 300 4.3.1 Einsatzbereiche 300 4.3.2 Kostenkategorien 301 4.3.3 Eigenschaften angewandter Behördenkategorien 302 4.4 Strategische Dimension 303 4.4.1 Makroökonomische Betrachtung 304 4.4.2 Mikroökonomische Betrachtung 304 4.5 Gesamtergebnisse der Wirtschaftlichkeitsbetrachtung 304 4.6 Migrationsempfehlungen aufgrund der Wirtschaftlichkeitsbetrachtung 306 4.6.1 Vollständige Migration 308 4.6.2 Fortführende Migration 309 4.6.3 Teilmigration 310 4.7 Fazit 312 4.8 Aufwände für unterschiedliche Migrationsszenarien 313 4.8.1 Allgemeine Annahmen für Migrationsaufwände 313 4.8.2 Migrationsaufwände von Windows NT nach Windows 2000 314 4.8.3 Migrationsaufwände von Windows NT nach Linux 317 4.8.4 Migrationsaufwände von Exchange 5.5 nach Exchange 2000 320 Seite 5 INHALTSVERZEICHNIS 4.8.5 Migrationsaufwände von Exchange 5.5 nach Samsung Contact 322 4.8.6 Einschätzungsempfehlungen zu Produkten/ Produktgruppen 323 4.9 Beispiel Bewertung Dringlichkeit und Qualität/ Strategie 352 4.9.1 Dringlichkeits-Kriterien 353 4.9.2 Qualitativ-strategischen Kriterien 353 4.9.3 Nutzwertanalyse 353 5 Migrationsempfehlungen........................................... 360 5.1 Grundsätzliche Aussagen 360 5.1.1 Weg der Entscheidungsfindung 360 5.1.2 Grundsatzempfehlungen 361 5.2 Vollständig „Ablösende Migration“ 363 5.2.1 Architekturmodell 364 5.2.2 Mittlere und große Behörden 368 5.2.3 Spezialisierte Behörden mit IT-Dienstleistung 371 5.2.4 Kleine Behörden 373 5.3 Vollständig „Fortführende Migration“ 375 5.3.1 Minimierung des Grades an Integration, Bewahrung von Freiheitsgraden 377 5.3.2 Weitere Migrationspfade 379 5.4 Teilmigration 380 5.4.1 Punktuelle Migration 380 5.4.2 Serverseitige Teilmigration 382 5.5 Migrationswege 383 5.5.1 Schnelle Migration 383 5.5.2 Sanfte Migration 385 5.5.3 Kritische Erfolgsfaktoren 387 6 Mitwirkende Experten ................................................ 400 7 Abkürzungsverzeichnis ............................................. 401 Seite 6 INHALTSVERZEICHNIS 8 Glossar........................................................................ 410 9 Tabellenverzeichnis ................................................... 416 10 Abbildungsverzeichnis .............................................. 419 11 Anhang ........................................................................ 423 11.1 Anhang -WiBe 423 11.1.1 Überblick empfohlener Kriterienkataloge 423 11.1.2 Genereller Kriterienkatalog IT-WiBe21 für Migrationsszenarien 423 11.1.3 Spezieller Kriterienkatalog IT-WiBe21 für Migrationsobjekte 428 11.1.4 Erläuterung ergänzter Kriterien 431 Seite 7 Einleitung 1 Einleitung „Ein Produkt ersetzt ein anderes, wenn es den Abnehmern einen Umstellungsan- reiz bietet, der stärker ist als die Umstellungskosten, oder der den Widerstand gegen die Umstellung überwindet. Ein Ersatzprodukt bietet einen Umstellungsan- reiz, wenn es im Vergleich zu seinem Preis dem Abnehmer einen höheren Wert als das bislang benutzte Produkt bietet.“ M.E. Porter 1.1 Über das Vorhaben Kaum eine Formulierung beschreibt den Kern der seit einiger Zeit in der Öffent- lichkeit intensiv stattfindenden Diskussion über den Einsatz der Open Source Software besser als dieser eher einfache Grundsatz des Harvard Business School Professors zu den Grundlagen der Wettbewerbsfähigkeit. Das Open Source Flaggschiff Linux hat im Bereich der Betriebssysteme schon längst die Position eines – aus der Sicht der Wettbewerbstheorie etablierten „Ersatzproduk- tes“ – erreicht, andere Softwareprodukte wie MySQL oder Open Office sind auf dem Weg dorthin. (Für diejenigen, die in dieser Aufstellung den OSS-Klassiker Apache vermissen, sei die Feststellung erlaubt, dass es sich nach Meinung der Autoren bei diesem Produkt selbst um das Original und nicht um einen Ersatz handelt). Insbesondere das Freie Betriebssystem Linux ist eines der wenigen Software- produkte überhaupt, das heute über kontinuierliche Wachstumsraten verfügen und in der Zwischenzeit in über 40% der deutschen Unternehmen und Organisa- tionen produktiv eingesetzt wird2, mit steigender Tendenz. Angesichts dieser Entwicklung müsste die Frage nach den Anreizen, die zu dieser Entwicklung der Open Source Software geführt haben, leicht zu beantworten sein.
Load more

Recommended publications
  • Email Issues
    EMAIL ISSUES - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - TABLE OF CONTENTS NEW POLICY WITH RESPECT TO EMAIL ADDRESSES A NECESSARY EMAIL SETTING WHY OUR EMAILS POSSIBLY ARRIVED LATE OR NOT AT ALL STOP USING YAHOO, NETZERO, AND JUNO EMAIL PROVIDERS - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - NEW POLICY WITH RESPECT TO EMAIL ADDRESSES: There are two important issues here. FIRST, members must not supply CFIC with their company email addresses. That is, companies that they work for. (If you own the company, that's different.) All email on a company's server can be read by any supervisor. All it takes is one pro vaccine activist to get hold of our mobilization alerts to throw a monkey wrench in all of our efforts. Thus, do not supply me with a company email address. We can help you get an alternative to that if necesary. SECONDLY, CFIC needs members' email addresses to supply important information to mobilize parents to do things that advances our goal to enact our legislative reforms of the exemptions from vaccination. That has always been CFIC's sole agenda. CFIC has been able to keep the membership fee to zero because we don't communicate via snail mail. But people change their addresses frequently and forget to update CFIC. When this happens over the years, that member is essentually blind and deaf to us, and is no longer of any value to the coalition---your fellow parents. Therefore, it warrants me to require that members supply CFIC with their most permanent email account. That means the email address of the company in which you are paying a monthly fee for internet access, be it broadband or dialup service.
    [Show full text]
  • SMTP (Simple Mail Transfer Protocol)
    P1: JsY JWBS001A-60.tex WL041/Bidgoli WL041-Bidgoli.cls May 12, 2005 3:27 Char Count= 0 SMTP (Simple Mail Transfer Protocol) Vladimir V. Riabov, Rivier College Introduction 1 SMTP Security Issues 12 SMTP Fundamentals 1 SMTP Vulnerabilities 12 SMTP Model and Protocol 2 SMTP Server Buffer Overflow Vulnerability 15 User Agent 4 Mail Relaying SMTP Vulnerability 15 Sending e-Mail 4 Mail Relaying SMTP Vulnerability in Microsoft Mail Header Format 4 Windows 2000 15 Receiving e-Mail 4 Encapsulated SMTP Address Vulnerability 15 The SMTP Destination Address 4 Malformed Request Denial of Service 16 Delayed Delivery 4 Extended Verb Request Handling Flaw 16 Aliases 5 Reverse DNS Response Buffer Overflow 16 Mail Transfer Agent 5 Firewall SMTP Filtering Vulnerability 16 SMTP Mail Transaction Flow 5 Spoofing 16 SMTP Commands 6 Bounce Attack 16 Mail Service Types 6 Restricting Access to an Outgoing Mail SMTP Service Extensions 8 Server 17 SMTP Responses 8 Mail Encryption 17 SMTP Server 8 Bastille Hardening System 17 On-Demand Mail Relay 8 POP and IMAP Vulnerabilities 17 Multipurpose Internet Mail Extensions Standards, Organizations, and (MIME) 8 Associations 18 MIME-Version 10 Internet Assigned Numbers Authority 18 Content-Type 10 Internet Engineering Task Force Working Content-Transfer-Encoding 10 Groups 18 Content-Id 11 Internet Mail Consortium 18 Content-Description 11 Mitre Corporation 18 Security Scheme for MIME 11 Conclusion 18 Mail Transmission Types 11 Glossary 18 Mail Access Modes 11 Cross References 19 Mail Access Protocols 11 References 19 POP3 11 Further Reading 22 IMAP4 12 INTRODUCTION and IMAP4), SMTP software, vulnerability and security issues, standards, associations, and organizations.
    [Show full text]
  • Understanding Post Office Protocol (POP3)
    Understanding Post Office Protocol (POP3) Author: Conrad Chung, 2BrightSparks Introduction Most Internet users with email accounts would have used some form of “client” software (Outlook, Thunderbird etc.) to access and manage their email at one point or another. To retrieve emails, these email clients may require the configuration of Post Office Protocol (or POP3) before messages can be downloaded from the server. This article will help readers understand what POP3 is and how it works. What is Post Office Protocol? The Post Office Protocol (POP3) is an Internet standard protocol used by local email software clients to retrieve emails from a remote mail server over a TCP/IP connection. Since the first version was created in 1984, the Post Office Protocol (currently at Version 3) has since became one of the most popular protocols and is used by virtually every email client to date. Its popularity lies in the protocol’s simplicity to configure, operate and maintain. Email servers hosted by Internet service providers also use POP3 to receive and hold emails intended for their subscribers. Periodically, these subscribers will use email client software to check their mailbox on the remote server and download any emails addressed to them. Once the email client has downloaded the emails, they are usually deleted from the server, although some email clients allow users to specify that mails be copied or saved on the server for a period of time. Email clients generally use the well-known TCP port 110 to connect to a POP3 server. If encrypted communication is supported on the POP3 server, users can optionally choose to connect either by using the STLS command after the protocol initiation stage or by using POP3S, which can use the Transport Layer Security (TLS) or Secure Sockets Layer (SSL) on TCP port 995 to connect to the server.
    [Show full text]
  • What Is the Difference Between Email Protocols
    What Is The Difference Between Email Protocols Interactions between email servers and users are governed by email protocols. The most common incoming email protocols are POP, and IMAP. Most email applications/programs support one or more of these. This article is to help users understand and choose which protocol should be selected for each user’s situation. Outgoing Incoming POP (Post Office Protocol): IMAP (Internet Message Access Protocol): SSL (Secure Socket Layer): Differences Between POP and IMAP Backups / Email Loss Outgoing SMTP (Simple Mail Transfer Protocol) is the protocol used in sending (outgoing) emails. SMTP is the protocol always used for sending (outgoing) emails. Incoming POP (Post Office Protocol) and IMAP (Internet Message Access Protocol) are two different protocols that do the same thing differently. They are both used in receiving emails from a mail server and can both are available for standard and secure (?) connections. POP (Post Office Protocol): POP is an email accessing protocol used to download emails from a mail server. Applications like Outlook and Outlook Express using POP will download all emails from the server to the user’s computer, and then delete them on the server. Generally POP server uses port 110 to listen to the POP requests or securely using SSL (Secure Socket Layer) (?) POP uses port number 995. The POP protocol assumes that there is only one client/computer that will be connecting to the mailbox. Even though there is an option in most mail applications to leave the copies of the emails in the server, it is not generally used due to various reasons.
    [Show full text]
  • Ii Jacobs Rp316
    !II JACOBS RP316 RACIBORZ FLOOD RESERVOIR Public Disclosure Authorized Resettlement Action Plan Public Disclosure Authorized DRAFT Public Disclosure Authorized Public Disclosure Authorized March 2005 JACOBS Document control sheet Form IP180/B Client: PCU Project: Odra Flood Mitigation Job No: J24201A Title: Draft Resettlement Action Plan Prepared by Reviewed by Approved by ORIGINAL0 NAME NAME NAME P Devitt L J S Attewill see list of authors H Fiedler-Krukowicz J Loch | DATfE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE REVISION NAME NAME NAME DATE SIGNATURE SIGNATURE SIGNATURE This report, and infonnabon or advice which it contains, is provided by JacobsGIBB Ltd solely for internal use and reliance by its Cient in performance of JacobsGIBB Ltd's duties and liabilities under its contract with the Client Any advice, opinions, or recomrnendatons within this report should be read and retied upon only in the context of the report as a whole. The advice and opinions in this report are based upon the information nmadeavailable to JacobsGIBB Ltd at the date of this report and on current UK standards, codes, technology and constnuction practices as at the date of this report. Folloving final delvery of this report to the Client, JacobsGIBB Ltd will have no further obligations or duty to advise She Client on any mafters, including developrrient affecting the information or advice provided in ths report This report has been prepared by JacobsGIBB Ltd in their professional capaaty as Consuhing Engineers The contents of the report do not, in any way, purport to include any mranner of legal advice or opinion This report is prepared in accordance wrth the terms and conditions of JacobsGIBB Ltd's contract with the Client.
    [Show full text]
  • HTTP Cookie - Wikipedia, the Free Encyclopedia 14/05/2014
    HTTP cookie - Wikipedia, the free encyclopedia 14/05/2014 Create account Log in Article Talk Read Edit View history Search HTTP cookie From Wikipedia, the free encyclopedia Navigation A cookie, also known as an HTTP cookie, web cookie, or browser HTTP Main page cookie, is a small piece of data sent from a website and stored in a Persistence · Compression · HTTPS · Contents user's web browser while the user is browsing that website. Every time Request methods Featured content the user loads the website, the browser sends the cookie back to the OPTIONS · GET · HEAD · POST · PUT · Current events server to notify the website of the user's previous activity.[1] Cookies DELETE · TRACE · CONNECT · PATCH · Random article Donate to Wikipedia were designed to be a reliable mechanism for websites to remember Header fields Wikimedia Shop stateful information (such as items in a shopping cart) or to record the Cookie · ETag · Location · HTTP referer · DNT user's browsing activity (including clicking particular buttons, logging in, · X-Forwarded-For · Interaction or recording which pages were visited by the user as far back as months Status codes or years ago). 301 Moved Permanently · 302 Found · Help 303 See Other · 403 Forbidden · About Wikipedia Although cookies cannot carry viruses, and cannot install malware on 404 Not Found · [2] Community portal the host computer, tracking cookies and especially third-party v · t · e · Recent changes tracking cookies are commonly used as ways to compile long-term Contact page records of individuals' browsing histories—a potential privacy concern that prompted European[3] and U.S.
    [Show full text]
  • Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University
    Toward an Automated Vulnerability Comparison of Open Source IMAP Servers Chaos Golubitsky – Carnegie Mellon University ABSTRACT The attack surface concept provides a means of discussing the susceptibility of software to as-yet-unknown attacks. A system’s attack surface encompasses the methods the system makes available to an attacker, and the system resources which can be used to further an attack. A measurement of the size of the attack surface could be used to compare the security of multiple systems which perform the same function. The Internet Message Access Protocol (IMAP) has been in existence for over a decade. Relative to HTTP or SMTP, IMAP is a niche protocol, but IMAP servers are widely deployed nonetheless. There are three popular open source UNIX IMAP servers – UW-IMAP, Cyrus, and Courier-IMAP – and there has not been a formal security comparison between them. In this paper, I use attack surfaces to compare the relative security risks posed by these three products. I undertake this evaluation in service of two complementary goals: to provide an honest examination of the security postures and risks of the three servers, and to advance the study of attack surfaces by performing an automated attack surface measurement using a methodology based on counting entry and exit points in the code. Introduction Contributions and Roadmap System administrators frequently confront the The paper makes two major contributions. First, problem of selecting a software package to perform a I undertake an in-depth discussion of the relative secu- desired function. Many considerations affect this deci- rity postures of the three major open source IMAP sion, including functionality, ease of installation, soft- servers in use today.
    [Show full text]
  • Downloadable Email Program for My Pc 32 Best Free Email Clients
    downloadable email program for my pc 32 Best Free Email Clients. Here are 32 best free email client software . These let you manage and access all of your email accounts in one single place easily. All these email client software are completely free and can be downloaded to Windows PC. These free software offer various features, like: can be used with IMAP, SMTP, POP3 and Gmail, keeps your emails safe and secure, lets you open various emails simultaneously, provide protection from spam, lets you view your emails offline, manage and access all of your email accounts in one single place, supports PH, LDAP, IMAP4, POP3 and SMPT mail protocols etc. So, go through this list of free email client software and see which ones you like the most. Thunderbird. Thunderbird is a free and handy email client software for your computer. It can be used with IMAP, SMTP, POP3 and Gmail. It will also work with email accounts provided by MS Exchange Server. The user interface of Thunderbird is tabbed. It lets you open various emails simultaneously. Thunderbird keeps your emails safe and secure. It also has special filters for filtering the mail. Windows Live Mail. Windows Live Mail is a free email client for your computer. It works with various email accounts. It lets you access Yahoo, Gmail, Hotmail and emails from different servers which supports POP3 and SMTP. Its security features are excellent it will also provide protection from spam. You can also view your emails offline in this freeware. Zimbra Desktop. Zimbra Desktop is a free email client.
    [Show full text]
  • [MS-STANOPOP3]: Outlook Post Office Protocol Version 3 (POP3) Standards Compliance
    [MS-STANOPOP3]: Outlook Post Office Protocol Version 3 (POP3) Standards Compliance Intellectual Property Rights Notice for Open Specifications Documentation . Technical Documentation. Microsoft publishes Open Specifications documentation for protocols, file formats, languages, standards as well as overviews of the interaction among each of these technologies. Copyrights. This documentation is covered by Microsoft copyrights. Regardless of any other terms that are contained in the terms of use for the Microsoft website that hosts this documentation, you may make copies of it in order to develop implementations of the technologies described in the Open Specifications and may distribute portions of it in your implementations using these technologies or your documentation as necessary to properly document the implementation. You may also distribute in your implementation, with or without modification, any schema, IDL’s, or code samples that are included in the documentation. This permission also applies to any documents that are referenced in the Open Specifications. No Trade Secrets. Microsoft does not claim any trade secret rights in this documentation. Patents. Microsoft has patents that may cover your implementations of the technologies described in the Open Specifications. Neither this notice nor Microsoft's delivery of the documentation grants any licenses under those or any other Microsoft patents. However, a given Open Specification may be covered by Microsoft's Open Specification Promise (available here: http://www.microsoft.com/interop/osp) or the Community Promise (available here: http://www.microsoft.com/interop/cp/default.mspx). If you would prefer a written license, or if the technologies described in the Open Specifications are not covered by the Open Specifications Promise or Community Promise, as applicable, patent licenses are available by contacting iplg@microsoft.com.
    [Show full text]
  • NBG6515 User's Guide
    NBG6515 AC750 Dual-Band Wireless Gigabit Router Version 1.00 Edition 1, 01/2016 Quick Start Guide User’s Guide Default Details LAN IP Address - Router Mode http://192.168.1.1 (Default mode) - AP/Repeater http://192.168.1.2 Mode www.zyxel.com User Name admin Password 1234 2.4G SSID ZyXEL + Last 6 digits of the 2.4G MAC address (ZyXEL734916) 5G SSID ZyXEL+ Last 6 digits of the 5G MAC address + .speed (ZyXEL734917.speed) Pre-shared Key Serial number + Random key Copyright © 2016 ZyXEL Communications Corporation IMPORTANT! READ CAREFULLY BEFORE USE. KEEP THIS GUIDE FOR FUTURE REFERENCE. Screenshots and graphics in this book may differ slightly from your product due to differences in your product firmware or your computer operating system. Every effort has been made to ensure that the information in this manual is accurate. Related Documentation •Quick Start Guide The Quick Start Guide shows how to connect the NBG and access the Web Configurator. Note: It is recommended you use the Web Configurator to configure the NBG. •More Information Go to support.zyxel.com to find other information on the NBG. NBG6515 User’s Guide 2 Contents Overview Contents Overview User’s Guide ....................................................................................................................................... 11 Getting to Know Your NBG .....................................................................................................................12 Connection Wizard ..................................................................................................................................17
    [Show full text]
  • Groupwise Internet Agent
    GroupWise Internet Agent April 7, 2000 Novell Confidential Manual Rev 99a24 8 February 00 Legal Notices Novell, Inc. makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to revise this publication and to make changes to its content, at any time, without obligation to notify any person or entity of such revisions or changes. Further, Novell, Inc. makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, Novell, Inc. reserves the right to make changes to any and all parts of Novell software, at any time, without any obligation to notify any person or entity of such changes. This product may require export authorization from the U.S. Department of Commerce prior to exporting from the U.S. or Canada. Copyright © 1993-1999 Novell, Inc. All rights reserved. No part of this publication may be reproduced, photocopied, stored on a retrieval system, or transmitted without the express written consent of the publisher. U.S. Patent Nos. 4,555,775; 4,580,218; 5,412,772; 5,701,459; 5,717,912; 5,760,772; 5,870,739; 5,873,079; 5,884,304; 5,903,755; 5,913,209; 5,924,096; 5,946,467; D393,457 and U.S. Patents Pending. Novell, Inc. 122 East 1700 South Provo, UT 84606 U.S.A. www.novell.com GroupWise Internet Agent February 2000 104-001304-001 Online Documentation: To access the online documentation for this and other Novell products, and to get updates, see www.novell.com/documentation.
    [Show full text]
  • Persistent E-Mail Identification Is Viable!
    Proceedings of the 4th International Workshop on Semantic Digital Archives (SDA 2014) Persistent e-mail identification is viable! Stefan Haun and Andreas N¨urnberger Data and Knowledge Engineering Group, Faculty of Computer Science, Otto-von-Guericke-University Magdeburg, Germany http://www.dke.ovgu.de Abstract. Persistent identification of entities in Personal Information Management (PIM) is necessary to enable stable, long-term references in archives and semantic applications. In the case of e-mails, the standard offers Message-IDs (MID), which are widely deployed. However, stores do not use the MID but rather rely on a path, which is likely to change, to refer to e-mails and thus do not offer a stable identification. We show that MIDs are viable to identify and retrieve e-mails from an IMAP store in real-world scenarios. The presented concept can be integrated into any store, but we also offer a software solution that serves as an additional layer above the store and allows real-time access over MID. We propose a validation method to prove that the concept is working and some applications that are enabled by e-mail identification are sketched. 1 Introduction Sending e-mails has long replaced traditional letters, especially in the business and research context. Being digital, e-mails can be easily stored and accessed from different locations, building up large archives as part of the personal infor- mation managed by each user. Although a central element of communication, e-mails are still tied to special software, the Mail User Agent, instead of being integrated into the overall workflow.
    [Show full text]