On Fri, Oct 18, 2013 at 3:04 PM, Viktor Dukhovni wrote:
>
> > If this is the case do a header_check with a regex and then respond a
> > "FILTER transport:".
>
> That's silly, a "-o content_filter=transport:" in master.cf is
> simpler and much more robust. The goal is after all to set the
> tran
On Fri, Oct 18, 2013 at 01:56:18PM +0100, Jose Borges Ferreira wrote:
> On Thu, Oct 17, 2013 at 8:45 PM, Roel Bouwman wrote:
>
> > @Jose: thanks for the suggestion, but sender_dependent transport
> > maps are not a solution here. As in this case, it's not the sender
> > address, but the inbound s
On Thu, Oct 17, 2013 at 8:45 PM, Roel Bouwman wrote:
> @Jose: thanks for the suggestion, but sender_dependent transport
> maps are not a solution here. As in this case, it's not the sender
> address, but the inbound service to which the message was submitted
> that should determine how the messag
Hi Wietse,
Op Thu, Oct 17, 2013 at 02:22:36PM -0400 schreef Wietse Venema:
> If one must force the outbound SMTP IP address depending on the
> inbound SMTP IP address, specify "-o content_filter=foo:" in
> master.cf.
I've thought about that, but it will fail if the message can't
be delivered imme
Roel Bouwman:
> Hi Wietse,
>
> Op Thu, Oct 17, 2013 at 02:22:36PM -0400 schreef Wietse Venema:
> > If one must force the outbound SMTP IP address depending on the
> > inbound SMTP IP address, specify "-o content_filter=foo:" in
> > master.cf.
>
> I've thought about that, but it will fail if the m
On Oct 17, 2013 4:59 PM, "Roel Bouwman" wrote:
>
> Hello,
>
> I've been trying to simplify our multi-instance Postfix setup,
> however, I'm wondering whether it's actually possible. So I
> was wondering if anyone could tell me whether my idea is futile
> or could actually work.
>
> Let me explain.
Grr. the text editor ate up one line from my example.
It's fixed below.
Wietse
Viktor Dukhovni:
> > You made some mistake in a master.cf service name field, or some
> > "security" feature (selinux, apparmor, or the like) is getting in
> > the way.
>
> However, all these pathnames are que
Viktor Dukhovni:
> > You made some mistake in a master.cf service name field, or some
> > "security" feature (selinux, apparmor, or the like) is getting in
> > the way.
>
> However, all these pathnames are queue-directory relative, and so
> a second queue-manager with a custom queue directory need
On Thu, Oct 17, 2013 at 01:30:50PM -0400, Wietse Venema wrote:
> Roel Bouwman:
> > I have tried duplicating the "cleanup" and "qmgr" and "rewrite"
> > services in master.cf with a duplicate one, and using the
> > -o queue_directory and -o ..._service_name and -o default_transport
> > parameters to
Roel Bouwman:
> I have tried duplicating the "cleanup" and "qmgr" and "rewrite"
> services in master.cf with a duplicate one, and using the
> -o queue_directory and -o ..._service_name and -o default_transport
> parameters to seperate traffic flows.
>
> However, this doesn't seem to work as I woul
On Thu, Oct 17, 2013 at 05:58:16PM +0200, Roel Bouwman wrote:
> I have tried duplicating the "cleanup" and "qmgr" and "rewrite"
> services in master.cf with a duplicate one, and using the
> -o queue_directory and -o ..._service_name and -o default_transport
> parameters to seperate traffic flows.
Hello,
I've been trying to simplify our multi-instance Postfix setup,
however, I'm wondering whether it's actually possible. So I
was wondering if anyone could tell me whether my idea is futile
or could actually work.
Let me explain.
We run SMTP services for multiple organisations on a cluster
o
12 matches
Mail list logo
