<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML xmlns="http://www.w3.org/TR/REC-html40" xmlns:v =
"urn:schemas-microsoft-com:vml" xmlns:o =
"urn:schemas-microsoft-com:office:office" xmlns:w =
"urn:schemas-microsoft-com:office:word" xmlns:m =
"http://schemas.microsoft.com/office/2004/12/omml"><HEAD>
<META content="text/html; charset=iso-8859-1" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.6001.18852">
<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;}
@font-face
        {font-family:Consolas;
        panose-1:2 11 6 9 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;}
-->
</STYLE>
<!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></HEAD>
<BODY lang=EN-US link=blue vLink=purple>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>Karl,</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>When you say "the list is not current," I hope you mean that not
all of your customers signed up for it, which means the
recipient membership of the mailing list is not up to date. But adding
new ways to deliver product announcements will not change that fact: customers
will still have to sign up for the new ways, and not everyone
will.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>I hope "the list is not current" does NOT mean that RenderX has
already made product announcements in ways other than the xep-announce mailing
list! </FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>Whatever announcement methods you provide to customers, you pretty
much have to use all of them for every announcement. Using a mailing list and
RSS is ideal for professional announcements, because they go into our received
e-mail storage systems and can be searched and found retroactively.
</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>I might sign up for a Twitter feed, but I hope it is never made the
primary product announcement mechanism for RenderX or anyone. I don't want to
have to remember to go to a vendor's Twitter page to retroactively look through
product announcements -- not when I already have searchable local storage of
e-mail and RSS feeds.</FONT></SPAN></DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia></FONT></SPAN> </DIV>
<DIV dir=ltr align=left><SPAN class=442182619-10112009><FONT color=#0000ff
face=Georgia>Requiring your customers to sign up for a Facebook account in order
to receive new product announcements would be unwise. Those who
already have a Facebook page might sign up as fans of a RenderX page, and might
not. Facebook pages are generally personal, but RenderX product announcements
are part of our professional life. </FONT></SPAN></DIV><BR>
<BLOCKQUOTE
style="BORDER-LEFT: #0000ff 2px solid; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; MARGIN-RIGHT: 0px"
dir=ltr>
<DIV dir=ltr lang=en-us class=OutlookMessageHeader align=left>
<HR tabIndex=-1>
<FONT size=2 face=Tahoma><B>From:</B> owner-xep-support@renderx.com
[mailto:owner-xep-support@renderx.com] <B>On Behalf Of </B>Karl
Stubsjoen<BR><B>Sent:</B> Tuesday, November 10, 2009 1:51 PM<BR><B>To:</B>
xep-support@renderx.com<BR><B>Cc:</B> 'Roman Kagarlitsky'<BR><B>Subject:</B>
[xep-support] Socializing RenderX News Announcements<BR></FONT><BR></DIV>
<DIV></DIV>
<DIV class=Section1>
<P class=MsoNormal>Hello All and Any,<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>RenderX is interested in your feedback. We are
considering different avenues for socializing news and announcements about our
product(s). We are considering RSS, Twitter, and other socializing
sites. For example, would you be more interested in following us
on Twitter, or becoming a fan of RenderX on Facebook?<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Traditionally, we have sent announcements through the
mailing list xep-announce. We can continue using this, but to date the
list is not current.<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Thanks, and we appreciate your feedback!<o:p></o:p></P>
<P class=MsoNormal><o:p> </o:p></P>
<P class=MsoNormal>Karl..<o:p></o:p></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">Karl
Stubsjoen<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">Senior Sales Engineer /
Professional Services <o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">RenderX, Inc. (Phoenix,
AZ)<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">Got
XML?<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">Get
RenderX!<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">The
Leader in XML to Print Technology<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN
style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt"><o:p> </o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">+1
(925) 392-0011 Direct<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt">+1
(602) 451-6157 Cell +1 (650) 328-8008 Fax<o:p></o:p></SPAN></P>
<P class=MsoNormal><SPAN style="FONT-FAMILY: Consolas; FONT-SIZE: 10.5pt"><A
href="mailto:stubsjoen@renderx.com">stubsjoen@renderx.com</A> <A
href="http://www.renderx.com/">http://www.renderx.com</A>
<o:p></o:p></SPAN></P>
<P class=MsoNormal><o:p> </o:p></P></DIV></BLOCKQUOTE></BODY></HTML>