Adam Nielsen wrote:
>>What do you have for PTR records?
>>What you HELO as is one thing, what the far-end recovers from rDNS may
>>not match.
>
>
> Yep, the PTR records are fine, the problem is that the HELO responses
> *don't* match the rDNS records.
>
>
>>But any router that can ascertain which domain and interface is to be
>>used [1] can call a transport set such as this (note I am not showing
>>prefixes here):
>
>
>>beedomain_remote_smtp:
>> driver = smtp
>> helo_data = beedomain.tld
>
>
> Ah, brilliant! That worked *perfectly* - just what I was after!
>
>
>>[1] This presumes you already have a working method to select the
>>desired outbound interface.
>
>
> The machine is a sort of a mailhub, so I know all mail for a certain
> domain will be sent to a single smarthost. This smarthost is connected
> via a different subnet, so I know the OS will always pick a certain
> interface when connecting to it. I've set the "helo_data" to the rDNS
> name of that interface and it all works perfectly now!
>
> Many thanks for your quick response!
>
> Cheers,
> Adam.
>
Just stuff learned right here.
And the blessing/curse of not having a biorythm tied to any particular time-zone..
:-(
Bill
