Template problem resolved but poses another question

To all,

I was really pulling my hair on this one. Thanks for your help, Roy, 

but once I got the code in, it still wasn’t working. After playing with
the &^%$ thing thru a thousand variations, I finally found out why the
template failed. It wasn’t the code. I had removed a blank line after
the initial Subject line and that’s what nixed the whole thing.Subject: Created Ticket: {$Ticket->Subject}

When I put the blank line back in, all the code worked.

Subject: Created Ticket: {$Ticket->Subject}

Now, did I miss some instruction somewhere? Where is this bit of
knowledge kept so that I could have found it? This really took up alot
of time and I can only assume that my beginner ignorance of some facet
of Perl of RT or something was the problem. Any comments???

Kenn
LBNL

It wasn’t the code. I had removed a blank line after the initial
Subject line and that’s what nixed the whole thing.

Subject: Created Ticket: {$Ticket->Subject}

When I put the blank line back in, all the code worked.

Subject: Created Ticket: {$Ticket->Subject}


I haven’t been following this thread in all that much detail, but this
strikes me as probably being just a question of the template needing to
result in a valid message. Both RFC822 and RFC2822 (the old and new
versions of the message format spec) specify that an empty line marks
the boundary between the headers and the body.

That said, those RFCs are not the most helpful place from the
perspective of an RT user like you. It would be better for the RT docs
to at least point to 2822, preferably to a brief summary of it with a
note that 2822 is the real authority and needs to be read for full
details. (I assume they don’t already have such a pointer, or you
would have found it yourself; I haven’t looked. This is an aspect of
RT I don’t really know - I just know message format quite well from an
email perspective.)

/~\ The ASCII der Mouse
\ / Ribbon Campaign
X Against HTML mouse@rodents.montreal.qc.ca
/ \ Email! 7D C8 61 52 5D E7 2D 39 4E F1 31 3E E8 B3 27 4B

der Mouse,

Well, that certainly explains it. Although I have read EVERY WORD in 

the RT Essential book, I had read quite a bit and don’t remember any
comment to that bit of technical detail and yes, that would have helped
a lot. Thanks again.

Kenn
LBNL

der Mouse wrote: