Re: SMTP Banner info

[Vernon Hamberg <vhamberg@xxxxxxxxx>]

IBM uses message files so much for this kind of thing. But I had my doubts
that these were the messages in use, because the text did not exactly match
the message description. Yellow brick road time, eh?

They might be using one that has a single substitution variable, then
building the string in the app. Then there's nothing to be done. Or there's
another message file somewhere. This is as much as I know or can guess at
reasonably.

Maybe Carol Woodbury or Wayne Evans or John Earl would have some ideas. I
just saw some notice of Carol Woodbury going into business for herself.
Wayne Evans is one of the authors of the Tips & Tools for Security.
Questions to Carol can be submitted at
<http://Search400.techtarget.com/ateQuestion/0,289624,sid3_cid423497_tax288767,00.html>,
last I saw in a Search400 newsletter. John is on the list.

At 08:00 AM 4/23/02 -0600, you wrote:
>Vernon,
>I modified TCP2273 and TCP2219, ended TCP and TCPSVR but no change. Any
>ideas?
>Thanks,
>Kyle
>
>"Vernon Hamberg" <vhamberg@attbi.com> wrote in message
>news:<5.1.0.14.2.20020419194348.00a9db40@127.0.0.1>...
> > Some responses for TCP/IP apps are found in a message file,
> > QTCP/QTCPMSGF. Take a look at TCP2273 - that's this one, or something
> > like it. This is different from below - and on a v5r1 system I work
> > on, so it doesn't seem to be using this.
> >
> >      220 &1 running IBM AS/400 SMTP at &2.
> >
> > You could try changing this message - be sure to preserve its original
>
> > values - and see what happens.
> >
> > Another message appears when you quit the connection - TCP2219 -
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>Before posting, please take a moment to review the archives
>at http://archive.midrange.com/midrange-l.