Re: Postfix SMTP server: errors from something.net[ip address]

2 msg	Postfix SASL Help
6 msg	Slowing down postfix
2 msg	need help deciphering a line

Postfix SMTP server: errors from something.net[...
\ Guy Story KC5GOI (22 Jan 2008)
. \ (Wietse Venema) (22 Jan 2008)
. . \ Guy Story KC5GOI (22 Jan 2008)
. . . \ (Wietse Venema) (22 Jan 2008)

4 msg	2.5.0-RC and 2.6 should recognize FreeBSD 8
9 msg	Postfix not following my access file.
3 msg	postfix logs delay, delays, dsn
3 msg	Best way to shutdown postfix prior to servicing...
1 msg	the bounce process hangs a mail (?)
3 msg	messages destined for content_filter stuck in d...
2 msg	Domain in username
5 msg	missing authentication on recipient
5 msg	postfixadmin
5 msg	check_policy_service before reject_rbl_client
9 msg	MXBackup via LDAP
5 msg	header and body check exemptions
5 msg	Relay recipient maps and relocated users
4 msg	mail forwarding loop :: SPAM
3 msg	transport_maps how to match mx's
2 msg	Where/when to insert a missing Message-ID

Subject:	Re: Postfix SMTP server: errors from something.net[ip address]
Group:	Postfix-users
From:	(Wietse Venema)
Date:	22 Jan 2008

Guy Story KC5GOI:
> Found it. I hope the next time someone runs into this that it is found
> via Google. This was a case of me being my worst enemy. It was an
> unknown smtpd restriction. For some reason I used ACCEPT instead of OK.
> I took care of the mistake, postmap -d the file, reloaded, retested and
> bingo.

For safety reasons, the Postfix SMTP server tries to avoid divulging
system internal details in its replies. These details are written
to the local logfile.

> One question that is OT. I see a lot of hostname verification failures
> with name or service not known. I understand this can be a symptom of
> broken DNS, but isn't it also a sign of an invalid, UCE server, or
> poorly configured server? I am sure this question has been asked and
> grey listing would help. I found why my grey listing is broke but that
> is not for that list.

Postfix is merely the messenger of bad news (the client IP address
resolves to a name, but that name does not resolve to the client
IP address). There are many possible reasons, but a broken remote
DNS configuration is by far the most common cause.

Wietse