DOCSLIB.ORG

CYRUS: BUILD YOUR TUTORIAL OWN EMAIL SERVER Don’T Trust Google? We’Ll Help You Navigate the Sea of JOHN LANE Acronyms to Build Your Own Mailserver

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
CYRUS: BUILD YOUR TUTORIAL OWN EMAIL SERVER Don’T Trust Google? We’Ll Help You Navigate the Sea of JOHN LANE Acronyms to Build Your Own Mailserver TUTORIAL MAILSERVER CYRUS: BUILD YOUR TUTORIAL OWN EMAIL SERVER Don’t trust Google? We’ll help you navigate the sea of JOHN LANE acronyms to build your own mailserver. ou can’t beat the convenience and ease of use access their mail by connecting to the server using WHY DO THIS? offered by Gmail. But unfortunately, all that any IMAP-capable email client application. • Take control of your Yfree storage comes at a price: your privacy. You will need a, preferably new, server for this email provision. Spam, intrusive adverts and snooping from unnamed project and you’ll need root access to it. Our examples • Stop outside agencies government agencies are the inevitable downside of use Arch Linux, and we created a new virtual server. from scanning the using someone else’s service for free. So why not Begin by installing Cyrus (build the Arch User content of your emails. build your own email server including anti-spam, Repository package first – see the boxout below-right): • Get webmail without advertising. anti-virus and webmail? $ pacman -U ~build/cyrus-imapd/cyrus-imapd-2.4.17-5-x86_64. You can use your own server to retrieve messages pkg.tar.xz from other mailservers, such as those provided by The default configuration writes data to /var/imap internet service providers, or other services like those and user mailboxes to /var/spool/imap. You can from Google and Yahoo. But you don’t need to rely on change this if you prefer another location; we’ll others if you have your own server. If you have a configure our server to use /srv/mail/cyrus to domain name that you control, and if you can give your illustrate this. If you follow suit, you can also delete the server a static public IP address then you can receive default locations: email directly. rm -r /var/spool/imap /var/imap We’re going to implement a sealed server, which Some command line tools are installed to /usr/lib/ means that users cannot cyrus/bin so it’s worth extending your PATH (do it in log in to it. They have /etc/profile to make this permanent): “Why not build your own email email accounts that are export PATH=”$PATH”:/usr/lib/cyrus/bin only accessible using There are two configuration files, and the first of server, including anti-spam, client applications that these is /etc/cyrus/cyrus.conf. It defines the services anti-virus and webmail?” connect to the server that the server will offer, and the default file is generally using IMAP, the Internet acceptable unless, like us, you want to change the data Message Access path. This requires one entry in the file to be altered: Protocol (we could, but won’t, also use the older Post lmtpunix cmd=”lmtpd” listen=”/srv/mail/cyrus/socket/lmtp” Office Protocol, POP). prefork=0 You can give your test account a meaningful At the heart of the system is the IMAP server, Cyrus. The listen argument points to the Unix domain name and enter your This accepts messages using a protocol called the socket where the server accepts LMTP protocol own name in the identity Local Mail Transfer Protocol, or LMTP, and stores them connections. We change this to be in a subdirectory of section. in mailboxes – it’s a mail delivery agent. Users can our chosen data path. You can also take this opportunity to disable unwanted services; we commented out pop3 and pop3s because we plan to offer IMAP-only access. The second file, /etc/cyrus/imapd.conf, configures the IMAP server and needs to be written from scratch. The following example will get you started, but you may want to read the documentation and configure it to meet your needs. configdirectory: /srv/mail/cyrus partition-default: /srv/mail/cyrus/mail admins: cyrus sasl_pwcheck_method: saslauthd sasl_saslauthd_path: /var/run/saslauthd/mux sasl_mech_list: PLAIN allowplaintext: yes altnamespace: yes unixhierarchysep: yes virtdomains: userid 90 www.linuxvoice.com MAILSERVER TUTORIAL defaultdomain: mydomain.com hashimapspool: true sieve_admins: cyrus sievedir: /srv/mail/cyrus/sieve This tells Cyrus to use /srv/mail/cyrus for its configuration and, within that, a mail subdirectory where it should store mail. Virtual domains allows domain-specific mailboxes – you can have accounts for [email protected] and alice@example- two.com. The defaultdomain is the domain that unqualified user accounts, like “alice”, belong to. To improve the end-user experience, we set altnamespace so that users’ email folders appear alongside, rather than within, their inbox, and unixhierarchysep delimits mail folders with slashes instead of the default, which is to use a period. SASL Our configuration uses SASL for authentication. This . logout You can specify the server is the Simple Authentication and Security Layer, and If everything went well, the server responses will by its host name or IP was automatically installed as a dependency of the begin with * OK. You can now set up your email client address. The username is the IMAP “testuser” IMAP server. We just use the default configuration to connect to the IMAP account, but it doesn’t have account that we set up on here, which passes plain-text passwords to the any folders yet. The cyradm tool is used to create the server. saslauthd daemon that, in the default configuration mailboxes, and the minimum is an inbox: on Arch Linux, uses PAM for authentication. This is $ su cyrus -c ‘cyradm -u cyrus -w cyrus localhost acceptable for a test system, but you should consider localhost.localdomain> cm user/testuser configuring SASL to use more secure methods that You can then use your email client to create satisfy your own security requirements. subfolders, or you can use cyradm – cm creates So, create a test account for testing and verify that mailboxes (folders) and lm lists them: SASL can authenticate it. The default SASL localhost.localdomain> cm user/testuser/Sent PRO TIP configuration authenticates system users so we use a localhost.localdomain> lm Cyrus documentation is nobody account that can be authenticated but cannot user/testuser (\HasChildren) available at http://cyrusimap.org/ be used to log in to the server. user/testuser/Sent (\HasNoChildren) docs/cyrus-imapd. $ useradd -c ‘Test email account’ -u 99 -o -g nobody -d /dev/null user/testuser/Trash (\HasNoChildren) -s /bin/false testuser You can now send a message to the test user. $ echo testuser:testpass | chpasswd Create a test message in a file (call it testmessage) Start saslauthd (also enable it so that it starts on with the following contents (the empty line is required boot) and test that SASL authentication works for the – it marks the beginning of the message body). new test user: From: Test Message <[email protected]> $ systemctl enable saslauthd Subject: This is a test message $ systemctl start saslauthd This is a basic test e-mail message $ testsaslauthd -u testuser -p testpass To send the message into Cyrus, use the deliver tool 0: OK “Success.” The installation also created a cyrus user, and the server’s processes run as this user. We can also use it A virtual mailserver for administrative tasks if we set its home directory, shell and password: We used Linux Containers to create a virtual $ pacman -S base-devel devtools server to implement our mailserver on. Here’s $ useradd -c ‘Build Account’ -m -g users -d / $ usermod -s /bin/bash -d /srv/mail/cyrus cyrus what we did. As root, on any host machine home/build -s /bin/bash build $ echo cyrus:cyrus | chpasswd (ours runs Arch Linux): $ echo build:build | chpasswd To complete the configuration, make the required lxc-create -n mailserver -t archlinux -- -P $ echo ‘build ALL=(ALL) NOPASSWD: ALL’ >> / directories and build the IMAP folders: dhcpcd,openssh,wget --ewnable_units etc/sudoers dhcpcd,sshd.socket -r mysecret To build a package, log on as the “build” $ mkdir -p -m 750 /srv/mail/cyrus/mail lxc-start -n mailserver user, download and extract the package’s $ chown -R cyrus:mail /srv/mail/cyrus You can then log in with ssh AUR tarball and use makepkg to build it. $ su cyrus -c ‘mkimap /etc/cyrus/imapd.conf’ root@mailserver using mysecret as Further instructions are available on the Arch Now start the server the password. Linux website. Here is an example: $ systemctl enable cyrus-master Some of the packages that we will use $ wget https://aur.archlinux.org/packages/cy/ aren’t in the repositories, but they can be cyrus-imapd/cyrus-imapd.tar.gz $ systemctl start cyrus-master built from the Arch User Repository, AUR. We $ tar xf cyrus-imapd.tar.gz Test IMAP access for the test user created a build account on our new server for $ cd cyrus-imapd $ telnet localhost imap building these packages. $ makepkg -s . login testuser testpass www.linuxvoice.com 91 TUTORIAL MAILSERVER MXToolbox.com can test from Gmail: your server from outside… poll poll imap.gmail.com protocol imap user [email protected] there pass abc123 is alice here user [email protected] there pass secretword is alice here user [email protected] there pass secretword is jane here and similar examples for Yahoo and Microsoft mail accounts: poll pop.mail.yahoo.com protocol pop3 user johndoe there pass mypassword is john here ssl poll pop3.live.com protocol pop3 user [email protected] there pass 123abc is bob here ssl You can fetch mail on demand (the optional -v makes it verbose): $ fetchmail -v -f /etc/fetchmailrc Or, what you will most likely want to do is start it as a daemon that regularly polls for available messages. The daemon on Arch Linux runs as the fetchmail user and requires that it owns the /etc/fetchmail file.
Load more

