I recently upgraded our RT 3.8.9 by making a new RT 4.0.5 installation and
then moving and upgrading the database by the upgrade instructions. Before
doing so, I upgraded the OS of the computer from Debian Lenny to Debian
Squeeze.
After that, I installed RT-Extension-CommandByMail-0.10 using the
On 04/18/2012 09:59 AM, Fritz Mahnke wrote:
I made the required changes to /opt/rt4/etc/RT_SiteConfig.pm:
@MailPlugins = qw(Auth::MailFrom Filter::TakeAction);
Set(@Plugins, (qw(RT::Extension::CommandByMail)));
You're using the RT 3.6 era syntax for @MailPlugins, not the 3.8 and
beyond era
That's true, but I tried it both ways. I just changed it:
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
And then I issued /etc/init.d/apache2 restart. But the ticket still doesn't
process correctly and no CommandByMail messages in the logs.
I suggest you check /Admin/Tools/Configuration.html to see if @MailPlugins and
@Plugins were set successfully.
sunnavy
On 12-04-18 09:30, Fritz Mahnke wrote:
That's true, but I tried it both ways. I just changed it:
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
And then I
Thank you very much for that useful hint. @MailPlugins was not being set
correctly and I traced it to a typo in RT_SiteConfig.pm after all.
Thanks again!
To list,
I've finally got CommandByMail to work with Custom Fields. Apparently,
for any Custom Field to work, it needs to have a one-word name or a
hyphenated name. I didn't read this in any of the READ ME's. So, since
98% of my Custom Fields have more than one word, like Migrated Date, I
Since the parsing for this is via regex, maybe we can adjust
the regex used to incorporate spaces in CFs.
Cheers,
Ken
On Wed, Mar 03, 2010 at 11:39:29AM -0800, Ken Crocker wrote:
To list,
I've finally got CommandByMail to work with Custom Fields. Apparently, for
any Custom Field to work, it
Oops, the syntax for Custom Fields using CommandByMail is
CustomField.{CFName}: custom field value
or
CF.{CFName}: custom field value
That works here with spaces.
Cheers,
Ken
On Wed, Mar 03, 2010 at 02:09:46PM -0600, Kenneth Marshall wrote:
Since the parsing for this is via regex, maybe we
Oh, and the dot (.) should not be there. You also need the
latest release to fix the regex space bug.
Cheers,
Ken
On Wed, Mar 03, 2010 at 02:29:07PM -0600, Kenneth Marshall wrote:
Oops, the syntax for Custom Fields using CommandByMail is
CustomField.{CFName}: custom field value
or
Kenneth,
Are you saying I need a and a on each side of the CF name? In
addition to the brackets?
Kenn
LBNL
On 3/3/2010 12:29 PM, Kenneth Marshall wrote:
Oops, the syntax for Custom Fields using CommandByMail is
CustomField.{CFName}: custom field value
or
CF.{CFName}: custom field
Kenneth,
To be honest, we just installed this a few day (maybe a week) ago. So I
assumed we HAD the latest version. I'll take a look in the wiki and see
what's up.
Kenn
LBNL
On 3/3/2010 12:37 PM, Kenneth Marshall wrote:
Oh, and the dot (.) should not be there. You also need the
latest
Use version 0.08 from last August. You do not include , just
the text of the name or value.
Ken
On Wed, Mar 03, 2010 at 12:35:36PM -0800, Ken Crocker wrote:
Kenneth,
Are you saying I need a and a on each side of the CF name? In addition
to the brackets?
Kenn
LBNL
On 3/3/2010 12:29
Kenneth,
That was it. My guy installed .08 and now all works well. I do get an
error for the command Content, but as long as I put any comments at
the end, it works fine.
Thanks again for your help.
Kenn
LBNL
On 3/3/2010 12:53 PM, Kenneth Marshall wrote:
Use version 0.08 from last August.
Kevin,
Did you get my earlier response with the data I used in the Email?
Kenn
LBNL
On 2/23/2010 1:43 PM, Kevin Falcone wrote:
On Tue, Feb 23, 2010 at 10:59:51AM -0800, Ken Crocker wrote:
I've installed CommandByMail. The instructions describe the ability to
create a ticket WITH
To list,
I've installed CommandByMail. The instructions describe the ability to
create a ticket WITH CustomField values. However, I'm finding this
doesn't seem to be true. Do I also need to install an additional
extension for this?
Thanks.
Kenn
LBNL
On Tue, Feb 23, 2010 at 10:59:51AM -0800, Ken Crocker wrote:
I've installed CommandByMail. The instructions describe the ability to
create a ticket WITH CustomField values. However, I'm finding this
doesn't seem to be true. Do I also need to install an additional
extension for this?
What
Kevin,
Thanks for responding. The following are the several tries to get a
CustomFIeld set:
This was in the body the first time:
Status: open
Owner: CACasaretto
Priority: 3
CustomField.{Description}: This is the first test for CommandByMail
José de Paula Eufrásio Júnior wrote:
[snip]
But I have other fields, like CF.{Classificação do Chamado} that are
not working with the CommandByMail extension. No log messages,
nothing, it just don't execute the command. I have two theories:
1) The extension has some problem with the
I agree that it's most probably an issue with encodings, but I don't
when we'll have time to fix it, so patches are welcome.
On 5/16/07, Robert G. Werner [EMAIL PROTECTED] wrote:
José de Paula Eufrásio Júnior wrote:
[snip]
But I have other fields, like CF.{Classificação do Chamado} that are
Hi everyone,
I am having trouble installing the CommandByMail extension. I have
looked through the archives but only managed to find how easy it was to
installbut they forgot to mention the easy steps they took.
Is there a step by step somewhere I could follow? When I type in the
Helmuth Ramirez wrote:
Hi everyone,
I am having trouble installing the CommandByMail extension. I have
looked through the archives but only managed to find how easy it was
to install….but they forgot to mention the easy steps they took.
Is there a step by step somewhere I could follow?
. No wonder the Makefile never worked.
Thanks Chaim!
-Original Message-
From: chaim rieger [mailto:[EMAIL PROTECTED]
Sent: Friday, March 30, 2007 5:28 PM
To: Helmuth Ramirez
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] CommandByMail Extension
Helmuth Ramirez wrote:
Hi
22 matches
Mail list logo
