[Info-vax] A second SMTP recevier on an alternate non-prived port.

[Jan-Erik Soderholm]

JF Mezei wrote 2011-10-14 20:03:
> R.A.Omond wrote:
>
>> I took a quick look at TCPIP$CONFIG.COM and you could edit it
>> replacing all occurrences of SMTP with XMTP, and use your new
>> port number (and then throw the edited procedure away).
>
>
> Just use the TCPIP>  utility to define a new service.
>
> Do a show service SMTP with all the defails and just create a new
> service based on those details, with different log files and different port.
>
> Remember to make this a permanent definition, and you can also define
> the service to "autostart" in the permanent definitions. I forgot the
> exact syntax.
>
> There is a caveat however: the TCPIP$SMTP_RECEIVER.EXE  *might* be
> hardcoded to use port 25. On the other hand, this exec doesn't run 7/24,
> it is an "on demand" type of service where the image is invoked bt the
> TCPIP kernel when a call to 25 comes in.
>
> You will not be able to have a different config (SMTP.CONFIG) unless you
> play tricks with logical names so that the second instance gets to a
> different logical name table.

OK. Thanks a lot ! Maybe I'll give some background.

I'd like to help someone out that is experimenting with a smtp stack
on a microcontroller. He has some trouble when using his regular
smtp service at his ISP and I thought I'd let him try sending
some test mails through my (VMS) server. Now, my ISP seems to be
blocking port 25 from external (external to my ISP) sources.

Ports above 1024 are usualy not blocked. I'll experiment some...

Jan-Erik.