Paul C:
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: warning: hostname
> cleers.dustypex.com does not resolve to address xx.xx.xx.xx: Temporary
> failure in name resolution
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: connect from
> unknown[xx.xx.xx.xx]
The client IP address has no PTR record, or the PTR record name
does not resolve to the client IP address. Postfix therefore logs
the client as "unknown" instead of cleers.dustypex.com.
> Jun 3 14:22:41 PHX1-1831 postfix/smtpd[2092]: improper command
> pipelining after EHLO from unknown[xx.xx.xx.xx]: HELO
> hostname.domain.net.net\r\n
The client sends
EHLO some-host-name<CR><LF>HELO hostname.domain.net.net<CR><LF>
This violates SMTP, and Postfix logs this. You can block mail from
such clients by using reject_unauth_pipelining in smtpd_*_restrictions.
> First is probably someone trying to relay to my server, the
> cleers.dustypex.com hostname is not one of mine, but the ip I X'd out
> is mine, so my guess is they try to connect on that ip and send mail,
> and postfix is stopping it? I've gotten maybe 1000 of them in the last
> 2-3 days.
You have a bot on your network, and you need to clean up that
machine. Unless Postfix is configured to block this, it will
forward their mail.
Wietse
