Hi,
On Mon, May 22, 2023 at 9:47 PM Viktor Dukhovni via Postfix-users <
postfix-users@postfix.org> wrote:
> On Mon, May 22, 2023 at 06:06:00PM -0400, Alex wrote:
>
> > Yes, I wasn't aware that's how it worked. I've now explicitly defined the
> > bcc-user to use the same transport, but the problem
On Mon, May 22, 2023 at 06:06:00PM -0400, Alex wrote:
> Yes, I wasn't aware that's how it worked. I've now explicitly defined the
> bcc-user to use the same transport, but the problem is that there is one
> bcc-user but multiple transports, each with their own policy.
This is where recipient_bcc_
Hi,
>
> The BCC recipient is processed in much the same way as any other message
> recipient. The only special handling that comes to mind is DSN, where
> this recipient is treated as if NOTIFY=NEVER were specified.
>
> > local_transport = error:5.1.1 Mailbox unavailable
> > default_transport = s
On Sun, May 21, 2023 at 02:05:31PM -0400, Alex via Postfix-users wrote:
> Can I follow up on this? I can't figure out why always_bcc mail is being
> sent through the default content filter while mail designated for my
> domain-specific transport is sent through another in my multi-instance
> postf
Hi,
Can I follow up on this? I can't figure out why always_bcc mail is being
sent through the default content filter while mail designated for my
domain-specific transport is sent through another in my multi-instance
postfix config. I'd like the always_bcc user mail to still benefit from
being fil
Viktor,
On Thu, May 18, 2023 at 7:16 PM Viktor Dukhovni via Postfix-users <
postfix-users@postfix.org> wrote:
> On Thu, May 18, 2023 at 09:20:38AM -0400, Alex via Postfix-users wrote:
>
> > Maybe my issue is that the always_bcc user is going through a transport
> at
> > all, and instead should ju
On Thu, May 18, 2023 at 09:20:38AM -0400, Alex via Postfix-users wrote:
> Maybe my issue is that the always_bcc user is going through a transport at
> all, and instead should just be delivered locally, or perhaps processed
> only by the local_transport? How can I do that?
>
> I recall many years
Hi,
Maybe my issue is that the always_bcc user is going through a transport at
all, and instead should just be delivered locally, or perhaps processed
only by the local_transport? How can I do that?
I recall many years ago doing that, before I set up multi-instance postfix.
Thanks,
Alex
On Thu,
On Thu, May 18, 2023 at 4:39 AM Matus UHLAR - fantomas via Postfix-users <
postfix-users@postfix.org> wrote:
> On 17.05.23 22:11, Alex via Postfix-users wrote:
> >I'm using postfix (postmulti) with amavisd and trying to have separate
> >content filters based on the domain so I can make decisions o
On 17.05.23 22:11, Alex via Postfix-users wrote:
I'm using postfix (postmulti) with amavisd and trying to have separate
content filters based on the domain so I can make decisions on the destiny
of the email from within amavisd. Currently all mail is processed by the
same amavisd policy_bank.
s
10 matches
Mail list logo
