Marian D(urkovic( wrote:
>>> as a public-facing MTA really, really does need to have a fixed-IP
>>> with a valid PTR RR
>> It doesn't matter how many times you say this, it's simply not true.
>> No RFC requires this. This is you saying "I think a public-facing
>> MTA really, really does need to have a fixed-IP with a valid PTR RR".
>> Please express such things as opinions, and not as universally
>> accepted facts or technical requirements, which is what they, however
>> unintentionally, come across as.
>>
>> And, yes, I know I'll get my usual bounce from your mail server when
>> it throws away yet another perfectly legitimate non-spam email,
>> because I dare to send email from my home ADSL connection, starting
>> the email in RFC1918 space, with no matching reverse DNS.
>
> Sorry, but I fail to understand what point you're trying to make.
> Your *public facing* MTA does have a valid PTR RR and your
> envelope from doesn't use RFC1918 either. So your real problem is
> most probably the fact, that your HELO uses completely different
> domain than the PTR points to:
Which could easily be fixed by adding this to the smtp transport:
helo_data = ${lookup dnsdb{ptr=$sending_ip_address}}
--
Mike Cardwell - IT Consultant and LAMP developer
Cardwell IT Ltd. (UK Reg'd Company #06920226)
http://cardwellit.com/
