Skip site navigation (1)Skip section navigation (2)
Date:      Sat, 24 Apr 2004 09:05:35 +0100
From:      Matthew Seaman <m.seaman@infracaninophile.co.uk>
To:        Duane Winner <duanewinner@att.net>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: stupid sendmail question (did not issue MAIL/EXPN/VRFY/ETRN)
Message-ID:  <20040424080535.GA7994@happy-idiot-talk.infracaninophile.co.uk>
In-Reply-To: <40897F4A.30200@att.net>
References:  <40897F4A.30200@att.net>

next in thread | previous in thread | raw e-mail | index | archive | help

--NzB8fVQJ5HfG6fxh
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Apr 23, 2004 at 04:40:42PM -0400, Duane Winner wrote:

> I am getting this in my /var/log/maillog:
>=20
> Apr 23 15:23:39 library sm-mta[169]: i3NJNd8g000169: localhost=20
> [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to MTA

Which means that the Java side did not issue any SMTP commands after
connecting and issuing an EHLO or HELO.  Which perhaps indicates that
the sendmail side didn't respond with the expected
'250-smtp.example.com Hello ...' and following list of capabilities in
response.

What do you see if you telnet to localhost port 25 and then type in an
EHLO command? It should look something like this, although you
probably won't have the AUTH or STARTTLS parts unless you've modified
your sendmail:

    % telnet localhost 25
    Trying 127.0.0.1...
    Connected to localhost.
    Escape character is '^]'.
    220 smtp.infracaninophile.co.uk ESMTP Sendmail 8.12.11/8.12.11; Sat, 24=
 Apr 2004 08:59:29 +0100 (BST)
    EHLO localhost
    250-smtp.infracaninophile.co.uk Hello localhost [127.0.0.1], pleased to=
 meet you
    250-ENHANCEDSTATUSCODES
    250-PIPELINING
    250-8BITMIME
    250-SIZE
    250-DSN
    250-ETRN
    250-AUTH DIGEST-MD5 CRAM-MD5 LOGIN
    250-STARTTLS
    250-DELIVERBY
    250 HELP
    quit
    221 2.0.0 smtp.infracaninophile.co.uk closing connection
    Connection closed by foreign host.

Nb. That sequence generates precisely the sort of log message you saw:

    Apr 24 08:59:41 happy-idiot-talk sm-mta[8543]: i3O7xTra008543: localhos=
t [127.0.0.1] did not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4

> when my Tomcat serlvets attempt to send an email from my web app.
>=20
> I only want sendmail listing on 127.0.0.1:25, and the web app is=20
> configured to use 127.0.0.1 as it's mail server. It works fine on my Red=
=20
> Hat implementation, but I'm guessing FreeBSD sendmail is tightened up=20
> even more.
>=20
> I know that sendmail is working, because I can use the 'mail' MUA and=20
> send myself a quick email.
>=20
> I'm guessing this is a little different that just going #mail blahblah,=
=20
> because I'm doing mail relaying? But why would sendmail be denying mail=
=20
> relaying from itself (localhost).
>=20
> Is this fairly simple to address? I know its probably stupid, but I=20
> haven't played with sendmail in about 3 years, and never completely=20
> understood then either.

Hmmm... in server.xml I have:

            <Resource name=3D"mail/Session" auth=3D"Container"
                      type=3D"javax.mail.Session"/>

            <ResourceParams name=3D"mail/Session">
              <parameter>
                <name>mail.smtp.host</name>
                <value>smtp.infracaninophile.co.uk</value>
              </parameter>

              <parameter>
                <name>mail.smtp.port</name>
                <value>587</value>
              </parameter>
            </ResourceParams>

and in the per-application web.xml there is:

    <resource-ref>
        <res-ref-name>mail/Session</res-ref-name>
        <res-type>javax.mail.Session</res-type>
        <res-auth>Container</res-auth>
    </resource-ref>

and that seems to work very well.  This is from within a jail, and
speaking to sendmail in the host environment, which is why it can't
use a connection via localhost.  Port 587 is 'submission' -- the port
designated for local submission on new messages by the MUA,
distinguishing it from port 25 intended now for MTA to MTA transfer of
messages.  However, that's a new standard that has not yet reached
universal acceptance, so speaking on port 25 should work as well.

	Cheers,

	Matthew

--=20
Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

--NzB8fVQJ5HfG6fxh
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (FreeBSD)

iD8DBQFAih/PdtESqEQa7a0RAh4aAKCdl2ceZ7vecpZkHE+90aXLls/UHwCff6W/
DN+W85GQiPjLWjQs1bQ2JCI=
=2obM
-----END PGP SIGNATURE-----

--NzB8fVQJ5HfG6fxh--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040424080535.GA7994>