List:Eventum Development« Previous MessageNext Message »
From:Christopher McAvaney Date:May 22 2007 7:29am
Subject:auto created issue - email notification issues [possible duplicate
- apologies]
View as plain text  
G'day,

We have Eventum v2.0.1 installed and have noticed one difference to v1.7.x.

When an issue is created from an email, Eventum now tries to email the
original recipient of the issue, which is the system itself and is
subsequently "rejected" (aka blocked).  This happens with every issue
now created.

The end result is issues with a note that has (at the top of the note):
---
WARNING: This message was blocked because the sender was not allowed to
send emails to the associated issue. Only staff members listed in the
assignment or authorized replier fields can send emails.
----------------------------------------------------------------------

Dear rsd-it-support@...
---

The only way I have found to fix this issue is to change the PHP code of
include/class.support.php so that it doesn't specify any recipient to
the Notification::notifyAutoCreatedIssue() call.

Has anybody else hit this issue?
Is it a configuration issue at our end?


Looking at the auto created template:
templates/notifications/new_auto_created_issue.tpl.text

The implied logic within that file is a bit strange to me too.
...
{if $is_message_sender}
{t escape=no}We received a message from you and for your convenience, we
created an issue that will be used by our staff to handle your message
.{/t}
{else}
{t escape=no}We recieved a message from {$sender_name} and created an
issue from it. Since you were a recipient of the original message, we are
  sending you the issue details.{/t}
{/if}
...

Why would an email need to be sent to the "recipient of the original
message"?
Is there some work flow issue that we have overlooked?

Thanks heaps to anybody that can shed some light on the issue.

Christopher

Thread
auto created issue - email notification issues [possible duplicate- apologies]Christopher McAvaney22 May