No subject

Mon Jul 6 14:47:58 EDT 2009

e-mail campaigns and I was asked a question today concerning the
interpretation of the 1st rule of the Can-Spam Act.=20

=20

#1 reads:

Don't use false or misleading header information. Your "From," "To,"
"Reply-To," and routing information - including the originating domain
name and email address - must be accurate and identify the person or
business who initiated the message.=20

=20

=20

We currently have a "no-reply" email address set in the reply for some
emails (our news updates etc). Without going into great detail it's a
valid email address, but any NDRs or anything else comes to our mail
server and is then delivered to nowhere...it disappears into the e-mail
ether.=20

=20

For requests to be removed from the mail list we have instruction on how
to do so and an email box that remove requests are delivered to and IS
checked by a group here.=20

=20

Now the question...

Does our setup above comply to Can-Spam rule #1? One person here says it
does not because a person is not checking the reply-to email address.
However, the other school of thought is we ARE in compliance because #1
states the email must accurately ID the person OR business who initiated
the message. While the reply-To email address  (when using the "NDR
blackhole" reply-to address) doesn't ID a person, it does ID the
business (our domain name).=20

=20

Any thoughts or experience with this would be greatly appreciated. =20

------_=_NextPart_001_01CAB95C.29563459
Content-Type: text/html;
	charset="US-ASCII"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" =
xmlns:o=3D"urn:schemas-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" =
xmlns:p=3D"urn:schemas-microsoft-com:office:powerpoint" =
xmlns:a=3D"urn:schemas-microsoft-com:office:access" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
xmlns:s=3D"uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" =
xmlns:rs=3D"urn:schemas-microsoft-com:rowset" xmlns:z=3D"#RowsetSchema" =
xmlns:b=3D"urn:schemas-microsoft-com:office:publisher" =
xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadsheet" =
xmlns:c=3D"urn:schemas-microsoft-com:office:component:spreadsheet" =
xmlns:odc=3D"urn:schemas-microsoft-com:office:odc" =
xmlns:oa=3D"urn:schemas-microsoft-com:office:activation" =
xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" =
xmlns:rtc=3D"http://microsoft.com/officenet/conferencing" =
xmlns:D=3D"DAV:" xmlns:Repl=3D"http://schemas.microsoft.com/repl/" =
xmlns:mt=3D"http://schemas.microsoft.com/sharepoint/soap/meetings/" =
xmlns:x2=3D"http://schemas.microsoft.com/office/excel/2003/xml" =
xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" =
xmlns:ois=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" =
xmlns:dir=3D"http://schemas.microsoft.com/sharepoint/soap/directory/" =
xmlns:ds=3D"http://www.w3.org/2000/09/xmldsig#" =
xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint/dsp" =
xmlns:udc=3D"http://schemas.microsoft.com/data/udc" =
xmlns:xsd=3D"http://www.w3.org/2001/XMLSchema" =
xmlns:sub=3D"http://schemas.microsoft.com/sharepoint/soap/2002/1/alerts/"=
 xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#" =
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" =
xmlns:sps=3D"http://schemas.microsoft.com/sharepoint/soap/" =
xmlns:xsi=3D"http://www.w3.org/2001/XMLSchema-instance" =
xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/soap" =
xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile" =
xmlns:udcp2p=3D"http://schemas.microsoft.com/data/udc/parttopart" =
xmlns:wf=3D"http://schemas.microsoft.com/sharepoint/soap/workflow/" =
xmlns:dsss=3D"http://schemas.microsoft.com/office/2006/digsig-setup" =
xmlns:dssi=3D"http://schemas.microsoft.com/office/2006/digsig" =
xmlns:mdssi=3D"http://schemas.openxmlformats.org/package/2006/digital-sig=
nature" =
xmlns:mver=3D"http://schemas.openxmlformats.org/markup-compatibility/2006=
" xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" =
xmlns:mrels=3D"http://schemas.openxmlformats.org/package/2006/relationshi=
ps" xmlns:spwp=3D"http://microsoft.com/sharepoint/webpartpages" =
xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/services/2006/types"=
 =
xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/services/2006/messag=
es" =
xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/SlideLibrary/=
" =
xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPortalServer/Pub=
lishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" =
xmlns:st=3D"&#1;" xmlns=3D"http://www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @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:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
 /* List Definitions */
 @list l0
	{mso-list-id:2100060366;
	mso-list-template-ids:895246628;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

From time to time we review our CAN-SPAM compliance =
in
regard to our e-mail campaigns and I was asked a question today =
concerning the interpretation
of the 1st rule of the Can-Spam Act. <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>#1 reads:<o:p></o:p></p>

Don&#8217;t
use false or misleading header information. Your &#8220;From,&#8221;
&#8220;To,&#8221; &#8220;Reply-To,&#8221; and routing information =
&#8211;
including the originating domain name and email address &#8211; must be
accurate and identify the person or business who initiated the message. =
<o:p></o:p>

<p class=3DMsoNormal><span =
style=3D'font-size:9.0pt;font-family:"Arial","sans-serif"'><o:p>&nbsp;</o=
:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

We currently have a &#8220;no-reply&#8221; email =
address set
in the reply for some emails (our news updates etc). Without going into =
great
detail it&#8217;s a valid email address, but any NDRs or anything else =
comes to
our mail server and is then delivered to nowhere&#8230;it disappears =
into the
e-mail ether. <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

For requests to be removed from the mail list we =
have instruction
on how to do so and an email box that remove requests are delivered to =
and IS
checked by a group here. <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>Now the question&#8230;<o:p></o:p></p>

Does our setup above comply to Can-Spam rule #1? =
One person
here says it does not because a person is not checking the reply-to =
email
address. However, the other school of thought is we ARE in compliance =
because
#1 states the email must accurately ID the person OR business who =
initiated the
message. While the reply-To email address&nbsp; (when using the =
&#8220;NDR
blackhole&#8221; reply-to address) doesn&#8217;t ID a person, it does ID =
the
business (our domain name). <o:p></o:p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

Any thoughts or experience with this would be =
greatly
appreciated. &nbsp;<o:p></o:p>

</div>

</body>

</html>

------_=_NextPart_001_01CAB95C.29563459--