<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">Additional information won't hurt
anyway. The only regexp which is configured in RT_Siteconfig.pm is
<br>
<br>
Set($RTAddressRegexp , '^rt@domain.com$');<br>
<br>
What should be Regexp in order to detect the [XXXX] anywhere in
the Subject field<br>
<br>
<br>
<br>
<div class="moz-signature">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
---<br>
<a
href="http://cloudware.bg/?utm_source=email&utm_medium=signature&utm_content=link&utm_campaign=newwebsite"
style="font-family:Verdana; color:#00ACE5; font-size:12px;
text-decoration:none;">Find out about our new Cloud service -
Cloudware.bg</a><br>
<div style="font-family:Verdana; color:#A0A0A0;font-size:12px;">Access
anywhere. Manage it yourself. Pay as you go.</div>
<hr color="#103E81" noshade="noshade" size="1" width="400px"
align="left">
<div style="font-family:Verdana; color:#103E81; font-size:12px;">
<strong>Yavor Marinov</strong><br>
System Administrator<br>
<br>
Neterra Ltd.<br>
Telephone: +359 2 975 16 16<br>
Fax: +359 2 975 34 36<br>
Mobile: +359 888 610 048<br>
</div>
<a href="http://www.neterra.net" style="font-size:12px;
font-family:Verdana; color:#00ACE5; text-decoration:none;">www.neterra.net</a>
<br>
<br>
<br>
</div>
On 02/13/2014 05:13 PM, Kevin Falcone wrote:<br>
</div>
<blockquote cite="mid:20140213151308.GG6350@jibsheet.com"
type="cite">
<pre wrap="">On Thu, Feb 13, 2014 at 04:47:42PM +0200, Yavor Marinov wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> I've manage to solve this with [1]RT-Interface-Email-Filter-CheckMessageId extension.
</pre>
</blockquote>
<pre wrap="">
I'm glad that this fixed your issues, however for the archives, RT
works just fine and has for years with the subject tag (the [XXXXXX]
part) being anywhere in the subject.
Usually this points to a misconfiguration in RT's rtname, the regexp
that understands it or Queue level subject tags. But since you didn't
provide enough information about that, we can't even guess.
-kevin
</pre>
<blockquote type="cite">
<pre wrap=""> On 02/13/2014 12:29 PM, Yavor Marinov wrote:
Hello,
i have the following configs for getmail:
create a ticket to address [<a class="moz-txt-link-abbreviated" href="mailto:2]request@company.com">2]request@company.com</a>:
arguments = ("--url", [3]<a class="moz-txt-link-rfc2396E" href="https://localhost">"https://localhost"</a>, "--queue", "Internal-IT", "--action",
"correspond",)
comment to a ticket to address [<a class="moz-txt-link-abbreviated" href="mailto:4]request-comment@company.com">4]request-comment@company.com</a>:
arguments = ("--url", [5]<a class="moz-txt-link-rfc2396E" href="https://localhost">"https://localhost"</a>, "--queue", "Internal-IT", "--action",
"comment",)
everything works as it should be, but the following is annoying our colleagues, and I need
to fix it. So, if someone create a ticket via email, the ticket is getting into the queue
correctly and the members of the group (responsible for the queue) are getting mail from RT
with subject:
[XXXXXX] Subject of the email which is send to corresponding email.
Once anyone tried to reply via email (e.g. reply from their email client - subject changes
to Re: [XXXXX] ....) the reply isn't inserted in the correct ticket, but instead RT creates
a new ticket with subject "Re: [XXXXX]....."
If they reply and remove the "Re:" and leave subject as in RT the comment is properly added
to the ticket.
Summed up - getmail and rt-mailgate are working properly - the only problem is the subject,
and what should i modify in order RT to lookup into the Subject field even if "Re:" is
supplied.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
</blockquote>
</blockquote>
<br>
</body>
</html>