Is it possible to share some of your Subject text (changing the names to protect the innocent Smile ) Do you use GTD context and so on. Thanks.
I added Project and Action fields to Outlook journal items to support GTD, and replaced the 'Entry type' field with Action. In addition, I added the following fields:
  • Sender -- the initiator, if any, of an action
    Recipient -- the target or object, if any, of an action
The GTD Addin uses the Action field to store context (@Agenda, @Waiting For, etc.) The way I'm using it in journal items, the meaning of 'context' refers more specifically to the generic type of action -- what you actually did, and doesn't connote location or access to people, facilities, and resources, as it does in tasks. E.g., 'telephone' in a journal item means a telephone call rather than access to a telephone, whereas 'anywhere' is meaningless. Thus, I use a subset of my 'context' terms in journal items, typically:.
  • email
    internet
    meeting
    note (in the sense of Outlook Notes)
    letter
    read
    telephone
I link journal entries to the relevant contacts so I can retrieve actions & events with respect to a particular contact using Outlook's activity facility.
Typical journal item subjects:
  • birthday gift
    shipped birthday gift
    responded to invite
    purchased train tickets to my brother's for Thanksgiving
    paid telephone 123 456 7890 check 1234 $12.34 14 Feb 2005
    paid cablemodem account 1234567 check 1235 $32.81 14 Feb 2005
    submitted service request re including project and action dropdown lists in Outlook journal items
    registered with David Allen GTD forum
    reset password at David Allen GTD forum
    regarding status [of the referenced project]
    regarding travel schedule [in connection with the referenced project]
    in response to my email [telephone call, etc.]
    left vmail regarding status
    updated contact info
Some of these items could also be ad hoc tasks.

Finally, I don't recommend Outlook's automated journaling capability. I tried it briefly and found it overly resource intensive -- too much cpu and disk usage.

Hope you find this useful.

Regards,
Michael