Postfix-Cyrus-Web-Cyradm-HOWTO
Total Page：16
File Type：pdf, Size：1020Kb
Load more
Recommended publications
-
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. -
Postfix−Cyrus−Web−Cyradm−HOWTO
Postfix−Cyrus−Web−cyradm−HOWTO Luc de Louw luc at delouw.ch Revision History Revision 1.2.0 2002−10−16 Revised by: ldl The first release of the 1.2 version. Revision 1.1.7 2002−10−15 Revised by: ldl Added Michael Muenz' hints for SMTP AUTH, corrected ca−cert related mistake, improved SGML code (more metadata), updated the software mentioned in the document. Revision 1.1.6 2002−06−14 Revised by: ldl Added sasl_mech_list: PLAIN to imapd.conf, added web−cyradm Mailinglist, added more to web−cyradm Revision 1.1.5 2002−06−11 Revised by: ldl Added new SQL query to initialize web−cyradm to have full data integrity in the MySQL Database, mysql−mydestination.cf reported to be operational as expected. Revision 1.1.4 2002−05−15 Revised by: ldl Added description what is needed in /etc/services Another fix for pam_mysql compile, updated software versions. Revision 1.1.3 2002−05−08 Revised by: ldl Added more description for web−cyradm, fix for wrong path of the saslauthdb−socket, Fix for wrong place of com_err.h, protection of the TLS/SSL private key. Revision 1.1.2 2002−04−29 Revised by: ldl Added description for Redhat users how to install the init scripts. Revision 1.1.1 2002−04−29 Revised by: ldl Fixed bug in configuring cyrus−IMAP (disabled unused kerberos authentication) Revision 1.1.0 2002−04−28 Revised by: ldl Initial support for building cyrus from source, dropped binary installation for Cyrus, because configuration has changed with Release 2.1.x Revision 1.0.2 2002−04−25 Revised by: ldl Added basic description for sieve and correct sender handling, minor fixes to db related stuff, Added mysql−lookup for »mydestination« , fixed bug for building postfix with mysql support. -
Brave Gnu World
LINUXCOVERCOMMUNITY USERSTORY SchlagwortSchlagwortBrave GNU sollte Worldsollte hier hier stehen stehen Schlagwort sollte hier stehen COVER STORY The Monthly GNU Column BRAVE GNU WORLD This column looks into projects and current affairs in the world of free software from the perspective of the GNU Project and the FSF. In this issue, I’ll focus on Comspari and the EU decision on software patents. BY GEORG C.F. GREVE n the past, the German government the Kroupware project in 2002. The pub- principles back to front. For example, has often caused a (positive) stir due lic tender by the BSI was aimed to pro- many other solutions are based on the Ito its activities with free software. duce a groupware solution that would principle that the server is the king of The Federal Ministry of the Economy support strong cryptography and inte- the hill and the users have to bow down (BMWi) sponsored Gnupg [1], for exam- grate seamlessly into a heterogeneous and worship it. The Kolab server does ple. Add to this a number of accompany- environment. things differently. The program makes ing activities, such as a report by the The government office gave a consor- the user king, and gives the user power Bavarian Accounts Office, the KBST let- tium comprising Erfrakon, Klarälvdalens to do things. The software simply helps ter, and the highly acclaimed migration Datakonsult [2], and Intevation [3] the coordinate things as a central intermedi- guide by the Federal Ministry of the Inte- task of developing the software. Inter- ary. rior (BMI). nally, the design and the software was Kolab 1 combined so-called partial referred to as Kolab 1. -
Analysis and Performance Optimization of E-Mail Server
Analysis and Performance Optimization of E-mail Server Disserta¸c~aoapresentada ao Instituto Polit´ecnicode Bragan¸capara cumprimento dos requisitos necess´arios `aobten¸c~aodo grau de Mestre em Sistemas de Informa¸c~ao,sob a supervis~aode Prof. Dr. Rui Pedro Lopes. Eduardo Manuel Mendes Costa Outubro 2010 Preface The e-mail service is increasingly important for organizations and their employees. As such, it requires constant monitoring to solve any performance issues and to maintain an adequate level of service. To cope with the increase of traffic as well as the dimension of organizations, several architectures have been evolving, such as cluster or cloud computing, promising new paradigms of service delivery, which can possibility solve many current problems such as scalability, increased storage and processing capacity, greater rationalization of resources, cost reduction, and increase in performance. However, it is necessary to check whether they are suitable to receive e-mail servers, and as such the purpose of this dissertation will concentrate on evaluating the performance of e-mail servers, in different hosting architectures. Beyond computing platforms, was also analze different server applications. They will be tested to determine which combinations of computer platforms and applications obtained better performances for the SMTP, POP3 and IMAP services. The tests are performed by measuring the number of sessions per ammount of time, in several test scenarios. This dissertation should be of interest for all system administrators of public and private organizations that are considering implementing enterprise wide e-mail services. i Acknowledgments This work would not be complete without thanking all who helped me directly or indirectly to complete it. -
Installation and Configuration Guide
Installation and Configuration Guide SOGo v5.1.1 Table of Contents 1. About this Guide . 2 2. Introduction . 3 2.1. Architecture and Compatibility . 3 3. System Requirements . 6 3.1. Assumptions . 6 3.2. Minimum Hardware Requirements. 6 3.3. Operating System Requirements . 7 4. Installation . 9 4.1. Software Downloads . 9 4.2. Software Installation . 10 5. Configuration. 11 5.1. GNUstep Environment Overview . 11 5.2. Preferences Hierarchy . 11 5.3. General Preferences . 12 5.4. Authentication using LDAP. 24 5.5. LDAP Attributes Indexing . 31 5.6. LDAP Attributes Mapping . 32 5.7. Authenticating using C.A.S.. 33 5.8. Authenticating using SAML2 . 35 5.9. Database Configuration . 35 5.10. Authentication using SQL . 40 5.11. SMTP Server Configuration . 43 5.12. IMAP Server Configuration. 44 5.13. Web Interface Configuration . 47 5.14. SOGo Configuration Summary. 57 5.15. Multi-domains Configuration . 58 5.16. Apache Configuration . 60 5.17. Starting Services . 61 5.18. Cronjob — EMail reminders. 61 5.19. Cronjob — Vacation messages activation and expiration . 62 6. Managing User Accounts . 63 6.1. Creating the SOGo Administrative Account . 63 6.2. Creating a User Account . 63 7. Microsoft Enterprise ActiveSync . 65 8. Microsoft Enterprise ActiveSync Tuning . 68 9. S/MIME Support in SOGo . 70 10. Using SOGo. 71 10.1. SOGo Web Interface. 71 10.2. Mozilla Thunderbird and Lightning . 71 10.3. Apple Calendar (macOS, iOS, iPadOS). 72 10.4. Apple AddressBook . 72 10.5. Microsoft ActiveSync . 73 11. Upgrading . 74 12. Additional Information . 76 13. Commercial Support and Contact Information . -
Measuring Attack Surfaces of Open Source IMAP Servers
Measuring Attack Surfaces of Open Source IMAP Servers E. Chaos Golubitsky May 2005 Abstract The attack surface metric 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. The attack surface metric can be used to compare the security of multiple systems which provide the same function. The Internet Message Access Protocol (IMAP) is a protocol which has been in existence for over a decade. Relative to web (HTTP) and e-mail transfer (SMTP) servers, IMAP servers are a niche product, but they 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 project, i use the attack surface metric to discuss 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. 1 Contents 1 Introduction 3 1.1 Contributions and Roadmap . 3 1.2 Attack Surfaces . 4 1.3 IMAP Servers . 5 2 Observation of IMAP Server Software 6 2.1 Observation Methodology . 6 2.2 High-Level Interactions of IMAP Servers . 7 2.3 UW-IMAP Server . -
Ausgesiebt Server-Seitige Mailfilter Mit Sieve Oder Wegsperren, Ohne Den Maildienst Damit Zu Belasten
Server-seitige Mailfilter mit Sieve Titelthema Ausgesiebt Sieve 54 E-Mails auf dem Server filtern befreit von überflüssigem Ballast: Die leistungsfähige Skriptsprache Sieve ist als RFC standardisiert. Unerwünschte Nachrichten mit Spam oder Viren können Sieve-Skripte automatisch löschen Linux-Magazin 06/07 06/07 Linux-Magazin oder wegsperren, ohne den Maildienst damit zu belasten. Markus Feilner nutzer mit einem Webmailer Abhilfe schafft erst der offene und per wie Squirrelmail an, stellt er RFC definierte Standard für die Server- enttäuscht fest, dass Spam seitige Filterung von E-Mail namens und Viren-Mails, die Kontact, Sieve [1]. Frühe Versionen dieser Fil- Evolution oder Outlook auto- tersprache wurden seit 1994 diskutiert, matisch löschen, immer noch 1999 veröffentlichte die Carnegie Mellon in seinem Posteingang auf University die Sieve-Implementation, die dem IMAP-Server landen. der Cyrus-POP/ IMAP-Server als erster Wenn verschiedene Mailpro- übernahm. Bereits im Jahre 2001 spezi- gramme zum Einsatz kom- fizierte RFC 3028 dann „Sieve – A Mail men, müssen alle Regeln Filtering Language“ [2]. Die einheitliche doppelt gepflegt und bei Mi- Sprache für Filterregeln umfasst auto- grationen mühselig von Hand matische Weiterleitung, Abwesenheits- zusammengeklickt werden, notizen und Sortieren von Nachrichten da die meisten Mailclients sowie zahlreiche Erweiterungen. über keine Import/ Export- Funktionen für Filterregeln Cyrus IMAP und Sieve verfügen. Der in vielen Groupwaresystemen inte- Server-basierte grierte Cyrus-IMAP-Server bietet neben Regeln POP und IMAP auch den Dienst »timsie- ved« für die Remote-Administration von Besser ist es daher, die Regeln Filterregeln über das Managesieve-Proto- gleich auf dem Mailserver koll [3]. Timsieved kommuniziert über zu speichern und zentral zu das Local Mail Transfer Protocol (LMTP, verwalten. -
Linux Journal | January 2011 | Issue
HTML5 | VLAN | SOGo | LVM 2 | Swap Space | KVM | Clonezilla ™ CLONEZILLA High-Performance Open-Source Cloning SOGo a Real Exchange Replacement Since 1994: The Original MagazineSystem of the Linux Community Administration LVM2 Snapshots for Data Backup Manage KVM Build Your with Virtual Own SAN Machine with AoE Manager TurnYour Fault Linux Box Tolerance into a VLAN with Ethernet Smart Bonding Switch Configure JANUARY 2011 | ISSUE 201 Swap Space for www.linuxjournal.com $5.99US $5.99CAN Stability and 01 Performance 0 09281 03102 4 More TFLOPS, Fewer WATTS Microway delivers the fastest and greenest floating point throughput in history 2.5 TFLOPS Enhanced GPU Computing with Tesla Fermi 480 Core NVIDIA® Tesla™ Fermi GPUs deliver 1.2 TFLOP single precision & 600 GFLOP double precision performance! New Tesla C2050 adds 3GB ECC protected memory New Tesla C2070 adds 6GB ECC protected memory Tesla Pre-Configured Clusters with S2070 4 GPU servers WhisperStation - PSC with up to 4 Fermi GPUs OctoPuter™ with up to 8 Fermi GPUs and 144GB memory New Processors 12 Core AMD Opterons with quad channel DDR3 memory 8 Core Intel Xeons with quad channel DDR3 memory Superior bandwidth with faster, wider CPU memory busses Increased efficiency for memory-bound floating point algorithms Configure your next Cluster today! 10 TFLOPS 5 TFLOPS www.microway.com/quickquote 508-746-7341 FasTree™ QDR InfiniBand Switches and HCAs 45 TFLOPS 36 Port, 40 Gb/s, Low Cost Fabrics Compact, Scalable, Modular Architecture Ideal for Building Expandable Clusters and Fabrics MPI Link-Checker™ and InfiniScope™ Network Diagnostics FasTree 864 GB/sec Achieve the Optimal Fabric Design for your Specific Bi-sectional Bandwidth MPI Application with ProSim™ Fabric Simulator Now you can observe the real time communication coherency of your algorithms. -
7 Configure the Network
7 Configure The Network Because the Ubuntu installer has configured our system to get its network settings via DHCP, we have to change that now because a server should have a static IP address. Edit /etc/network/interfaces and adjust it to your needs (in this example setup I will use the IP address 192.168.0.100): vi /etc/network/interfaces # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). # The loopback network interface auto lo iface lo inet loopback # The primary network interface auto eth0 iface eth0 inet static address 192.168.0.100 netmask 255.255.255.0 network 192.168.0.0 broadcast 192.168.0.255 gateway 192.168.0.1 Then restart your network: /etc/init.d/networking restart Then edit /etc/hosts. Make it look like this: vi /etc/hosts 127.0.0.1 localhost.localdomain localhost 192.168.0.100 server1.example.com server1 # The following lines are desirable for IPv6 capable hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters Now run echo server1.example.com > /etc/hostname /etc/init.d/hostname restart Afterwards, run hostname hostname -f Both should show server1.example.com now. 8 Edit /etc/apt/sources.list And Update Your Linux Installation Edit /etc/apt/sources.list. Comment out or remove the installation CD from the file and make sure that the universe and multiverse repositories are enabled. It should look like this: vi /etc/apt/sources.list # # deb cdrom:[Ubuntu-Server 11.10 -
Native Microsoft Outlook Configuration Guide for Version 2.3.22 Native Microsoft Outlook Configuration Guide Version 2.3.22 - July 2017
Native Microsoft Outlook Configuration Guide for version 2.3.22 Native Microsoft Outlook Configuration Guide Version 2.3.22 - July 2017 Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License". The fonts used in this guide are licensed under the SIL Open Font License, Version 1.1. This license is available with a FAQ at: http:// scripts.sil.org/OFL Copyright © Łukasz Dziedzic, http://www.latofonts.com, with Reserved Font Name: "Lato". Copyright © Raph Levien, http://levien.com/, with Reserved Font Name: "Inconsolata". Table of Contents About this Guide ............................................................................................................... 1 Introduction ...................................................................................................................... 2 Architecture ...................................................................................................................... 3 Requirements .................................................................................................................... 4 LDAP Server ............................................................................................................. 4 Microsoft Active Directory ........................................................................................ -
Databases Theoretical Introduction Contents
Databases Theoretical Introduction Contents 1 Databases 1 1.1 Database ................................................ 1 1.1.1 Terminology and overview .................................. 1 1.1.2 Applications .......................................... 2 1.1.3 General-purpose and special-purpose DBMSs ........................ 2 1.1.4 History ............................................ 2 1.1.5 Research ........................................... 6 1.1.6 Examples ........................................... 6 1.1.7 Design and modeling ..................................... 7 1.1.8 Languages ........................................... 9 1.1.9 Performance, security, and availability ............................ 10 1.1.10 See also ............................................ 12 1.1.11 References .......................................... 12 1.1.12 Further reading ........................................ 13 1.1.13 External links ......................................... 14 1.2 Schema migration ........................................... 14 1.2.1 Risks and Benefits ...................................... 14 1.2.2 Schema migration in agile software development ...................... 14 1.2.3 Available Tools ........................................ 15 1.2.4 References .......................................... 15 1.3 Star schema .............................................. 16 1.3.1 Model ............................................ 16 1.3.2 Benefits ............................................ 16 1.3.3 Disadvantages ....................................... -
DISTRIBUTED SYSTEMS CONTENTS 1.0 Aim And
UNIT – I LESSON 1: DISTRIBUTED SYSTEMS CONTENTS 1.0 Aim and Objectives 1.1. Introduction 1.2. Organization 1.3. Goals and Advantages 1.4. Disadvantages 1.5. Architecture 1.6. Concurrency 1.7. Languages 1.8. Let us Sum UP 1.9. Lesson-End Activities 1.10. Points for Discussion 1.11. References 1.0. AIM AND OBJECTIVES At the end of this Lesson you will be able to understand the concept of Distributed Computing, organization of Distributed Computing, advantages and limitations of Distributed Computing 1.1. INTRODUCTION Distributed computing is a method of computer processing in which different parts of a program are run simultaneously on two or more computers that are communicating with each other over a network. Distributed computing is a type of segmented or parallel computing, but the latter term is most commonly used to refer to processing in which different parts of a program run simultaneously on two or more processors that are part of the same computer. While both types of processing require that a program be segmented—divided into sections that can run simultaneously, distributed computing also requires that the division of the program take into account the different environments on which the different sections of the program will be running. For example, two computers are likely to have different file systems and different hardware components. An example of distributed computing is BOINC, a framework in which large problems can be divided into many small problems which are distributed to many computers. Later, the small results are reassembled into a larger solution.