<div><br>Changes to Email.pm worked when a ticket is created by sending email to RT . Has anyone attempted to implement writing a scrip? </div>
<div> </div>
<div>I could not get <em>RT-Extension-MandatorySubject</em> plugin to work for opening tickets via the web interface. I am hoping writing scrip may work for both the cases.</div>
<div> </div>
<div>-vm<br></div>
<div class="gmail_quote">On Tue, Oct 5, 2010 at 3:30 PM, testwreq wreq <span dir="ltr"><<a href="mailto:testwreq@gmail.com">testwreq@gmail.com</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>YOU ALL ARE THE BEST!!!</div>
<div> </div>
<div>I have RT 3.8.4; But hacking as suggested by Steve worked. I will be trying replacing the changes to local/lib/RT/Interface/Email.pm </div>
<div> </div>
<div>Thanks a million,</div>
<div>vm<br></div>
<div>
<div></div>
<div class="h5">
<div class="gmail_quote">On Tue, Oct 5, 2010 at 2:57 PM, Mathieu Longtin <span dir="ltr"><<a href="mailto:mathieu@closetwork.org" target="_blank">mathieu@closetwork.org</a>></span> wrote:<br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Or saving the changed file in local/lib/RT/Interface/Email.pm instead. That way you don't lose the changes at the next upgrade.<br>
<br>--<br>Mathieu Longtin<br>1-514-803-8977<br><br><br>
<div class="gmail_quote">
<div>
<div></div>
<div>On Tue, Oct 5, 2010 at 1:21 PM, Steve Anderson <span dir="ltr"><<a href="mailto:steve.anderson@bipsolutions.com" target="_blank">steve.anderson@bipsolutions.com</a>></span> wrote:<br></div></div>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">
<div>
<div></div>
<div>As with the thread mentioned by Konstantin, a lot of it will depend on how you bring the email into RT.<br><br>If I were doing it, with the way I have RT set up, I'd just adjust the Exim filter I'm using to check for a blank subject, and send a bounce email on that. But I'm doing a bundle of filtering already. If you're just using a mail alias with sendmail, that's going to need more work. The thread mentioned does suggest an edit to the lib/RT/Interface/Email.pm::Gateway, to check for a subject, before it's accepted.<br>
<br><br><br>Steve Anderson<br><br><br><br><br>From: testwreq wreq [mailto:<a href="mailto:testwreq@gmail.com" target="_blank">testwreq@gmail.com</a>]<br>Sent: 05 October 2010 18:17<br>To: Steve Anderson<br>Cc: <a href="mailto:rt-users@lists.bestpractical.com" target="_blank">rt-users@lists.bestpractical.com</a><br>
Subject: Re: [rt-users] mandatory subject<br>
<div>
<div></div>
<div><br>I meant don't create a ticket, if there's no subject. I'd like bounce the request back to sender asking to create it again with some subject.<br><br><br><br>On Tue, Oct 5, 2010 at 1:11 PM, Steve Anderson <<a href="mailto:steve.anderson@bipsolutions.com" target="_blank">steve.anderson@bipsolutions.com</a>> wrote:<br>
Depends what you mean by mandatory.<br><br>If you mean a default, if the inbound email doesn't have a subject, should be possible to have a create scrip that sets the ticket's title, if it doesn't have one.<br>
Something like a scrip with the on create condition, then something like the following in the custom action cleanup. (not tested in any way)<br><br>my $t_subject = $self->TicketObj->Subject;<br>if ($t_subject eq ''){<br>
$self->TicketObj->SetSubject('No subject given');<br>}<br><br> I'd probably set the stage to transactionbatch.<br><br><br><br>If you mean don't create a ticket, if there's no subject, I'd suggest doing that with however you're getting the email into RT first. As long as you're running it through procmail, or an exim filter, or something like that. Otherwise, you'd need a scrip to send an email, and to close the ticket. Better not to create it in the first place.<br>
<br><br><br>Steve Anderson.<br><br>BiP Solutions Limited is a company registered in Scotland with Company<br>Number SC086146 and VAT number 383030966 and having its registered<br>office at Medius, 60 Pacific Quay, Glasgow, G51 1DZ.<br>
<br>****************************************************************************<br>This e-mail (and any attachment) is intended only for the attention of<br>the addressee(s). Its unauthorised use, disclosure, storage or copying<br>
is not permitted. If you are not the intended recipient, please destroy<br>all copies and inform the sender by return e-mail.<br>This e-mail (whether you are the sender or the recipient) may be<br>monitored, recorded and retained by BiP Solutions Ltd.<br>
E-mail monitoring/ blocking software may be used, and e-mail content may<br>be read at any time.You have a responsibility to ensure laws are not<br>broken when composing or forwarding e-mails and their contents.<br>****************************************************************************<br>
<br></div></div>________________________________________<br>This email has been scanned by Netintelligence<br><a href="http://www.netintelligence.com/email" target="_blank">http://www.netintelligence.com/email</a><br>________________________________________<br>
<div><br>BiP Solutions Limited is a company registered in Scotland with Company<br>Number SC086146 and VAT number 383030966 and having its registered<br>office at Medius, 60 Pacific Quay, Glasgow, G51 1DZ.<br><br>****************************************************************************<br>
This e-mail (and any attachment) is intended only for the attention of<br>the addressee(s). Its unauthorised use, disclosure, storage or copying<br>is not permitted. If you are not the intended recipient, please destroy<br>
all copies and inform the sender by return e-mail.<br>This e-mail (whether you are the sender or the recipient) may be<br>monitored, recorded and retained by BiP Solutions Ltd.<br>E-mail monitoring/ blocking software may be used, and e-mail content may<br>
be read at any time.You have a responsibility to ensure laws are not<br>broken when composing or forwarding e-mails and their contents.<br>****************************************************************************<br><br>
</div></div></div>
<div>
<div></div>
<div>RT Training in Washington DC, USA on Oct 25 & 26 2010<br>Last one this year -- Learn how to get the most out of RT!<br></div></div></blockquote></div><br><br><br>RT Training in Washington DC, USA on Oct 25 & 26 2010<br>
Last one this year -- Learn how to get the most out of RT!<br></blockquote></div><br></div></div></blockquote></div><br>