Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email email@example.com
From: mouss (moussnetoyen.net)
Date: Mon May 12 2008 - 14:39:20 CDT
Jason Pruim wrote:
> On May 12, 2008, at 3:25 PM, Victor Duchovni wrote:
>> On Mon, May 12, 2008 at 02:15:22PM -0500, Noel Jones wrote:
>>> Leonardo Rodrigues Magalh?es wrote:
>>>> Hello Guys,
>>>> Would it be too difficult to backport the BCC access function to
>>>> postfix-2.4 ?? i'm really interested on that function, but because of
>>>> other things i still have to stick with postfix-2.4 now ....
>>> No, the BCC access maps feature is available in snapshots
>>> only. Since new features (except for emergencies) are not
>>> added to stable releases, it will never be added to 2.4 or
>>> 2.5, and probably won't be in postfix 2.6.
>> Not too sure about the "probably not in 2.6", the main limitation
>> is that there is only one BCC recipient slot, so if multiple access
>> lookups generate "BCC" actions, the last one wins. If the at most
>> one BCC interfac is not objectionable, the feature is otherwise fine.
> Would it be possible to set the BCC recipient to a alias that could be
> expanded into multiple addresses? Such as 1 for the company owner, 1
> for archives, 1 for the lawyers?
> That way you just maintain it from a separate file but have the
> function in 2.6 working.
The limitation is that you can't do something like:
- if client is foo.example.com, bcc fooexample.org
- if sender is barexample.com, bcc barexample.org
and hope to bcc both fooexample.org and barexample.org when both the
client and sender conditions hold, but only bcc fooexample.org if
client condition holds but not sender, ... etc.