On 7 Oct 2006, at 10:37, Andreas Metzler wrote:
Quote http://www.postfix.org/SMTPD_POLICY_README.html#protocol | The "instance" attribute value can be used to correlate different | requests regarding the same message delivery. and an example value is "instance=123.456.7".
I read that, insufficient description.
I have not really wrangled with the source code, but this looks like instance identifies a command in a smtp session. This woud make it useful for a single purpose: Identifying a duplicate request, i.e. if postgrey was invoked for exactly the same triplett on exactly the same smtp session twice, due to some special configuration. Exim caches these lookups, therfore it should be a noop and instance=$pid.$tod_epoch.$sender_host_port
I didn't read postfix code, I just read what postgrey did with it. It was under my impression that 'instance' is used to identify the message uniquely to add the X-Greylist header later. If that's the case, with your expansion, X-Greylist would never be added.
I didn't read the full source code to validate my statement tough, is_new_instance usage looks unclear and suspicious to me. I'll wait to the developer's answer.
If instance needs to be a no-op, then you can go as far as instance=0 (why expanding at all?).
-- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
