Thread View: vmsnet.mail.mx
1 messages
1 total messages
Started by Eric Thomas
Mon, 14 Dec 1992 18:52
Turnaround time problem with MX 3.1/JNET
Author: Eric Thomas
Date: Mon, 14 Dec 1992 18:52
Date: Mon, 14 Dec 1992 18:52
20 lines
1586 bytes
1586 bytes
In order to provide an 8-bit clean path for nordic users wishing to create LISTSERV mailing lists where the official languages are scandinavian, I am starting to make intensive use of MX and am having a turnaround time problem. Users post to 'listname@LISTSERV.SUNET.SE', which is forwarded via a MX router rule to 'listname@SEARN.BITNET'. LISTSERV processes the message and sends mail with a %-hack back to the VAX, via JNET, which then takes care of the SMTP delivery. This bypasses the SMTP translation tables on the VM system which, unfortunately, I am not at liberty to change for 8-bitness as they are imposed by the INTERBIT specifications. It has already been agreed that INTERBIT must be updated to use 8-bit tables but we have not yet agreed on the table to use. Anyway the problem is that it takes a while for the VAX to forward mail - in either direction. The machine being mostly idle, it looks like there is a built-in delay for polling the JNET queues, but of course I may have misconfigured something. I am running MX V3.1. Is there anything I can do to make MX more responsive? It gives the users the impression the machine is heavily loaded at 3am on a sunday :-) Eric
Thread Navigation
This is a paginated view of messages in the thread with full content displayed inline.
Messages are displayed in chronological order, with the original post highlighted in green.
Use pagination controls to navigate through all messages in large threads.
Back to All Threads