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.
-- Mathieu Longtin 1-514-803-8977 On Tue, Oct 5, 2010 at 1:21 PM, Steve Anderson < steve.ander...@bipsolutions.com> wrote: > As with the thread mentioned by Konstantin, a lot of it will depend on how > you bring the email into RT. > > 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. > > > > Steve Anderson > > > > > From: testwreq wreq [mailto:testw...@gmail.com] > Sent: 05 October 2010 18:17 > To: Steve Anderson > Cc: rt-users@lists.bestpractical.com > Subject: Re: [rt-users] mandatory subject > > 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. > > > > On Tue, Oct 5, 2010 at 1:11 PM, Steve Anderson < > steve.ander...@bipsolutions.com> wrote: > Depends what you mean by mandatory. > > 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. > Something like a scrip with the on create condition, then something like > the following in the custom action cleanup. (not tested in any way) > > my $t_subject = $self->TicketObj->Subject; > if ($t_subject eq ''){ > $self->TicketObj->SetSubject('No subject given'); > } > > I'd probably set the stage to transactionbatch. > > > > 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. > > > > Steve Anderson. > > BiP Solutions Limited is a company registered in Scotland with Company > Number SC086146 and VAT number 383030966 and having its registered > office at Medius, 60 Pacific Quay, Glasgow, G51 1DZ. > > > **************************************************************************** > This e-mail (and any attachment) is intended only for the attention of > the addressee(s). Its unauthorised use, disclosure, storage or copying > is not permitted. If you are not the intended recipient, please destroy > all copies and inform the sender by return e-mail. > This e-mail (whether you are the sender or the recipient) may be > monitored, recorded and retained by BiP Solutions Ltd. > E-mail monitoring/ blocking software may be used, and e-mail content may > be read at any time.You have a responsibility to ensure laws are not > broken when composing or forwarding e-mails and their contents. > > **************************************************************************** > > ________________________________________ > This email has been scanned by Netintelligence > http://www.netintelligence.com/email > ________________________________________ > > BiP Solutions Limited is a company registered in Scotland with Company > Number SC086146 and VAT number 383030966 and having its registered > office at Medius, 60 Pacific Quay, Glasgow, G51 1DZ. > > > **************************************************************************** > This e-mail (and any attachment) is intended only for the attention of > the addressee(s). Its unauthorised use, disclosure, storage or copying > is not permitted. If you are not the intended recipient, please destroy > all copies and inform the sender by return e-mail. > This e-mail (whether you are the sender or the recipient) may be > monitored, recorded and retained by BiP Solutions Ltd. > E-mail monitoring/ blocking software may be used, and e-mail content may > be read at any time.You have a responsibility to ensure laws are not > broken when composing or forwarding e-mails and their contents. > > **************************************************************************** > > RT Training in Washington DC, USA on Oct 25 & 26 2010 > Last one this year -- Learn how to get the most out of RT! >
RT Training in Washington DC, USA on Oct 25 & 26 2010 Last one this year -- Learn how to get the most out of RT!