[Info-vax] Latest TCPIP Services seem irreparably horked...

[Simon Clubley]

On 2012-03-04, VAXman-  @SendSpamHere.ORG <VAXman- at SendSpamHere.ORG> wrote:
>
> OK.  I have some more information and I have repaired my POP issues.
>
> The configuration, as I posted in one of the first messages as TOP_HEADER
> set:
>
> $ TCPIP SHOW CONFIGURATION SMTP
> SMTP Configuration
>                                                                    Options
> Initial interval:   0 00:30:00.00       Address_max:    16       NOEIGHT_BIT
> Retry interval:     0 01:00:00.00       Hop_count_max:  16       NORELAY
> Maximum interval:   3 00:00:00.00                                TOP_HEADERS
>  :
>  :
>
> The POP configuration file has: Ignore-Mail11-Headers: TRUE
>
> Yet, attempts to start the POP server with this configuration yielded an
> error in the log file complaining about the option not being set:
>
> 2012-03-02 08:47:15 Warning! You have not configured SMTP /OPTION=TOP_HEADERS and at the same time
> 2012-03-02 08:47:15          you have configured POP to ignore mail11 headers. This combination
> 2012-03-02 08:47:15          of options is not acceptable. Either turn on SMTP top headers
> 2012-03-02 08:47:15          or don't turn on POP ignore mail11 headers. For this run the POP
> 2012-03-02 08:47:15          server will *not* ignore mail11 headers.
> 2012-03-02 08:47:15 starting TCPIP POP server V5.7-ECO3, OpenVMS V8.4 Alpha on host ALPHA.TMESIS.COM and port 110
>
> Yesterday, I played around and started the SMTP server.  Not completely,
> however, as I'm running MX% for my SMTP server.  Now, with a SMTP_node_1
> process on the system, the POP server is happy!  Still no success in the
> IMAP department but the mail is, once again, properly delivered from the
> post office.  The documentation is lame and requiring the SMTP server to
> run as part of serving up email via POP is lame.  There are several third-
> party SMTP servers and, until now, POP would function with them.
>

So basically, TCP/IP is now been developed on the basis that customers
will not be able plug in third party components to replace the HP
supplied components.

I am assuming this is _NOT_ a deliberate policy (at least I hope it
isn't), but simply a result of the people currently maintaining TCP/IP
not even thinking about this issue. I wonder what other issues they
are not thinking about.

I'm seriously unimpressed with what is going on with VMS at the moment.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980s technology to a 21st century world