BCC access function

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
11 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

BCC access function

Leonardo Rodrigues Magalhães

    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 ....

--


        Atenciosamente / Sincerily,
        Leonardo Rodrigues
        Solutti Tecnologia
        http://www.solutti.com.br

        Minha armadilha de SPAM, NÃO mandem email
        [hidden email]
        My SPAMTRAP, do not email it





Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Ralf Hildebrandt
* Leonardo Rodrigues Magalhães <[hidden email]>:
>
>    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 ....

Which function is that?

--
Ralf Hildebrandt ([hidden email])          [hidden email]
Postfix - Einrichtung, Betrieb und Wartung       Tel. +49 (0)30-450 570-155
http://www.arschkrebs.de
Lesbian Nazi Hookers Abducted by UFOs and Forced Into Weight Loss
Programs - -all next week on Town Talk.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Leonardo Rodrigues Magalhães


Ralf Hildebrandt escreveu:

> * Leonardo Rodrigues Magalhães <[hidden email]>:
>  
>>    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 ....
>>    
>
> Which function is that?
>  

    sorry for not being clear ..... i would like to backport the BCC
access action to postfix 2.4:

       *BCC* /user@domain/
              Send one copy  of  the  message  to  the  specified
              recipient.

              If  multiple  BCC  actions are specified within the
              same SMTP MAIL transaction, only  the  last  action
              will be used.

              This  feature  is  not  part  of the stable Postfix
              release.



--


        Atenciosamente / Sincerily,
        Leonardo Rodrigues
        Solutti Tecnologia
        http://www.solutti.com.br

        Minha armadilha de SPAM, NÃO mandem email
        [hidden email]
        My SPAMTRAP, do not email it




Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Noel Jones-2
In reply to this post by Leonardo Rodrigues Magalhães
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.

You could pull out the code for the feature and maintain your
own local patch for 2.4, but you're on your own for that.  I
don't think it's too big, but I haven't looked...

--
Noel Jones

Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Victor Duchovni
In reply to this post by Leonardo Rodrigues Magalhães
On Mon, May 12, 2008 at 04:07:11PM -0300, Leonardo Rodrigues Magalh??es wrote:

>
>
> Ralf Hildebrandt escreveu:
> >* Leonardo Rodrigues Magalh??es <[hidden email]>:
> >  
> >>   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 ....
> >>    
> >
> >Which function is that?
> >  
>
>    sorry for not being clear ..... i would like to backport the BCC
> access action to postfix 2.4:
>
>       *BCC* /user@domain/
>              Send one copy  of  the  message  to  the  specified
>              recipient.
>
>              If  multiple  BCC  actions are specified within the
>              same SMTP MAIL transaction, only  the  last  action
>              will be used.
>
>              This  feature  is  not  part  of the stable Postfix
>              release.

It is not even in 2.5, just 2.6 snapshots. This is extremely unlikely
to be backported. The stable releases are *stable*.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Victor Duchovni
In reply to this post by Noel Jones-2
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.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Jason Pruim

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.

Just a thought.

--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424-9337
www.raoset.com
[hidden email]



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Victor Duchovni
On Mon, May 12, 2008 at 03:29:34PM -0400, Jason Pruim wrote:

> >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?
>

Of course, but this is still at most one BCC action per message. The
number of recipients this expands to is not the issue. If multiple
access(5) lookups generate different BCC actions, only the last one
takes effect.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

mouss-2
In reply to this post by Jason Pruim
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?
>

yes.
> 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 [hidden email]
- if sender is [hidden email], bcc [hidden email]
and hope to bcc both [hidden email] and [hidden email] when both the
client and sender conditions hold, but only bcc [hidden email] if
client condition holds but not sender, ... etc.


Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Jason Pruim
In reply to this post by Victor Duchovni

On May 12, 2008, at 3:37 PM, Victor Duchovni wrote:

> On Mon, May 12, 2008 at 03:29:34PM -0400, Jason Pruim wrote:
>
>>> 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?
>>
>
> Of course, but this is still at most one BCC action per message. The
> number of recipients this expands to is not the issue. If multiple
> access(5) lookups generate different BCC actions, only the last one
> takes effect.

Okay, I misunderstood what the issue was... Is it that if I BCC  
someone a copy of the message, AND the server BCC's the message to  
someone which ever gets run last is the one that gets it?


--

Jason Pruim
Raoset Inc.
Technology Manager
MQC Specialist
3251 132nd ave
Holland, MI, 49424-9337
www.raoset.com
[hidden email]



Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: BCC access function

Victor Duchovni
On Mon, May 12, 2008 at 03:41:03PM -0400, Jason Pruim wrote:

> >If multiple
> >access(5) lookups generate different BCC actions, only the last one
> >takes effect.
>
> Okay, I misunderstood what the issue was... Is it that if I BCC  
> someone a copy of the message, AND the server BCC's the message to  
> someone which ever gets run last is the one that gets it?

Last try:

    If multiple access(5) lookups generate different BCC actions, only the
    last one takes effect.

please don't re-interpret this to mean something else.

--
        Viktor.

Disclaimer: off-list followups get on-list replies or get ignored.
Please do not ignore the "Reply-To" header.

To unsubscribe from the postfix-users list, visit
http://www.postfix.org/lists.html or click the link below:
<mailto:[hidden email]?body=unsubscribe%20postfix-users>

If my response solves your problem, the best way to thank me is to not
send an "it worked, thanks" follow-up. If you must respond, please put
"It worked, thanks" in the "Subject" so I can delete these quickly.
Loading...