Hello list,
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
Thanks in advance.
--
sent from https://dkinbox.com/
On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
messages will g
On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
My postfix has setup another MTA for relay host,
relayhost = [relay_ip]
If I setup this postfix as backup mx for a domain, such as foo.com.
will messages for foo.com relay from relay_ip too, or go directly to the
primary MX?
On 21.05.23 11:
> On 21.05.23 15:53, Tom Reed via Postfix-users wrote:
>>My postfix has setup another MTA for relay host,
>>
>>relayhost = [relay_ip]
>>
>>If I setup this postfix as backup mx for a domain, such as foo.com.
>>will messages for foo.com relay from relay_ip too, or go directly to the
>>primary MX?
Hi,
I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be
able to control which header and body checks apply to which domain in a
specific instance. I'm looking for advice on the best way to do this.
I have about ten domains right now, and would probably need a number of
policies
Alex via Postfix-users:
> Hi,
> I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be
> able to control which header and body checks apply to which domain in a
> specific instance. I'm looking for advice on the best way to do this.
>
> I have about ten domains right now, and woul
Wietse Venema via Postfix-users:
> Alex via Postfix-users:
> > Hi,
> > I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be
> > able to control which header and body checks apply to which domain in a
> > specific instance. I'm looking for advice on the best way to do this.
> >
>
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
Hi,
On Sun, May 21, 2023 at 12:39 PM Wietse Venema via Postfix-users <
postfix-users@postfix.org> wrote:
> Wietse Venema via Postfix-users:
> > Alex via Postfix-users:
> > > Hi,
> > > I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be
> > > able to control which header and bo
I'm using multi-instance postfix-3.7.2 on fedora37 and would like to be
able to control which header and body checks apply to which domain in a
specific instance. I'm looking for advice on the best way to do this.
I'd say, start with one instance per domain. The 'cost' of doing so
is really sma
Alex via Postfix-users:
> > > I'd say, start with one instance per domain. The 'cost' of doing so
> > > is really small.
> >
> > Once you run out of IP addresses, you will need policy selection
> > based on the recipient domain. For example:
> >
> > internet -> front-end Postfix instance -> fil
Hi,
On Sun, May 21, 2023 at 4:41 PM Wietse Venema via Postfix-users <
postfix-users@postfix.org> wrote:
> Alex via Postfix-users:
> > > > I'd say, start with one instance per domain. The 'cost' of doing so
> > > > is really small.
> > >
> > > Once you run out of IP addresses, you will need policy
Alex via Postfix-users:
> Hi,
>
> On Sun, May 21, 2023 at 4:41?PM Wietse Venema via Postfix-users <
> postfix-users@postfix.org> wrote:
>
> > Alex via Postfix-users:
> > > > > I'd say, start with one instance per domain. The 'cost' of doing so
> > > > > is really small.
> > > >
> > > > Once you r
Hi,
> > > > internet -> front-end Postfix instance -> filter -> back-end
> > > Postfix
> > > > > instance
> > > > >
> > > > > The front-end Postfix instance uses transport_maps to select a
> suitable
> > > > > filter.
> > > > >
> > > > > example.com: smtp:
> > > > > example.org: smtp:
Alex via Postfix-users:
> Hi,
>
> > > > > internet -> front-end Postfix instance -> filter -> back-end
> > > > Postfix
> > > > > > instance
> > > > > >
> > > > > > The front-end Postfix instance uses transport_maps to select a
> > suitable
> > > > > > filter.
> > > > > >
> > > > > > exampl
Hi,
> According to the subject, you appear to be looking for per-domain
> header/body check. That is not the right tool, and I would not
> spend my cycles on a design for that.
>
> Instead I recommend filters between a front and back-end instance,
> using transport_maps to select a filter dependi
On Sun, May 21, 2023 at 06:26:34PM -0400, Alex via Postfix-users wrote:
> I don't have any content filters set up in the front-end postfix. How do I
> connect the front-end postfix with the filters?
For per-domain message content modification you need to first "split the
envelope", so that each c
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
18 matches
Mail list logo
