On 02/11/2011 05:36 PM, Victor Duchovni wrote:
On Fri, Feb 11, 2011 at 04:54:00PM +0100, Jeroen Geilman wrote:
I've tried simply setting:
fallback_transport = mail.domain.co.za
fallback_transport means "use this route if other routes are not
functional".
This is unrelated to sepc
On Fri, Feb 11, 2011 at 04:54:00PM +0100, Jeroen Geilman wrote:
>> I've tried simply setting:
>>
>> fallback_transport = mail.domain.co.za
>>
>
> fallback_transport means "use this route if other routes are not
> functional".
> This is unrelated to sepcific recipients; it only deals in mail
On 02/11/2011 09:25 AM, Pieter Steyn wrote:
Hi,
We currently have mail infrastructure setup like:
mail.domain.co.za (primary in our dc)
ptamail.domain.co.za (pta office)
jhbmail.domain.co.za (jhb office)
Currently we use mail.domain.co.za as the outgoing server for all
users, but I want to cha
Hi,
We currently have mail infrastructure setup like:
mail.domain.co.za (primary in our dc)
ptamail.domain.co.za (pta office)
jhbmail.domain.co.za (jhb office)
Currently we use mail.domain.co.za as the outgoing server for all
users, but I want to change that so that user will use
$branchmail.dom