On Thu, Apr 30, 2015 at 10:43:44AM +1100, J?r?me Alet wrote:
> > If you change the requirements, you can indeed deploy alternative
> > solutions.
>
> Correct.
>
> If our requirements can't find a simple solution, maybe our requirements
> need to be simplified.
Rewriting is ultimately simpler an
On Wed, Apr 29, 2015 at 11:39:33PM +, Viktor Dukhovni wrote:
>
> If you change the requirements, you can indeed deploy alternative
> solutions.
Correct.
If our requirements can't find a simple solution, maybe our requirements
need to be simplified.
Thanks again.
--
Jérôme Alet - - Directio
On Thu, Apr 30, 2015 at 10:20:08AM +1100, J?r?me Alet wrote:
> In Backend2's main.cf :
>
> --- CUT ---
> fallback_transport = relay:[Server1-IP]
> local_recipient_maps =
> --- CUT ---
>
> In Backend2's virtual-ldap.cf (used in virtual_maps), I've modified the
> LDAP filter to only return migrate
Hi again,
On Thu, Apr 30, 2015 at 08:05:25AM +1100, Jérôme Alet wrote:
>
> On Wed, Apr 29, 2015 at 06:12:45PM +, Viktor Dukhovni wrote:
> >
> > See http://www.postfix.org/ADDRESS_REWRITING_README.html
>
> I'll read this again then, and try to better understand it.
Thanks to a second reading o
Hi,
On Wed, Apr 29, 2015 at 06:12:45PM +, Viktor Dukhovni wrote:
> On Wed, Apr 29, 2015 at 05:45:24PM +1100, jerome alet wrote:
>
> > Sorry but I think it will be difficult to add more to my previous message.
> > I don't understand what is missing in it.
>
> What is missing is detailed config
On Wed, Apr 29, 2015 at 05:45:24PM +1100, jerome alet wrote:
> > And yet you still have not provided a complete set of requirements
> > and configuration details, while at the same time asking for
> > implementation guidance that is highly dependent on how the moving
> > parts fit together in your
>
> From: Viktor Dukhovni
> Sent: Wed Apr 29 16:49:01 NCT 2015
> To:
> Subject: Re: Question wrt partial migration from old postfix to newer one on
> two servers
>
> And yet you still have not provided a complete set of requirem
On Wed, Apr 29, 2015 at 03:53:09PM +1100, J?r?me Alet wrote:
> On Wed, Apr 29, 2015 at 04:32:22AM +, Viktor Dukhovni wrote:
> > On Wed, Apr 29, 2015 at 03:23:20PM +1100, J?r?me Alet wrote:
> >
> > You've not explained how you intend to manage mailboxes, or shown any
> > details of your configu
On Wed, Apr 29, 2015 at 04:32:22AM +, Viktor Dukhovni wrote:
> On Wed, Apr 29, 2015 at 03:23:20PM +1100, J?r?me Alet wrote:
>
> You've not explained how you intend to manage mailboxes, or shown any
> details of your configuration. My advice was correspondingly sketchy.
My bad, sorry.
> If yo
On Wed, Apr 29, 2015 at 03:23:20PM +1100, J?r?me Alet wrote:
> I've tried several combinations of your suggestions, but now
> unfortunately delivery doesn't work anymore (it used to, as explained
> previously) : newu...@backend2.example.com is always rejected as unknown
> in local recipient table.
Hi again,
On Wed, Apr 29, 2015 at 12:34:35AM +, Viktor Dukhovni wrote:
>
> Replace this (on Server1) with a rewriting configuration:
>
> virtual:
> newu...@example.com newu...@backend2.example.com
>
> transport:
> example.com relay:[backend1.example.com]
>
Hi, and thanks for your fast answer,
On Wed, Apr 29, 2015 at 12:34:35AM +, Viktor Dukhovni wrote:
> > On Backend2 mydestination is defined as :
> >
> >mydestination = example.com, backend2.example.com,
> >localhost.localdomain, localhost
>
> Looks like you're using loca
On Wed, Apr 29, 2015 at 11:18:47AM +1100, J?r?me Alet wrote:
> For a few users only, we are planning to have, in addition to
> the setup above :
>
> Internet ==> MX ==> Server1 ==> Backend2
> Internet <== Server1 <== Backend2
>
> Where Backend2 is a Debian Wheezy machine hosting Postfix 2.9.
Hello,
As a part of our existing mail setup we've got something like this :
Internet ==> MX ==> Server1 ==> Backend1
Internet <== Server1 <== Backend1
Backend1 handles SMTP authentication and is used as the end users' SMTP
server in their MUAs whenever they want to send emails to anywhere (e
14 matches
Mail list logo
