> This is great to hear. :) Even though it will be more work I would
> recommend upgrading to Postfix 2.0.x. The feature I especially like
> about it is the X-Original-To: header. It is very useful for mail
> filtering. There are even more exciting features in the experimental
> branch of Postfix. Mostly having to do with spam prevention.

I will upgrade to postfix 2; I'm just waiting to determine whether the
upgrade will go okay over the top of my existing postfix 1 install. The
1.11.11-11.rpm is configured chroot by default, whereas Wietse's own
distribution is not. (There was a discussion between him and the RPM
developer in the postfix list the morning because of my question.) I have
not found an RPM that claims to work with RH9.

> "/etc/hosts". If you forward me a copy of one of the undeliverable
> messages I will be able to help you better.
> 

Here's the exact message...

Postfix; Name service error for groupone.intranets.com: Host found but no
data
record of requested type

When this happens, I check the target MX manually, and it resolves just
fine...

[EMAIL PROTECTED] root]# host -t MX groupone.intranets.com groupone.intranets.com
mail
is handled by 5 inbound.groupone.intranets.com.criticalpath.net.

After I check it like this, the mail goes through the next time I try to
send the same message.

It appears that postfix's call to gethostbyname() is not triggering a
recursive lookup. At least, named does not do anything. But when I make
named go get the record from a shell prompt, the next time postfix asks for
it, it finds it in the local cache. Does that sound reasonable?

At any rate, I removed the acls from named.conf, and the problem seems to
have gone away. I'll put them back in later, only I'll add 127.0.0.1, and
see if I shoot myself in the foot again.

--Eric

_______________________________________________
RLUG mailing list
[EMAIL PROTECTED]
http://www.rlug.org/mailman/listinfo/rlug

Reply via email to