On Jul 24, 2012, at 02:22, Ori Bani wrote:
> On Mon, Jul 23, 2012 at 5:07 PM, Viktor Dukhovni
> wrote:
>> On Mon, Jul 23, 2012 at 03:33:53PM -0700, Marty Beckler wrote:
>>
>>> Transport next hops can have MX lookups disabled by adding [] around
>>> the next hop.
>>>
>>> Is it possible to define
On 7/23/2012 7:22 PM, Ori Bani wrote:
> On Mon, Jul 23, 2012 at 5:07 PM, Viktor Dukhovni
> wrote:
>> What's wrong with MX lookups? If the records are absent, Postfix
>> will use A records,
>
> Interesting, for me, postfix was throwing up its hands instead.
That's not normal behavior. If possibl
On Mon, Jul 23, 2012 at 5:07 PM, Viktor Dukhovni
wrote:
> On Mon, Jul 23, 2012 at 03:33:53PM -0700, Marty Beckler wrote:
>
>> Transport next hops can have MX lookups disabled by adding [] around
>> the next hop.
>>
>> Is it possible to define a transport that always has MX lookups
>> disabled with
On Mon, Jul 23, 2012 at 4:27 PM, Wietse Venema wrote:
> Marty Beckler:
>> Transport next hops can have MX lookups disabled by adding [] around
>> the next hop.
>>
>> Is it possible to define a transport that always has MX lookups
>> disabled without specifying the next hop?
>
> /etc/postfix/transp
On Mon, Jul 23, 2012 at 03:33:53PM -0700, Marty Beckler wrote:
> Transport next hops can have MX lookups disabled by adding [] around
> the next hop.
>
> Is it possible to define a transport that always has MX lookups
> disabled without specifying the next hop?
>
> man 5 transport says that triv
On Mon, Jul 23, 2012 at 07:27:05PM -0400, Wietse Venema wrote:
> Marty Beckler:
> > Transport next hops can have MX lookups disabled by adding [] around
> > the next hop.
> >
> > Is it possible to define a transport that always has MX lookups
> > disabled without specifying the next hop?
>
> /et
Marty Beckler:
> Transport next hops can have MX lookups disabled by adding [] around
> the next hop.
>
> Is it possible to define a transport that always has MX lookups
> disabled without specifying the next hop?
/etc/postfix/transport:
example.com smtp-no-mx:
/etc/postfix/master.cf:
sm
Transport next hops can have MX lookups disabled by adding [] around
the next hop.
Is it possible to define a transport that always has MX lookups
disabled without specifying the next hop?
man 5 transport says that trivial-rewrite(8) doesn't allow
substitutions in pcre tables, otherwise, this is
