attachment-0001
<html 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" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><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:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Impact;
        panose-1:2 11 8 6 3 9 2 5 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman","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;}
p
        {mso-style-priority:99;
        mso-margin-top-alt:auto;
        margin-right:0in;
        mso-margin-bottom-alt:auto;
        margin-left:0in;
        font-size:12.0pt;
        font-family:"Times New Roman","serif";}
tt
        {mso-style-priority:99;
        font-family:"Courier New";}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
        {mso-style-priority:99;
        mso-style-link:"Balloon Text Char";
        margin:0in;
        margin-bottom:.0001pt;
        font-size:8.0pt;
        font-family:"Tahoma","sans-serif";}
span.EmailStyle19
        {mso-style-type:personal;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
span.BalloonTextChar
        {mso-style-name:"Balloon Text Char";
        mso-style-priority:99;
        mso-style-link:"Balloon Text";
        font-family:"Tahoma","sans-serif";}
span.EmailStyle22
        {mso-style-type:personal-reply;
        font-family:"Calibri","sans-serif";
        color:#1F497D;}
.MsoChpDefault
        {mso-style-type:export-only;
        font-size:10.0pt;}
@page WordSection1
        {size:8.5in 11.0in;
        margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
        {page:WordSection1;}
--></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 class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Bill,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>I agree that secure retrieval of printed FaxIn document via PIN is not a basic FaxIn use case. I prefer to defer this type of workflow to a document specifically on MFD workflows.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>Pete<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Impact","sans-serif";color:navy'>Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br><br></span><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif";color:navy'>Xerox Research Center Webster<br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Email: <a href="mailto:Peter.Zehler@Xerox.com">Peter.Zehler@Xerox.com</a></span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Voice: (585) 265-8755</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>FAX: (585) 265-7441</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>US Mail: Peter Zehler</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Xerox Corp.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>800 Phillips Rd.</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>M/S 128-25E</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><br></span><span style='font-size:10.0pt;font-family:"Arial","sans-serif";color:navy'>Webster NY, 14580-9701</span><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'> </span><span style='color:#1F497D'><o:p></o:p></span></p></div><p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> mfd-bounces@pwg.org [mailto:mfd-bounces@pwg.org] <b>On Behalf Of </b>William Wagner<br><b>Sent:</b> Wednesday, August 10, 2011 5:21 PM<br><b>To:</b> mfd@pwg.org<br><b>Subject:</b> RE: [MFD] Why FaxIn should NOT add the PrintService attributes<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'>OK, that seems consistent with what we have been doing. I would suggest that this is a case where a scenario narrative would be useful. If </span><span style='font-size:14.0pt;font-family:"Calibri","sans-serif"'>secure retrieval of printed FaxIn document via PIN is a desired basic FaxIn use case (and I am not sure that it is), the components and steps necessary to achieve it should be outlined. Conceivably, if there are more of this sort of multiple-service application which are not obvious as simple applications of a service but do not require the complexity of a workflow solution, perhaps they could be addressed in a separate MFD document?<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif"'>Thanks,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif"'>Bill W.<span style='color:#1F497D'><o:p></o:p></span></span></p><p class=MsoNormal><span style='font-size:14.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>From:</span></b><span style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> Ira McDonald [mailto:blueroofmusic@gmail.com] <br><b>Sent:</b> Wednesday, August 10, 2011 3:58 PM<br><b>To:</b> William Wagner; Ira McDonald<br><b>Cc:</b> Zehler, Peter; Nancy.Chen@okidata.com; mfd@pwg.org; mfd-bounces@pwg.org<br><b>Subject:</b> Re: [MFD] Why FaxIn should NOT add the PrintService attributes<o:p></o:p></span></p></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi, <br><br>For PIN printing, the destination of the FaxIn must be an electronic <br>document or a user's electronic mailbox under access control.<br><br>As a *separate* job, the end user has to walk up and start<br>a secure print job. There is no support for *any* DestinationURI<br>in any PWG MFD service to have a job ticket or other metadata<br>associated with it.<br><br>Fancy printing is NOT the use case of classic fax - just best<br>effort with the local PrintService's default job ticket is fine.<br><br>Real workflow is intentionally out-of-scope in PWG Semantic Model<br>(at least until SM/3.0 starts up as a project).<br><br>Cheers,<br>- Ira<br><br>Ira McDonald (Musician / Software Architect)<br>Chair - Linux Foundation Open Printing WG<br>Co-Chair - IEEE-ISTO PWG IPP WG<br>Chair - TCG Embedded Systems Hardcopy SWG<br>IETF Designated Expert - IPP & Printer MIB<br>Blue Roof Music/High North Inc<br><a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a><br><a href="http://sites.google.com/site/highnorthinc" target="_blank"><span style='color:#6600CC'>http://sites.google.com/site/highnorthinc</span></a><br>mailto:<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a><br>Christmas through April:<br> 579 Park Place Saline, MI 48176<br> 734-944-0094<br>May to Christmas:<br> PO Box 221 Grand Marais, MI 49839<br> 906-494-2434<o:p></o:p></p><p class=MsoNormal style='margin-bottom:12.0pt'><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Aug 10, 2011 at 2:43 PM, William Wagner <<a href="mailto:wamwagner@comcast.net">wamwagner@comcast.net</a>> wrote:<o:p></o:p></p><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:14.0pt;color:#1F497D'>I thought that the available job ticket just related to FaxIn processing (including the destination). The default job ticket for the destination printer would define print processing. I don’t recall that we had available job ticket capability for printers (do we?). At any rate, the path for communication the PIN code to the printer (and the intended recipient) is not clear.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:14.0pt;color:#1F497D'>Thanks.</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:14.0pt;color:#1F497D'>Bill Wagner</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:14.0pt;color:#1F497D'> </span><o:p></o:p></p><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a> [mailto:<a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a>] <b>On Behalf Of </b>Zehler, Peter<br><b>Sent:</b> Wednesday, August 10, 2011 2:06 PM<br><b>To:</b> <a href="mailto:Nancy.Chen@okidata.com" target="_blank">Nancy.Chen@okidata.com</a>; Ira McDonald<br><b>Cc:</b> <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a>; <a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a><br><b>Subject:</b> RE: [MFD] Why FaxIn should NOT add the PrintService attributes</span><o:p></o:p></p></div></div><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'>This can be accomplished via the AvailableJobTicket, its FaxInMetrics and FaxInJobTicket, and a properly configured Printer pointed to by DestinationUri. </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:navy'>Peter Zehler</span><span style='font-size:11.0pt;color:#1F497D'><br><br></span><span style='font-size:10.0pt;color:navy'>Xerox Research Center Webster<br>Email: <a href="mailto:Peter.Zehler@Xerox.com" target="_blank">Peter.Zehler@Xerox.com</a></span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>Voice: <a href="tel:%28585%29%20265-8755" target="_blank">(585) 265-8755</a></span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>FAX: <a href="tel:%28585%29%20265-7441" target="_blank">(585) 265-7441</a></span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>US Mail: Peter Zehler</span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>Xerox Corp.</span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>800 Phillips Rd.</span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>M/S 128-25E</span><span style='font-size:11.0pt;color:#1F497D'><br></span><span style='font-size:10.0pt;color:navy'>Webster NY, 14580-9701</span><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt;color:#1F497D'> </span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:10.0pt'>From:</span></b><span style='font-size:10.0pt'> <a href="mailto:Nancy.Chen@okidata.com" target="_blank">Nancy.Chen@okidata.com</a> [mailto:<a href="mailto:Nancy.Chen@okidata.com" target="_blank">Nancy.Chen@okidata.com</a>] <br><b>Sent:</b> Wednesday, August 10, 2011 1:33 PM<br><b>To:</b> Ira McDonald<br><b>Cc:</b> Ira McDonald; <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a>; <a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a>; Zehler, Peter<br><b>Subject:</b> Re: [MFD] Why FaxIn should NOT add the PrintService attributes</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br><span style='font-size:10.0pt'>How can secure retrieval of printed FaxIn document via PIN be supported this way? I remember somebody mentioned before in one of our meetings that this feature is desired. Just won't be supported?</span> <br><br><span style='font-size:10.0pt'>-Nancy</span> <o:p></o:p></p><table class=MsoNormalTable border=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td width="40%" valign=top style='width:40.0%;padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><b><span style='font-size:7.5pt'>Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>></span></b><span style='font-size:7.5pt'> </span><br><span style='font-size:7.5pt'>Sent by: <a href="mailto:mfd-bounces@pwg.org" target="_blank">mfd-bounces@pwg.org</a></span> <o:p></o:p></p><p><span style='font-size:7.5pt'>08/10/2011 11:57 AM</span> <o:p></o:p></p></td><td width="59%" valign=top style='width:59.0%;padding:.75pt .75pt .75pt .75pt'><table class=MsoNormalTable border=0 cellpadding=0 width="100%" style='width:100.0%'><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right'><span style='font-size:7.5pt'>To</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:7.5pt'>"Zehler, Peter" <<a href="mailto:Peter.Zehler@xerox.com" target="_blank">Peter.Zehler@xerox.com</a>>, Ira McDonald <<a href="mailto:blueroofmusic@gmail.com" target="_blank">blueroofmusic@gmail.com</a>>, <a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a></span> <o:p></o:p></p></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right'><span style='font-size:7.5pt'>cc</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td></tr><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal align=right style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto;text-align:right'><span style='font-size:7.5pt'>Subject</span><o:p></o:p></p></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:7.5pt'>[MFD] Why FaxIn should NOT add the PrintService attributes</span><o:p></o:p></p></td></tr></table><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'> <o:p></o:p></p><table class=MsoNormalTable border=0 cellpadding=0><tr><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td><td valign=top style='padding:.75pt .75pt .75pt .75pt'></td></tr></table></td></tr></table><p class=MsoNormal style='mso-margin-top-alt:auto;margin-bottom:12.0pt'><br><br><tt><span style='font-size:10.0pt'>Hi Pete,</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br></span><br><tt><span style='font-size:10.0pt'>Originally, we had some boolean to say "and by the way print"</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>for FaxIn (and EmailIn, presumably) - no longer in the schema.</tt><br></span><br><tt><span style='font-size:10.0pt'>Then we decided instead to tread print as just another destination.</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br></span><br><tt><span style='font-size:10.0pt'>And treating it that way let's the hardcopy for the FaxIn document</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>happen easily off-box (e.g., on a printer nearer the user).</tt><br></span><br><tt><span style='font-size:10.0pt'>I strongly favor no extra privilege/details for the print destination of</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>FaxIn - just a URI that points to some PrintService that prints with</tt><br><tt>the configured defaults.</tt><br></span><br><tt><span style='font-size:10.0pt'>Otherwise FaxIn-to-Print becomes more of a true compound</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>service - very undesirable.</tt><br></span><br><tt><span style='font-size:10.0pt'>WDYT?</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br></span><br><tt><span style='font-size:10.0pt'>Cheers,</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>- Ira</tt><br></span><br><br><tt><span style='font-size:10.0pt'>Ira McDonald (Musician / Software Architect)</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>Chair - Linux Foundation Open Printing WG</tt><br><tt>Co-Chair - IEEE-ISTO PWG IPP WG</tt><br><tt>Chair - TCG Embedded Systems Hardcopy SWG</tt><br><tt>IETF Designated Expert - IPP & Printer MIB</tt><br><tt>Blue Roof Music/High North Inc</tt><br><tt><a href="http://sites.google.com/site/blueroofmusic" target="_blank">http://sites.google.com/site/blueroofmusic</a></tt><br><tt><a href="http://sites.google.com/site/highnorthinc" target="_blank">http://sites.google.com/site/highnorthinc</a></tt><br><tt><a href="mailto:blueroofmusic@gmail.com" target="_blank">mailto:blueroofmusic@gmail.com</a></tt><br><tt>Christmas through April:</tt></span> <br><tt><span style='font-size:10.0pt'>579 Park Place Saline, MI 48176</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt><a href="tel:734-944-0094" target="_blank">734-944-0094</a></tt></span> <br><tt><span style='font-size:10.0pt'>May to Christmas:</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>PO Box 221 Grand Marais, MI 49839</tt><br><tt><a href="tel:906-494-2434" target="_blank">906-494-2434</a></tt></span> <br><br><tt><span style='font-size:10.0pt'>--</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>This message has been scanned for viruses and</tt><br><tt>dangerous content by MailScanner, and is</tt><br><tt>believed to be clean.</tt><br></span><br><br><tt><span style='font-size:10.0pt'>_______________________________________________</span></tt><span style='font-size:10.0pt;font-family:"Courier New"'><br><tt>mfd mailing list</tt><br><tt><a href="mailto:mfd@pwg.org" target="_blank">mfd@pwg.org</a></tt><br><tt><a href="https://www.pwg.org/mailman/listinfo/mfd" target="_blank">https://www.pwg.org/mailman/listinfo/mfd</a></tt></span> <o:p></o:p></p></div></div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><br>-- <o:p></o:p></p><div><p class=MsoNormal>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/" target="_blank"><b>MailScanner</b></a>, and is <br>believed to be clean. <o:p></o:p></p></div></div></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal><br>-- <br>This message has been scanned for viruses and <br>dangerous content by <a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is <br>believed to be clean. <o:p></o:p></p></div><br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body></html>