I have 2.0.11 up and running fine except for one last issue.
I have tried to set up a an autoresponder for the requestor when they open a ticket via email. The ticket is opened fine however no email is sent out. The following error is in the logs…
RT::Transaction=HASH(0x87c89d4): Prepared NotifyRequestor
RT::Action::Notify=HASH(0x886189c): No recipients found. Not sending.
RT::Transaction=HASH(0x87c89d4): Committed NotifyRequestor
When I view the ticket via WebRT I can see the ticket and the Requestor. I have tried opening the group permissions to see if this was it. Even with every group with everything on I get this message.
I do get an email when a ticket is updated …however the REquestors field in that is as follows…
Queue: Support
Owner: seth
Requestors: ARRAY(0x8e8100c)
Status: new
I have problems with generating copies of comments in several cases
(e.g. while adding an e-mail to Cc field while generating comment from
web interface). I guess the reason is in syslog:
########3
RT: DBD::Pg::st execute failed: ERROR: pg_atoi: zero-length string at
/usr/local/share/perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 410. (/opt/rt3/lib/RT.pm:235
RT: RT::Handle=HASH(0x92a21fc) couldn’t execute the query ‘SELECT *
FROM ScripConditions WHERE id = ?’ at /usr/local/share/perl/5.8.0/DBIx/SearchBuilder/Handle.pm line 417.
(/opt/rt3/lib/RT.pm:235)
I have problems with generating copies of comments in several cases
(e.g. while adding an e-mail to Cc field while generating comment from
web interface). I guess the reason is in syslog:
Well, it seems the problem with atoi was in DBIx:Searchbuilder - upgrade to 0.88
did help.
Now RT does send e-mail according to scripactions (e.g. after generating
comment, if there is scrip for a queue to notify adminCC’s), but it
still doesn’t send notifications, when I just add an e-mail to Cc field
in comment generation screen. I suppose it has something to do with
configuration. Am I right? Do I have to define a scripaction to send
such a single notification?
I receive an error message similar to this, trying to use rt-crontool to send timed notifications of unresolved tickets. I also receive this message when attempting to make an “OnCreate, Notify Owner” scrip, though the error is slightly different in each case. What am I doing wrong?
The command & template for the crontool job follows: