OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
Re: connect to 127.0.0.1 refused

From: /dev/rob0 (rob0gmx.co.uk)
Date: Fri Jul 27 2007 - 16:08:02 CDT


On Friday 27 July 2007 11:16:19 Wietse Venema wrote:
> > <xxxzzzzzzz.net>: connect to 127.0.0.1[127.0.0.1]: Connection refused
>
> It does not help now, but Postfix 2.5 will log the destination port,
> to simplify trouble shgooting.

I've been using an "accidental feature" with smtpd: making symbolic
links, using those as daemon names:

$ v /usr/libexec/postfix | grep smtpd
-rwxr-xr-x 1 root root 1376651 2006-07-29 09:59 smtpd*
lrwxrwxrwx 1 root root 5 2006-12-17 11:41 smtps -> smtpd*
lrwxrwxrwx 1 root root 5 2006-08-11 10:17 submission -> smtpd*
$ egrep 's(mtp[ds]|ubmission)$' /etc/postfix/master.cf
smtp inet n - n - - smtpd
submission inet n - n - - submission
smtps inet n - n - - smtps

The renamed smtpd(8) dutifully reports itself in logs as the name by
which it was called.

As you say, it does help in troubleshooting. It's especially useful in
content_filter setups where you can have a reinjection symlink and
service. But of course it does not work for the smtp => content filter
because smtp(8) only works when invoked as smtp or lmtp.

Has this been considered as an official feature? If not, please do.
--
    Offlist mail to this address is discarded unless
    "/dev/rob0" or "not-spam" is in Subject: header