Custom mail headers for TurboMail identification.

[amcgregor]

Currently the X-Mailer header is being set to the following:

X-Mailer: TurboMail TurboGears Extension v.X.Y.Z

As TurboMail is becoming independent of TurboGears, this needs to change.

X-Mailer: TurboMail <http://www.python-turbomail.org/>
X-TurboMail-Version: 3.0

Does that look fine? On the other hand, should we allow extensions to be represented in the headers? How should extensions represent their version, and what are appropriate names? X-TurboMail-Extension headers? E.g.

X-TurboMail-Manager: Demand <http://somesite/>
X-TurboMail-Manager-Version: 1.0
X-TurboMail-Provider: SMTP <http://somesite/>
X-TurboMail-Provider-Version: 1.0
X-TurboMail-Extension: SMIME <http://somesite/>
X-TurboMail-SMIME-Version: 1.0

Is it late or am I on crack? That's a lot of information to add to each message.

[amcgregor]

To help with examining logs and genrally tracing the path of a message through the system, I've added GUIDs to milestone:3.0 as of r39, which are represented like the following:

X-TurboMail-Message-GUID: b404fc2b-ae0d-43ab-ba28-1950a68f5a2f

[amcgregor]

GUIDs take a long time to generate, so are only being generated if mail.debug is True. Otherwise I'm using the random.uniform function. I'm not sure of the speed difference.

[amcgregor]

After further investigation it wasn't GUIDs that were taking the time, it was the digital signature of my test suite. Gah. GUIDs are back by default.