sending mail on lan...

[Dan Shoop]

On Aug 2, 2007, at 5:02 PM, Jerry LeVan wrote:

> Uggh,
>
> Yesterday I screwed up the postfix config so bad that I could
> not even send my to myself...
>
> Fortunately I was able to recover the error.
>
> By setting:
> mynetworks = 192.168.1.0/28, 127.0.0.0/8
>
> I was able to send to other machines on my lan
> by using strings like
>
>    user@[192.168.1.xxx]
>
> as the address.
>

That would be the expected and documented behavior.

Have you considered reading the postfix docs or better yet the  
O'Reilly Postfix "Dove" book???????
See http://www.oreilly.com/catalog/postfix/

> It appears that if a "name" is used ie jerry at server.localdomain
> that a name lookup occurs an one gets an error on a "A" address
> lookup.

Actually it fails b/c there is no A record OR MX record for the  
domain server.localdomain.

This also would be expected if you had no DNS for these hosts. Mail  
requires FQDNs. Read the RFC.

> I enabled Flat Files in Directory Access, but nothing changed...

Because mail requires DNS and FQDNs.

> I peeked at netinfo and thought that perhaps adding a "machine"
> entry might help, but could not figure out the "serves" entry.

But mail uses DNS and FQDNs.

> Dan Shoop suggested reading the lookupd man page, but found it
> to be relatively opaque...

Then you should consult your sysadmin.

> The linux box runs smtp and has a "caching name server" ( of which
> I know nothing...) and does not have any problem sending mail to
> the other machines on the lan.

Then you should consult your hostmaster.

> It is interesting that the host command fails for linux and macs
> on the lan.

Because you don't have DNS and FQDNs??

> So, is there something I can do with Directory Access, NetInfo and
> Lookupd so that I don't get lookup errors in the mail system for
> machines on  the lan?

No, that is an invalid conclusion. It fails b/c you have neither  
FQDNs or DNS.

-dhan

------------------------------------------------------------------------
Dan Shoop <shoop at iwiring.net>
Tactical Operations Center: 1.866.901.8787 (24x7)
Ph: 714.363.1174
AIM: iWiring