All,
I have RT 4.0.5 set up to accept mail and not create new users. I am using
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 the
AutoRejectRequest Template globally, hoping that it would give my users a
more graceful error message.
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?
Anything I have found on this seems to be old, deprecated, or not using
ExternalAuth. Thanks!
April
I have RT 4.0.5 set up to accept mail and not create new users. I am using
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 the AutoRejectRequest
Template globally, hoping that it would give my users a more graceful error message.
These options were removed from the config in
e3d012c1165fbdf5954ecd760c25e8830e01d273
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.
-kevin
Kevin,
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
_NoAuthorizedUserFound.
AprilFrom: rt-users-bounces@lists.bestpractical.com
[mailto:rt-users-bounces@lists.bestpractical.com] On Behalf Of Kevin
Falcone
Sent: Monday, August 20, 2012 7:43 AM
To: rt-users@lists.bestpractical.com
Subject: Re: [rt-users] AutoRejectRequest Template not working?
I have RT 4.0.5 set up to accept mail and not create new users. I am
using
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
the AutoRejectRequest
Template globally, hoping that it would give my users a more graceful
error message.
These options were removed from the config in
e3d012c1165fbdf5954ecd760c25e8830e01d273
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.
-kevin