Mike,
You're right that using the EXITCODE hack causes RT to fail to realize
that there has been a successful delivery and continue to search for
a place to deliver the message. This is the behavior I referred to
in my posting.
I think your problem may be with the implementation of my proposed
On 9/19/06, Isaac Vetter [EMAIL PROTECTED] wrote:
All,
Sorry for answering my own post. My problem was with the
$RTAddressRegexp value in RT_SiteConfig.pm.
As I understand it, this variable is used to avoid creating email loops
by not sending email to any addresses that match the regex stored
On 9/19/06, Isaac Vetter [EMAIL PROTECTED] wrote:
Ruslan Zakirov wrote:
'^systems|helpdesk|[EMAIL PROTECTED]'
This is also incorrect :) you need
'^(systems|helpdesk|webmaster)[EMAIL PROTECTED]'
No, actually parentheses are not necessary due, I think, to order of
precedence.
regexp
On Thu, 2006-09-14 at 16:59 -0400, Isaac Vetter wrote:
rt.log doesn't contain an error, even at [debug]. The default scrips are
in place. All four users are privileged, Global SuperUsers and AdminCC
Watchers on the queue.
I just had this happen to me on Friday, too. No error in any of my
Duncan McEwan wrote:
As to the original posters problem:
There are some users that RT won't send email to, upon 'Reply'ing to a
ticket, these users, both as Requestors and as AdminCC's, are not listed
in the This message will be sent to box.
On a clean install (rt3.4.5, perl5.8.8,
Kanwar Ranbir Sandhu wrote:
On Thu, 2006-09-14 at 16:59 -0400, Isaac Vetter wrote:
rt.log doesn't contain an error, even at [debug]. The default scrips are
in place. All four users are privileged, Global SuperUsers and AdminCC
Watchers on the queue.
I just had this happen to me on
