aprilr at yelp
Aug 20, 2012, 4:16 PM
Post #3 of 3
Re: AutoRejectRequest Template not working?
[In reply to]
Thanks for pointing me at the right files. I found the three places mail
is going out.
Sub createUser sends out two of the emails as the unless statements that
call mailError then don't seem to error out of the sub.
The third message is coming from further down in sub
From: rt-users-bounces [at] lists
[mailto:rt-users-bounces [at] lists] On Behalf Of Kevin
Sent: Monday, August 20, 2012 7:43 AM
To: rt-users [at] lists
Subject: Re: [rt-users] AutoRejectRequest Template not working?
On Fri, Aug 17, 2012 at 11:27:03AM -0700, April Rosenberg wrote:
> I have RT 4.0.5 set up to accept mail and not create new users. I am
> RT::Authen::ExternalAuth. I have a problem where some of my users are
not using their original
> email address to send emails to RT. When they send an email into an
RT monitored address they
> get three emails, *Could not load a valid user*, *User could not be
loaded*, and *User could
> not be created*. I have added
> Set($LookupSenderInExternalDatabase, 1);
> Set($SenderMustExistInExternalDatabase, 1);
> But I do not think those are relevant to ExternalAuth. I have added
> Template globally, hoping that it would give my users a more graceful
These options were removed from the config in
because there was never any code implemented in core to use them.
They've been deleted from the documentation since 3.8.9.
> Is there anyone to change the outgoing error messages so that a user
doesn*t get three, and
> that the, hopefully, one message they get has more info in it?
I'm not sure why they're getting three messages, I'd expect one.
Unfortunately, most of the error messages are handle in the library code
and are hard to change. You can look at lib/RT/Interface/Email.pm to get
an idea of what methods you'd need to overlay.