It appears to me that, when the policy daemon is called during the
RCPT protocol state, the queue_id attribute is empty only for the
first recipient of a message with more than one recipient but has a
value for each recipient after the first. Is this is generally true
and can it be relied upon, as it seems it may be a fundamental
consequence of the Postfix architecture?
If the absence and presence of a value for the queue_id attribute can
be relied upon, would using something like
return "PREPEND $...-spf_header"
unless ($attr->{queue_id} ne '');
instead of
return "PREPEND $..._spf_header"
unless $cache->{added_spf_header}++;
and doing away with the cache be simpler and better?
Please pardon my poor Perl, I am not a native Perl speaker. :)
jam
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007
RCPT protocol state, the queue_id attribute is empty only for the
first recipient of a message with more than one recipient but has a
value for each recipient after the first. Is this is generally true
and can it be relied upon, as it seems it may be a fundamental
consequence of the Postfix architecture?
If the absence and presence of a value for the queue_id attribute can
be relied upon, would using something like
return "PREPEND $...-spf_header"
unless ($attr->{queue_id} ne '');
instead of
return "PREPEND $..._spf_header"
unless $cache->{added_spf_header}++;
and doing away with the cache be simpler and better?
Please pardon my poor Perl, I am not a native Perl speaker. :)
jam
-------
To unsubscribe, change your address, or temporarily deactivate your subscription,
please go to http://v2.listbox.com/member/?list_id=1007