Hello,
There is a setting in System Settings --> Organizations, Users, Licenses that needs to be enabled...
8.8 Automatic create contact person for unregistered emails
This should resolve the issue.
Sincerely,
Boris
I setup an InterAct rule that will create an issue when an email is sent to the create mailbox. It works fine for my email that is registered, but does not work for an email that is not registered. I get a failed email reply from Clarizen with the following message.
Original sender of message was not found
Thanks! Clarizen The Way to Work
What needs to be done, to allow any person to send an email and create an issue.
Also, I am populating the Open By with the EmailObject.From is there something needed if it is not a registered user?
Some kind of formula that would check if it is registered and use EmailObject.From and if not then use some default.
Please share what that formula would be.
Please sign in to leave a comment.
Hello,
There is a setting in System Settings --> Organizations, Users, Licenses that needs to be enabled...
8.8 Automatic create contact person for unregistered emails
This should resolve the issue.
Sincerely,
Boris
Thanks Boris, but it is already enabled and we get the error message still and a new contact is not created
Unfortunately the 'Issue' module is not considered an "Email-to-Case' mailbox. Please see the following screenshot for the interact disclaimer - http://screencast.com/t/KOADcsuQAF
Only Email to Case Mailboxes and their rules can be triggered by anyone, including unregistered users.
Hi everyone, I actually have the same question but for "Risks": I created an Interact Rule that generates a risk from an email but, when I try it, I get the same error message "Original Sender not found".
Now, I created another rule on the "Email to Case" which looks for a specific string in the Subject and then, based on what's found, will create a risk.
This rule works, but I can't use the variables. Is there no way at all to create a risk by using the risk mailbox for external users?
Was this resolved? We are experiencing it when trying to send an email to any work item.