|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: Curtis (postfixuser
isparks.com)
Date: Fri Apr 16 2010 - 19:38:48 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>It's not documented, because there is no promise that it will work
>the same way in a future Postfix version.
>
>However, the names of the records give a hint.
>
>> Most particularly, I'm concerned about the following three fields:
>>
>> named_attribute: dsn_orig_rcpt=rfc822;email
example.com
>> original_recipient: email
example.com
>> recipient: email
example.com
>>
>> Would it be safe to say that all local recipients of the message will be
>> found in the "recipient:" field? (Repeated for each recipient?)
>
>That's how Postfix works at the moment, but there is no promise
>that it will always work that way.
A quick follow up on this. The field I was actually looking for turned out
to be "original_recipient:". Just in case anybody else goes through this,
let me document what I've learned about these three fields:
>> named_attribute: dsn_orig_rcpt=rfc822;email
example.com
Well, I'm not really sure where this value comes from, but it can not be
used as a reliable way to determine who the local recipient is. Sometimes
it contains a non-local list address.
>> original_recipient: email
example.com
This one appears to be the actual local recipient that was probably captured
during the smtp session.
>> recipient: email
example.com
This value is what appears to be what postfix translated the address to
after it accepted the message. For example, if you use virtual_alias_maps
to alias one address to another, then it will contain the target email
address.
Again, as Wietse would say, these values are not guaranteed to work this way
in future versions of Postfix. In fact, they may not even work this way in
the current version. I'm using version 2.5.6.
Thanks,
Curtis
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]