Recommended publications
  • 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]
  • 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]
  • Understanding Email Sending in Nagios XI
    The Industry Standard In Infrastructure Monitoring Nagios XI Understanding Email Sending Purpose This document describes how Nagios XI sends emails and explains how to configure your email settings. Nagios XI uses email to send notifications as well as for sending reports. Target Audience This document is intended for use by Nagios Administrators who want to understand in detail how emails are sent by Nagios XI. Navigation Email settings in Nagios XI are located in Admin > System Config > Manage Email Settings. 1295 Bandana Blvd N, St. Paul, MN 55108 [email protected] US: 1-888-624-4671 INTL: 1-651-204-9102 www.nagios.com © 2017 Nagios Enterprises, LLC. All rights reserved. Nagios, the Nagios logo, and Nagios graphics are the servicemarks, trademarks, or registered trademarks owned by Nagios Enterprises. All other servicemarks and trademarks are the property of their respective owner. Page 1 / 7 Updated – September, 2018 The Industry Standard In Infrastructure Monitoring Nagios XI Understanding Email Sending Web Browser Behavior There are some behaviors of your web browser which you need to be aware of. A lot of different web browsers will auto-complete / auto-populate fields on a web page when it loads. This usually only occurs when it sees a common field that does not have a value, it may have a saved value for that "named field" and hence it will populate that field with that saved value. If you open the Manage Email Settings page in Nagios XI you might notice that the username and password fields are already populated. You know that you didn't put a value in here, especially when this is the first time you've visited this page on a fresh install of Nagios XI.
    [Show full text]
  • 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.
    [Show full text]
  • 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.
    [Show full text]
  • Set up Mail Server Documentation 1.0
    Set Up Mail Server Documentation 1.0 Nosy 2014 01 23 Contents 1 1 1.1......................................................1 1.2......................................................2 2 11 3 13 3.1...................................................... 13 3.2...................................................... 13 3.3...................................................... 13 4 15 5 17 5.1...................................................... 17 5.2...................................................... 17 5.3...................................................... 17 5.4...................................................... 18 6 19 6.1...................................................... 19 6.2...................................................... 28 6.3...................................................... 32 6.4 Webmail................................................. 36 6.5...................................................... 37 6.6...................................................... 38 7 39 7.1...................................................... 39 7.2 SQL.................................................... 41 8 43 8.1...................................................... 43 8.2 strategy.................................................. 43 8.3...................................................... 44 8.4...................................................... 45 8.5...................................................... 45 8.6 Telnet................................................... 46 8.7 Can postfix receive?..........................................
    [Show full text]
  • ESET MAIL SECURITY Installation Manual and User Guide
    ESET MAIL SECURITY Installation Manual and User Guide (intended for product version 4.0 and higher) Linux, BSD and Solaris Contents 1. Introduction..................................................................3 1.1 Main .........................................................................................3functionality 1.2 Key features.........................................................................................3 of the system 2. Terminology..................................................................5 and abbreviations 3. System..................................................................6 requirements 4. Installation..................................................................7 5. Architecture..................................................................8 Overview 6. Integration..................................................................10 with Email Messaging System 6.1 Bi-directional.........................................................................................11 email message scanning in MTA 6.2 Scanning.........................................................................................11 of inbound email messages 6.3 Scanning.........................................................................................11 of outbound email messages 6.4 Scanning of email messages downloaded from POP3/IMAP.........................................................................................11 server 6.5 Alternative.........................................................................................12
    [Show full text]
  • 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.
    [Show full text]
  • Opensmtpd: Current State of Affairs
    From: "Gilles Chehade" <[email protected]> To: "Ah, Jacques Cousteau" <[email protected]> Date: Sun, 24 Sep 2017 CET Subject: OpenSMTPD, current state of affairs The plan - Made tons of slides, I'll just skip over some if needed... - Sick AF, may need to run out during the talk… - Should this happen, stay calm and don’t panic, I’ll be back :-) $ whoami - Gilles Chehade <[email protected]> - I'm also @poolpOrg on twitter and github - I live in the beautiful city of Nantes, France (west coast riprizent !) - OpenBSD user since 2.6 (1999), OpenBSD developer since 4.2 (2007) - Also used NetBSD and FreeBSD a lot in the past, I enjoyed all BSD systems - Started working on smtpd in 2007 as personal project for my own needs - pyr@, reyk@ and henning@ tricked me into turning it into OpenSMTPD - "It will be fun", they said with a grin. $ whoami - Currently a Lead-Developer for the Vente-Privée Group - Platinum Sponsor of EuroBSDCon 2017 btw, woohoo ! - We are hiring. We are hiring. We are hiring. We are hiring. Mail me ;-) - I no longer do R&D work in the mail industry - Still do mail experiments in private though ;-) - My daily job has NOTHING to do with mails whatsoever, no conflicts of interest - Vente-Privée has a few OpenSMTPD instances as main MTA - I wasn't sure, I had to ask Miky Mike, the guy who knows this stuff - We also have a few OpenBSD installs, not sure I can say where and why, so… The OpenSMTPD crew - Eric Faurot <[email protected]> aka "The Doctor" - Sunil Nimmagadda <[email protected]> - Jung Joerg <[email protected]> - We tend to cc: our diffs to Todd Miller <[email protected]> - We receive a few contributions from the community - Mostly Linux people, just saying..
    [Show full text]
  • Opensmtpd: We Deliver
    OpenSMTPD: we deliver Giovanni Bechis <[email protected]> LinuxCon Europe 2015 About Me I sys admin and developer @SNB I OpenBSD developer I Open Source developer in several other projects OpenSMTPD story I first import in late 2008 I default smtp server in OpenBSD since March 2014 I current version is 5.7.3 released October 5, 2015 I portable version is available for *BSD, Linux and MacOSX why OpenSMTPD ? I in OpenBSD we needed a new smtp server to replace sendmail(8) I Postfix has not a "good" licence (from an OpenBSD pov) I OpenSMTPD is designed with security in mind I pf.conf(5) like configuration file OpenSMTPD: security in mind I multiple processes I privilege revocation I chroot I strlcpy(3), reallocarray(3), arc4random(3), imsg, ... I no auth on unsecure connections I crypt(3) as password hashing function OpenSMTPD: features I smtp protocol as defined in RFC 5321 I backup mx support I mbox and maildir support I authentication inbound and outbound with multiple backends I masquerade support I mailwrapper(8) for sendmail(8) I filters I compressed or crypted mail queue OpenSMTPD: extras I in base src code lives the main smtp server implementation I in extra src code lives all extra features: I table(5) support for different databases I different queue backends I different schedulers I filters OpenSMTPD: basic configuration listen on lo0 table aliases db:/etc/mail/aliases.db # accept from any for domain "example.org" alias <aliases> deliver to mbox accept for local alias <aliases> deliver to mbox accept from local for any relay OpenSMTPD:
    [Show full text]
  • Installing and Configuring HCL Domino 11.0.1 on Centos 8 Enterprise Linux
    Installing and Configuring HCL Domino 11.0.1 on CentOS 8 Enterprise Linux Devin S. Olson ([email protected]) Reviewed by Wes Morgan ([email protected]) 09 October 2020 Copyright 2020 HCL Technologies Ltd. Introduction ............................................................................................................................................... 3 CentOS 8 Enterprise Linux ........................................................................................................................... 4 System Requirements ............................................................................................................................................4 Domino Specific Configuration .................................................................................................................... 5 Security Enhanced Linux ........................................................................................................................................5 Required Packages ................................................................................................................................................5 Conflicting Services ...............................................................................................................................................5 User Account .........................................................................................................................................................5 Domino Installation ...................................................................................................................................
    [Show full text]
  • Postfix, Sendmail, Exim ●SMTP: Rfcs 821, 1123, 2821 ●Terminology: Client, Server Mamailil Ddeelliivveerryy Aaggeenntt
    PPoossttffixix by Rod Roark http://www.sunsetsystems.com/ TTeerrmmiinnoollooggyy ●MTA ●MDA ●MUA ●SMTP ●IMAP ●POP3 ●UCE MMaailil TTrraannssffeerr AAggeenntt ●Receives mail from or sends mail to other computers ●Talks with other MTAs and certain other agents ●Analogous to post offices ●SMTP is the language of MTAs ●MTAs are security-conscious ●Examples: Postfix, Sendmail, Exim ●SMTP: RFCs 821, 1123, 2821 ●Terminology: Client, Server MaMailil DDeelliivveerryy AAggeenntt ●Deposits received mail on the local computer ●Common storage formats are Mbox and Maildir ●Analogous to a mail carrier ●Usually invoked by an MTA ●Examples: Maildrop, Procmail PPOOPP33 SSeerrvveerr ●Post Office Protocol ●Provides for temporary storage and retrieval of mail ●Mail is usually deleted after retrieval ●Supported by most mail clients ●RFC 1939 and others define POP3 IIMAMAPP SSeerrvveerr ●Internet Message Access Protocol ●Provides temporary and long-term storage and retrieval of mail ●More sophisticated than POP3 ●Provides folders for organizing and archiving ●Supported by most mail clients ●Examples: Qmail, Courier IMAP ●RFC 3501 defines IMAP4rev1 MaMailil UUsseerr AAggeenntt ●Mail Client ●your tool for composing, reading, searching, archiving, etc. ●Commonly understands SMTP, POP3, IMAP and local storage formats ●Examples: Mutt, KMail, Evolution, Pine, Mozilla Thunderbird, MS Outlook SSMMTTPP CCoonnvveerrssaattiioonn $ telnet localhost 25 helo somewhere.org mail from: [email protected] rcpt to: [email protected] data From: Me To: Rod Subject: Test Hi,
    [Show full text]