[Info-vax] upgrading from VMS 7.3-2 and TCPIP 5.4 ECO 7 to VMS 8.4 and TCPIP 5.7

Jan-Erik Soderholm jan-erik.soderholm at telia.com
Sun May 17 17:22:51 EDT 2015


Phillip Helbig (undress to reply) skrev den 2015-05-17 21:34:
> In article <mjampk$27va$1 at news.kjsl.com>,
> helbig at asclothestro.multivax.de (Phillip Helbig (undress to reply))
> writes:
>
>>> Operating as an open relay is one of the most truly absurd default
>>> settings I've ever encountered for a modern SMTP mail server, too.
>>
>> I agree that it's not a good default.  Mine came up as NORELAY,
>> presumably because that is what I had before.
>>
>> In those events---which should be rare---that a change of basic
>> configuration-file formats or whatever is needed, then I too would
>> expect that it should just work out of the box, inheriting the old
>> settings.  I'll have to investigate more.  I had read so much about how
>> SMTP had changed and that this wasn't documented that I was expecting
>> the worst.
>
> It looks like the new TCPIP$SMTP.CONF took over stuff from
> TCPIP$CONFIGURATION.DAT (set with TCPIP> SET CONF SMTP) as well as stuff
> from SMTP.CONFIG (which is presumably obsolete now).
>
> Does anyone know the reasoning behind this?  I liked the SET and SHOW
> commands better than editing a text file by hand.  Hopefully other stuff
> one can set and show with TCPIP> commands won't change to configuration
> files which one has to edit by hand?!
>

As far as I know, it was only *SMTP* that changed from a CLI
config interface to a text file config.

Reasoning? Why do you think there was any reason?

Other then "Hm, I'll put it in a text file so that I do not
have to maintain the SET/SHOW interfaces. Saves me work...".





More information about the Info-vax mailing list