Re: [rt-users] CommandByMail 2.1 and RT 4.4.0 - Permission denied.

2016-06-16 Thread Armin Liedtke
I don’t know how I missed it but a bug was already reported about this 6 weeks 
ago.  I looked at the list multiple times and somehow missed seeing the almost 
exact subject line that I used was already there.
https://rt.cpan.org/Public/Bug/Display.html?id=114132

Let us know if you find a fix. 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 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 to make changes 
including delete tickets.

Thanks for any help!
Che

On Wed, Jun 15, 2016 at 3:44 PM, Armin Liedtke 
<armha...@uw.edu<mailto:armha...@uw.edu>> wrote:
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 as if it was a 
regular ticket.

Now with 2.1 and 4.4.0. If you are in the group it will run the command 
correctly. However, if you are not in the group then you get a bounce message 
that says:

User [the email address] is not in the configured CommandByMailGroup

This happens every time and even if you send a normal email  or reply to a 
ticket.  My test messages didn’t have any of the “Commands”, there were just a 
general test.



Essential, during my test, EVERYONE would have to be in the group or no one 
could reply or send in a ticket.



Settings from RT_SiteConfig.pm

Set(@MailPlugins, qw(Auth::MailFrom Action::CommandByMail));

Set($CommandByMailGroup, 27713);

Set(@Plugins, qw(RT::Extension::CommandByMail 
RT::Extension::Assets::Import::CSV));



Does anyone have the new version working in the way I described it did in the 
past or is this some sort of bug?
Thanks

Armin


Armin Liedtke
Senior Computer Specialist
UW Bothell/Cascadia College Campus Library

-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016

-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016


Re: [rt-users] CommandByMail 2.1 and RT 4.4.0 - Permission denied.

2016-06-15 Thread Che Geiser
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 to make changes including delete tickets.

Thanks for any help!
Che

On Wed, Jun 15, 2016 at 3:44 PM, Armin Liedtke  wrote:

> 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 as if
> it was a regular ticket.
>
>
>
> Now with 2.1 and 4.4.0. If you are in the group it will run the command
> correctly. However, if you are not in the group then you get a bounce
> message that says:
>
> User [the email address] is not in the configured CommandByMailGroup
>
> This happens every time and even if you send a normal email  or reply to
> a ticket.  My test messages didn’t have any of the “Commands”, there were
> just a general test.
>
>
>
> Essential, during my test, EVERYONE would have to be in the group or no
> one could reply or send in a ticket.
>
>
>
> Settings from RT_SiteConfig.pm
>
> Set(@MailPlugins, qw(Auth::MailFrom Action::CommandByMail));
>
> Set($CommandByMailGroup, 27713);
>
> Set(@Plugins, qw(RT::Extension::CommandByMail
> RT::Extension::Assets::Import::CSV));
>
>
>
> Does anyone have the new version working in the way I described it did in
> the past or is this some sort of bug?
>
> Thanks
>
>
>
> Armin
>
>
>
>
>
> Armin Liedtke
>
> Senior Computer Specialist
>
> UW Bothell/Cascadia College Campus Library
>
> -
> RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
> * Los Angeles - September, 2016
>
>
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016


[rt-users] CommandByMail 2.1 and RT 4.4.0 - Permission denied.

2016-06-15 Thread Armin Liedtke
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 as if it was a 
regular ticket.

Now with 2.1 and 4.4.0. If you are in the group it will run the command 
correctly. However, if you are not in the group then you get a bounce message 
that says:

User [the email address] is not in the configured CommandByMailGroup

This happens every time and even if you send a normal email  or reply to a 
ticket.  My test messages didn't have any of the "Commands", there were just a 
general test.



Essential, during my test, EVERYONE would have to be in the group or no one 
could reply or send in a ticket.



Settings from RT_SiteConfig.pm

Set(@MailPlugins, qw(Auth::MailFrom Action::CommandByMail));

Set($CommandByMailGroup, 27713);

Set(@Plugins, qw(RT::Extension::CommandByMail 
RT::Extension::Assets::Import::CSV));



Does anyone have the new version working in the way I described it did in the 
past or is this some sort of bug?
Thanks

Armin


Armin Liedtke
Senior Computer Specialist
UW Bothell/Cascadia College Campus Library
-
RT 4.4 and RTIR Training Sessions https://bestpractical.com/training
* Los Angeles - September, 2016