There is no optimal way to do this. One way would be to print (to pdf) the tickets and you have them.
The following is just an idea:
But what would be the goal? you'd still need to get (something) into an email and I can pretty much guarantee you're not going to get something immediately threadable and certainly not attachments.
TicketID 1 looks like this:
=====================================================================
TicketNumber: 2010080210123456
TicketID: 1
Created: 2010-08-02 08:00:00
Queue: Raw
State: new
Priority: 3 normal
Lock: unlock
---------------------------------------------------------------------
ArticleID: 1
To: Your OTRS System <otrs@localhost>
Subject: Welcome to OTRS!
Created: 2010-08-02 08:00:00
SenderType: customer
Body:
---------------------------------------------------------------------
Then you'll need to parse this into something that you'll want to use in email. You can use any command line command, with ARG[1] being the ticket id
maybe something like
This might (?) make a bunch of text files. Note that you could, in theory, pipe the thread(s) to a command that nicely formats your email or mail it or ...
Nothing here is tested. It may break things. It may not even work. Note that if you do export a LOT, you should make sure you don't run out of disk space.