DOCSLIB.ORG

IMAP Index.Pdf

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Index Symbols frontend server 282–285 *, in server reply 31 allowanonymouslogin (Cyrus option) 203 *, wildcard for LIST 300 allowsubscribes (Cyrus option) 287 ., as mailbox separator (Cyrus) 205, 235, 238 allowusermoves (Cyrus option) 287 /, as mailbox separator (Cyrus) 205, 235, 238 altnamespace (Cyrus option) 277 % (wildcard), for LIST 300 annotation database (Cyrus) 259 8-bit characters see eight-bit characters annotation_db (Cyrus parameter) 259 annotations.db (file) 267, 278 A \Answered (flag) 35 a (permission) 37 in the filename (maildir) 113 access permissions see ACLs searching for 305 access time, of a file see atime APOP 27, 28, 148 account options see user options (Courier) POP3 command 317, 319 ACLs 34, 36, 37, 154 AppArmor 193 Cyrus 231, 232 APPEND (IMAP command) 302 group-based (Courier) 144 Apple Mail 279 identifier 154 aquota.user (file) 168 IMAP extension 34, 316 arbitron 263 activating (Courier) 102 arbitronsort.pl (tool) 190, 269 listing (Cyrus) 272 atime, switching off 57–58, 64 manipulating (Courier) see maildiracl (tool) attachments, retrieving individually (IMAP) 310 negative permissions 155 AUTH (IMAP extension) 315 removing (Cyrus) 272 AUTH (POP3 command) 317, 319 saving in Courier see courierimapacl (file) AUTH=PLAIN (capability) 296 setting (Cyrus) 272 authcram (Courier) 120, 129, 144, 148 switching off at filesystem level 58 authcustom (Courier) 121, 130 for virtual domains (Cyrus) 236, 237 authdaemond (Courier) active directory with user data 81 activating 99 ADDRESS (Courier parameter) 98 configuration file see authdaemonrc address (Sieve command) 246 starting 88 administration directory (Cyrus) 203 daemon 20, 121–123 administrator, creating (Cyrus) 194 configuration file see authdaemonrc admins (Cyrus option) 203, 287, 288 custom authentication modules see aggregator 51, 281–290 authcustom backend server 282, 286–287 using with Cyrus SASL 189, 213 331 The Book of IMAP (C) 2008 by Peer Heinlein and Peer Hartleben Index authdaemonrc (Courier configuration file) 95, authProg (authentication tool) 131 123, 134, 145 authpwd (authentication module for Courier) AUTHENTICATE (IMAP command) 218, 297 120, 143 Authenticated (IMAP status) 32 authshadow (authentication module for Courier) available commands 298–303 120, 143 switching to 303 authtest (tool) 121–122 Authenticated Post Office Protocol see APOP authuserdb (authentication module for Courier) authentication see logging in 120, 124–129, 144 by fingerprint 213 authvchkpw (authentication module for Courier) by hash values instead of passwords 213 120 by iris scan 213 autocreate_sieve_script (Cyrus option) 251 Cyrus 207–224 autocreatequota (Cyrus option) 203, 226, 251 via Kerberos 212, 214, 223–224 autologout timer, resetting 296 via LDAP 212–214, 220–223 auxprop (Cyrus SASL module) 189, 194, 213 via MySQL 213, 216–220 LDAP connection via 220, 221 via PAM 219–220 MySQL connection via 216 via SQL database 213 availability 19, 43–51 daemon (Courier) see authdaemond avelsieve (Squirrelmail plugin) 244 choosing method (POP3) 319 choosing method (Courier) 99, 122 B IMAP commands 297 backup (IMAP folders) 29 library (Courier) see Courier Authlib backup (main Cyrus database) 278 password in cleartext 210 backup/ (directory) 278 POP3 commands 317 BALANCE (iptables) 47 programs, custom (Courier) 121 Bcc header, searching in 305 proxy (Courier) see authdaemond benchmark tools 55 authenumerate 160 berkeley (Cyrus database format) 259 tool 138, 145 berkeley-nosync (Cyrus database format) 259 authldap (authentication module for Courier) berkeley_cachesize (Cyrus parameter) 258 121, 140–146 berkeley_txns_max (Cyrus parameter) 258 caching requests 122 block size, for NFS 64 authldaprc (file) 95, 140 body authlib 120–144 retrieving (IMAP) 310 AUTHMODULES (Courier parameter) 99, 122, retrieving partially (IMAP) 311 123 retrieving partially (POP3) see TOP (POP3 authmysql (authentication module for Courier) command) 120, 133–139, 144, 147 searching in 305 caching requests 122 bonnie 55 authmysqlrc (file) 134–139 byte-octet conversion 296 authorization state (POP3) 317 authpam (Courier) 120, 123–124 C authpgsql c (permission) 37 authentication module for Courier 120, 139, CA see certificate authority (CA) 140, 144, 147 cache proxy 51, 73–74 caching requests 122 cached IMAP see offline IMAP file 139 CAPA (POP3 command) 319 authpipe (Courier) 121, 131–133 capabilities 33 332 The Book of IMAP (C) 2008 by Peer Heinlein and Peer Hartleben Index for encrypted communication (IMAP) 297 configuration parameters polling (IMAP) 296 Courier 96–105 polling (POP3) 319 reading out (Courier) 100 specifying for Courier 100 connection CAPABILITY (IMAP command) 175, 295, 296, 314 information, caching (SSL) 260 for encrypted communication 297 keeping open see NOOP case sensitive terminating folder names 301 automatically for POP3 (Cyrus) 259 search 40 with IMAP see LOGOUT (IMAP com- Cc header, searching in 306 mand) cell phone (and IMAP) 176, 273 with POP3 see QUIT (POP3 com- certificate authority (CA) 208 mand) 318 list in email clients 208 unintended (IMAP) 32 trustworthy 208 testing see NOOP certificates see SSL certificates contents, of an email see body challenge-response procedure 129, 148, 242, 297 convert-sieve.pl (tool) 190, 269 change time, of a file see ctime COPY (IMAP command) 313 character encoding, considering during a search using the Unique ID 313 305 Courier 18, 85–179 character set, considering during a search 305 configuration 95–105 CHECK (IMAP command) 303 configuring SSL encryption 102–105 CHILDREN (IMAP extension) 34, 315 crashing 93 chk_cyrus 264 vs. Cyrus 20–21 chmod, influence on c and mtime 57 downloading 322 cleartext IMAP proxy 50, 145 login see LOGIN (IMAP command) installation 86–87 passwords 81 installing from the source code 321, 324 client, workaround for faulty 101 migration problems 110 CLOSE (IMAP command) 32, 303 misleading reply to LIST (POP3) 25 cluster 20 MTA 85 Cyrus 281, 291 paths 87 Cluster filesystem, as email repository 45 project 85 CLUSTERIP (iptables) 47 Courier Authlib 85 cm see createmailbox Courier team com_err.h (Common Error library) 329 reaction to bug reports 93 compile_sieve (tool) 268 reaction to change requests 110 compiling courierimapacl (file) 109, 154–155 Courier 321, 324 courierimapkeywords (directory) 116 Cyrus 325, 330 courierimapsubscribed (file) 109 CONCAT (SQL command) 137 courierlogger (tool) 98, 103 conditional query (Sieve) see if (Sieve) couriertcpd 88 Cone 85 specifying command-line parameters 98 config2header (tool) 269 COURIERTLS (Courier parameter) 104 config2man (tool) 269 couriertls (tool) 87, 104 configdirectory CPU see processor Cyrus option 203 CRAM 129 Cyrus parameter 270 CRAM-MD5 100, 119, 148, 214 333 The Book of IMAP (C) 2008 by Peer Heinlein and Peer Hartleben Index using with Cyrus 213 installation 184–187 when testing the login with imtest 218 under Debian 186 CRAM-SHA1 100, 119, 148 under Red Hat 186 CRAM-SHA256 148 from source code 325, 330 crash, Courier 93 under SuSE 185 CREATE (IMAP command) 300 LMTP see LMTP createmailbox location in the filesystem 204 cyradm command 239 lowercase addresses 204 cyradmin command 272 maximum email size 204 creating users Murder cluster 51, 281–290 Cyrus 194 ports 191 with saslpasswd2 194 and Postfix 191–197 Crispin, Mark 33 project origins 183 crypt Red Hat source RPM for 186 hash, instead of cleartext password 119 refusing to accept email (quota) 204 as password hash algorithm 147 SASL authentication methods 205 ctime 57 Sieve directory 205 ctl_cyrusdb (tool) 266 SSL certificates 205 ctl_deliver 266 user vs. Unix system account 215 ctl_mboxlist 266 working directory 188 cur Cyrus (IMAP server) for creating directories 88 data security 255, 257 for listing contents of a directory 108, 112 domain administrators 237 for listing purpose of a directory 108 notify daemon 252 cvt_cyrusdb 267 operating with other MTAs 254, 255 cyr_expire (tool) 202, 268 sorting email 237 cyradm (tool) 21, 194, 271–274, 277 specifying a timeout 205 setting quotas 228 virtual domains 232 setting up shared folders 230 Cyrus Aggregator see aggregator cyrdump (tool) 267 Cyrus SASL see libsasl Cyrus 18, 183–291 library 190 activating SSL support 210 cyrus-admin-2.2 (Debian package) 186 administration information 277–280 cyrus-clients-2.2 (Debian package) 186 as administration tool see cyradm, (tool) cyrus-common-2.2 (Debian package) 186 allowing anonymous users 203 cyrus-imap-utils (Red Hat package) 186 connecting to MySQL 213, 216–220 cyrus-imapd connecting to PostgreSQL 213 Red Hat package 186 vs. Courier 20–21 SuSE package 185 creating an administrator 194 cyrus-imapd-2.2 (Debian package) 187 creating users 194 cyrus-murder-2.2 (Debian package) 187 with saslpasswd2 194 cyrus-nntpd-2.2 (Debian package) 187 directory hierarchy 187 cyrus-pop3d-2.2 (Debian package) 187 downloading 325 cyrus-sasl encrypting access data 189 package 189 and firewalls 191, 220 Red Hat package 186 function test 195–197 cyrus-sasl-crammd5 (SuSE package) 185 IMAP proxy 51 cyrus-sasl-digestmd5 (SuSE package) 185 334 The Book of IMAP (C) 2008 by Peer Heinlein and Peer Hartleben Index cyrus-sasl-otp (SuSE package) 185 possible (Cyrus) 259 cyrus-sasl-plain quota database (Cyrus) 260 Red Hat package 186 quotalegacy (Cyrus) 260 SuSE package 185 subscription database (Cyrus) 260 cyrus-sasl-saslauthd (SuSE package) 185 date cyrus-sasl-sqlauxprop (SuSE package) 185 as search criterion 305, 307 cyrus.cache (file) 276 determining the internal (IMAP) 311 cyrus.conf 188, 199–202, 266 format in IMAP commands 305 checkpoint 202 db.backup1/ (directory) 278 cleanup
Recommended publications
  • Oldschool E-Mail Setup Eine Freakshow

    Oldschool E-Mail Setup Eine Freakshow

    Oldschool E-mail Setup Eine Freakshow [email protected] Chemnitzer Linuxtage, 2016 (Screenshot GMX vor >15 Jahren: Waybackmachine zu www.gmx.net) (Screenshot GMX heute) (Screenshot Gmail heute) Lösungen? ● Claws ● Mutt ● Eudora ● Netscape Navigator ● Evolution ● Opera M2 ● GMX ● Outlook ● Gnus ● SquirrelMail ● Hotmail ● The Bat! ● Hushmail ● Thunderbird ● KMail ● … Flußgrafik Email Netz MTA MRA MDA MUA MSA MTA Netz Hipster! ● KISS ● YAGNI ● DRY ● NIH ● Divide And Conquer ● Everything is a file ● No vendor lock-in ● Mißtraue Autoritäten – fördere Dezentralisierung Netz Netz Emails Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools mbox Maildir mh Client, den ich Remote verwenden kann Leicht erweiterbar Emails lokal Filter Offenes Format Adressen Netz Netz Abholen Transportformat? Pull Subject 1 Email = 1 File Keine Spuren X-List-ID Mit Hierarchien am Server Beliebige Einfaches Suchen Header Verlässliches Suchen Verarbeitung mit Unix Tools mbox Maildir mh tmp 1439306571.1269_0.elvis ~/Post/Technik/Wikitech new 1448267819.5940_0.spencer ... 1457079728.2000_0.spencer:2, cur 1456839383.9873_0.nepomuk:2,SR 1457166567.23654_0.spencer:2,S ... Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header fetchmail getmail mpop ..
  • Email Issues

    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.
  • Thanos Tsouanas --- C.V

    Thanos Tsouanas --- C.V

    Curriculum Vitæ Thanos Tsouanas 02/05/2017 I Personal details hello photo full name: Athanasios (Thanos) Tsouanas date of birth: 22/02/1983 place of birth: Athens, Greece nationality: Hellenic office address: IMD, Universidade Federal do Rio Grande do Norte Av. Cap. Mor Gouveia, S/N CEP: 59063-400, Natal{RN, Brasil phone number: (+55) (84) 9 8106-9789 (mobile, Telegram, WhatsApp) email address: [email protected] personal website: http://www.tsouanas.org/ GitHub: http://github.com/tsouanas Spoken languages Greek (native); English (proficient); Brazilian Portuguese (fluent). I Studies & academic positions 2016 { Associate professor (permanent position) in Instituto Metr´opole Digital of Universidade Federal do Rio Grande do Norte (UFRN), Brazil. 2015 Postdoctoral researcher in the Mathematics Department of Universidade Federal do Rio Grande do Norte (UFRN), Brazil. 2014 PhD from Ecole´ Normale Superieure´ de Lyon, under the supervision of Olivier Laurent, in the field of theoretical computer science. I was employed by CNRS under the Marie Curie fellowship \MALOA", and had a 1-month secondment split between the University of Oxford (in the team of Luke Ong) and Ecole´ Polytechnique (in the team of Dale Miller). Thesis title: On the Semantics of Disjunctive Logic Programs1 2010 Master of Science degree from MPLA (graduate program in Logic, Algorithms and Computation of the University of Athens and of the Technical University of Athens),2 mathematical logic specialty, grade 8.23/10. 2007 Bachelor's degree from the Department of Mathematics of the University of Athens, specialty of pure mathematics, grade \excellent" (8.51/10). Seminars and schools • Logoi school on Linear Logic and Geometry of Interaction.
  • Diplomarbeit Kalenderstandards Im Internet

    Diplomarbeit Kalenderstandards Im Internet

    Diplomarbeit Kalenderstandards im Internet Eingereicht von Reinhard Fischer Studienkennzahl J151 Matrikelnummer: 9852961 Diplomarbeit am Institut für Informationswirtschaft WIRTSCHAFTSUNIVERSITÄT WIEN Studienrichtung: Betriebswirtschaft Begutachter: Prof. DDr. Arno Scharl Betreuender Assistent: Dipl.-Ing. Mag. Dr. Albert Weichselbraun Wien, 20. August 2007 ii Inhaltsverzeichnis Abbildungsverzeichnis vi Abkürzungsverzeichnis vii 1 Einleitung 1 1.1 Problemstellung . 1 1.2 Inhalt und Vorgehensweise . 3 2 Standards für Kalender im Internet 5 2.1 iCalendar und darauf basierende Standards . 6 2.1.1 iCalendar und vCalendar . 6 2.1.2 Transport-Independent Interoperability Protocol (iTIP) . 8 2.1.3 iCalendar Message-Based Interoperability Protocol (iMIP) . 8 2.1.4 iCalendar über WebDAV (WebCAL) . 10 2.1.5 Storage of Groupware Objects in WebDAV (GroupDAV) . 11 2.1.6 Calendaring and Scheduling Extensions to WebDAV (CalDAV) . 12 2.1.7 IETF Calendar Access Protocol (CAP) . 13 2.2 XML-basierte Formate . 15 2.2.1 XML iCalendar (xCal) . 15 2.2.2 RDF Calendar (RDFiCal) . 16 2.2.3 RDFa (RDF/A) . 16 2.2.4 OWL-Time . 17 2.3 Mikroformate (hCalendar) . 18 2.4 SyncML . 20 2.5 Weitere Formate . 21 2.6 Zusammenfassung . 22 iii 3 Offene Kalenderanwendungen im Internet 24 3.1 Server . 24 3.1.1 Citadel/UX . 24 3.1.2 Open-Xchange . 26 3.1.3 OpenGroupware.org . 26 3.1.4 Kolab2 . 27 3.1.5 Weitere Server . 28 3.2 Clients . 29 3.2.1 Mozilla Calendar Project . 29 3.2.2 KDE Kontact . 30 3.2.3 Novell Evolution . 30 3.2.4 OSAF Chandler . 31 3.2.5 Weitere Open-Source- und Closed-Source-Clients .
  • Military-Grade Cyber Security

    Military-Grade Cyber Security

    MILITARY-GRADE CYBER SECURITY EdgeWave ePrism Email Security Email Archive Email Volume is Growing The volume of email your business has to process has grown over 500% in the last 10 years and there appears to be no decline in sight. It is likely the amount will continue to increase, pushing your organization’s email servers to the limit, resulting in costly downtime and reduced productivity. Of even greater concern are industry-wide legal and regulatory requirements mandating that you retain all your organization’s email in an unalterable state. A comprehensive email archiving solution will not only help you meet corporate, legal and regulatory requirements, it can also help your organization achieve other critical goals. • Simplify mailbox management, shrink storage costs and reduce backup windows • Protect critical business information and intellectual property • Accelerate legal discovery and enforce corporate email policies EdgeWave has the Solution EdgeWave Email Archive is a secure enterprise SaaS solution for storage management that retains your email in an unalterable state to help meet compliance requirements, provide litigation support and meet corporate best practices guidelines. EdgeWave’s policybased archiving and built-in reporting features combine with easy-to-use management tools to assure your archived messages are indexed and easy to retrieve whenever you need them. EdgeWave’s feature-rich email archiving supports client software integration, email stubbing to maximize server storage, mobilearchive access, litigation support tools, centralizing, importing all historical emails and more. EdgeWave Email Archive supports all major messaging servers including Exchange, Domino, GroupWise, and Linux-based environments and can be deployed easily with minimal resource expenditures.
  • Migrationsleitfaden

    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: [email protected]) 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
  • Postfix-Cyrus-Web-Cyradm-HOWTO

    Postfix-Cyrus-Web-Cyradm-HOWTO

    Postfix-Cyrus-Web-cyradm-HOWTO Luc de Louw luc at delouw.ch Revision History Revision 1.2.6 2004-03-30 Revised by: ldl Added minor additions and corrected to amavisd-new, corrected cronjob-time for freshclam Revision 1.2.5 2004-03-28 Revised by: ldl Added Anti-Virus and SPAM methods (amavisd-new, spamassassin, clamav), updated cyrus-imapd section with update instructions, added instruction to restrict imapd admin access. Revision 1.2.4 2003-11-30 Revised by: ldl Input from English proofreading, minor correction and enhancements from user-input, updated software mentioned in the HOWTO Revision 1.2.3 2003-03-24 Revised by: ldl Some minor correction and enhancements from user-input, updated software mentioned in the HOWTO Revision 1.2.2 2003-02-14 Revised by: ldl Lots of grammar and typos fixed. Some corrections to the pam_mysql Makefile Revision 1.2.1 2003-02-12 Revised by: ldl Non-official test-release: Added lots of fixes and updates. Added OpenSSL and more pam related stuff. Revision 1.2.0 2002-10-16 Revised by: ldl Added lot of user requests, updated the software mentioned in the HOWTO 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.
  • 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

    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.
  • Sysinfotools Maildir Converter

    Sysinfotools Maildir Converter

    SysInfoTools MailDir Converter SysInfoTools MailDir Converter Table of Contents 1. SysInfotools MailDir Converter .................................................................................. 2 2. Overview ................................................................................................................... 2 3. Getting Started .......................................................................................................... 3 Installation procedure ............................................................................................... 4 4. Order and Activation .................................................................................................. 4 How to Order ............................................................................................................ 4 How to Activate ......................................................................................................... 4 5. Using SysInfoTools MailDir Converter ....................................................................... 5 Understanding the User Interface .............................................................................. 6 Button Used .............................................................................................................. 6 How to use MailDir Converter Tool ............................................................................ 7 6. Uninstall the Software .............................................................................................. 13 7. Legal Notice ...........................................................................................................
  • Design and Management of Email Service

    Design and Management of Email Service

    Design and Management of Email Service Source : homepage.ntu.edu.tw/~jsc/2005-mail.ppt Outline Introduction to the architecture and operation of SMTP Design of a suitable email system – Webmail solutions Postfix and simple configuration samples Spam and virus filtering Conclusion 2 Overview Electronic mail service has already evolved into one of the major Internet applications. It is not only fundamental, but also a must. Users may become impatient when mails were delayed, not to mention failed to access their emails. – Imagine we meet the situation of power failure or cut of water supply 3 Architecture of a Simple Mail System Consists of the following components – MTA - Mail transfer agent Sending and forwarding emails Server end – MDA - Mail delivery agent Delivering emails to recipients’ mailbox Server end – Pop3/Imap4 Daemons For users to download their mailboxs Server end – MUA - Mail user agent Reading and composing emails 4 Client end Architecture of a Simple Mail System Protocols Used for Mail System Protocols – For computer programs to communicate with each other – Similar to languages that human beings speak SMTP – Simple Mail Transfer Protocol – Too simple to provide any “advanced features” Authentication Authorization POP3 – Post Office Protocol version 3 – Simple IMAP4 – Internet Message Access Protocol version 4 – Fully compatible with internet message standards, e.g. MIME. – Allow messages to be accessed from more than one computer. – Provide support for online, offline, and disconnected modes. 6 – Multiple and share folders. Mail Forwarding Between Servers How to Find the Way to the Destination? How do we find the way to [email protected]? 8 DNS: The Key to All Internet Services Query DNS server by the address part of email address.([email protected]) 1.
  • Freebsd Opengroupware - English

    Freebsd Opengroupware - English

    FreeBSD OpenGroupware - English FreeBSD As Basis For OpenGroupware.org PostgreSQL As Database FreeBSD can currently look back on a history of over 30 PostgreSQL, like BSD, originated at the University of Ca- years. It originated at the University of Berkeley and lifornia and is also distributed under the BSD license. It's FreeBSD evolved over a few intermediate steps into the project one of the oldest and most advanced object-relational founded in 1993 called FreeBSD. The supported architec- database management systems (ORDBMS) in the realm tures are the following: i386, amd64, Alpha, Itanium, of free software and looks back on a development of OpenGroupware.org SPARC, PPC (Mac) and others. over 15 years. PostgreSQL is largely conforming to the FreeBSD has very good support for multiprocessor sys- SQL92/SQL99 standards, that means that all functions in The ideal solution for professional the standards are available and behave as defined; that tems (SMP) and is distributed under the BSD license team communication on the Internet, which grants the user nearly every freedom and is free is not always the case with some commercial and non- commercial SQL database systems. of cost. Apart from having to name the origins of the with FreeBSD and PostgreSQL code, the user may use it in any which way he or she pleases. FreeBSD is a gift to humanity, we are pleased when you use it! FreeBSD has not only got many features, it also has a What is a groupware solution? huge amount of free and open software in its so-called Ports Collection.
  • 200106-Mutt.Pdf

    200106-Mutt.Pdf

    ●サポートしている機能 プロトコルに関しては、以下のものサポートしています。 Muttの概要 他のメーラでも対応しているプロトコルは、ほとんど実装し ていますが、送信に関しては、外部プログラムを使用するよ 皆さんは「Mutt」というMUA＊1をご存じでしょうか？ 非常 うになっています。ただし、一部のプロトコル＊3は、バー に軽快で高機能な割には、日本国内では知名度がイマイチで ジョン1.3以降だけで実装されています。 利用者も少ないMUAです。知名度が低い原因には、Muttに関 ・MIME（RFC2231も含む） する日本語の情報が少ないことが挙げられます。Muttに関す ・POP3、IMAP4 Rev.1 る日本語のWebサイトも片手の指で数えられるくらいしかあ ・POP/IMAP over SSL りませんし、UNIX系の雑誌でMuttに関する記事もほとんどあ りません＊2。 そこで本記事では、「Muttとは何ぞや」から始まり、インス トール、設定、メールの送受信が出来るまでの説明を行いま す。この記事を読んでMuttについて興味を持っていただけた ら幸いです。 Muttとは？ Muttは、Michael R. Elkins氏によって開発されたUNIX系OS の端末で動く、CUIなMUAです（記事末のRESOURCE［1］を 参照）。ユーザーインターフェイスや実装している機能は、 「ELM」、「pine」、「Mush」、「slrn」といった他のMUAやニュー ズリーダーを参考にして作られており、文字通り、「雑種犬 （mutt）」のようなメーラです（画面1）。 画面1 CUIながら、豊富なカラー対応など、見た目は派手（にもできる） ＊1 「Mail User Agent」あるいは「Message User Agent」の略。ユーザーによるメールの読み書きを補助するためのプログラム。メールリーダやメーラとも 呼ばれる。 ＊2 筆者の知る限り、これまで1つしか見たことはない。 Linux Japan June 2001 35 SPECIAL さらに、Mutt自身が持っていない機能（エディタや送信の機能 など）は外部プログラムを用いることになります。 ●安定版と開発版およびその日本語パッチ Muttは、安定版と開発版の2つのバージョンが公開されてい ます。現在は、安定版が「バージョン1.2」、開発版が「バージョ ン1.3」となっています。バージョン1.2までは、マルチバイト 文字をサポートしていなかったため、そのままでは日本語が 扱えず、吉田行範氏を中心として開発された日本語パッチが 必要でした。一方、バージョン1.3は、XPG5＊4の国際化機能が 画面2 インデックス一覧画面では、文字罫線でスレッドを表現 実装され、基本的には日本語を扱えるようになりました。し ・POP/IMAP over ssh かし、日本語特有の事情（いわゆる「ヘッダの生JIS問題」や「機 ・APOP、SASLによる認証 種依存文字の文字化け」など）があるため、そのままでは実用 ・DSN（Delivery Status Notification）、PGP/MIME 上、問題があります。そこで、筆者が中心となって、実際に ・mbox、MMDF、MH、Maildir形式のメールボックス 日本語を扱う上で問題となる点を修正し、ほぼ通常の利用に 表示に関しては以下のような特徴を持っています（画面2、 は差し支えないようにした日本語パッチを開発しています。 画面3、画面4）。 バージョン1.2とバージョン1.3の日本語パッチは全く別の実 装なので、バージョン1.2以前のものからバージョン1.3に移行 ・カラフルな表示