Difference between revisions of "OPS335 Email Lab"
(→Test email using host names) |
m (Replacing references to 'learn' email with the new myseneca.) |
||
Line 5: | Line 5: | ||
{{Admon/important|Prerequistites|Your hard drive should have Fedora 16, 64 bit Live edition already installed.<br />Both host and guest should have all software updated.<br />Ensure the clocks on both machines are set to the correct date and time.}} | {{Admon/important|Prerequistites|Your hard drive should have Fedora 16, 64 bit Live edition already installed.<br />Both host and guest should have all software updated.<br />Ensure the clocks on both machines are set to the correct date and time.}} | ||
=== Testing your network === | === Testing your network === | ||
− | *Start Firefox on your host and authenticate yourself on Senenet with your | + | *Start Firefox on your host and authenticate yourself on Senenet with your Seneca account. |
*Ensure you can surf the web on your host machine. | *Ensure you can surf the web on your host machine. | ||
*Ensure you can access the web on your VM (you can use wget for that). NOTE: you should not have to authenticate yourself on the guest. | *Ensure you can access the web on your VM (you can use wget for that). NOTE: you should not have to authenticate yourself on the guest. | ||
Line 13: | Line 13: | ||
*Install mailx on both the host and the guest. | *Install mailx on both the host and the guest. | ||
yum install mailx | yum install mailx | ||
− | *Test email from the host by sending an email to your | + | *Test email from the host by sending an email to your Seneca account. |
− | mail -s "PART C3" xxxxxx@ | + | mail -s "PART C3" xxxxxx@myseneca.ca |
− | Note: xxxxxx is your | + | Note: xxxxxx is your Seneca ID.<br /> |
Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key. | Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key. | ||
− | *Check your | + | *Check your myseneca email to see if you got the email. If you did make a note of the return address. |
− | *Test email from the host by sending an email to your | + | *Test email from the host by sending an email to your myseneca account. |
− | mail -s "PART C4" -r hacker@evil.com xxxxxx@ | + | mail -s "PART C4" -r hacker@evil.com xxxxxx@myseneca.ca |
− | Note: xxxxxx is your | + | Note: xxxxxx is your Seneca ID.<br /> |
Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key. | Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key. | ||
− | *Check your | + | *Check your myseneca email to see if you got the email. If you did make a note of the return address. |
*Repeat these steps on the guest machine. | *Repeat these steps on the guest machine. | ||
Line 32: | Line 32: | ||
yum install postfix | yum install postfix | ||
*Edit the Postfix configuration file, /etc/postfix/main.cf, and change the following lines ( be sure that there are no other instances of that line as well, comment as needed): | *Edit the Postfix configuration file, /etc/postfix/main.cf, and change the following lines ( be sure that there are no other instances of that line as well, comment as needed): | ||
− | mydomain = < | + | mydomain = <senecaID>.org |
myorigin = $mydomain | myorigin = $mydomain | ||
mynetworks = 127.0.0.0/8, 192.168.X.0/24 | mynetworks = 127.0.0.0/8, 192.168.X.0/24 | ||
Line 44: | Line 44: | ||
*Try sending an email from vm01 to your host. | *Try sending an email from vm01 to your host. | ||
mail -s "PART E2" yyyyyy@[192.168.X.1] | mail -s "PART E2" yyyyyy@[192.168.X.1] | ||
− | Note: yyyyyy is your | + | Note: yyyyyy is your Seneca ID<br /> |
Note: the square brackets around the host IP address | Note: the square brackets around the host IP address | ||
*Try sending an email from your host to vm01. | *Try sending an email from your host to vm01. | ||
mail -s "PART E3" zzzzzz@[192.168.X.2] | mail -s "PART E3" zzzzzz@[192.168.X.2] | ||
− | Note: zzzzzz is your | + | Note: zzzzzz is your Seneca ID<br /> |
===Test email using host names=== | ===Test email using host names=== | ||
Line 54: | Line 54: | ||
Restart postfix if you change this. | Restart postfix if you change this. | ||
− | Now try sending mail to yourself on both machines. For example, as < | + | Now try sending mail to yourself on both machines. For example, as <senecaID> on f16, use the command: |
− | $ mail < | + | $ mail <senecaID>@f16 |
the machine will prompt for a subject: enter "testing" without the quotes. | the machine will prompt for a subject: enter "testing" without the quotes. | ||
Line 73: | Line 73: | ||
==Completing the Lab== | ==Completing the Lab== | ||
− | # | + | #Create a copy of your main.cf file on vm01 (your guest) with this lab - but delete all commented and blank lines first - like this. [cat /etc/postfix/main.cf | grep -v ^# | awk 'NF > 0 {print $0}'] |
#What is the output of the iptables-save command on both your host and guest machines? | #What is the output of the iptables-save command on both your host and guest machines? | ||
#What firewall rule or rules, if any, did you have to enter on the guest and/or host so that email to/from each other would work? | #What firewall rule or rules, if any, did you have to enter on the guest and/or host so that email to/from each other would work? | ||
#What is the meaning of the square brackets surrounding the IP address in the examples? | #What is the meaning of the square brackets surrounding the IP address in the examples? | ||
#What were the results of sending email between the host and the vm? Show log segments to verify your answers. | #What were the results of sending email between the host and the vm? Show log segments to verify your answers. |
Revision as of 10:32, 21 September 2012
Basic Mail (Postfix) Setup
This lab will show you how to set up a Postfix email server using a Fedora 16 installed PC.
- You will need at least two systems to do this lab. The first could be Fedora on your removable hard drive while the second could be a virtual machine.
Testing your network
- Start Firefox on your host and authenticate yourself on Senenet with your Seneca account.
- Ensure you can surf the web on your host machine.
- Ensure you can access the web on your VM (you can use wget for that). NOTE: you should not have to authenticate yourself on the guest.
Testing email to the outside world using mailx and sendmail
- Sendmail is installed and running by default on Fedora 16 so there is no need to install it.
- Install mailx on both the host and the guest.
yum install mailx
- Test email from the host by sending an email to your Seneca account.
mail -s "PART C3" xxxxxx@myseneca.ca
Note: xxxxxx is your Seneca ID.
Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key.
- Check your myseneca email to see if you got the email. If you did make a note of the return address.
- Test email from the host by sending an email to your myseneca account.
mail -s "PART C4" -r hacker@evil.com xxxxxx@myseneca.ca
Note: xxxxxx is your Seneca ID.
Note: after you type in your letter, enter a period in the first column on the last line and hit the ENTER key.
- Check your myseneca email to see if you got the email. If you did make a note of the return address.
- Repeat these steps on the guest machine.
Install and configure Postfix
- On both machines do the following:
- Stop sendmail.
systemctl stop sendmail.service
- Install Postfix
yum install postfix
- Edit the Postfix configuration file, /etc/postfix/main.cf, and change the following lines ( be sure that there are no other instances of that line as well, comment as needed):
mydomain = <senecaID>.org myorigin = $mydomain mynetworks = 127.0.0.0/8, 192.168.X.0/24 relay_domains = inet_interfaces=all
- Start Postfix on both machines:
systemctl start postfix.service
Testing email using IP Addresses
- If you have problems with the following you may have to set SELinux to permissive mode and/or adjust your firewall to allow traffic to/from port 25.
- Try sending an email from vm01 to your host.
mail -s "PART E2" yyyyyy@[192.168.X.1]
Note: yyyyyy is your Seneca ID
Note: the square brackets around the host IP address
- Try sending an email from your host to vm01.
mail -s "PART E3" zzzzzz@[192.168.X.2]
Note: zzzzzz is your Seneca ID
Test email using host names
For this part make sure that your f16 machine has a correct host name - f16.yourdomain.org. Restart postfix if you change this.
Now try sending mail to yourself on both machines. For example, as <senecaID> on f16, use the command:
$ mail <senecaID>@f16
the machine will prompt for a subject: enter "testing" without the quotes.
- Now enter the body of your letter. When you're done, enter a period (.) in column 1 on the last line of your letter. This will signal end-of-file and your letter will be mailed. You should end up back at the $ prompt. If you mess up use CTRL-C to cancel the email, DO NOT USE CTRL-Z.
- Use the mailq command (you will need to be root) to view the mail queue.
Use the mail command to check if you have mail.
Test your configuration and view your logs
- Restart your postfix servers on both machines.
- Check your /var/log/messages file to see that your postfix servers started without error.
- Send some emails from both guest and host to each other and to the outside world.
- Check your /var/log/maillog file to see that your email messages were sent correctly.
Learning the mail command
- Read the mail manual page and learn how it works.
Completing the Lab
- Create a copy of your main.cf file on vm01 (your guest) with this lab - but delete all commented and blank lines first - like this. [cat /etc/postfix/main.cf | grep -v ^# | awk 'NF > 0 {print $0}']
- What is the output of the iptables-save command on both your host and guest machines?
- What firewall rule or rules, if any, did you have to enter on the guest and/or host so that email to/from each other would work?
- What is the meaning of the square brackets surrounding the IP address in the examples?
- What were the results of sending email between the host and the vm? Show log segments to verify your answers.