1: What information about a user’s email, the origin of a message, and the path it took, can you glean from an email message? (Allen, n.d)

· The message was received on Thur, 29 May 2008 14:08:08
· The message was from * OpenCurtin@curtin.edu.au
* The first part of the address is the user name (eg. homer@ or homer241@)
*The second part of the address is the domain. This address is .edu.au (education domain in Australia), you may also come across free domains (eg. Yahoo and Hotmail) or Government domains (.gov.au).
· The To field is the receiver of the email. If it is your inbox then it would be you.
The above message says To: Undisclosed recipients ( because this is an email regarding studies, I would imagine that it would be sent to all the Net11 students. Undisclosed hides the other students details)
· The Subject field gives a brief inclination of what the message is about.
If a message is urgent, you may see a subject as eg URGENT : school interview cancelled
· In the field labelled Path(s) I can see that the message has 4 attachments
The above attachments are documents outlining my course.
· The body of the email contains the whole message and as this one, the signature of who sent it.
In reflection of the Email Task question, when I gleaned this message for more information, I found the following screenshot within ‘Message Source’. I perceive from this information that the message passed through 4 servers from Curtin to my Inbox.
Not showing in the email used here, you are also able to see whether the message has been forwarded to you from the sender (eg the subject will show Fw: bla bla bla)
Also whether the message has been CC to another host. (eg a copy of the email is sent to another recipient other than you) This feature will be covered in more depth in question 2:)
Curriculum Reference:
Dr Matthew Allen (n.d) Curtin University of Technology; Net 11 The Internet Communications,Module two, Email Task, Retrieved 25 June 2008 from http://webct.curtin.edu.au/SCRIPT/305033_b/scripts/serve_home.
Email Task to be continued.......

No comments:
Post a Comment