On Thu, Jan 20, 2011 at 04:48:15PM -0800, Alberto Vazquez wrote:
>    This worked, but I had to check the "Allow access to RT" option, otherwise 
> it would not work.

Yes, otherwise you would disable the user, but they cannot log in without a 
password.

-kevin

>    On Thu, Jan 20, 2011 at 9:00 AM, Kevin Falcone 
> <[1][email protected]> wrote:
> 
>      On Thu, Jan 20, 2011 at 08:49:50AM -0800, Alberto Vazquez wrote:
>      > Thank you Sir, I will give it a try. I was under the impression that 
> this is for users
>      with
>      > the need to access RT, since this external just needs to be able to 
> send an email to RT
>      and
>      > get a ticket create.
> 
>      Anyone who sends mail to RT gets a user account. If you're limiting
>      ticket creation to existing accounts, you will need to create a user
>      that doesn't have a password and isn't allowed to be granted rights
>      but does have an email address.
>      -kevin
>      > I will give a shot and see if it does the trick. I will let you know 
> how it tuns out.
>      > Alberto
>      >
>      > On Wed, Jan 19, 2011 at 3:44 PM, Kevin Falcone 
> <[1][2][email protected]> wrote:
>      >
>      > On Wed, Jan 19, 2011 at 03:05:22PM -0800, Alberto Vazquez wrote:
>      > > Guys,
>      > > I am new to RT and a novice on MySQL. Currently, we do not allow 
> auto create for
>      external
>      > > senders to any of our Q's, but one of our departments want to use RT 
> to start receiving
>      > emails
>      > > (tickets) from an external source.
>      > > My questions is, if I create this external entity in the RT 
> database, would RT accept
>      > that,
>      > > and if so, how in the heck do I create that entry in MySQL, with the 
> right permissions?
>      >
>      > You should be able to do this from Configuration -> Users -> Create
>      > -kevin
> 
>    --
>    Alberto Vazquez-Dzul
>    Email: [3][email protected]
>    Mobile: (805) 444-0835
>    GVoice: (805) 768-4798
> 
> References
> 
>    Visible links
>    1. mailto:[email protected]
>    2. mailto:[email protected]
>    3. mailto:[email protected]

Attachment: pgpAM0GkId5Aj.pgp
Description: PGP signature

Reply via email to