Joe,<br><br>That is EXACTLY what I'm getting.<br><br>Although I don't include a "time" portion, so the only colon that exists is right after the command.<br><br>Kenn<br>LBNL<br><br><div class="gmail_quote">
On Tue, Nov 23, 2010 at 9:44 AM, Joe Harris <span dir="ltr"><<a href="mailto:drey111@gmail.com">drey111@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
I believe this is the same issue I was having and it stemmed from there being colons in the same line with the command. <br>i.e. Due: 2010-11-25 17:30:00<br><br>This command works both on update and create, but the mail server returns an error when updating:<br>
Extended mailgate error<br>Failed command 'due: 2010-11-25 17:30:00'<br>Error message (no message)<br><br>Is this the same issue you are having?<div class="im"><br><br><p>Sent from blackberry</p><hr><div><b>From: </b> Kenneth Crocker <<a href="mailto:kfcrocker@lbl.gov" target="_blank">kfcrocker@lbl.gov</a>>
</div><div><b>Sender: </b> <a href="mailto:rt-users-bounces@lists.bestpractical.com" target="_blank">rt-users-bounces@lists.bestpractical.com</a>
</div></div><div><b>Date: </b>Tue, 23 Nov 2010 09:25:39 -0800</div><div class="im"><div><b>To: </b><<a href="mailto:rt-users@lists.bestpractical.com" target="_blank">rt-users@lists.bestpractical.com</a>></div></div>
<div><b>Subject: </b>Re: [rt-users] Revisiting CommandByMail problem</div><div><div></div><div class="h5"><div><br></div>Kevin,<br><br>I've never written a perl program in my life. I've coded a few scrips here and there.<br>
I apologize for not having done a better job of testing my problems earlier. They were all updates. I hadn't tried a fresh create at that time.<br>
When I create a new ticket via CommanbByMail, all commands work well. When I copy/paste those same commands into an update email, the dates DO get updated, but I get an error message in a returned email.<br>That's the best info I can give you.<br>
I wouldn't know where to begin when it comes to coding a patch or testsuite.<br><br>Kenn<br>LBNL<br><br><div class="gmail_quote">On Mon, Nov 22, 2010 at 4:53 PM, Kevin Falcone <span dir="ltr"><<a href="mailto:falcone@bestpractical.com" target="_blank">falcone@bestpractical.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"><div><div></div><div>On Mon, Nov 22, 2010 at 02:01:00PM -0800, Kenneth Crocker wrote:<br>
> To List,<br>
><br>
> I've continued to have problems with getting an error message from RT when using CommandByMail<br>
> and I found an interesting situation:<br>
><br>
> When I create a ticket using email and include many fields (dates and otherwise), the ticket<br>
> is created and I get no error message back.<br>
><br>
> When I try to update a ticket using CommandByMail (referencing the ticket in the Subject<br>
> line), the ticket is updated, yet I get an error message back from RT in email stating errord<br>
> for the date fields. Yet the data WAS updated.<br>
><br>
> I went to the rt.log and noticed that the update fields get updated, then a transaction Type<br>
> "Correspond" is processed and THEN the error messages get sent.<br>
><br>
> I then went to the DataBase and looked at the TRANSACTION Table and found the transactions and<br>
> sure enough, there is a transaction record Type "Set" for each date field and any other fields<br>
> all followed by that "Correspond": Type trans record. I also noticed that regardless of what<br>
> non-date fields I am updating in sequence after the date fields, the transactions for the date<br>
> fields are always processed last just before the transaction type "correspond".<br>
><br>
> I just did a complete install of CommandByMail to ensure I hadn't accidentally messed up any<br>
> files.<br>
><br>
> So, I have two questions:<br>
><br>
> 1) Why does the "Create" email work without any error messages and the "Update" work but send<br>
> error messages?<br>
> 2) Why would CBM go ahead and update the ticket and then only when it processes the<br>
> "Correspond" transaction decide to send out error messages for the date fields?<br>
<br>
</div></div>If you're passing a correctly formatted Due date on Correspond emails<br>
and getting errors, then that may well be a bug. Your previous emails<br>
have shown that you weren't passing a valid Due date.<br>
<br>
The easiest way to get this fixed is a patch that adds a failing test<br>
to the testsuite.<br>
<font color="#888888"><br>
-kevin<br>
</font></blockquote></div><br>
</div></div></blockquote></div><br>