On Thu, May 02, 2013 at 11:14:23PM +0200, Michael Ionescu wrote:
> > "C" Multiple postfix instances is the preferred solution. Postfix
> > supports multiple instances on the same machine quite well. The
> > added overhead to the machine is negligible. There is some extra
> > administration, but
Am 03.05.2013 00:40, schrieb Noel Jones:
> Postfix transport features are global to each instance, and are
> non-conditional. If you're using sender dependent transports, you're
> going to have a hard time without multiple instances
not if you are firm with mysql-tables and queries
sender/sende
On 5/2/2013 4:14 PM, Michael Ionescu wrote:
>
>
> On 02.05.2013 17:57, Noel Jones wrote:
>>> [...]
>>> prequeue proxy virusfilter [...] precludes
>>> rewriting the Received: header [...]
>>> QUESTION 1: Is this correct?
>>> [...]
>>> QUESTION 2: Is there a definitive overview of all the ways post
On 02.05.2013 17:57, Noel Jones wrote:
>> [...]
>> prequeue proxy virusfilter [...] precludes
>> rewriting the Received: header [...]
>> QUESTION 1: Is this correct?
>> [...]
>> QUESTION 2: Is there a definitive overview of all the ways postfix
>> detects loops and at what stages these are employ
On 5/2/2013 1:20 AM, Michael Ionescu wrote:
> I have a corner case where I need to allow an emails generated at my
> site with certain off-site sender addresses to be routed through my MTA
> to the off-site smarthost officially responsible for the sender domain.
>
> This can be easily done using s
I have a corner case where I need to allow an emails generated at my
site with certain off-site sender addresses to be routed through my MTA
to the off-site smarthost officially responsible for the sender domain.
This can be easily done using sender-based-routing. However, it becomes
an issues as
