To: Dunbar, Brian
Cc: rt-users
Subject: Re: [rt-users] CommandByMail config
Is the command you are sending on the very first line of the message? Did you
really send an email with both of those commands with the word Or between them
or was that two examples? Is there anything in the log (ie
Is the command you are sending on the very first line of the message? Did you
really send an email with both of those commands with the word Or between them
or was that two examples? Is there anything in the log (ie.
/opt/rt4/var/log/rt.log) when the email correspondence is being dealt with?
Hello All,
I am trying to enable CommandByMail
I installed the plugin and patch
Added these two lines to my RT_SiteConfig.pm
Plugin('RT::Extension::CommandByMail');
Set(@MailPlugins, qw(Auth::MailFrom Action::CommandByMail));
When I send an email with
Queue: Nameofqueue
Or
Status: resolved
. Thanks.
Armin
From: Che Geiser [mailto:chegei...@gmail.com]
Sent: Wednesday, June 15, 2016 4:53 PM
To: Armin Liedtke <armha...@uw.edu>
Cc: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] CommandByMail 2.1 and RT 4.4.0 - Permission denied.
I've had this exact same result with Command
I've had this exact same result with CommandByMail 2.1 and RT 4.4.0. I'm
new to RT and didn't know this was not the way it used to work. It does
open up the system to some risk as I do need to accept emails into RT from
outside sources and though unlikely it does make it possible for outside
users
Hello,
I have had our CommandByMail updated to the new version 2.1 and our RT is
4.4.0. I have setup a group that is allowed to use CommandByMail.
In the past; If you where is the group it would run the commands correctly. If
you were not in the group it bypassed the CommandByMail and work
Le 06/10/2014 18:00, Kevin Falcone a écrit :
On Mon, Oct 06, 2014 at 10:03:59AM +0200, Olivier Lumineau wrote:
I'm trying to install CommandByMail Plugin and it's not working.
What version of RT?
Sorry for this missing...
It's RT 4.2.5
# make install
Installing
On Tue, Oct 07, 2014 at 11:45:38AM +0200, Olivier Lumineau wrote:
Also, did you already add RT::Extension::CommandByMail to Plugins in
your RT_SiteConfig.pm, before running make install?
Yes but not correctly :-[
I've added it like other plugins :
Plugin('RT::Extension::CommandByMail');
Hello,
I'm trying to install CommandByMail Plugin and it's not working.
The end of installation give me an error message (see below) :
# perl Makefile.PL
Using RT configuration from /opt/rt4/lib/RT.pm:
lib =
On Mon, Oct 06, 2014 at 10:03:59AM +0200, Olivier Lumineau wrote:
I'm trying to install CommandByMail Plugin and it's not working.
What version of RT?
# make install
Installing /opt/rt4/local/plugins/RT-Extension-CommandByMail/lib/RT/Extension/
CommandByMail.pm
Installing
On Wed, Apr 17, 2013 at 1:32 PM, Asif Iqbal vad...@gmail.com wrote:
Looks like this time it is trying to use CommandByMail by failing with
permission error. I am sending the reply and I am owner of the ticket. What
permission
is missing?
It worked this time. Looks like I have multiple
On Sun, Apr 14, 2013 at 2:55 PM, Asif Iqbal vad...@gmail.com wrote:
I installed RT-Extension-CommandByMail-0.10 on my RT 3.8.2 and setup the
config like below.
Set( @Plugins, qw( RT::Authen::ExternalAuth RT::Extension::CommandByMail )
);
Set(@MailPlugins, qw(Auth::MailFrom
Hi Asif,
Can you test basic functionality. Like change the status with:
Status: resolved
at the top of your reply email. I'm just wondering if CommandByMail isn't
working or you are just having issues with the interaction with Custom Fields.
I just installed CommandByMail, but it was on
On Tue, Apr 16, 2013 at 4:01 PM, Miles Scruggs mi...@digitalphotobox.netwrote:
Hi Asif,
Can you test basic functionality. Like change the status with:
Status: resolved
at the top of your reply email. I'm just wondering if CommandByMail isn't
working or you are just having issues with
I installed RT-Extension-CommandByMail-0.10 on my RT 3.8.2 and setup the
config like below.
Set( @Plugins, qw( RT::Authen::ExternalAuth RT::Extension::CommandByMail )
);
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
Setup a custom field TAG of type 'Enter one value' for the help
On 13/03/04 6:23 AM, Kevin Falcone wrote:
On Sun, Mar 03, 2013 at 08:35:48AM -1000, Camron W. Fox wrote:
After migrating from RT3.6.6 to RT4.0.10, the
RT::Extension::CommandByMail plugin now fails. It installed with no
errors and we made sure the MailPlugins were set:
@MailPlugins =
On Sun, Mar 03, 2013 at 08:35:48AM -1000, Camron W. Fox wrote:
After migrating from RT3.6.6 to RT4.0.10, the
RT::Extension::CommandByMail plugin now fails. It installed with no
errors and we made sure the MailPlugins were set:
@MailPlugins = qw(Auth::MailFrom Filter::TakeAction);
All,
After migrating from RT3.6.6 to RT4.0.10, the
RT::Extension::CommandByMail plugin now fails. It installed with no
errors and we made sure the MailPlugins were set:
@MailPlugins = qw(Auth::MailFrom Filter::TakeAction);
Has anyone seen this before?
Best Regards,
Camron
--
Hi All,
We have RT 4.0.7 installed on a freeBSD system with postgres 9.0.10
In /var/log/messages we get these errors when the command by mail is called :
Feb 14 11:00:50 RT: Use of uninitialized value $1 in concatenation (.) or
string at
On Thu, Feb 14, 2013 at 11:12:15AM -, Nikolas Chrysandreas wrote:
In /var/log/messages we get these errors when the command by mail is called :
Feb 14 11:00:50 RT: Use of uninitialized value $1 in concatenation (.) or
string at
Hi Kevin,
Thanks for the reply.
These are all warnings not errors.
Are you seeing them manifest as errors somewhere?
No, we haven't had any real issues but we have another instance of RT on an
ubuntu server and we don't see the same warnings.
I was wondering if there is something we could do
On Thu, Feb 14, 2013 at 04:09:02PM -, Nikolas Chrysandreas wrote:
These are all warnings not errors.
Are you seeing them manifest as errors somewhere?
No, we haven't had any real issues but we have another instance of RT on an
ubuntu server and we don't see the same warnings.
I was
Hi,
I've pushed a few updates recently into repository and as part of that
fixed a few annoying warnings. Would you mind testing code from
repository?
On Thu, Feb 14, 2013 at 9:07 PM, Kevin Falcone
falc...@bestpractical.com wrote:
On Thu, Feb 14, 2013 at 04:09:02PM -, Nikolas Chrysandreas
Is it possible to use commandbymail to change a 'checkbox' for select multiple
values in a list? I can't figure out the syntax.
Thanks,
William
We're hiring! http://bestpractical.com/jobs
@lists.bestpractical.com
Subject: Re: [rt-users] CommandByMail rt 4.0.7
On 11/01/2012 09:47 AM, Edsall, William (WJ) wrote:
Does CommandByMail work in rt 4.0.7? I’ve installed it, added the
following two lines to my RT_Siteconfig
Set( @Plugins, qw(RT::Authen::ExternalAuth RT::Extension::CommandByMail
Does CommandByMail work in rt 4.0.7? I've installed it, added the following two
lines to my RT_Siteconfig
Set( @Plugins, qw(RT::Authen::ExternalAuth RT::Extension::CommandByMail
RT::Interface::Email::Filter::TakeAction) );
Set($CommandByMailStripOut, 1);
Yet when I try commands by mail (Like
On 11/01/2012 09:47 AM, Edsall, William (WJ) wrote:
Does CommandByMail work in rt 4.0.7? I’ve installed it, added the
following two lines to my RT_Siteconfig
Set( @Plugins, qw(RT::Authen::ExternalAuth RT::Extension::CommandByMail
RT::Interface::Email::Filter::TakeAction) );
You didn't
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 had another thought on Custom FIelds that are defined as Upload If
I sent in an email and used the CommandByMail command for a CF (CF{name of
CF}: value) would I be able to put an attachment as that value and have CBM
put that value in the CF?
Just a thought.
Kenn
LBNL
On Mon, Aug 15, 2011 at 9:33 PM, Kenneth Crocker kfcroc...@lbl.gov wrote:
To list,
I had another thought on Custom FIelds that are defined as Upload If
I sent in an email and used the CommandByMail command for a CF (CF{name of
CF}: value) would I be able to put an attachment as that
Hi,
we are using the current version 0.03 of
http://search.cpan.org/~ruz/RT-Extension-SLA/
in a productive environment - works great - very
good work.
Also, we are using RT-Extension-CommandByMail to
set e.g. the SLA by email (AddCF.{SLA}:Task-low),
but this does not work.
The logfile tells me
Hi,
Also, we are using RT-Extension-CommandByMail to
set e.g. the SLA by email (AddCF.{SLA}:Task-low),
but this does not work.
Try to use TransactionBatch stage for the SLA scrip that sets default value.
no, this does not work either.
regards
Danny
On Mon, May 30, 2011 at 9:33 PM, Daniel Schwager
daniel.schwa...@dtnet.de wrote:
Hi,
Also, we are using RT-Extension-CommandByMail to
set e.g. the SLA by email (AddCF.{SLA}:Task-low),
but this does not work.
Try to use TransactionBatch stage for the SLA scrip that sets default value.
Is it possible that you have several custom fields named SLA? Check database.
SELECT * FROM `CustomFields` WHERE `Name` LIKE 'SLA' LIMIT 0 , 30
-- 1 record found
No, only one SLA CF-field.
Danny
Hello list!
Is there a possibility to activate (or deactivate) the CommandByMail
extension only for certain queues ?
Thanks for your help
Horst
___
Le contenu de ce courriel est uniquement réservé à la personne ou
l'organisme à qui
On Fri, Jan 21, 2011 at 03:46:34PM +0100, Horst Kriegers wrote:
Is there a possibility to activate (or deactivate) the CommandByMail
extension only for
certain queues ?
It can be restricted to a group, but not specifically to a queue.
-kevin
pgphveSDTJyFW.pgp
Description: PGP
, 2010 6:49 PM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] CommandByMail Custom Fields not updated
Hi Kevin,
These are the logs I'm getting. It includes an example where I used a different
syntax and it displays the errors (And I also get an email back with the
problem
On Thu, Nov 18, 2010 at 12:42:43AM -0800, Osnat Shapira wrote:
Hi,
I'm using the CommandByMail extension.
My Content looks as follows:
Priority: 1
CustomField.{Number-Test}: 1
Comment Test
The Priority is updated (and any other non-custom field I'm adding).
The CustomField is not
-users@lists.bestpractical.com
Subject: Re: [rt-users] CommandByMail Custom Fields not updated
On Thu, Nov 18, 2010 at 12:42:43AM -0800, Osnat Shapira wrote:
Hi,
I'm using the CommandByMail extension.
My Content looks as follows:
Priority: 1
CustomField.{Number-Test}: 1
Comment Test
Right now, I've got CommandByMail setup and functioning with my RT. The
only issue I have, is that if I send a command like status: resolved, it
sends the requesting user a copy of that email AND the email saying Your
ticket is closed (the second email being expected, of course).
If there any
On Wed, Sep 22, 2010 at 01:50:38PM -0700, Jon Davis wrote:
Right now, I've got CommandByMail setup and functioning with my RT. The
only issue I have, is
that if I send a command like status: resolved, it sends the requesting
user a copy of that
email AND the email saying Your
On Thu, Jul 22, 2010 at 11:50:31PM -0400, anthony acquanita wrote:
So I never enter this while loop. If I run a script outside of RT it works
How do you know it is the same current user?
Compare $queue-CurrentUser-UserObj-Id to be sure
Generally this fails when a user doesn't have SeeQueue
So i've done some debug in TakeAction.pm and it seems that
custom_fields is empty because I never see the ACTIONCF2 log
any leads at to debugging $queue-TicketCustomFields; ?
# Canonicalize custom fields
my $custom_fields = $queue-TicketCustomFields;
$RT::Logger-info( ACTIONCF1-
On Wed, Apr 21, 2010 at 01:39:04PM -0700, Kenneth Crocker wrote:
1) Email from any RT User creates a ticket in a queue, EVEN when the right
CreateTicket has
NOT been applied to that User/group/role/Sys group for that Queue. It
still gets in and
becomes a ticket. I checked the
On 04/22/2010 09:53 AM, Kevin Falcone wrote:
On Wed, Apr 21, 2010 at 01:39:04PM -0700, Kenneth Crocker wrote:
1) Email from any RT User creates a ticket in a queue, EVEN when the right
CreateTicket has
NOT been applied to that User/group/role/Sys group for that Queue. It still
Sorry,
This ^%$%Gemail doesn't do a reply like I'm used to. I wanted to include
the list.
Kenn
On Thu, Apr 22, 2010 at 9:00 AM, Kenneth Crocker kfcroc...@lbl.gov wrote:
Jeff, Kevin,
I agree that something is configured wrong. The plugins look like this:
Set(@MailPlugins,
To List Kevin Jeff,
Whomever created RightsMatrix, I owe them a beer. Actually a pitcher.
I SSOOO embarrassed by this mistake. However, confession is good for
the soul.
I've been on 3.6.4 so for so long, I completely forgot that 3.8.7 allows the
granting of SuperUser at the group
To list,
We're discovering that even though we have set rights in a Queue for
CreateTicket for only 1 person, it seems like anyone can create a ticket
when we have CommandByMail turned on. I have checked the global rights and
the queue rights and I had someone without that right create a ticket.
Sorry, this was to go to the list as well,
Ruslan,
Maybe you can help me here. I have been testing 3.87 with great success and
am ready to install into production. Then someone noticed a problem I had
not tested for (shame on me). It seems that when we turn on CommandByMail,
two things happen
To list,
I have added a couple new values for the Status field via the
RT_SiteConfig.pm file. However, when I try to update a ticket with one of
those new values, the update is rejected.
Question: How can I update CommandByMail to allow those new Status values?
Thanks.
Kenn
LBNL
Discover
It seems like the requestor receives mail sent to rt-comment. Or is
this a option I can disable?
On Tue, Mar 23, 2010 at 7:06 PM, Kenneth Marshall k...@rice.edu wrote:
The comment address is the mail to RT that is only sent to
admins and adminccs and not requestors or ccs. The default
is
This does not happen out of the box. Comments only go to
AdminCc's and not the Requestor. This sounds like a local
modification, either to make requestors AdminCc's or to
send comments to requestors. Check your Scrips.
Cheers,
Ken
On Mon, Mar 29, 2010 at 02:30:45PM +0100, polloxx wrote:
It
Bad, bad, bad, bad idea. Did I mention that this is a bad
idea? :) Seriously, the CommandByMail gives a lot of access
to the internals of your RT system. It can totally subvert
your workflow. Imagine a generic E-mail that can close or
delete any ticket in the system. What are you trying to
The comment address is the mail to RT that is only sent to
admins and adminccs and not requestors or ccs. The default
is usually rt-comment. I hope that helps.
Ken
On Mon, Mar 22, 2010 at 05:47:37PM +0100, polloxx wrote:
Can you be more specific?
I also posted my question on the cpanforum but
What about using the comment address and not the E-mail
address. It should also be possible to make a patch to
strip them out, maybe to a separate attachment to help
debug problems.
Ken
On Sun, Mar 21, 2010 at 01:39:53PM +0100, polloxx wrote:
Dear list,
Is there a way to hide CommandByMail
Can you be more specific?
I also posted my question on the cpanforum but that seems death.
P.
On Mon, Mar 22, 2010 at 2:04 PM, Kenneth Marshall k...@rice.edu wrote:
What about using the comment address and not the E-mail
address. It should also be possible to make a patch to
strip them out,
Dear list,
Is there a way to hide CommandByMail commands from the requestor?
When we 'resolve' a ticket via mail the requestor receives the mail.
Can we hide this?
Thx,
P.
___
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users
Community
When I try to install RT::Extension::CommandByMail on a Denian Lenny
running Postfix I get the following error:
cpan[2] install RT::Extension::CommandByMail
Running install for module 'RT::Extension::CommandByMail'
Running make for F/FA/FALCONE/RT-Extension-CommandByMail-0.07.tar.gz
Has already
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
On Wed, Feb 03, 2010 at 01:19:51AM +0100, Eesti Mate wrote:
Hello CommandByMail users,
how do you address the possibility that (in theory) everyone can change
the status of tickets by faking the email address of a
$CommandByMailGroup member? Does CommandByMail provide any kind of
Hello CommandByMail users,
how do you address the possibility that (in theory) everyone can change
the status of tickets by faking the email address of a
$CommandByMailGroup member? Does CommandByMail provide any kind of
authentication options? Is there a best practice to prevent this sort of
Now I can use spaces between custom field name.
I changed line 200 from
last if $line !~ /^(?:(\S+)\s*?:\s*?(.*)\s*?|)$/;
to:
last if $line !~ /^(?:(.+)\s*?:\s*?(.*)\s*?|)$/;
and there is no C before custom fields name ( at least in version 0.07 ) of
commandbymail.
Bye
2009/11/9 Sergio
On Tue, Nov 10, 2009 at 11:02:36AM -0200, Sergio Charpinel Jr. wrote:
Now I can use spaces between custom field name.
I changed line 200 from
last if $line !~ /^(?:(\S+)\s*?:\s*?(.*)\s*?|)$/;
to:
last if $line !~ /^(?:(.+)\s*?:\s*?(.*)\s*?|)$/;
and there is no C
Yes
This are my lines:
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
Set(@Plugins,(qw(RT::FM RT::Extension::MandatorySubject)));
Set(@Plugins,(qw(RT::FM RT::Extension::MandatoryRequestor)));
Set(@Plugins,(qw(RT::FM RTx::Calendar)));
Set(@Plugins,(qw(RT::FM
On Tue, Nov 10, 2009 at 16:43, Sergio Charpinel Jr.
sergiocharpi...@gmail.com wrote:
Yes
This are my lines:
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
Set(@Plugins,(qw(RT::FM RT::Extension::MandatorySubject)));
Set(@Plugins,(qw(RT::FM RT::Extension::MandatoryRequestor)));
Hi,
I have installed CommandByMail plugin, and added these lines do
RT_SiteConfig.pm:
Set(@MailPlugins, qw(Auth::MailFrom Filter::TakeAction));
Set(@Plugins,(qw(RT::FM RT::Extension::CommandByMail)));
But I getting this error:
[error]: Couldn't load RT::Interface::Email::Filter::TakeAction:
Seems like I cant use space in custom field name. And there is C before the
name.
Does anyone can use this plugin with space in custom fields?
Thanks
2009/11/9 Sergio Charpinel Jr. sergiocharpi...@gmail.com
Hi,
I have installed CommandByMail plugin, and added these lines do
Hello
I'd like to modify the colon that seperates the command from the value
(command:value) to somewhat less common (e.g. ]~] ).
Is this possible? And if so, where do I've to define the new seperator/string?
Kind regards
Eesti
--
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
On Wed, Aug 26, 2009 at 05:17:04PM +0200, Eesti Matee wrote:
I'd like to modify the colon that seperates the command from the value
(command:value) to somewhat less common (e.g. ]~] ).
Is this possible? And if so, where do I've to define the new seperator/string?
Look for pseudoheaders in the
I'd like to modify the colon that seperates the command from the value
(command:value) to somewhat less common (e.g. ]~] ).
Is this possible? And if so, where do I've to define the new
seperator/string?
Look for pseudoheaders in the code and you'll find the regular
expressions
On Wed, Aug 26, 2009 at 05:54:55PM +0200, Eesti Matee wrote:
I'd like to modify the colon that seperates the command from the
value
(command:value) to somewhat less common (e.g. ]~] ).
Is this possible? And if so, where do I've to define the new
seperator/string?
Look for
To all,
FIRST and FOREMOST!!! I am NOT a Unix guy. I know it runs on a server
and we have a Sparc server and our DataBase is Oracle 10g and we are on
RT 3.6.4.
However, I have NO IDEA how directories work when it comes to how an
install program looks for or defines where to go
Kenneth Crocker wrote:
To all,
FIRST and FOREMOST!!! I am NOT a Unix guy. I know it runs on a server
and we have a Sparc server and our DataBase is Oracle 10g and we are on
RT 3.6.4.
However, I have NO IDEA how directories work when it comes to how an
install program looks
Joop,
Thanks for your response. I'll look in my several directories and see
if there are redundant perl modules. Thanks.
Kenn
LBNL
On 3/12/2009 1:04 PM, Joop van de Wege wrote:
Kenneth Crocker wrote:
To all,
FIRST and FOREMOST!!! I am NOT a Unix guy. I know it runs on a
Kenneth Crocker wrote, On 3/12/09 3:37 PM:
To all,
FIRST and FOREMOST!!! I am NOT a Unix guy. I know it runs on a server
and we have a Sparc server and our DataBase is Oracle 10g and we are on
RT 3.6.4.
However, I have NO IDEA how directories work when it comes to how an
Hi all,
*Since the Queue contains mandatory fields, if these fields are not filled
(fill in the e-mail or rather empty), the ticket will not be created. Is
there a way to notify the person who sends the mail that his application has
not been created?*
Thank you,
Hi all
I have installed RT-Extension-CommandByMail-0.06 on my RT 3.8.1 and it works
for existing tickets but I want to set it up so that my staff (ticket
owners) are able to create tickets for requesters from mail. I have tried
sending a new mail from one of the owners with the following codes
I upgraded our RT from 3.6.6 to 3.8 and the CommandByMail extension has stop
working.
I found the updated version posted by Kevin Falcone at CPAN; 0.06. I
followed the instructions to get it setup with 3.8, but it is still not
working.
Any help is welcome.
Thanks,
_
| | __ _
Subject: [rt-users] CommandByMail not working in RT 3.8
I upgraded our RT from 3.6.6 to 3.8 and the CommandByMail extension has stop
working.
I found the updated version posted by Kevin Falcone at CPAN; 0.06. I
followed the instructions to get it setup with 3.8, but it is still not
working.
Any help
-2481 ext.212
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Leo Gorauskas
Sent: Wednesday, August 06, 2008 12:43 PM
To: rt-users@lists.bestpractical.com
Subject: [rt-users] CommandByMail not working in RT 3.8
I upgraded our RT from 3.6.6
We were having the same issue here, but it looks like I got it fixed...
Caveat: we're running v3.6.1.
I gave Everyone the following custom field rights:
AssignCustomFields
ModifyCustomField
SeeCustomField
With those rights set, unprivileged users' emails are setting the custom
fields
Looking at the perldoc, Parent or Child don't seem to be link options. Is there
fix for this or are they just not listed in the documentation?
Mathew
--
Keep up with me and what I'm up to: http://theillien.blogspot.com
___
:[EMAIL PROTECTED] On Behalf Of Mathew Snyder
Sent: lunes, 17 de septiembre de 2007 20:47
To: RT Users
Subject: [rt-users] CommandByMail links
Looking at the perldoc, Parent or Child don't seem to be link options. Is
there fix for this or are they just not listed in the documentation?
Mathew
--
Keep
Hi,
I am using version 3.4.2, and I have configured the CommandByMail extension.
We use a php form to generate an email to our system, which creates the
ticket. When I use the form, because I have superuser privileges, a new
ticket is created with the custom fields autopopulated. However, if
Hi,
I cant get the custom part of commandbymail to work
I try to update or create a ticket and change a CF called GAPPInform by
sending the command:
CustomField.{GAPPInform}: Whatever
But even I get no error message, I dont get the CF updated.
Any errors on the systax?
Thanks
Alvaro
1 - 100 of 114 matches
Mail list logo
