<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 08/13/2011 06:44 PM, Kyle Oetken wrote:
<blockquote
cite="mid:CAPv7g3cPsfizaB3ZkDffkETkrE1W6BRQh=ZA0LeBWAzF_yEObQ@mail.gmail.com"
type="cite">
<pre class="fragment"><font size="2"><span style="font-family: verdana,sans-serif;" class="keyword">In the example code this section assigns a unique ID to the milter instance:
def </span><span style="font-family: verdana,sans-serif;">__init__(self): </span><span style="font-family: verdana,sans-serif;" class="comment"># A new instance with each new connection.</span><span style="font-family: verdana,sans-serif;">
<a moz-do-not-send="true" href="http://self.id">self.id</a> = Milter.uniqueID() </span></font><span class="comment"><font size="2"><span style="font-family: verdana,sans-serif;"># Integer incremented with each call.</span>
</font></span></pre>
<span class="comment"><font size="2"><span style="font-family:
verdana,sans-serif;">In my testing it appears that the
Milter.uniqueID appears to assign an ID to each specific tcp
connection. As a result, if multiple messages are sent over
that tcp connection each message will have the same
uniqueID. Is there a good way to assign a unique ID to a
particular message within the tcp connection? </span></font></span><br>
</blockquote>
<font size="2">You could assign an id within envfrom also (or
instead). However, since the tcp connection is a single thread,
I would recommend simply incrementing a count in envfrom (no need
for locking as with uniqueID). You can concatenate the connection
id and message index to form an id unique for that milter run.
Note that uniqueID starts over each time you start milter, it is
not something you can use for Message-ID. You could count milter
startups in a file, and prepend that to connection id and mail
from count to form a unique id.</font><br>
</body>
</html>