Duncan Watson wrote:
> > All mail sent is shown to come from 'mail.movielink.net.au' with
> > the IP of the firewall. That IP currently resolves to 'mail.movielink.net.au'
> > which does not match with <[EMAIL PROTECTED]> and the error 451 is
> > sent back to us.
> >
> > Should I have that IP reverse lookup to resolve to 'movielink.net.au'
> > instead?
>
> >From my point of view the bouncing programs are broken. Having no address
> record for a domain but having MX records as you do is 100% valid. I have
>
That is what I thaught...
2 domains that do consistently not work are 'guestmail.net' and 'is.com.fj'
when I have reverse lookup set to 'mail.movielink.net.au'.
> used that setup many times. You want mail.movielink.net.au to reverse resolve
> to the domain it claims to be (mail.movielink.net.au) for other reasons and
> for filters that do checking correctly. There is nothing wrong with
> mascarading either ethically or technically. Some zeolots are preaching that
> all should resolve in their ideologically correct way but unfortunately many
> of their ideologies are flawed in that they do not handle:
> 1. dialup users needs
> 2. certain types of firewall needs (yours)
> 3. basically anything past a certain level of complexity.
'guestmail.net' and 'is.com.fj'
I have got my ISP to change the reverse lookup to 'movielink.net.au'.
I dont know if this is valid but at least it the IP '139.130.11.172'
should reverse lookup to 'movielink.net.au' (Qmail still says HELO
'mail.movielink.net.au' which results in a message that it may
be forged but at least it should not stop things)
Now the "MAIL From:<[EMAIL PROTECTED]>" should result in an OK
response if the receiving SMTP server looks up the IP address.
Anthony
