<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 22/11/2016 3:54 PM, David Beveridge
wrote:<br>
</div>
<blockquote
cite="mid:CAM9f+Zy3SKdeiKYvAd8gs8PmWzjMmwGJVpmjcQ+9k1nNkDg4CA@mail.gmail.com"
type="cite">
<div dir="ltr">Really, I'm sorry, but how does the purported
sender email address tell you the source of on email
communication?</div>
</blockquote>
<br>
It doesn't.<br>
The legislation says you need to give them what they asked for. Its
not your problem if it is useful to them or not, or if the
originator has faked it.<br>
<br>
The purported 'From:' line that users see displayed on the screen is
part of the body (content) of the message anyway (it is sent in the
DATA block for SMTP protocol messages) so its arguably irrelevent,
but most email servers log it anyway.<br>
Assuming its the SMTP protocol that underpins your email message
transport service, the name that their email server put in the
'RCVD:' SMTP field would be relevent identifiers for the source of
the communication, as would the IP address logged by your email
server of the email server that pushed the message to you [usually
logged in the same log line in square brackets]. Most email servers
log these items of information on the same log line. You cannot
know the original source IP address of the machine that sent the
message five SMTP transactions before, so no point trying to find
that out - thats their job.<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<blockquote
cite="mid:CAM9f+Zy3SKdeiKYvAd8gs8PmWzjMmwGJVpmjcQ+9k1nNkDg4CA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra"><br>
<div class="gmail_quote">On Tue, Nov 22, 2016 at 2:49 PM, Paul
Brooks <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:paul.brooks@tridentsc.com.au"
target="_blank">paul.brooks@tridentsc.com.au</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000"><span class="">
<div class="m_-2032241774313459379moz-cite-prefix">On
22/11/2016 3:27 PM, David Beveridge wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr"><a moz-do-not-send="true"
href="https://www.ag.gov.au/NationalSecurity/DataRetention/Documents/Dataset.pdf"
target="_blank">https://www.ag.gov.au/<wbr>NationalSecurity/<wbr>DataRetention/Documents/<wbr>Dataset.pdf</a><br>
<div><br>
</div>
<div>2. The source of a communication </div>
<div>Identifiers of a related account, service or
device from which a communication has been sent
or attempted to be sent by means of the relevant
service.</div>
<div><br>
</div>
<div>Identifiers for the source of a communication
may include, but are not limited to: </div>
<div>• the phone number, IMSI, IMEI from which a
call or SMS was made </div>
<div>• identifying details (such as username,
address, number) of the account, service or
device from which a text, voice, or multi-media
communication was made (examples include email,
Voice over IP (VoIP), instant message Topic
Description of information Explanation or video
communication) </div>
<div><b>• the IP address and port number allocated
to the subscriber or device connected to the
internet at the time of the communication, or </b></div>
<div>• any other service or device identifier
known to the provider that uniquely identifies
the source of the communication.<b> </b><b><font
color="#ff0000">In all instances, the
identifiers retained to identify the source
of the communication are the ones relevant
to, or used in, the operation of the
particular service in question.</font></b><br>
</div>
</div>
</blockquote>
<br>
</span> The question is about email application and
email communications. Retaining the addressing
information at the level of 'email application service'.
The CAC and AGs have confirmed there is no requirement
to retain addressing information at a different 'layer'
than the service under question.<br>
TCP port numbers do not need to be retained for
retaining information about emails and an email service.
Nor ethernet MAC addresses or ATM cell IDs if thats the
way you roll. Only identifiers relevent to the service
under consideration - e.g. email addresses, and
potentially email server DNS names if you provide
specific names to your customers as part of your service
definition.<br>
<br>
Note you aren't breaking any law by voluntarily
providing port address information if you have it -
nothing in the legislation says you can't provide
additional information voluntarily. But you don't need
to, for an email application service.<span class=""><br>
<br>
<br>
</span></div>
</blockquote>
</div>
</div>
</div>
</blockquote>
<br>
<p><br>
</p>
<div class="moz-signature">-- <br>
<style>
<!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin-top:0cm; margin-right:0cm; margin-bottom:0cm; margin-left:0cm;
line-height:100%;
color:darkblue;
font-size:10.0pt;
font-family:"Calibri","sans-serif";}
-->
</style>
<div>
<p class="MsoNormal"><b><span
style="color:black;font-size:14.0pt;line-height:115%">Paul
Brooks</span></b></p>
<p class="MsoNormal"><b><style='color:black'>Executive GM -
Networks & Technology</style='color:black'></b></p>
<p class="MsoNormal">Email: <a class="moz-txt-link-abbreviated" href="mailto:paul.brooks@tridentsc.com.au">paul.brooks@tridentsc.com.au</a></p>
<p class="MsoNormal">Mobile +61 414 366 605</p>
<p class="MsoNormal"> </p>
<p class="MsoNormal"><a href="http://www.tridentsc.com.au"><img
alt="Trident Logo"
src="cid:part3.EE18F6A1.FBEE0FDD@tridentsc.com.au"
height="69" width="213"></a></p>
<p class="MsoNormal"><b><span
style="color:#6600CC;font-size:14.0pt;line-height:115%">Trident
Subsea Cable Pty Ltd</span></b></p>
<p class="MsoNormal"><b><span>Pilbara Connectivity // South East
Asia Systems</span></b></p>
<p class="MsoNormal">Level 12, 37 Bligh Street, Sydney NSW 2000,
Australia</p>
<p class="MsoNormal"><a class="moz-txt-link-freetext" href="http://www.tridentsc.com.au">http://www.tridentsc.com.au</a></p>
</div>
</div>
</body>
</html>