Is your script using the "Autoreply to Requestors" action? If not then the the general "NotifyActor" configuration setting will take precedence and the Actor will be stripped from the mail. And with no recipients an email message is aborted.

Joby Walker
C&C SSG, University of Washington


David Langenberg wrote:
David Langenberg wrote:
Hi All,

Version: RT 3.6.1

I'm having an issue with autoreply.  Let's say I have a queue setup
called foo.  This queue has a submission address of [EMAIL PROTECTED]
 I also have queue foo setup to send an autoreply on create back to the
requester.  Everything works fine, mail to [EMAIL PROTECTED] causes
the tickets to be created and autoreplies to be sent, now the problem.
Foo used to be a mailing list with an additional top level alias on it.
 So we had [EMAIL PROTECTED] -> [EMAIL PROTECTED]  We're now going
to handle all requests to foo via rt, so I've setup [EMAIL PROTECTED]
as the only member of the list [EMAIL PROTECTED]  Now, if I send a
message to [EMAIL PROTECTED] or [EMAIL PROTECTED] RT creates a
ticket, correctly recognizes the address I used (this address doesn't
have an RT account associated with it) as the requester, but doesn't
send the autoreply.  The logs show the familiar message

Sorry -- forgot the rest of the log message:No recipients found. Not
sending.

Dave




------------------------------------------------------------------------

_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
_______________________________________________
http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users

Community help: http://wiki.bestpractical.com
Commercial support: [EMAIL PROTECTED]


Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com

Reply via email to