Re: The mailq service

[VIP Lists Account <viplists@vip.maestro.com.pl>]

On Mon, 29 Jun 1998 mea@nic.funet.fi wrote:

> > > > from the outside, I still want the mailq command to work locally)
> > > 	use tcp wrappers.
> >
> > Won't work. Zmailer daemons are not invoked via the inet superserver, they
> > are started from the command line and "daemonized" - they listen on the
> > ports in question on their own. The tcp wrappers never get in their way -
> > that is unless I can use the wrappers from within zmailer? I was looking
> > for information on this topic, but alas to no avail... ;-((
> 
>   ./configure ...  --with-tcp-wrappers=...
That's what I did. I used the Red Hat spec file for zmailer 2.99.49p4,
which uses that option by default.

> > access to it in /etc/hosts.deny would work - the assumption was that inetd
> > and thus tcp wrappers will get the connection first and refuse it. But
> > that doesn't work. strobe still reports the mailq service on tcp port
> > 174....
> 
> And after you have tcp-wrapper code in, the strobe will still report that
> the mailq service replies -- but the strobe does not TEST to see, if it
> really works.  (Strobe does connect(), and then close(), doesn't it?)
Not quite. Below is a fragment of what strobe displays when run from the
localhost against itself (actual mail addresses removed to protect the
users' privacy):

vip.maestro.com.pl   174 mailq        MAILQ [RXZ]
                         -> version zmailer 1.0\n
                         -> Vertices:\n
                         -> 1:\tY/573454-327\t1; 165\t#smtp; 500 (nameserver data inconsistency. No MX, no add
                         -> ress: 'maestro.com.pl', errno=Success, gai_errno='name or service is not known'
                         -> ) (retry in 2m11s, expires in 2d20h, tries=4)\n
                         -> 2:\tJ/573465-328\t1; 194\t#smtp; 500 (nameserver data inconsistency. No MX, no add
                         -> ress: 'maestro.com.pl', errno=Success, gai_errno='name or service is not known'
                         -> ) (retry in 2m11s, expires in 2d22h, tries=2)\n
                         -> 3:\tM/573468-327\t1; 87\t#procmail: Quota exceeded while writing "/var/spool/mail/
                         -> usernameremoved"[exit status 73/75 (can't create output file)] (retry in 8m12s, expire
                         -> s in 2d7h, tries=3)\n
                         -> Channels:\n
                         -> local:\t>3\n
                         -> smtp:\t>1>2\n
                         -> Hosts:\n
                         -> usernameremoved@vip.maestro.com.pl:\t>3\n
                         -> maestro.com.pl:\t>1>2\n
                         -> End:\n
                         -> smtp/*/0\n
                         ->     smtp/maestro.com.pl/0\tR=2  A=4  W=131s QA=3h35m34s\n
                         -> \tThreads:    1 Msgs:     2 Procs:   1 Idle:   1 Plim:  50 Flim: 150 \n
                         -> local/*/0\n
                         ->     local/username@vip.maestro.com.pl/0 R=1  A=3  W=492s QA=1d16h\n
                         -> \tThreads:    1 Msgs:     1 Procs:   1 Idle:   1 Plim:   5 Flim: 150 \n
                         -> Kids: 2  Idle:  2  Msgs:   3  Thrd

So, strobe actually starts conversation with the server thus giving away
loads of information...