>> > receive_override_options = no_address_mappings
>> >
>> > and then permit mappings (which include always_bcc) to occur in the 2nd
>> > instance (for the mail that is returned by amavis), for example this
>> > might be in master.cf by:
>> >
>> > 127.0.0.1:10025 inet n - n -
Hi,
> > > > I thought I said transport...
> > >
> > > Postfix instance 1
> > >
> > > main.cf
> > > always_bcc = f...@example.com
> > >
> > > transport_maps
> > > f...@example.com -> Postfix instance 2
> > > all other mail -> content filter -> Postfix instance 2
> > >
> > > Perhaps a
On Wed, Apr 21, 2021 at 04:19:52PM -0400, Alex wrote:
> > > I thought I said transport...
> >
> > Postfix instance 1
> >
> > main.cf
> > always_bcc = f...@example.com
> >
> > transport_maps
> > f...@example.com -> Postfix instance 2
> > all other mail -> content filter -> Postfix
Alex:
> > It is more or less Viktor's suggestion.
> >
> > Some details will be missing: relay_domains needs to be set u so
> > that Postfix instance 1 won't reject mail with "relay access denied".
>
> Thanks for sticking with me here. That's a pretty big change for me.
> Victor helped me create
Hi,
> Wietse:
> > Postfix instance 1
> >
> > main.cf
> > always_bcc = f...@example.com
> >
> > transport_maps
> > f...@example.com -> Postfix instance 2
> > all other mail -> content filter -> Postfix instance 2
> >
> > Perhaps a picture is worth 1e3 words.
>
> Alex:
> > Does this
Wietse:
> Postfix instance 1
>
> main.cf
> always_bcc = f...@example.com
>
> transport_maps
> f...@example.com -> Postfix instance 2
> all other mail -> content filter -> Postfix instance 2
>
> Perhaps a picture is worth 1e3 words.
Alex:
> Does this mean modifying my existing
> > > I'm currently using the default_transport to route mail to 10025 for
> > > amavisd. Would I then just use the local transport for local mail then
> > > define it in the transport file?
> >
> > No, because presumably the Bcc mail is supposed to be delivered
> > somewhere else via SMTP.
Viktor Dukhovni:
> On Wed, Apr 21, 2021 at 03:53:34PM -0400, Alex wrote:
>
> > > This is why you have a multi-instance configuration. You can use the
> > > transport table to selectively route specific recipients to specific
> > > filter transports, ... by avoiding content_filter and using
On Wed, Apr 21, 2021 at 03:53:34PM -0400, Alex wrote:
> > This is why you have a multi-instance configuration. You can use the
> > transport table to selectively route specific recipients to specific
> > filter transports, ... by avoiding content_filter and using normal
> > Postfix
> > I should have made that more clear. The problem is that I'm trying to
> > create an address to which amavisd should forward all mail unfiltered,
> > but it only works if either all addresses are included in the policy
> > or the unfiltered address is the only address.
>
> This is why you have
On Wed, Apr 21, 2021 at 03:29:07PM -0400, Alex wrote:
> I should have made that more clear. The problem is that I'm trying to
> create an address to which amavisd should forward all mail unfiltered,
> but it only works if either all addresses are included in the policy
> or the unfiltered address
Hi,
> >> > > Apr 21 10:58:24 xavier postfix-out/local[2682940]: 19D63305F4A09:
> >> > > to=, relay=local, delay=0.01, delays=0.01/0/0/0,
> >> > > dsn=2.0.0, status=sent (delivered to command: /usr/bin/procmail)
>
> it was delivered - what's the problem?
>
> >> > If you are running amavis as a
> > How do I configure always_bcc to bypass amavisd altogether so it isn't
> > processed at all?
> >
> > # postconf -c /etc/postfix-116 always_bcc
> > always_bcc = bcc-user
> >
> > I'm unsure what postconf details I can provide, so I'll instead just
> > provide the log entries.
> >
> > Apr 21
On Wed, Apr 21, 2021 at 11:17:19AM -0400, Alex wrote:
> I have postfix configured in a multi-instance setup in conjunction
> with amavisd. I'm using always_bcc to create a copy of each email sent
> or received.
This does not create a "copy", it adds a recipient to the message.
> The problem is
Hi,
> > > How do I configure always_bcc to bypass amavisd altogether so it isn't
> > > processed at all?
> > >
> > > # postconf -c /etc/postfix-116 always_bcc
> > > always_bcc = bcc-user
> > >
> > > I'm unsure what postconf details I can provide, so I'll instead just
> > > provide the log
Hi,
On Wed, Apr 21, 2021 at 11:31 AM Dominic Raferd wrote:
>
> On 21/04/2021 16:17, Alex wrote:
> > I have postfix configured in a multi-instance setup in conjunction
> > with amavisd. I'm using always_bcc to create a copy of each email sent
> > or received.
> >
> > The problem is that, while
On 21/04/2021 16:17, Alex wrote:
I have postfix configured in a multi-instance setup in conjunction
with amavisd. I'm using always_bcc to create a copy of each email sent
or received.
The problem is that, while postfix appears to deliver the bcc-user
email separately from the other recipients,
Hi,
I have postfix configured in a multi-instance setup in conjunction
with amavisd. I'm using always_bcc to create a copy of each email sent
or received.
The problem is that, while postfix appears to deliver the bcc-user
email separately from the other recipients, amavis somehow delivers to
all
18 matches
Mail list logo
