First, I've solved the problem.
os2.ami.com.au is my computer; it's permanently attached to the Internet. it
also has an alias, www2.ami.com.au.
I also use the name os2.ami.com.au for the domain name of my home LAN. Except
for one or two glitches, it works well.
One of the glitches is that mail relaying has never worked for me. I
configured my sendmail at home to relay mail to the world via os2.ami.com.au.
I have also configured the same computer to receive mail for os2.ami.com.au;
it's the server for my home LAN after all.
relaying has never worked, but I'd never bothered as my mail's been getting
delivered. However, I recently encountered one of the few domains where the
postmaster is under the delusion that refusing mail from a machine which
announces itself with an unresolvable hostname reduces spam.
I updated my sendmail to the same version as I have on another box where
relaying actually does work and negotiated the pitfalls in configuring the new
version the way I want it (and resending some bounced mail). However, it still
would not relay via the box os2.ami.com.au. And, when I told it to relay via
www2.ami.com.au, it complained about mail loop.s
I checked that I could relay via my IAP's box. However, mail bounced when it
was unresolvable.
Eventually, I hit on the idea of adding a new entry to my zone file; not
relay.os2.ami.com.au is a name in my home LAN but with the IP address of the
486 box on the net.
Relaying through it works for me (but not for you!!) now; I've just checked
its log.
Hopefully, I won't get mail bouncing because my mail relay is unresolvable
either.
_______________________________________________
Redhat-devel-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-devel-list
