Oldschool E-Mail Setup Eine Freakshow

Total Page:16

File Type:pdf, Size:1020Kb

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 ... Client, den ich Remote POP3 verwenden kann IMAP Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header fetchmail getmail mpop ... Client, den ich Remote POP3 verwenden kann IMAP Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header fetchmail getmail mpop ... Client, den ich Remote POP3 verwenden kann IMAP Leicht erweiterbar Filter Adressen Netz Netz Abholen Pull Subject Maildir Keine Spuren X-List-ID am Server Beliebige Header fetchmail getmail mpop ... Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Subject fetchmail X-List-ID Maildir Beliebige Header Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Subject fetchmail X-List-ID Maildir Beliebige Header procmail maildrop Sieve ... Client, den ich Remote verwenden kann Leicht erweiterbar Filter Adressen Netz Netz Subject fetchmail X-List-ID Maildir Beliebige Header procmail maildrop Sieve ... Client, den ich Remote verwenden kann Leicht erweiterbar Netz Netz fetchmail procmail Maildir Eigenbau, weil nichts passt Client, den ich Remote verwenden kann Leicht erweiterbar Netz Netz fetchmail procmail Maildir mutt Gnus Thunderbird ... Client, den ich Remote verwenden kann Leicht erweiterbar Netz Netz fetchmail procmail Maildir mutt Gnus Thunderbird ... Client, den ich Remote verwenden kann Leicht erweiterbar Netz Netz fetchmail procmail Maildir mutt Netz Netz fetchmail procmail Maildir mutt Netz Netz msmtp fetchmail procmail Maildir 1995 mutt Netz Netz msmtp fetchmail procmail Maildir 2000 1994 1990 1995 Flußgrafik Email Netz MTA MRA MDA MUA MSA MTA Netz fetchmail procmail mutt msmtp 1994 1990 1995 2000 mutt Netz Netz msmtp fetchmail procmail Maildir Netz OpenSSH IMAP mutt Netz Netz msmtp fetchmail procmail Maildir mutt Netz Netz msmtp fetchmail procmail Maildir OpenSSL lynx GnuPG Emacs display forumscraper Gramps twitter4email .mailcap evince innd irc2email unzip cups mutt nntp3email nntpposter rss3email Netz Netz msmtp fetchmail procmail Maildir ClamAV mairix Wiedervorlagen apache spamassasin Tagging Archivierung feedgenerator OpenSSL lynx GnuPG Emacs display forumscraper Gramps twitter4email .mailcap evince innd irc2email unzip cups mutt nntp3email nntpposter rss3email Netz Netz msmtp fetchmail procmail Maildir ClamAV mairix Wiedervorlagen apache spamassasin Tagging Archivierung feedgenerator → Feedback: [email protected].
Recommended publications
  • Resurrect Your Old PC
    Resurrect your old PCs Resurrect your old PC Nostalgic for your old beige boxes? Don’t let them gather dust! Proprietary OSes force users to upgrade hardware much sooner than necessary: Neil Bothwick highlights some great ways to make your pensioned-off PCs earn their keep. ardware performance is constantly improving, and it is only natural to want the best, so we upgrade our H system from time to time and leave the old ones behind, considering them obsolete. But you don’t usually need the latest and greatest, it was only a few years ago that people were running perfectly usable systems on 500MHz CPUs and drooling over the prospect that a 1GHz CPU might actually be available quite soon. I can imagine someone writing a similar article, ten years from now, about what to do with that slow, old 4GHz eight-core system that is now gathering dust. That’s what we aim to do here, show you how you can put that old hardware to good use instead of consigning it to the scrapheap. So what are we talking about when we say older computers? The sort of spec that was popular around the turn of the century. OK, while that may be true, it does make it seem like we are talking about really old hardware. A typical entry-level machine from six or seven years ago would have had something like an 800MHz processor, Pentium 3 or similar, 128MB of RAM and a 20- 30GB hard disk. The test rig used for testing most of the software we will discuss is actually slightly lower spec, it has a 700MHz Celeron processor, because that’s what I found in the pile of computer gear I never throw away in my loft, right next to my faithful old – but non-functioning – Amiga 4000.
    [Show full text]
  • Design Document
    SPEC OSG Mailserver Subcommittee SPECmail2009 Benchmark Architecture White Paper Revision: v1.0 Date: 22 December 2008 Copyright © 2001-2009 Standard Performance Evaluation Corporation. All Rights Reserved. 1. Introduction 1.1 Overview SPECmail2009 is a software benchmark designed to measure a system's ability to act as an enterprise mail server servicing email requests, based on the Internet standard protocols SMTP and IMAP4. The benchmark concentrates on the workload encountered by corporate mail servers, with an overall user count in the range of 150 to 10,000 (or more) users. It models IMAP business users accessing IMAP servers over fast local area networks (LAN) instead of broadband, WAN or dialup access speeds. Two separate metrics measure e-mail servers with and without secure network connections (SSL). SPECmail2009 has been developed by the Standard Performance Evaluation Corporation (SPEC), a non-profit group of computer vendors, system integrators, universities, research organizations, publishers, and consultants. This paper discusses the benchmark principles and architecture, and the rationale behind the key design decisions. It also outlines the workload used in the benchmark, and the general steps needed to run a benchmark. However those aspects are covered in more detail in other documents. 1.2 Organization of this Paper Chapter 2 discusses the basic goals and non-goals of the benchmark. Chapter 3 introduces the two performance metrics for SPECmail2009 – IMAP sessions per hour - and how it relates to the transaction mix imposed on the system under test.. Chapter 4 explains the benchmark workload - how it was derived, how it translates into configuration parameters for the benchmark tool and size calculations for planning a benchmark, and how it relates to the benchmark metric.
    [Show full text]
  • Cyrus Mail Server 2 Table of Contents
    Univention Corporate Server Cyrus mail server 2 Table of Contents 1. Introduction ........................................................................................................................ 4 2. Installation ......................................................................................................................... 5 3. Management of the mail server data ....................................................................................... 6 3.1. Management of mail domains ..................................................................................... 6 3.2. Assignment of e-mail addresses to users ........................................................................ 6 3.3. Management of mailing lists ....................................................................................... 7 3.4. Management of mail groups ........................................................................................ 7 3.5. Management of shared IMAP folders ........................................................................... 8 3.6. Mail quota ............................................................................................................... 9 4. Spam detection and filtering ................................................................................................ 10 5. Identification of viruses and malware .................................................................................... 11 6. Identification of Spam sources with DNS-based Blackhole Lists (DNSBL) ...................................
    [Show full text]
  • 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 ...........................................................................................................
    [Show full text]
  • Symantec White Paper
    QUARTERLY REPORT: SYMANTEC ENTERPRISE SECURITY SYMANTEC REPORT: QUARTERLY Symantec Intelligence Quarterly July - September, 2009 Published October 2009 Technical Brief: Symantec Enterprise Security Symantec Intelligence Quarterly July - September, 2009 Contents Introduction . 1 Highlights . 2 Metrics. 2 Meeting the Challenge of Sophisticated Attacks . 8 Timeline of a zero-day event . 8 How secure are security protocols?. 11 Why attackers use packers. 14 Protection and Mitigation . 16 Appendix A—Best Practices . 18 Appendix B—Methodologies. 20 Credits . 24 Symantec Intelligence Quarterly July - September, 2009 Introduction Symantec has established some of the most comprehensive sources of Internet threat data in the world through the Symantec™ Global Intelligence Network. More than 240,000 sensors in over 200 countries monitor attack activity through a combination of Symantec products and services such as Symantec DeepSight™ Threat Management System, Symantec™ Managed Security Services and Norton™ consumer products, as well as additional third-party data sources. Symantec also gathers malicious code intelligence from more than 130 million client, server, and gateway systems that have deployed its antivirus products. Additionally, the Symantec distributed honeypot network collects data from around the globe, capturing previously unseen threats and attacks and providing valuable insight into attacker methods. Spam data is captured through the Symantec probe network, a system of more than 2.5 million decoy email accounts, Symantec MessageLabs™ Intelligence, and other Symantec technologies in more than 86 countries from around the globe. Over 8 billion email messages, as well as over 1 billion Web requests, are scanned per day across 16 data centers. Symantec also gathers phishing information through an extensive antifraud community of enterprises, security vendors, and more than 50 million consumers.
    [Show full text]
  • Designing a User Interface for the Innovative E-Mail Client Semester Thesis
    Designing a User Interface for the Innovative E-mail Client Semester Thesis Student: Alexandra Burns Supervising Professor: Prof. Bertrand Meyer Supervising Assistants: Stephanie Balzer, Joseph N. Ruskiewicz December 2005 - April 2006 1 Abstract Email Clients have become a crucial application, both in business and for per- sonal use. The term information overload refers to the time consuming issue of keeping up with large amounts of incoming and stored email. Users face this problem on a daily basis and therefore benefit from an email client that allows them to efficiently search, display and store their email. The goal of this thesis is to build a graphical user interface for the innovative email client developed in a previous master thesis. It also explores the possibilities of designing a user interface outside of the business rules that apply for commercial solutions. 1 Contents 1 Introduction 4 2 Existing Work 6 2.1 ReMail ................................. 6 2.1.1 Methods ............................ 6 2.1.2 Problems Identified ...................... 7 2.1.3 Proposed Solutions ...................... 7 2.1.4 Assessment .......................... 8 2.2 Inner Circle .............................. 8 2.2.1 Methods ............................ 8 2.2.2 Problems Identified ...................... 9 2.2.3 Proposed Solutions ...................... 9 2.2.4 Assessment .......................... 10 2.3 TaskMaster .............................. 10 2.3.1 Methods ............................ 10 2.3.2 Problems Identified ...................... 11 2.3.3 Proposed Solution ...................... 11 2.3.4 Assessment .......................... 12 2.4 Email Overload ............................ 12 2.4.1 Methods ............................ 12 2.4.2 Problems Identified ...................... 13 2.4.3 Proposed Solutions ...................... 13 2.4.4 Assessment .......................... 14 3 Existing Solutions 16 3.1 Existing Email Clients .......................
    [Show full text]
  • Mathematics Department's New Email Service
    Mathematics Department’s New Email Service The department’s new email service employs the widely-used IMAP email protocol to allow you to read and organize your email. You may use the Math web-based email service, http://webmail.math.vt.edu, and/or email software on Unix systems, such as elm, mutt or pine. The IMAP protocol stores your email on a department server computer that daily saves your email and files to backup tapes. The server does not have an infinite supply of disk storage, so you will need to periodically delete email you no longer need or transfer it to your PC or Mac for archival.1 You may use the webmail service in conjunction with other email applications. Elm Elm is no longer supported. You may use mutt which is very similar. Pine Before running pine, you must update your existing pine settings with this command, /local/calvin/bin/updatepinerc PID where PID is your Virginia Tech PID. This will create a new .pinerc file in your home directory containing settings for using the new Math Email system. A copy of your original .pinerc file is named .pinerc-pre4.64 in your home directory. If you have previously used an older version of pine, any of your old settings that were not migrated to the new .pinerc will be listed. These are saved in a file named pinerc- settings. If you want to continue using any old settings, you must edit .pinerc to include them. Pine groups mailboxes into collections. One collection will be any mailboxes on the mail server.
    [Show full text]
  • 22Nd International Congress on Acoustics ICA 2016
    Page intentionaly left blank 22nd International Congress on Acoustics ICA 2016 PROCEEDINGS Editors: Federico Miyara Ernesto Accolti Vivian Pasch Nilda Vechiatti X Congreso Iberoamericano de Acústica XIV Congreso Argentino de Acústica XXVI Encontro da Sociedade Brasileira de Acústica 22nd International Congress on Acoustics ICA 2016 : Proceedings / Federico Miyara ... [et al.] ; compilado por Federico Miyara ; Ernesto Accolti. - 1a ed . - Gonnet : Asociación de Acústicos Argentinos, 2016. Libro digital, PDF Archivo Digital: descarga y online ISBN 978-987-24713-6-1 1. Acústica. 2. Acústica Arquitectónica. 3. Electroacústica. I. Miyara, Federico II. Miyara, Federico, comp. III. Accolti, Ernesto, comp. CDD 690.22 ISBN 978-987-24713-6-1 © Asociación de Acústicos Argentinos Hecho el depósito que marca la ley 11.723 Disclaimer: The material, information, results, opinions, and/or views in this publication, as well as the claim for authorship and originality, are the sole responsibility of the respective author(s) of each paper, not the International Commission for Acoustics, the Federación Iberoamaricana de Acústica, the Asociación de Acústicos Argentinos or any of their employees, members, authorities, or editors. Except for the cases in which it is expressly stated, the papers have not been subject to peer review. The editors have attempted to accomplish a uniform presentation for all papers and the authors have been given the opportunity to correct detected formatting non-compliances Hecho en Argentina Made in Argentina Asociación de Acústicos Argentinos, AdAA Camino Centenario y 5006, Gonnet, Buenos Aires, Argentina http://www.adaa.org.ar Proceedings of the 22th International Congress on Acoustics ICA 2016 5-9 September 2016 Catholic University of Argentina, Buenos Aires, Argentina ICA 2016 has been organised by the Ibero-american Federation of Acoustics (FIA) and the Argentinian Acousticians Association (AdAA) on behalf of the International Commission for Acoustics.
    [Show full text]
  • Postfix Catch All and Mutt
    Postfix Catch All and Mutt End goal: having postfix saving all of the emails for a domain to a single “mailbox” in maildir format, and being able to send email using mutt (or similar). Specifics to my setup I'm not going to open port 25 on my server, I'm going through Net7's spam filter, which will then forward to my server on port 8025. So I need to open port 8025. The rule was already there for port 25, I just need to edit the thing. Make Postfix listen to another port There is always the plan of using iptables to redirect the traffic. You can do it in Postfix as well. Open master.cf and find this line: smtp inet n - - - - smtpd The smtp word up front is actually a port. You can replace it with this line: 8025 inet n - - - - smtpd If you restart Postfix and check with netstat it should be listening to another port. Setting up Maildir delivery By default Postfix will output emails to a single file in /var/mail/. I'd rather have the Maildir format which separates emails into different files that I can individually move and/or delete. I'm going off the rails here trying out things. Looks like we're going to need these configuration options in main.cf: home_mailbox = Maildir/ mailbox_command = Make sure mailbox_command isn't set somewhere else in the file. Reload Postfix. We should be able to test that this is working using a known user on the system. You can telnet-test like so: EHLO test MAIL FROM:<[email protected]> RCPT TO:<william> DATA Test.
    [Show full text]
  • Webfaction User Guide
    WebFaction User Guide WebFaction is a service of Paragon Internet Group Limited CONTENTS 1 Introduction 3 1.1 Services..................................................3 1.2 The Complete System..........................................4 2 The Control Panel 5 2.1 Log in to the Control Panel.......................................5 2.2 Change Your Control Panel Password..................................5 2.3 What to Do About a Lost Password...................................6 2.4 Two-Step Login.............................................6 3 Finding Details About Your Server9 3.1 Finding Your Server’s Name.......................................9 3.2 Finding Your Server’s Operating System................................9 3.3 Finding Your Server’s IP Address.................................... 10 4 Accessing Your Data 11 4.1 Connecting with SSH.......................................... 11 4.2 Connecting with FTP........................................... 14 4.3 Changing Your FTP or SSH Password.................................. 14 4.4 Additional Users............................................. 15 4.5 Backups................................................. 16 5 Accounts 17 5.1 Plans and Services............................................ 17 5.2 Communicating with WebFaction.................................... 18 5.3 Payments................................................. 19 5.4 Affiliate Program............................................. 23 5.5 Canceling Your Account......................................... 24 6 Domains 25 6.1 Getting
    [Show full text]
  • Implementing POP3 and IMAP4 Using Dovecot
    Implementing POP3 and IMAP4 Using Dovecot AfNOG 2017 Scalable Internet Services (SS-E) Nairobi, Kenya Presented by Kevin Chege (Built on materials developed by Joel Jaeggli) What is POP3 § POP3 stands for Post Office Protocol ver 3 § Described in RFC1913 § Runs on TCP Port 110 as a client server function § Allows for a maildrop service (similar to the post box mail service ) hence the name § By design its limited in features to download and delete email from server § Security was also limited to using APOP (md5 hash for authentication § RFC 2449 proposed POP3 extensions which included SASL Mechanism, Expiry, Pipelining, etc. § RFC 2595 describes using TLS with POP3 also known as POP3s and runs on port 995 What is IMAP4? § Internet Message Access Protocol version 4 § Described in RFC 1730 § Runs on TCP Port 143 as client-server function § More advanced in features compared to POP3 § IMAP4 stores mail on server and copies can be transferred to the client on request. § By default only the message headers are sent to the client, the rest of the message is accessed on opening the email. § Allows client to access and manipulate email residing on a server, creation of folders, filters, etc. § RFC 1731 describes the IMAP Authentication Mechanisms § RFC 2595 describes using TLS with IMAP4 running on TCP port 993 Mail Storage Formats § Mailbox Format (Mbox) § Defined in RFC 4155 § All messages in an Mbox mailbox are concatenated and stored as a plain text in a single file § Mails are stored in RFC822 format with a blank space separating each message (2 spaces as each message has one space) and “From” determining start of next message.
    [Show full text]
  • Configuring and Using Mutt
    Configuring and Using Mutt Ryan Curtin LUG@GT Ryan Curtin Configuring and Using Mutt - p. 1/21 Goals » Goals By the end of this presentation, hopefully, you should be able Introduction to: Basic Usage Know the differences between Mutt, Pine, and other CLI Making a muttrc mailreaders Questions and Comments? Know the capabilities of Mutt Configure Mutt to connect to GT PRISM accounts (IMAP) Configure Mutt to make parsing through mail easy Know basic Mutt commands Write a basic, working .muttrc Know where to find further reference on Mutt Ryan Curtin Configuring and Using Mutt - p. 2/21 What is Mutt? » Goals Mutt is a “small, but very powerful text-based mail client for Introduction Unix operating systems” » What is Mutt? » Why should I use mutt? » Comparison with Pine Based largely on the elm mail client » What else is out there? Highly customizable; keybindings, macros Basic Usage Features to support mailing-lists (list-reply) Making a muttrc Questions and Comments? IMAP, POP3 support MIME, DSN, PGP support Ryan Curtin Configuring and Using Mutt - p. 3/21 Why should I use mutt? » Goals Lightweight, fast, and simple Introduction » What is Mutt? » Why should I use mutt? Can run inside a screen session » Comparison with Pine » What else is out there? No need for an annoying mouse Basic Usage Making a muttrc It looks cool Questions and Comments? Ryan Curtin Configuring and Using Mutt - p. 4/21 Comparison with Pine » Goals Mutt is lighter (and presumably faster) Introduction » What is Mutt? » Why should I use mutt? Mutt supports more authentication methods » Comparison with Pine » What else is out there? Mutt has better encryption (PGP/MIME/OpenPGP) Basic Usage Making a muttrc Mutt is still in active development (Pine stopped at 4.64; Questions and Comments? development moved to Alpine) Ryan Curtin Configuring and Using Mutt - p.
    [Show full text]