1,234
edits
Changes
→Sending a Mail Message from your vm2 Machine to your Seneca Email Account
[[Category:OPS335]][[Category:OPS335 Labs]]
==MAIL SERVER RESOURCESOVERVIEW & PREPARATION== {{Admon/important|Warning|Your lab 3 must be complete with a functioning DNS server for your domain before this lab will work.}}
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.
[[Image:Email-servers.png]]
===Online References:===
* [http://www.simplehelp.net/2008/12/01/how-to-send-email-from-the-linux-command-line/ Mail Send Command] (examples how to send e-mail using mail command)* [Imagehttp://www.johnkerl.org/doc/mail-how-to.html#prompt_commands View and Manage Received e-mail Mesages] (Common commands to view and manage received email-setupmessages)* [https://support.google.pngcom/mail/answer/29436?hl=en Reading Full Email Headers](Explanation of message header information)* [http://wiki.dovecot.org/MailServerOverview Here's an overview](common mail server terms)
==INVESTIGATION 1: INSTALL, SET-UP, AND USE THE MAIL USER AGENT ('''MUA''')==
=== Confirm Network Connections Installing the Mail User Agent (MUA)===
#Make certain you are in your '''Perform vm2''' machine.#Install the following steps'''mailx''' application (MUA) using yum:'''NOTE:''' You can refer to the link below to acquaint yourself on how to send e-mail messages using '''mailx''' application:<br> [http://www.simplehelp.net/2008/12/01/how-to-send-email-from-the-linux-command-line/ Mail Send Command Examples]
We will now be installing the postfix application which will act as the Mail Transfer Agent ('''test to see if your MTA''') that will send and receive for your vm2 machine is correctly running by sending email messages from your vm2 machine to your Seneca e-mail messages between various server.<br>In our case, between our servers '''vm2''' and '''vm3''', as well as between our '''vm2''' server and an outside server: '''Seneca College''' (https://myseneca.ca)account.
'''Perform the following steps:'''
#Switch to Make certain you are still in your '''VM2vm2''' machine.#Check the status of the Test email from your machine by sending an email to your '''sendmailSeneca email account''' service by using the '''systemctl''' command. If the sendmail service is running, use the ''systemctl'' command to stop and disable that service. #Issue the following command to install the '''Postfix''' application (MTA):<br>'''yum install postfix'''<br><br>#What is the purpose of installing the postfix application in terms of using email -mail? Record your answer in your lab logbook.#We need to <u>configure</u> the postfix application (i.e. our MTA) to recognize our recentlys "Lab4a -created domain name that we setup in lab3.test1" <brYour Seneca email address>Edit the Postfix configuration file: '''/etc/postfix/main.cf''' and edit this file to contain only the contents displayed below:<br><br>'''mydomain = senecaID.orgNOTE:'''<br>after you type in the body of the mail message, move to an empty line, and then press the key combination '''myorigin = $mydomain<ctrl><d>'''<br>'''mynetworks = 127.0.0to send the message.0/8, 192.168.X.0/24'''<br>'''relay_domains ='''<br>'''inet_interfaces=all'''#Check your Seneca email account (Inbox / Junk Email Folder) to see if you got the email (note that it may take a <bru>few minutes to arrive<br/u>Your MTA has the ability to resolve "fake" public address , so you may also wish to try an actual user alternate email account name. For example, if you have a user account called "msaul"one like gmail, etc). When you can have the MTA resolve the fake name "murray.saul" to the account name "msaul". In order to do this you need to create an alias which is contained in receive that email, make a note of the MTA's alias filereturn address.<br><br>#Edit If you did not receive the '''/etc/postfix/aliases''' file and add mail, check the mail logs on your first name as an alias vm2 machine to be resolved to your VM2's account name:<br><br>'''your-first-name''' '''your-vm2-regular-username'''<br><br>determine any errors messages that would indicate a mail server setup problem.#In order Once you have succeeded in sending the first email, send a second email to update the MTA's database for the newly-create alias, issue same destination using the following command:<br>'''postalias hash:/etc/aliases'''mail -r "someone@hacker.com (Canadian Revenue Agency)" -s "Lab4a - test2" <br><brYour Seneca email address>#Finally, Check your email to start and enable your MTAsee if you got the email. If you did, issue make a note of the following commands:'''systemctl start postfixreturn address.service'''<br>'''systemctl enable postfix.service'''<br><br>#Check How would you think that including the '''/var/log/messages-r''' file option could be used by penetration hackers to gain access to a computer system? What sort of steps do you think should be taken to see that your MTA server started without error If there are any errors, correct them before continuing.help prevent this type of attack from happening?
===Sending a Mail Message within your vm2 Machine===
We will now test both your MUA (mailx) and MTA (postfix) by sending and receiving e-mail messages on the local vm2 machine only.
'''Perform the following Steps:'''
#Send an email message locally (i.e. only within your vm2 machine) by issuing the command:<br>'''mail -s "Lab4a - Local - Test1" <yourSenecaID>'''
#After you type in the body of the mail message, move to an empty line, type period "." and press the ENTER key to send the message.
#Login with your '''regular user''' and issue the following command to read the mail message you send to yourself:<br>'''mail'''<br><br>'''NOTE:''' You can refer to the link below to view a reference chart on how to read and delete received e-mail messages at the mail command prompt:<br>[http://www.johnkerl.org/doc/mail-how-to.html#prompt_commands Commands to View and Manage Received e-mail Mesages]<br><br>
#Issue the following command: '''cat /var/spool/mail/<yourSenecaID>'''<br>What do you see? What does this show you in terms of where mail is stored on your e-mail server?
#If you received an e-mail message, the message and subject line should appear as a listing in your mail command.<br><br>'''NOTE:''' If you did not receive a mail message, check your mail server settings, check to see if your mail server is running and also check '''/var/log/maillog''' and '''/var/log/messages''' (this step requires '''root''' privilege).<br><br>
#Once you have received the message, type the mail message number that is displayed in your e-mail message list in the prompt and press ENTER. You should be able to confirm the message body that you sent.
#Exit the mail program by typing the letter '''q''' and press ENTER.
#Re-issue the '''mail''' command. What happened? Issue the command: '''cat /var/spool/mail/<yourSenecaID>'''. What do you notice?
#Exit the mail command.
'''Record steps, commands, and your observations in INVESTIGATION 1 in your OPS335 lab log-book'''
==INVESTIGATION 2: SETUP MTA TO SEND MAIL MESSAGES (NO ENCRYPTION)==
#The '''Perform postfix''' application should be installed by default. If it isn't, install it.#Postfix is capable of sending email with the default configuration, so start and enable this service, and verify that the postfix service is running.#Look for the running postfix service in the list of listening ports by issuing the following Stepscommand:'''<br><source>ss -atnp</source>#Which service is postfix running? Locate the port used by SMTP, and look for connections with the state LISTEN (i.e. currently listening).#Write your observations in your lab logbook.
# If the '''nc''Perform ' command is not installed on your vm2 machine, install it (install '''nc''' command for your '''vm3''' as well).# Connect from your '''vm2''' to itself using the '''nc''' command by issuing the following stepscommand:<br><source >nc localhost 25</source># You should see a response: <br><source >220 vm2.yourdomain.ops ESMTP Postfix</source># You could theoretically use SMTP commands to send an email here, but this would be a very unusual use of your mail server. You have an '''MUA''' for a reason.#Enter the command '''QUIT''' to close the connection to the server, then '''<ctrl>-c''' to terminate the nc command.
<ol><li value===Testing email using IP Addresses==="4">Let's see if it works from other machines. Use '''nc''' to connect to '''vm2''' from '''vm3''' and see if it works. If your firewall is set up properly, the nc command should not permit a connection (i.e. ''no route to host'').</li><li>Create an iptables rule to allow incoming connections to your '''SMTP''' server on your '''vm2'''.</li><li>Once you open the port in the firewall, retry the '''nc''' command. You should get a different error this time (e.g. ''connection refused''). 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 (lo) interface.</li><li>Make sure the new iptables rule gets saved so that it will be loaded automatically from startup.</li></ol>
# In your '''vm2''' machine, launch in editing session for the postfix configuration file called: '''/etc/postfix/main.cf'''# Our first editing change to the Postfix configuration will be to make the service "listen" for incoming connections on the external interface (i.e '''eth0''' from the VMs point of view).<br>Change the value of the following parameter to what is displayed below:<br><source>inet_interfaces =all</source># We should also set the string that will end up in the '''From:''' header in messages sent by this server.<br>Change the '''mydomain''' option to YOUR domain name (shown below):<source>mydomain =yoursenecaid.ops</source># Also you must set the '''hostname''' for this server so that will correctly specify the hostname in the '''From:''' header in a sent mail message.<br>Make certain the following parameter only appears once (shown below):<source>myorigin =$myhostname</source>#Ensure that your '''hostname''' and '''DOMAIN''' name is properly set on your machine, otherwise you will need to set the '''myhostname''' parameter.<br>{{Admon/important|Warning|Make sure there are no other un-commented copies of those above-mentioned parameters in the Postfix configuration file.}}<br><ol><li value="6">Restart the postfix service, then use the '''ss''' command to confirm that the your MTA is now listening on <u>all</u> interfaces (not just loopback)</li><li>Test email by connecting to it (using host names===the '''nc''' command) from your '''vm3''' machine.</li></ol>
'''Record Perform the following steps, commands, and your observations in INVESTIGATION 2 in your OPS335 lab log-book:'''
# Repeat the configuration from investigation 2 on '''vm3''' (swap vm2 and vm3 when issuing command so that you are configuring vm3, and using your vm2 server to test the connections).
# Once that is complete, send an email from '''root on vm2''' to '''root on vm3''', and then reply '''from vm3 to vm2'''.
# If both messages arrive, both MTAs are working. If not, use the troubleshooting tools and techniques you have already learned to diagnose and fix the problem.<br><br>
{{Admon/important |Backup your VMs!|You MUST perform a '''full backup''' of ALL of your VMs whenever you complete your '''OPS335 labs''' 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.}}
<br>
'''Record steps, commands, and your observations in INVESTIGATION 3 in your OPS335 lab log-book'''
==COMPLETING THE LAB==
Upon completion of this lab you should have postfix mail servers running on two machines, and starting automatically when they do. These servers must have sent email both ways between each other (from vm2 to vm3, and from vm3 to vm2), and to your seneca email (or other external mail server).
===Online Submission===
Follow the instructions for lab 4a on blackboard.
<!--
===Andrew's sections===
You may choose to:
* Submit screenshots of your work on Blackboard, in which case you don't need to come to the lab.
* Or come to the 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'll get the same grade regardless of how you choose to submit your work.
::<span style="color:green;font-size:1.5em;">✓</span>Arrange proof that you can send e-mail from your '''vm2''' machine to your '''Seneca College e-mail account''', and than you can '''send and receive e-mail messages between on your vm2 and vm3 machines'''.
::<span style="color:green;font-size:1.5em;">✓</span>Download and run '''https://ict.senecacollege.ca/~andrew.smith/ops335/labcheck4a.bash''' on your '''host''' machine.
::<span style="color:green;font-size:1.5em;">✓</span>Completed Lab4a log-book notes.
-->
==EXPLORATION QUESTIONS==
#What did changing Briefly list the steps to install the relay_domains parameter do?MUA on your server for text-based messaging.#What firewall rule or rules, Briefly list the steps to trouble-shoot your server if any, did you have could not send e-mail messages from your vm2 machine to an external e-mail server.#Write the command to send an e-mail message from your vm2 to enter so that email between your VMs would work?Seneca College e-mail account.#What is are the commands to issue in the mail prompt to:<ul><li>Read the first e-mail message displayed</li><li>Save the 4th e-mail message to the meaning of file pathname: ~/maildir/3.msg.txt</li><li>Delete the square brackets surrounding 3rd e-mail message displayed</li><li>Exit the IP address in mail command prompt and return to the examples?shell</li></ul>#What were the results of sending email between the VMsemails locally on your vm2 machine? Show log segments to verify your answers.# What is the purpose of an MTA?# What is the purpose of an MUA?# Draw a simple diagram showing how an MUA and an MTA are used to send e-mail messages between different servers.# List the steps to test a running postfix service using the nc application.