<HTML >
<HEAD>
<META http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name=Generator content="Microsoft Word 12 (filtered medium)">
<title>AW: [rt-users] Issue with Extended mail commands / CommandByMail</title>
<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;}
/* 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";}
span.EmailStyle18
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@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>
<div class=Section1>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Well, I don’t know how to “fix it”, but what we do here is put
asterisks after we put in our commands and it looks like that stops
CommandByMail to continue looking for commands. If we don’t do the asterisks,
then it will definitely continue going down the line looking for words with “:”
at the end (this is annoying when forwarding messages into RT). <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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>So, we would do:<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Requestor: BillyBob<o:p></o:p></span></p>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Owner: JoeSchmoe<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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'><content of ticket here><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>
<p class=MsoNormal><span style='font-size:11.0pt;font-family:"Calibri","sans-serif";
color:#1F497D'>Also as a side note, we’ve found if you send in Tickets in HTML
format it will only read the first “Command” and the not following lines.<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>
<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"'>
rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] <b>On Behalf Of </b>Ham
MI-ID, Torsten Brumm<br>
<b>Sent:</b> Thursday, August 16, 2007 6:42 AM<br>
<b>To:</b> Ham MI-ID, Torsten Brumm; rt-users@lists.bestpractical.com<br>
<b>Cc:</b> j@bestpractical.com<br>
<b>Subject:</b> AW: [rt-users] Issue with Extended mail commands /
CommandByMail<o:p></o:p></span></p>
</div>
</div>
<p class=MsoNormal><o:p> </o:p></p>
<p><span style='font-size:10.0pt'>Nobody have a hint on this problem?!?<br>
<br>
Torsten<br>
<br>
-----Original Message-----<br>
From: rt-users-bounces@lists.bestpractical.com
<rt-users-bounces@lists.bestpractical.com><br>
To: rt-users@lists.bestpractical.com <rt-users@lists.bestpractical.com><br>
CC: j@bestpractical.com <j@bestpractical.com><br>
Sent: Mon Jul 30 10:10:01 2007<br>
Subject: [rt-users] Issue with Extended mail commands / CommandByMail<br>
<br>
Hi RT Users, Jesse,<br>
<br>
At weekend we tried to use commandbymail extension, but it ends up in<br>
lots of trouble.<br>
<br>
For me it looks like (and that's what I also found at the lilst inside a<br>
posting from Robert G. Werner) Command By Mail is trying to handle all<br>
Words he find with an ":", that's not good!<br>
<br>
Example:<br>
<br>
A Mail with the Content:<br>
<br>
System_Name: ASKNEHST<br>
Order_Type: new<br>
<br>
Generates this Error:<br>
<br>
Failed command 'system_name: ASKNEHST'<br>
Error message: Command 'system_name' is unknown<br>
<br>
Failed command 'Order_type: new'<br>
Error message: Command 'order_type' is unknown<br>
<br>
But from my Point of view, it will make more sense to handle only the<br>
known commands and not each word he finds separated with the ":"<br>
<br>
Any Ideas how to fix this???<br>
<br>
Torsten<br>
_______________________________________________<br>
<a href="http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users">http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users</a><br>
<br>
Community help: <a href="http://wiki.bestpractical.com">http://wiki.bestpractical.com</a><br>
Commercial support: sales@bestpractical.com<br>
<br>
<br>
Discover RT's hidden secrets with RT Essentials from O'Reilly Media.<br>
Buy a copy at <a href="http://rtbook.bestpractical.com">http://rtbook.bestpractical.com</a></span><o:p></o:p></p>
</div>
</DIV>
<DIV STYLE="FONT-SIZE: 9pt; FONT-FAMILY: Courier New">This message from CompuPay (and any associated files) is intended only for the <BR>use of the individual or entity to which it is addressed and may <BR>contain information that is confidential, subject to copyright or<BR>constitutes a trade secret. If you are not the intended recipient <BR>you are hereby notified that any dissemination, copying or <BR>distribution of this message, or files associated with this message, <BR>is strictly prohibited. If you have received this message in error, <BR>please notify us immediately by replying to the message and deleting <BR>it from your computer. Messages sent to and from us may be monitored. <BR><BR>For more information regarding CompuPay, please visit www.compupay.com.<BR></DIV></BODY></HTML>