Open main menu

CDOT Wiki β

Changes

OPS335 Lab 4b

8,152 bytes added, 02:37, 12 March 2021
INVESTIGATION 1: INSTALL THUNDERBIRD (MUA) and SETUP A REFERENCE CLIENT
= Email Servers = You may not be aware of it as an user, but email is a very <u>complex</u> system to administer. In fact, the more modern e-mail systems (eg. web-based mail applications, etc) are more technically involved than the other archaic, hard-to-configure, and sometimes inter-operable mail systems. We are going to spread the remaining email labs over a few weeks, so that by the end of this topic, you will have a sufficient understanding of what services are involved in sending, filtering, and reading email. You will also have the skills to configure a basic mail setup using the default services provided for your Centos7 Linux distribution.[[Category:OPS335]][[Category:OPS335 Labs]]
==LAB RESOURCESOVERVIEW=={{Admon/important|Warning|Your lab 4a must be complete before you can start this lab.}}
Online References:In Lab 4a, you configured and ran the '''Postfix''' application for our MTA (a.k.a. SMTP server) on your '''vm2''' and '''vm3''' machines.
That setup has some major drawbacks::* [http://wiki.dovecot.org/MailServerOverview Here's It required an overview] SMTP server (common mail server terms'''MTA''')to be configured on each machine.:* [https://inside.senecacollege.ca/its/services/email/email_clients/imap.html Seneca Client Settings] The Message Store (Seneca Server settings for mail client '''MS''') would also be unique to each machine - Thunderbird) what a user received on one server would not exist on any other.
In this lab you will centralize some of this information, so that a user can send email from any machine in the network, and have incoming mail sent to a centralized messages store.
== OVERVIEW &amp; PREPARATION=='''The a diagram below (duplicate to lab 4a) shows your basic setup of your email system:'''
This is a simple (yeah, really!) diagram of how you can send an email to someone else:
[[Image:Email-servers.png]]
[[Category:OPS335]][[Category:OPS335 Labs]]You will begin by modifying the existing '''Postfix''' ('''MTA''') servers to make mail they send come from your domain (instead of each machine). Then you will add a record to your DNS server to allow mail to be sent to the domain itself, instead of the individual machines. Next, you will add a Local Delivery Agent ('''LDA''') to your '''vm3''' by installing '''dovecot-lda''', configure it, and test it to make sure that is is working correctly.
In factFinally, the above diagram does not include reading mail messagesyou will set up an '''IMAP''' server called '''Dovecot''' on your '''vm3''' machine, but this acts so you can read your email from an MUA such as ''Thunderbird'' or a starting point in order to run a basic email server''Webmail'' application. Although You will be learning to administer the mail services set up a webmail application called '''Roundcube''' in the diagram above, we will not required you to go into tremendous depth (just the minimum requirementsa later lab). For example, we will not go over every aspect of the Postfix MTA service, but you should know what it represents and what is its main purpose, as opposed to the following: [https://en.wikipedia.org/wiki/Postfix_%28software%29#Architecture complex diagram 1] , [https://www.credativ.de/blog/postfix-architecture-overview complex diagram 2].
=== Learning About the Services involved Involved in email delivery an Email Delivery ===
In reality, the terms '''MTA''', '''MDA''', '''MUA''', '''LDA''' can actually be considered misleading since some of those services can be combined together to form a single entity (application), while other applications may operate as separate entities. There may be overlap, so if you don't find those acronyms helpful, don't worry too much about them. On the other hand, when referred to in diagrams, they can help to visualize those processes when try trying to understand how an e-mail system works.
[http://wiki.dovecot.org/MailServerOverview Here's is an overview] of those terms (from the Dovecot wiki). It is worth viewing this link.
In the diagram displayed above, the elements include:
* A '''userUser Account'''. That's the person The individual who wants to send an emailor receive mail messages.* An '''MUA''' (email client). This is the application that the user individual uses to send an emailor receive mail messages. It can be a '''native application ''' or a '''web application'''. We'll set up You will learn how to setup and use both typesof these applications throughout the remainder of this course.* Two '''MTAsMTA'''servers. These are the servers responsible for getting your emails to the <u>destination</u> server.
** They are similar to routers (which route packets) but work on the <u>application</u> layer rather than the <u>network</u> layer.
** In our example, there are only two MTAs - but there can be several.
** You connect to your MTA over a <u>secure</u> connection, so your emails can't be read by the operators of the network you're connected to.
** The mail message then travels the rest of the way to the destination MTA <u>unencrypted</u>, so anyone with access to the routers in-between can read all your emails. That is why many organizations will refuse to send you confidential information over email.
* The '''LDA/MDA''' Server. This server will receive the email from the MTA, and will store it on disk in some format. '''MailDir''' and '''MBOX''' are the most popular mailbox formats.* '''IMAP/POP3''' server(s). When sending an email, you send it to the destination using your MTA, but you also want to save it in your '''"Sent"''' folder for yourself. This is accomplished by a separate connection to either your '''IMAP''' or '''POP3''' server.
** Thus, a situation can occur that although you sent your email successfully, it may never make it to your "Sent" folder - the <u>second</u> connection to your IMAP server is quite unrelated to the first connection to the '''SMTP''' server.
* Note that a '''DNS''' Server. A DNS server is also involved - it is needed to retrieve the address of the email server responsible for an email for a particular domain. This is done with the '''MX ''' records we looked at in the DNS labs===Online References=== * [https://help.ubuntu.com/community/Dovecot Dovecot Community Documentation]* [http://wiki.dovecot.org/LDA Dovecot-lda]* [http://wiki.dovecot.org/LDA/Postfix Configuring dovecot-lda with postfix] == INVESTIGATION 1: INSTALL THUNDERBIRD (MUA) and SETUP A REFERENCE CLIENT==
=== Install Unlike the '''mailx''' (MUA) application you installed and used in Lab 4a, this lab will be using the '''Thunderbird Application ''' (MUA) application instead which is a graphical application that uses a '''centralized Message Store''' (MS) to retrieve and Setup a Reference Client ===read mail messages.
Eventually Although wewill be eventually setting up the Thunderbird application to perform all the mail operations discussed above, you need to learn to '''"walk before you can run"''re '. Eventually, you are going to set up all those mail services, but to begin with, we you will set up an email client to connect to a (hopefully) an already working server - which is the '''Seneca email server'''. This will be a good exercise with an Once we learn how to do this for our Seneca email clientaccount, then we can use it for our mail servers for our VM2 and VM3.
Switch to your '''host''' machine, and install Perform the following steps:'''Thunderbird''' email application.
#Switch to your '''host''' machine, and install the '''Thunderbird''' email application.#When you see first launch the Thunderbird application, a configuration dialog box, configure it in a similar way (''using your own information'') should appear as shown in the diagram below:
<br>::[[Image:Seneca-student-thunderbird-email-setup.png|600px]]<br><ol><li value="3">Use the data in the table below to configure the Thunderbird settings dialog box for YOUR Seneca e-mail account:</li></ol>
Notice that there are <u>unencrypted</u> options available to connect to your {| class="wikitable" border="1" style="margin-left:40px;"! Setting !! '''Incoming: IMAP''' !! '''Outgoing: SMTP'''|-| '''Username'''|| yoursenecauserid@myseneca.ca || yoursenecauserid@myseneca.ca|-| '''servername''' || outlook.office365.com || outlook.office365.com|-| '''port''' || 993 || 587|-| '''security''' || SSL/IMAP servers but those are rarely used these days TLS || STARTTLS|- the potential for abuse is too great| '''References''' | colspan="2" | [1] [https://employees. On a free wifi network, the operator would be able to not only read your email, but also obtain your password without any passwordsenecacollege.ca/spaces/77/encryption cracking tools. In fact, even on a private wired network, it is not uncommon for an employer to use a packet sniffer utility to monitor all the traffic going over their network (Packet Sniffing applications were actually found to be legally acceptable practices if used by the management of organizations).-services/wiki/view/2394/other-email-clients ITS - Configuring other Email Clients]|}
The specific security settings depend on how ::Note that your username is your servers were configured. '''The settings for the seneca servers are [https://inside.senecacollegefull email address(<em>yourid@myseneca.ca</its/servicesem>) and not just <em>yourid</email/email_clients/imap.html published here]'''em>.
After you create your '''Thunderbird''' account, you should be able to read your existing email and send new email within the Thunderbird application.
{{Admon/important |Unencrypted Options|Notice that there are <u>unencrypted</u> options available to connect to your SMTP/IMAP servers but those are rarely used these days - the potential for abuse is too great. On a free wifi network, the operator would be able to not only read your email, but also obtain your password without any password/encryption cracking tools. In fact, even on a private wired network, it is not uncommon for an employer to use a packet sniffer utility to monitor all the traffic going over their network (Packet Sniffing applications were actually found to be legally acceptable practice if used by the management of organizations)}}<br><ol><li value="3">After you create your '''Thunderbird''' account, you should be able to read your existing email and send new email within the Thunderbird application.</li><li>Take time to view your ''Account Settings'' and ''Preferences'' to get a feel for what settings exist. For example:* <ul><li>How often will Thunderbird check for new messages?* </li><li>Will the messages you write be in HTML or plain text?* </li><li>How do you change your SMTP server settings? Why are they in a different section?</li></ul></li><li>The main objective of this section was to learn how to setup your Thunderbird application to read your Seneca email, so in the next section you can use the exact type of setup for your own email server.</li></ol>
The main objective of this section was to learn how to setup '''Record steps, commands, and your Thunderbird application to read your Seneca email, so observations in INVESTIGATION 1 in the next section you can use the exact type of setup for your own email server.OPS335 lab log-book'''
== INVESTIGATION 12: SETUP MAIL TRANSFER AGENT (MTA) FOR SENDING (NO ENCRYPTION) A CENTRALIZED MESSAGE STORE ==
We be using the '''Postfix''' application as the '''=== Setup Your MTA''', and we will be setting it up on your '''vm2''' machine. This will act as the email server for your internal network. You will be able to send email out of your network, and receive email from within your network, but you will '''<u>not</u>''' receive email from outside of your network due to the following reasons:* Individuals outside of your domain will never find the MX records because there are no '''.org''' servers pointing to your DNS server (i.e. you haven't paid for it).* Even if they the individuals could read your MX records, your local network is using IP addresses on a '''private subnet''', which is not routeable on the Internet, so it cannot be reached from outside of your system.Use Correct Domain===
=== Verify In Lab 4a, both of your email servers were sending mail messages addressed from users of the Postfix Service Status ===actual machines themselves. This would be confusing for the receiver who might get emails from the same user @vm1, vm2, and vm3. Which would they respond to? To avoid this problem from occurring, we can make all servers make the sent mail appear to come from a central location (usually the '''domain'''), and make incoming email sent to that address to be accessible from machines within our network.
'''Perform the following steps:'''
#The Issue the '''mail''' command to view the email messages you sent between your '''vm2''' and '''postfixvm3''' application should be installed by defaultin your lab 4a. If it isn't, install Notice that each is addressed from root on whichever machine sent it.#Install also On both machines (vm2 and vm3), edit the '''netstat/etc/postfix/main.cf''' application (tip: use yum search file to find the package name) and also install change the '''telnetmyorigin''' parameter from '''$myhostname''' to '''$mydomain''' command.#Postfix will work with the default configuration, so start and enable this service, and verify that Restart the '''postfix ''' service is running.#Look for Now, send emails messages (via the running postfix service in the list '''mail''' command) between both of listening ports by issuing the following command:<br><source lang="bash">netstat -atnp</source>#Which service is postfix running? Locate the port used by SMTPyour vm2 and vm3 machines, and look for connctions with view the state LISTEN (imail messages by issuing '''mail''' in each vm.e The sender address should now read that the received mail messages came from '''root@yourdomain. currently listening)ops'''.#Write your observations in your lab logbook.
=== Testing ::The next step is to configure what addresses that the connection server will receive email for. This is done using postfix by setting the '''mydestination''' parameter (configuration variable) to the Postfix Service ===include '''$mydomain''' (this is assuming you've set up '''mydomain''', '''myorigin''' , and '''inet_interfaces''' properly).
We <ol><li value="4">Edit the '''/etc/postfix/main.cf''' file for '''vm3 ONLY''', scroll down to the line containing: '''mydestination''' and change line to the text shown below:<br><source>mydestination = $mydomain, $myhostname, localhost.$mydomain, localhost</source>'''Note:''' Even though your machine's name is ''vm3.yoursenecaid.ops'', your postfix MTA will also receive emails addressed to the domain called: yoursenecaid.ops</li></ol><br>::In order for this to work, we need to add a DNS record that will be demonstrating point mail sent to the use domain towards one of the telnet application SMTP servers configured to test accept it. <ol><li value="5">Add an '''MX''' record to the forward lookup zone on '''host''' so that all incoming mail addressed to the domain is sent to your vm3.</li><li>Restart the postfix service and use the '''dig''' command to confirm that it works.</li><li>Send an email from your '''vm2''' to '''root@yourdomain.ops'''</li><li>Confirm that it arrives on your '''vm3''' machine</li></ol> === Relay Email Through Another Server=== When email is runningsent from either vm, it is addressed from the domain, but receiving MTAs might query why mail sent from vm2 doesn't match the address of the MX record for the domain. This would be a red-flag for potential spam. To avoid this, we can relay all mail sent from vm2 (or any other machine in our network) through vm3 so that it properly appears to come from the mail server that matches the MX record for the domain.
'''Perform the following steps:'''
# Connect from Move to your server vm2 machine.# Direct your '''vm2''' MTA to your server using telnet relay mail through vm3, by issuing making the following commandediting change for the '''/etc/postfix/main.cf''' file:<br><source lang>relayhost ="bash"vm3.<yourdomain>telnet localhost 25.ops</source># Note that it should indicated that you are connected by displaying Restart the the text:'''Escape character is postfix''' service.# Next, you must instruct your '''^]vm3''', which indicates that in order machine to allow your vm2 machine to end pass email through it by making the telnet session, you can hold control and press following editing change to the square bracket key'''/etc/postfix/main.cf''' file:<br><source>mynetworks = 192.168. Perform that key-combination to end the telnet sessionX.0/24</source>NOTE: Substitute in your '''own network''' for X<br><br>#Enter Restart the command '''exitpostfix''' to close the telnet applicationservice.
::'''NOTE:''' If it workedAll mail is now being delivered to a centralized location (and also appears to be coming from that same location), this indicates but a user would still have to access that the postfix service is running and listening and responding server to connectionsretrieve it.
<ol><li value="4">Let's see if it works from other machines. Telnet to vm2 from == Install and Configure the host Local Delivery Agent (connect to the SMTP port) and see if it works. If your firewall is set up properly, the telnet command should not permit a connection.<LDA/li><li>Issue an iptables rule to allow incoming connections to '''TCP port 25'''.</li><li>Once you open the port in the firewall, retry the '''telnet''' command. You should get a different error this time. This time the problem is that your service isn't listening on the outside interface, it's currently configured to listen only on the loopback (loMDA) interface.</li></ol>===
=== Listening on all interfaces === Our first editing change to the Postfix configuration will be to make is capable of performing the service "listen" function of an LDA, but its LDA capabilities are limited, thus postfix is generally not used for incoming connections on that purpose. Currently, the external interface (i.e most popular LDA is ''LMTP'', but we will be installing, configuring, and using an LDA called '''Dovecot''' since it is also popular and we will setting up Dovecot as an '''eth0IMAP''' from server later in this lab. Using both Postfix and Dovecot will actually increase the VMs point performance of view)our IMAP server.
'''Perform the following steps:'''
# Launch Move to your '''vm3''' machine.#Dovecot is not installed when you installed your Virtual machines in editing session for previous labs.<br>Install the Dovecot application by issuing the postfix configuration file calledfollowing command: <br><source>yum install dovecot</source>#Edit your '''/etc/postfix/main.cf'''# Change the value of file and scroll down to (or search for) '''mailbox_command'''. Add the following parameter to what is displayed belowline: inet_interfaces <br><source>mailbox_command = all/usr/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"</source>
::NOTE: Do <u>'''not'''</u> replace any variables, those are set automatically by Postfix when it runs the LDA. If you are interested in learning more about the Dovecot application, you can read about dovecot-lda [http://wiki.dovecot.org/LDA/Postfix here] and [http://wiki.dovecot.org/LDA here].<br><ol><li value="34">We should also set the string that will end up in Finally, edit the '''From:''' header in messages sent by this server/etc/dovecot/conf.d/10-mail. Change conf'''mydomain''' to file and indicate where you want your domain name and '''myorigin''' to '''$mydomain'''.mail delivered by including the following line:<source>mail_location = maildir:~/Maildir</source></li><li>Restart the your postfix service and confirm (using netstat) that the service is now listening on .<u/li>all<li>While the emails are still stored only on VM3, they will now be easier for other machines/u> interfaces (not just loopback)services to access.</li><li>Test by connecting Due to permissions on the directories where mail will now be stored, root will no longer receive mail. Check the logs for an indication as to it (using telnet) from your '''host''' machinewhy.</li></ol>
=== DNS Server used by the host ==='''Record steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book'''
So far you're probably not using vm1 as the DNS server for your host. We'll need to change that for email to work correctly. Normally you don't need an entire DNS server for running an email server, you just add an MX record in your registrar's web interface, but we haven't paid for our domains so we don't have a registrar with a web interface.==INVESTIGATION 3: USING THUNDERBIRD (MUA) FOR VM2 and VM3 MACHINES ==
Modify your /etc/resolv.conf to use vm1 as the name server. This will not be a permanent change but that's ok, we only need it for the email labs. You'll have to remember to do this every time you reboot your host.=== Accessing Received Mail Messages on VM3 VIA IMAP ===
If you regular (internet) DNS lookups slow down significantly - try to update First, we will set up the DNS IMAP server so we can read email. The current way we have configured our mail server configuration on vm1 to forward requests to our VM3 machine should allow all the Google nameserver (8email for anyaccount@yoursenecaid.8ops should be delivered to our '''vm3''' machine.8.8) instead of your hostWe will set up Dovecot with IMAP to get easy access to that email.
'''Record Perform the following steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book:'''
#The configuration file for the Dovecot service (which is not the same thing as dovecot-lda) is: '''/etc/dovecot/dovecot.conf'''. Modify the '''protocols''' option so that Dovecot will work with IMAP connections, no POP3 or LMTP.
# Start the dovecot service, and ensure it will always start automatically when the machine boots.
# Use the '''ss''' command to confirm the service is listening, and use '''nc''' on the '''host''' to confirm you can connect to it.
# You'll probably fail, so using the information gathered from '''ss''', modify the firewall on vm3 to allow IMAP connections from your local network and try '''nc''' again. Once it works, do not forget to save this change so it will still be there the next time you reboot.
#If you can connect - it's now time to do something wrong, that is allow connections to our IMAP server over an unencrypted connection.
# Edit the '''/etc/dovecot/conf.d/10-auth.conf''' file and set '''disable_plaintext_auth''' to '''no'''.
# Then edit the '''/etc/dovecot/conf.d/10-ssl.conf''' file and set '''ssl''' to '''yes'''.<br><br>'''Note:''' This combination of parameters will allow your username and password to be sent over the internet in plain text, for anyone interested to look at. In a later lab we'll set up secure SMTP and IMAP connections, for now this is all we have time for.<br><br>
# Restart dovecot so the changes take effect.
==INVESTIGATION 2: SETUP THUNDERBIRD MAIL USER AGENT (MUA) FOR YOUR VIRTUAL NETWORK (vm2, vm3) = Connecting to IMAP Servers Using Thunderbird===
We are far from having a working email server but at this point we have enough to be able to test it with Thunderbird.'''Perform the following steps:'''
The process is a little challenging because Thunderbird tries really hard #On your '''host''' machine, return to prevent you from connecting to a server that doesn't work the Mail Account Setup dialog box (and ours mostly doesn't work at this pointeg. near top of lab). # Set it up a '''new email account'''. You will be using account settings to connect to your '''vm2''' for '''SMTP ''' and '''vm3''' for '''IMAP'''. Use <u>no </u> encryption, and use normal password authentication for IMAP (we don't have an IMAP server running yet, but that's ok).Refer to the diagram below for reference:
[[Image:ops335-email-step1.png|600px]]
Thunderbird won't let you proceed with the <ol><li value="Done3" button because you will fail >Try to connect to your IMAPserver with Thunderbird by clicking on your '''Inbox'''.</li><li>If nothing happens, then check the Thunderbird Activity Manager for any errors. If the connection is successful, you should see the '''Trash''' box <u>appear</u> below Inbox. </li><li>Use the "Advanced config" button Thunderbird application to send an email to bypass your myseneca address. If you've done everything right, it will send the message successfully</li><li>Verify that checkyour message has been sent. Check your myseneca email and look at '''/var/log/maillog''' on vm2 (your email server).</li></ol>
Now use === Sending a Mail Message from VM2 (Using Thunderbird to send an email to your myseneca address. If you've done everything right - it will send the message successfully but it will fail to save it in the Sent folder, because that's done with IMAP and you don't have an IMAP server yet.)===
Still - verify that your message has been sent. Check your myseneca email and look at '''/var/log/maillogPerform the following steps:''' on vm2 (your email server).
#Use the '''ss''' and '''nc''' commands (like you did in lab 4a) to confirm your service is listening on the correct ports/interfaces. You will probably have to open the appropriate firewall port on '''vm3''' to allow incoming '''SMTP''' connections.<br><br>'''Note:''' You should be able to send email to any regular user <u>on</u> '''vm3''' using the email address '''yourusername@yoursenecaid.ops''' using the Thunderbird application on your host machine (which is configured to use the account on your vm2).<br><br>
<ol><li value="2">Create a new account on your '''vm3''' machine using only your <u>first</u> name. We will use this account as a one-time "test" if the mail message has been received on your VM3 machine (from your VM2 machine).<br><br>'''Note:''' It is <u>'''important'''</u> that you '''<u>don't</u>'''Record stepscreate this same account name on your vm2 machine, since you want to easily identify the difference between the sending and receiving SMTP servers.<br /><br /></li></ol> <ol><li value="3">Use the new account in Thunderbird to send an email to '''firstname@yoursenecaid.ops''' and then check the contents of '''/home/firstname/Maildir/new/''' on your '''vm3''' machine. There should be a file there with the contents of your email.</li><li>If there is no file, commandsthen check the log file '''/var/log/maillog''' to see what went wrong.</li><li>If you can see a file in the '''/home/firstname/Maildir/new/''' directory, then review the procedures on how you got the email server working (since you have performed many steps and set up many services).</li><li>Refer to the diagram at the top of this lab. Which services have you currently set up? Record your observations findings in your lab Logbook.</li></ol> {{Admon/important |Encountering error messages when sending email|If you cannot properly receive sent e-mail messages, check the '''/var/log/syslog''' file for errors.<br><br> If you locate an error message in INVESTIGATION 2 that file such as: '''Fatal: Error reading configuration: Invalid settings...''', then add the following <u>parameter</u> in '''/etc/dovecot/dovecot.conf''':<br />'''postmaster_address <nowiki>=</nowiki> DOMAIN''' (where DOMAIN is actually <u>your</u> domain).<br /><br />After you have saved those changes, then '''restart''' your dovecot service. This problem can also be resolved by properly setting the hostname of your machine to include the domain.}} {{Admon/important |Backup your VMs!|You MUST perform a '''full backup''' of ALL of your VMs whenever you complete your '''OPS335 lab log-booklabs''' or when working on your '''OPS335 assignments'''. You should be using the dump or rsync command, and you should use the Bash shell script that you were adviced to create in order to backup all of your VMs.}}
'''Record steps, commands, and your observations in INVESTIGATION 3 in your OPS335 lab log-book'''
== COMPLETING THE LAB ==
Students should be prepared with ===Online Submission===Follow the instructions for lab 4b on blackboard.<!--===Andrew's sections=== You may choose to:* Submit screenshots of your work on Blackboard, in which case you don''all required commands (system information) displayed in a terminal (or multiple terminals) prior t need to come to the lab.* Or come to calling the instructor for signoff''lab, show me your work, and talk to me about it. I want to hear what you've learned and answer any questions you have.
You'''Arrange evidence (command output) for each ll get the same grade regardless of these items on how you choose to submit your screen, then ask your instructor to review them and sign off on the lab's completion:'''work.
::<span style="color:green;font-size:1.5em;">&#x2713;</span>Status and configuration of your Postfix service on vm2.
::<span style="color:green;font-size:1.5em;">&#x2713;</span>Your Thunderbird configuration.
::<span style="color:green;font-size:1.5em;">&#x2713;</span>The email you sent to your myseneca account.
::<span style="color:green;font-size:1.5em;">&#x2713;</span>Download and run '''wget https://ict.senecacollege.ca/~andrew.smith/ops335/labcheck4b.bash''' on your '''c7host''' machine. ::<span style="color:green;font-size:1.5em;">&#x2713;</span>Completed Lab4b log-book notes.-->
==EXPLORATION QUESTIONS==
#What is the purpose of the Thunderbird application?# List the steps to configure your DNS to allow your Thunderbird application to connect to your mail server.# What is the purpose of the '''Dovecot''' package?# What is the purpose of the '''mydestination''' parameter contained in the '''/etc/postfix/main.cf''' file?# Why are '''IMAP''' and '''POP''' email servers placed on separate machines (vms)?# What is the purpose of the '''mail_location''' parameter contained in the '''/etc/dovecot/conf.d/10-mail.conf''' file?# Why is root not able to receive mail with the changed mail location? What could you change to allow mail to be sent to root again?