Re: gnus and RT ticket threads

Re: gnus and RT ticket threads

[Kai Großjohann]

Uri Guttman <uri@stemsystems.com> writes:

> rt (a request ticket tracker - http://www.bestpractical.com/rt/)
> supports tickets via email. it doesn't generate any references headers
> but it does generate in-reply-to headers

Gnus uses the In-Reply-To header by default if References is
missing.  So something else must be wrong...

kai
-- 
A large number of young women don't trust men with beards.  (BFBS Radio)

Re: gnus and RT ticket threads

[Uri Guttman]

>>>>> "KG" == Kai Großjohann <Kai.Grossjohann@CS.Uni-Dortmund.DE> writes:

  KG> Uri Guttman <uri@stemsystems.com> writes:
  >> rt (a request ticket tracker - http://www.bestpractical.com/rt/)
  >> supports tickets via email. it doesn't generate any references headers
  >> but it does generate in-reply-to headers

  KG> Gnus uses the In-Reply-To header by default if References is
  KG> missing.  So something else must be wrong...

i noticed that the initial rt ticket message has '[autoreply]' in the
subject but the followups don't but they have Re: in there. and i found this:

gnus-cite-reply-regexp's value is 
"^\\(Subject: Re\\|In-Reply-To\\|References\\):"

so it may be that the subject: Re is being found first and the subject
doesn't match due to the [autoreply]. so i could rearrange that so the
In-Reply-To comes first. sound like a plan?

thanx,

uri

-- 
Uri Guttman  ------  uri@stemsystems.com  -------- http://www.stemsystems.com
----- Stem and Perl Development, Systems Architecture, Design and Coding ----
Search or Offer Perl Jobs  ----------------------------  http://jobs.perl.org