Archive-Date: Fri, 01 Apr 1994 00:07:24 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 00:06:47 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <0097C47B.79174A20.9@WKUVX1.WKU.EDU> Subject: MX-LIST Administrivia: Monthly Post Posting statistics for list MX-LIST during March 1994 Total number of posts: 217 Total number of posters: 82 Total number of subscribers: 223 Total number of digest subscribers: 32 Last modified: 31-MAY-1993 23:55 (Added digest info.) Welcome to MX-List@WKUVX1.WKU.EDU, an electronic mailing list established for the discussion of the Message Exchange mail software. This is a routine posting you will see from time to time on MX-List. MX-List postings are also available in a daily digest format. To subscribe to the digest, send the following command in the body of a mail message to MXserver@WKUVX1.WKU.EDU: SUBSCRIBE MX-List-Digest "Your real name here" The MX-List archives are maintained at ARCHIVES@WKUVX1.WKU.EDU. To get a copy of any month's postings, send an e-mail message with the body SEND MX-List.yyyy-mm to ARCHIVES@WKUVX1.WKU.EDU, where "yyyy" is the year and "mm" is the numeric representation of the month. For example, the message SENDME MX-List.1992-04 will send the archives for April 1992. MX itself is available via anonymous ftp from ftp.spc.edu in [.MX.MX033]. You can also get it via e-mail by sending the commands SEND MX033 and SEND FILESERV_TOOLS on separate lines in the body of a mail message to FILESERV@WKUVX1.WKU.EDU. To remove yourself from the mailing list, send the following command to MXserver@WKUVX1.WKU.EDU: SIGNOFF MX-List MXserver supports a few other commands for your convenience. The following commands can be handled automatically by the list processor: SIGNOFF MX-List - to remove yourself from the list REVIEW MX-List - to get a list of subscribers QUERY MX-List - to get the status of your entry on the list SET MX-List NOMAIL - to remain on the list but not receive mail SET MX-List MAIL - to resume receiving mail from the list SET MX-List CONCEAL - to not report your address in a REVIEW SET MX-List NOCONCEAL - to report your address in a REVIEW SET MX-List REPRO - to receive posts you make to MX-List SET MX-List NOREPRO - to not receive posts you make to MX-List LIST - to get a list of mailing lists served by WKUVX1 HELP - to receive a help file By default, subscriptions are set to MAIL, REPRO, NOCONCEAL. If you have any questions, comments, or suggestions about MX-List, please contact the list owner at the address below. =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Hunter Goatley, VAX Systems Programmer goathunter@WKUVX1.WKU.EDU Western Kentucky University Academic Computing, STH 226 (502) 745-5251 Bowling Green, KY 42101 =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Fri, 01 Apr 1994 01:15:30 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 00:11:47 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097C47C.2C4F6AA0.28128@Data.Basix.COM> Subject: RE: How long should e-mail take to arrive? gilliam@alpha.hendrix.edu (Dan Gilliam) wrote: > Can anyone give me a ballpark figure for how long delivery of an e-mail > message to another site ought to take, on average? If a user tells me "It > took an hour for my message to get to so-and-so", should I care? I realize > this may be a difficult question to answer precisely. An hour is ALWAYS reasonable, even for EMail between directly-connected Internet sites, though "many" messages will arrive within minutes. Problem is that one end or the other might be "otherwise busy" and not complete the initial connection, and there's a host of other reasons for a short (hour or so) delay in delivery. Now, if the site is a UUCP or non-Internet site, delays of DAYS are not entirely unusual. Some site along the way accepts the message and often waits for the receiving site to dial in and receive their mail. Sometimes a remote site only dials in once a day, so a message sent in the morning doesn't arrive at the remote site until late that evening, and the remote user doesn't get it until that following morning. Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Adjunct Faculty, East Campus, RHarwood@Data.Basix.COM | Info@Data.Basix.COM | Pima Community College ================================================================================ Archive-Date: Fri, 01 Apr 1994 01:43:31 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 09:39:29 MET_DST From: "Jean-Louis Oneto (+33) 93.40.53.80" Reply-To: MX-List@WKUVX1.WKU.EDU To: Mx-List@WKUVX1.WKU.EDU CC: oneto@ocar01.OBS-AZUR.fr Message-ID: <0097C4CB.7A513DFF.3391@ocar01.OBS-AZUR.fr> Subject: Lists management commands "enhancements" suggestions Date sent: 1-APR-1994 09:09:15 MET Hi net ! First of all, I would like to thanks all the people developping and supporting MX, especially Mat and Hunter, since I think it's one of best piece of software I know, in both commercial and public domain. Recently I had problem with a bug in the SMTP agent of Multinet 3.2, which is corrected in recents versions, but wasn't able to get a version up-to-date from the almost inexistant support in France : I installed MX, the problem is gone, and I got all the listserv support that I needed ! A lot of people making gold out of "bugware" should have a look at MX, it's documentation, and its collective support ! I'm using MX 3.3, Multinet 3.2, VMS 5.5-2 if that matter, and I would suggest that the behavior of the following commands/procedures be altered (I apologise in advance if some/all of these are already in the MX 4.0 release...) : 1) from MCP, I discovered that the modify list/prot=... _doesn't_change_ the protection of the file associated with the list, i.e. you have to issue both MCP and DCL commands to change effectively the protection of a Mailing List. It would be great that the MCP command take care also of th RMS protections. 2) I would like an option in MLF_CONFIG.com to define VMSMail aliases for the two adresses associated with a Mailing list (normal & -Request), like : MAIL> set forward/user=liste "mx%""liste""" MAIL> set forward/user=liste-request "mx%""liste-request""" That allows access to the list without the MX% prefix, espacially for users from remote Decnet nodes that do not know that my node is running MX... (OK, I know there is a patch available for that, but I'm always reluctant to apply patches not supported by DEC, just since you need to remember you've done something nonstandard on your system... In fact, it would be really great if DEC modified VMSMail to recognize both Decnet and RFC822 syntaxes !) Thanks a lott in advance, Jean-Louis Oneto OCA-CERGA, Avenue Copernic, 06130 Grasse - FRANCE NSI/Decnet (formely SPAN) : ocar01::oneto (17494::oneto) Internet : oneto@ocar01.obs-azur.fr | Voice : (+33) 93.40.53.80 | Fax : (+33) 93.40.53.33 Transpac : PSI%(+2080)83159713::ONETO / 183159713::ONETO ================================================================================ Archive-Date: Fri, 01 Apr 1994 05:12:18 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 13:07:58 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C4E8.9AA7E6F0.13346@uni-lj.si> Subject: RE: How long should e-mail take to arrive? > Can anyone give me a ballpark figure for how long delivery of an e-mail > message to another site ought to take, on average? If a user tells me "It > took an hour for my message to get to so-and-so", should I care? I realize > this may be a difficult question to answer precisely. I have tried several times: To: @lsuvm.sncc.lsu:rok.vidmar@uni-lj.si (meaning I sent messages to myself across the Atlantic and back) and it allways took less than two minutes. The longest delay I experienced was four months. I believe somewhere on the route messages had been archived for the period. No, I don't care for an hour or two. Regards, Rok ------------ Rok Vidmar RCU, University of Ljubbljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 inet: rok.vidmar@uni-lj.si 61000 Ljubljana tel: (061) 1686-439 <-- Changed! Slovenia fax: (061) 1683-534 <-- Changed! ================================================================================ Archive-Date: Fri, 01 Apr 1994 11:49:35 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 11:45:47 CST From: Kenny Kon Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097C4DD.1F445EE0.12618@bible.acu.edu> Subject: Strip headers for only one mail account One of the users on this system is blind. He uses a screen reader to help him with his work on the VAX. I would like to be able to define a logical to strip the headers (the received lines) for all his incoming mail so that he doesn't have to hear 20 lines worth of nothing to him before he gets to his message. Is there a way to do this? Thanks. Kenny ----- Kenny Kon, Assistant Systems Manager College of Biblical Studies, Abilene Christian University E-Mail: kenny.kon@BIBLE.ACU.EDU, Postmaster@BIBLE.ACU.EDU ================================================================================ Archive-Date: Fri, 01 Apr 1994 12:43:18 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 11:39:30 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097C4DC.3EB1D4C0.28448@Data.Basix.COM> Subject: RE: Strip headers for only one mail account > One of the users on this system is blind. He uses a screen reader to help > him with his work on the VAX. I would like to be able to define a logical > to strip the headers (the received lines) for all his incoming mail so that > he doesn't have to hear 20 lines worth of nothing to him before he gets to > his message. Is there a way to do this? Thanks. Move all the headers to the END of the message for ALL users... they will all appreciate not having to wade through the stuf which only us techies really use. Use the MCP SET LOCAL /HEADER=(TOP=NOALL,BOTTOM=ALL) command followed by MCP RESET. Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Adjunct Faculty, East Campus, RHarwood@Data.Basix.COM | Info@Data.Basix.COM | Pima Community College ================================================================================ Archive-Date: Fri, 01 Apr 1994 13:27:12 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 13:26:57 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C4EB.411E4757.13@ALPHA.WKU.EDU> Subject: MX V4.0 is now available!! Message Exchange (MX) V4.0 is now available. This is a major release that offers a number of enhancements, including a redesigned queueing subsystem and direct support for Wollongong's WIN/TCP and Pathway products. The list of enhancements and bug fixes is included below my sig. The new message queue is a direct-access, sequential file. RMS block I/O is used to access the file, minimizing RMS overhead. In previous versions of MX, as you've seen on this list, keeping the indexed queue file tuned was a constant battle. That will no longer be a problem now. Let me repeat: you *will* need to create a new queue file with this version of MX. It isn't possible to convert the old format to the new, so be sure either your queue is empty or the messages aren't important before installing V4.0. Also, please read the release notes carefully!! ------------------------------------------------------------------------------- HOW TO GET MX V4.0 MX V4.0 can be obtained via anonymous ftp from the following ftp sites: ftp.wku.edu in [.MX] ftp.spc.edu in [.MX.MX040] niord.shsu.edu in [FILESERV.MX040] and [.MX] segate.sunet.se in [.MX] The latter is a temporary (?) mirror set up specifically for European sites. Thanks to Terry Kennedy, George Greenwade, and Eric Thomas for providing their sites. You can also get MX V4.0 via e-mail from FILESERV@WKUVX1.WKU.EDU, FILESERV@NIORD.SHSU.EDU (shortly), and FILESERV@SEGATE.SUNET.SE (for the European sites). If you don't already have Eric LaFranchi's PACKASM utility, I urge you to get it---it'll make assembling the parts a snap. MX V4.0 comes in 60 181-block files. To get MX V4.0, send the following commands in the body of a mail message to one of the FILESERVs listed above: SEND MX040 SEND FILESERV_TOOLS !Needed if you don't have UNZIP and MFTU SEND PACKASM and SEND PACKASM_OBJ_EXE will return PACKASM from WKUVX1 and SEGATE. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ------------------------------------------------------------------------------- 3 New Features and Changes 3.1 New MX Queue File Format The major change in this version of MX is that the MX message queue file has been changed from an indexed file to a sequential file. This change will make a major difference in MX performance. With previous versions of MX, performance quickly degenerated as messages were added to and deleted from the message queue as the index headers in the file became more and more fragmented. With some very active sites, MX couldn't even do CONVERT/RECLAIM passes on the file. With this version, no reclaim passes are needed. The same records within the sequential file are used over and over, resulting in a message file that offers significant performance increases. Note: The new file has a fixed size-the size determines the number of entries that can be in the queue at any given time. THE FILE WILL NOT GROW ON ITS OWN!! You must select a file size large enough to handle your site's requirements. Each entry takes 1 block; to allow for 5,000 entries in the queue, a file size of 5,036 blocks is required. A file that size should be sufficient for most sites. The maximum number of entries is 131,072. New MCP commands QUEUE CREATE, QUEUE EXTEND, QUEUE COMPRESS, QUEUE SYNCHRONIZE, and QUEUE STATISTICS have been added to allow you to manipulate the new queue file. In addition, a number of qualifiers have been added to QUEUE SHOW to let you control the entries displayed. Note: The message queue file has been renamed from SYSTEM_QUEUE.FLQ_CTL to MX_SYSTEM_QUEUE.FLQ_CTL in MX_ FLQ_DIR:. Any automated processes you may have running to do CONVERTs on the message queue file should be disabled, as they will not work with the new format. __________________________________________________________________ 3.2 NETLIB V1.6 MadGoat Software's NETLIB V1.6 is included with MX V4.0. NETLIB V1.6 offers the following enhancements to V1.5: o Wollongong's WIN/TCP and Pathway products are now directly supported by NETLIB. Previous versions of MX supported Pathway using Pathway's UCX emulation. All other products that use NETLIB (NEWSRDR, PACKASM, etc.) can now be used with TWG's products. MX now supports the WIN$TIME_ZONE logical. o For systems running UCX, the system's FQDN is now created by combining UCX$INET_HOST and UCX$INET_ DOMAIN. Previously, NETLIB expected UCX$INET_ HOST to contain the FQDN, which was contrary to Digital's intended use for the logical. Thanks to Matt Madison for the NETLIB updates. __________________________________________________________________ 3.3 MX Installation and Startup Changes o During MX upgrades, the MX installation procedure now automatically determines which MX components should be installed by default, based on the previously installed components. The installer is still given the chance to select additional components or remove those selected. o The MX installation procedure will now prompt the installer for the number of agent processes to be run on the selected nodes. Thanks to Dan Wing. o When upgrading from an older version of MX, the installation procedure will use the existing information in MX_STARTUP_INFO.DAT as the default values for the nodes and numbers for the MX agents. o MX___STARTUP.COM now checks to be sure the user starting MX has sufficient privileges to do so. o MX_START.COM was modified to: o allow as many as 99 instances of an MX agent; o start the MX agents using /UIC=[1,4] to prevent the accidental running of multiple agents from different accounts; o create log files with names that include the iteration of each agent. __________________________________________________________________ 3.4 MX Message Queue Processing Enhancements o A new optional agent, MX FLQ Manager, has been added. You can elect to run a separate MX FLQ Manager process to perform the maintenance on the queue (purging FINished entries, for example), freeing the MX Router process to do only routing. Sites that process a lot of mail may find it beneficial to use the separate process. o The file queue maintenance performed by the MX FLQ Manager and MX Router has been enhanced. When an MX agent dies abnormally (for example, during a system crash) or when a VMS Mail user is sending a message and gets disconnected or STOP/IDed, the entry in- progress at that time is left in the INPROG state in the queue. Under previous versions of MX, such entries had to be marked READY or CANCEL using MCP. The MX Router and MX FLQ Manager now automatically READY or CANCEL, as appropriate, any such entries that are found as part of their normal file queue maintenance. __________________________________________________________________ 3.5 MCP Enhancements o MCP now automatically sorts PATH definitions, eliminating previous problems where PATH definitions would appear after ``*'' PATH, for example. o Some sites using the MX_SITE_NAME_CONVERSION feature have encountered problems sending mail to non-RFC822 compliant mailers (IBM) when the Sender: and From: addresses don't match. To aid those sites, the MCP command SET ROUTER now accepts the qualifier /[NO]OMIT_VMSMAIL_SENDER to control the inclusion of Sender: lines for mail originating from VMS Mail. o New MCP commands QUEUE CREATE, QUEUE EXTEND, QUEUE COMPRESS, QUEUE SYNCHRONIZE, and QUEUE STATISTICS have been added to allow you to manipulate the new queue file. In addition, a number of qualifiers have been added to QUEUE SHOW to let you control the entries displayed. o Copies of all LOCAL delivery error messages can now be forwarded to the local POSTMASTER with the new MCP command SET LOCAL/CC_POSTMASTER. Such messages include those addressed to non-existent local accounts. o The display of the entry size display in MCP SHOW QUEUE/ALL was changed from from 6 digits to 7 digits. __________________________________________________________________ 3.6 MX Local Enhancements o Incoming mail is now delivered with the VMS Mail ``To:'' and ``CC:'' lines containing the addresses from the RFC822 To: and CC: lines. o Incoming MIME QUOTED-PRINTABLE messages are now automatically decoded by MX Local, in addition to BASE64 VMS messages. o The ability to disable local deliveries to users via MM was added with the MCP command SET LOCAL/NOMM_DELIVERY. o The MM delivery code now includes additional access checks. Thanks to Matt Madison. __________________________________________________________________ 3.7 MX MLF Enhancements and Changes o The hardcoded address LISTSERV was removed from MX. Sites still wanting to use it must define an alias using MCP that equates LISTSERV to MXserver. o Following the convention used by the latest version of Eric Thomas's LISTSERV processor, MX now supports -server addresses as synonyms for - request addresses for mailing lists. For example, YYZ-server and YYZ-request are both recognized as list processor addresses for list YYZ. o All outgoing mailing list mail now shows the sender as ``owner-listname''. When mail is received for such an address, it is automatically delivered to the user defined to receive errors for that list (/ERRORS_TO on the MCP command DEFINE LIST). o The ability to strip ``other'' headers from mailing list postings has been added to MX MLF. Stripping the ``other'' headers eliminates lots of garbage in headers, plus it handily gets around problems with return receipts getting requested by Pegasus Mail. Note that this can cause problems with mailing lists that are gatewayed to newsgroups, depending on the headers the gateway software uses to catch duplicate posts. o MX MLF now checks the list of system users when checking access to a file server, allowing users defined as MX system users to to access file servers that are restricted to members of a mailing list. o Mailing lists can now be set to ignore the case of the username portion of all subscriber addresses. The qualifier /[NO]CASE_SENSITIVE was added to the MCP commands DEFINE LIST and MODIFY LIST. __________________________________________________________________ 3.8 MX SMTP Server Enhancements o The MX SMTP server is now more lenient with regard to RCPT TO: addresses. Addresses that do not include the ``@node'' part of the address are now accepted. The local node name, as defined by MX_NODE_NAME, is used to create a valid RFC821 address. Both and are accepted. o The MX SMTP server also now accepts numeric IP addresses enclosed in brackets with the HELO command. Previously, though the mail was accepted, the MX SMTP server could not verify the address. o The process name for the SMTP Server has been changed to ``MX SMTP Server'' so that all MX process names begin with ``MX''. __________________________________________________________________ 3.9 MX SMTP Enhancements o The MX SMTP agent for outgoing mail now accepts generic success and failure responses (codes 2xx and 5xx) from the remote server. Previously, the SMTP transaction was aborted if an unknown response code was received. o The MX SMTP agents now return errors in the LISTSERV-friendly format used by MX Local. o The SMTP accounting log now includes the name of the host to which the message was actually sent (for example, mail exchangers, etc.). __________________________________________________________________ 3.10 MX MAILSHR (VMS Mail interface) Enhancements o The MX VMS Mail interface now checks for the logical MX_SHUTDOWN when a users tries to send mail through MX. If MX_SHUTDOWN is defined /SYSTEM/EXECUTIVE, users will not be allowed to send mail. A message will be displayed indicating that the system manager has temporarily disabled MX. Note that defining MX_SHUTDOWN does not prevent incoming mail from SMTP, etc. o MX V3.2 introduced the ability to resend SMTP files, retaining the original RFC822 headers, using the MAIL command SEND/FOREIGN/TYPE=1. There are two changes to this feature in MX V4.0: o The /TYPE value has been changed to 255 to allow for more options on non-privileged SEND/FOREIGN commands. o In previous versions of MX, the user had to have LOG_IO privilege to resend SMTP files. MX V4.0 now requires that the user hold the MX_FAKE_ RFC822 process rights identifier instead of LOG_ IO. If the user tries to resend an SMTP file and does not hold the identifier, an error message is displayed. o Usage of MX can now be restricted by defining the executive-mode logical MX_RESTRICT_USAGE in the system logical name table (/SYSTEM/EXEC). If the logical is defined, the user must hold the MX_MAIL_ ACCESS process rights identifier in order to send mail using MX. __________________________________________________________________ 3.11 MX SITE o Multiple MX Site Agent processes can now be executed on a single node. __________________________________________________________________ 3.12 Miscellaneous Enhancements o A standalone program, MX_DECODE, has been provided to decode VMS files mailed using BASE64 encoding. MX_DECODE can be used to decode files passed to the MX Site Agent. It should be invoked via a foreign command: $ MX_DECODE :== MX_EXE:MX_DECODE.EXE It accepts two parameters: the input file, which should contain all of the RFC822 headers, and the output file name. o The MAILQUEUE utility now displays an informational message if there are no queued messages from the user. o The MX accounting logs can now be opened for reading when they are open by one or more agents. o The following [CONTRIB] packages have been updated or added: o DIS-TO-MAIL.TXT-Convert .DIS files to MX mailing lists. o DIS-TO-MXALIAS.ZIP-Convert .DIS files to MXALIAS aliases. o MLF_MAINT.ZIP-A mailing list maintenance utility. o MX-NEWS-GATEWAY.ZIP-Programs to gateway between MX and ANU NEWS. Includes a couple of bug fixes. o MX_HELP_FILE.ZIP-Updated VMS Help files for MX. o MX_POST.ZIP-An MX to NEWS gateway for use with NNTP servers. o MX_SAS_REPORTS.ZIP-SAS procedures to generate reports for MX SMTP and LOCAL accounting. o MX_MAILSHR_PATCH.ZIP-Updated MAILSHR ``@'' patch for OpenVMS V6.0 and below. o PATCH_MAILSHR_ON_VMS_N_AXP_1_5.ZIP-MAILSHR ``@'' patch for OpenVMS AXP V1.5. _______________________________________________________ 4 Bug Fixes MX V4.0 provides the following fixes to bugs in V3.3: 1 The documentation for MX V3.3 was produced using VAX DOCUMENT V2.2. A bug in VAX DOCUMENT V2.2 causes revision bars in .TXT files to overwrite the text that was revised. VAX DOCUMENT V2.1 was used to create the documentation for MX V4.0 to make the .TXT files readable again. 2 Fixed memory leak in MCP. 3 Fixed missing underscores in MCP HELP. 4 Disabled bouncing of mail to DISUSERed accounts. Mail is now delivered to those accounts, as per VMS Mail. 5 Fixed generation of year in MM headers. (Matt) 6 Fixed STR$TRIM bug in MX_SITE_IN.B32. 7 Fixed two bugs in MX_JNET that could cause access violations. 8 Fixed erroneous MCP STATUS display that would list other processes also doing MCP STATUS. 9 Fixed missing quotes on LOCAL bounce messages (xx::uu@node is now "xx::uu"@node). 10 Fixed problem with MXalias keeping records locked. 11 Modified MXALIAS to allow addresses containing quotes to be defined. 12 Corrected handling of MX records in MX SMTP. Previously, depending on how the MX records for a host were defined, MX would not ignore records with a higher preference than the system running MX. (In other words, when the system handling a message was one of the mail exchangers for a remote host, it and all systems with a higher preference should have been ignored; previously, only the system handling the message was ignored, leaving the possibility that the message would get handed off to another system with a higher (lower) preference than the current system). (Tom Allebrandi) 13 Fixed bug in handling group addresses in RFC822 headers. The group comment was improperly removed, leaving an invalid RFC822 address. The comment is no longer removed. Thanks to Donald Buczek. 14 Modified MCP to CANCEL both pieces of an entry if the entry scheduled for retry by an agent was cancelled. Previously, the original ROUTER entry was not cancelled, leaving an IN-PROGRESS orphan entry. 15 Added proper locking of the MM.INIT file when checking for MM delivery to a user. 16 Modified MCP to parse filenames for DEFINE LIST so that invalid names are not allowed. 17 Modified MCP to check to make sure rewrite rules include the ``<>''. 18 Fixed a bug in the decoding of BASE64 files in MX Local. MX was not properly handling quotes in the FDL string. 19 Fixed bug in SMTP_SERVER that could cause the server to die if there was an error opening a debug log file. 20 Fixed bug in MX Jnet that would incorrectly rewrite RFC822 headers if the site is running Jnet V3.6+ and has a default route defined instead of maintaining local tables. 21 Fixed placement of MIME headers with regard to TOP and BOTTOM as defined using SET LOCAL. Previously, the MIME headers were always included at the TOP, regardless of the OTHER setting. [End of MX V4.0 release announcement] ================================================================================ Archive-Date: Fri, 01 Apr 1994 14:01:39 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 14:01:22 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C4F0.10140FE8.11@ALPHA.WKU.EDU> Subject: MX V4.0 sources ready Monday Hi. I forgot to mention that the sources for MX V4.0 will be made available on Monday. I haven't had time to package them yet, but will do so first thing Monday. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 01 Apr 1994 16:22:05 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 14:15:01 PST From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C4F1.F80BE2C0.27739@CCVAX.CCS.CSUS.EDU> Subject: In support of Pegasus (was: A "Really Needed" enhancement) "George D. Greenwade" writes: >One item I would LOVE to be able to strip is the da*n: > X-pmrqc: 1 > created by Pegasus Mail requesting receipt notification Not an issue, but... > In the wondrous minds of the people who designed Pegasus Mail... > ...beyond the marvelously simplistic proprietary minds of the PMail people > a shame thhat someone actually spent money to buy something along the > lines of this miscreant mailer software used on quite a few LANs. Excuse me while I stand up for the *sole author* of Pegasus Mail, Mr. David Harris in New Zealand (david@pmail.gen.nz). Pegasus Mail is *not* commercialware - it is totally FREE. If you want you can purchase a manual but you don't really need it. David has written, *by himself*, Pegasus for DOS, Pegsus for Windows, Pegasus for Mac, *plus* the Mercury SMTP mail gateway for Novell (a Netware NLM). All *free*. Yes - *one persson* doing it *for free*. David has a firm understanding of the RFCs and how mailers interact - I cannot say for sure who's wrong in the handling of the return-receipt (actually, yes I can: THE USER!!! It is THE USER'S FAULT for request return-receipt when mailing to a list!!!). If you think David is wrong, I humbly suggest that you politely discuss it with him, but he sure as h*ll doesn't deserve a flaming that his product is defective or inferior. Yes, we run Pegasus here. After evaluating DiVinci, CC:Mail, and QuickMail, pegasus was BY FAR the intelligent choice, COST NOT AN ISSUE. And I repeat, David does it for FREE, he even provides a darn good SMTP gateway FOR FREE, and he does it BY HIMSELF. If he put in one feature that tickles your listserver the wrong way, I do understand the problem. YES, it should be addressed. BUT NOT BY TRASHING DAVID AND HIS PRODUCT. Sorry for the passionate flame. But in the same vein that Matt Madison (original author of MX) and Hunter Goatley (current maintainer) should be constantly patted on the back and congratulated for their outstanding contributions, so should David Harris. John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Fri, 01 Apr 1994 18:14:22 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 16:07:51 PST From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <0097C501.BBA1EEA0.28052@CCVAX.CCS.CSUS.EDU> Subject: Tip for 4.0 upgrade *disclaimer* I haven't read the release notes yet; if this is covered there then my apologies for wasting bandwidth We were at first a little worried about the requirement to create a new queue file under MX 4.0, but have an idea that though we haven't tried it yet, thought might be worth sharing. Our biggest concern is in getting all the outbound messages flushed. We can upgrade in the middle of the night, and lock out incoming and local users, so that's not a big problem. But what about the few messages that always seem to be stuck waiting for delivery to a temporarily-down remote system? How do we aviod them? The likely answer: set a 'route=' statement to point *all* outbound traffic thru another machine that is available to you. Let this other machine worry about trying to deliver the messages, while you peacefully update MX to the latest, greatest version! John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Fri, 01 Apr 1994 19:16:55 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: byron@stimpy.hsc.ucalgary.ca (Byron Draudson) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: VAX: :MX% logical munging To: header? Message-ID: <1994Apr1.131838.1@stimpy.hsc.ucalgary.ca> Date: Fri, 1 Apr 1994 19:18:38 GMT To: MX-List@WKUVX1.WKU.EDU Hi all. I've got a bit of a problem with MX as a foreign protocol for VMSMail. I've got MX(3.3) setup on my mailhost, VAXA. MX is not installed on any other Vaxen on the net. On each Vax, I've defined a logical to point to MX as such: $ define/sys internet "VAXA::MX%" When users on any machine want to send Internet mail, they specify: To: internet::"user@your.domain" or To: internet"user@your.domain" My goal is to provide a consistant way of specifying an address as well as isolating the need to know the mailhost name from the users. My problem is that outgoing mail ends up with a bogus "To:" address. If I specify the destination address as: To: internet::"user@your.domain" The mail gets delivered ok, but the headers show a To: address of To: your.domain@dnet.my.domain When it should be To: user@your.domain I have no rewrite rules defined. When I specify VAXA::MX% as the transport (rather than using the INTERNET logical), the resulting To: header looks correct. How can I change MX's handling of the INTERNET logical? Are there any other alternatives to accomplish what I what to do? Note that I don't really want to install the VMSMail patch that sets MX as the default transport, as there are many machines that are using MX on VAXA that will not allow that patch to be applied. Any help is appreciated. Thanks. :b __ Byron Draudson, Diagnostic Imaging, Foothills Hospital, Calgary,Alberta,Canada DECnet: STIMPY::BYRON Internet: Byron.Draudson@FhHosp.AB.CA 403-670-2442 ================================================================================ Archive-Date: Fri, 01 Apr 1994 22:08:42 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 01 Apr 1994 22:08:02 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C534.0CE72695.1@ALPHA.WKU.EDU> Subject: RE: Tip for 4.0 upgrade "John F. Sandhoff" writes: > >*disclaimer* I haven't read the release notes yet; if this is covered >there then my apologies for wasting bandwidth > It's not, so thanks for posting it! >Our biggest concern is in getting all the outbound messages flushed. We [...] >The likely answer: set a 'route=' statement to point *all* outbound traffic >thru another machine that is available to you. Let this other machine >worry about trying to deliver the messages, while you peacefully update >MX to the latest, greatest version! > That's great! If I had thought of it, I'd have included it in the release notes. Another solution, if you have multiple systems running MX, is to leave one of them running SMTP, etc., with the old queue, while the other systems run V4.0. This is what I did when I first made the change here several months ago. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Sat, 02 Apr 1994 12:42:35 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 2 Apr 94 12:39:12 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Error during install of MX V4.0 To: mx-list@wkuvx1.wku.edu Message-ID: <0097C5ADC01AB960.20200360@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT MXers, I just tried to install MX V4.0 and received the following error... Does anyone have any idea what is wrong and what I need to do to fix it? Many TIA. MX V3.3 is installed, but I do NOT currently have MX running. = The existing queue files are being renamed to an [.OLD] subdirectory = under MX_FLQ_DIR:. You will probably want to delete these files = after the installation is finished. = = Remember that any messages in the old queue will not be processed. = =%MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... =%MCP-E-QCVTFAIL, error creating new system message queue =-RMS-F-ISI, invalid internal stream identifier (ISI) value = = An error occurred creating the MX queue file. Please correct = the problem and use MCP QUEUE CREATE to create the queue. = = = Installation of MX V4.0 completed at 11:59 = thanks for any light that can be shed on this... -- Rick +----------------------------------------------------------------------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: stacks@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | | |--------------------------------------+-------------------------------------| |- They that give up essential liberty to obtain a little temporary safety --| |- deserve neither liberty nor safety -- Benjamen Franklin, 1759 --| ================================================================================ Archive-Date: Sat, 02 Apr 1994 14:24:11 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com (Dan Wing) Subject: Re: VAX: :MX% logical munging To: header? Date: 2 Apr 1994 19:59:36 GMT Message-ID: <2nkir8$n7f@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <1994Apr1.131838.1@stimpy.hsc.ucalgary.ca>, byron@stimpy.hsc.ucalgary.ca (Byron Draudson) writes: >My goal is to provide a consistant way of specifying an address as well as >isolating the need to know the mailhost name from the users. Install MX on all nodes, and use MX's SMTP-over-DECnet -- then you don't need to be concerned about the mail gateway being up or reachable (as each node does its own store-and-forwarding). This gives the ability to do address rewriting per-node and stuff. You'd probably want to create DNS MX records for each VAX, pointing to your mail gateway, too. -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Sat, 02 Apr 1994 14:48:15 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 02 Apr 1994 12:44:53 EST From: Trevor Johnson Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: trevor@hepnsf.csudh.edu Message-ID: <0097C5AE.8B752280.1@hepnsf.csudh.edu> Subject: trouble using SMTP% with MX 4.0 Hi, I recently installed MX 4.0 am having some minor trouble with it. I want the SMTP% and IN% prefixes to be accepted along with MX%. With MX 3.3 I achieved this (kludgily) by just copying mx_exe:mx_mailshr.exe to in_mailshr.exe and smtp_mailshr.exe. Now I am doing it the recommended way, from sylogicals.com: $ DEFINE/SYSTEM/EXEC smtp MX_MAILSHR $ DEFINE/SYSTEM/EXEC in MX_MAILSHR but it doesn't work: MAIL> s To: in%trevor %MAIL-E-ERRACTRNS, error activating transport IN %LIB-E-ACTIMAGE, error activating image HEPNSF$DKB0:[MX.][EXE]MX_MAILSHRP.EXE -SYSTEM-F-SHRIDMISMAT, ident mismatch with shareable image ...until I use the mx% prefix once: MAIL> s To: mx%trevor MX rewrote TREVOR as Subj: Cancel ...after which in% and smtp% will work for the duration of the Mail session. I tried HELP ERROR SHRIDMISMAT and got this: Errors SHRIDMISMAT ident mismatch with shareable image Facility: SYSTEM, VMS System Services Explanation: The global section match found in a shareable image does not correspond with the global section match in the executable image. User Action: Relink the executable image. and did INSTALL LIST, which told me this: [...] DISK$VMS_5.5-1:.EXE DOMAIN_EXPANSION;2 Open Hdr Shar Lnkbl MAILQUEUE;2 Prv MX_FLQ_SHR;2 Open Hdr Shar Lnkbl MX_MAILSHR;2 Open Hdr Shar Lnkbl MX_MAILSHRP;2 Open Hdr Shar Prot Lnkbl MX_MSG;2 Open Hdr Shar Lnkbl MX_SHR;2 Open Hdr Shar Lnkbl [...] I looked in mx_exe: and all the files there are new. Help! ================================================================================ Archive-Date: Sat, 02 Apr 1994 15:06:54 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com (Dan Wing) Subject: Re: trouble using SMTP% with MX 4.0 Date: 2 Apr 1994 20:47:13 GMT Message-ID: <2nklkh$no7@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097C5AE.8B752280.1@hepnsf.csudh.edu>, Trevor Johnson writes: >$ DEFINE/SYSTEM/EXEC smtp MX_MAILSHR >$ DEFINE/SYSTEM/EXEC in MX_MAILSHR > >but it doesn't work: > >MAIL> s > >To: in%trevor > >%MAIL-E-ERRACTRNS, error activating transport IN From the MX Management Guide: 5.1.1 VMS MAIL Protocol Prefix MX by default uses the foreign protocol prefix MX% when interfacing with VMS Mail. You can define alternate foreign protocol prefixes for use with MX, to provide a migration path for users from other mail systems to MX. MX will correctly handle the following prefixes: SMTP%, WINS%, IN%, JNET%, IHMF%, VN%, ST%, INET%, and UUCP%.[1] To set up one of these alternate prefixes in VMS Mail, define the logical name MAIL$PROTOCOL_prefix: $ DEFINE/SYSTEM/EXEC MAIL$PROTOCOL_prefix MX_MAILSHR where prefix is one of the above-mentioned prefixes, without the trailing percent sign. Note that incoming mail from MX will always bear the MX% prefix. If you wish to use another prefix for incoming mail, you can define the logical name MX_ PROTOCOL_PREFIX: $ DEFINE/SYSTEM/EXEC MX_PROTOCOL_PREFIX prefix% where prefix is one of the above-mentioned prefixes, with the trailing percent sign. The default prefix MX% is the recommended prefix. ________________ [1] You should not re-direct the UUCP% prefix to MX if you are using MX with UUCP. Doing so will prevent messages from being delivered to UUCP from MX, since MX uses the UUCP_MAILSHR interface (the same as UUCP% does). -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Sat, 02 Apr 1994 16:40:41 CST Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 02 Apr 1994 16:40:06 CST From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C5CF.674C0592.13@ALPHA.WKU.EDU> Subject: RE: Error during install of MX V4.0 Rick Stacks writes: > >MXers, > >I just tried to install MX V4.0 and received the following error... Does >anyone have any idea what is wrong and what I need to do to fix it? Many >TIA. MX V3.3 is installed, but I do NOT currently have MX running. [...] >=%MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... >=%MCP-E-QCVTFAIL, error creating new system message queue >=-RMS-F-ISI, invalid internal stream identifier (ISI) value >= >= An error occurred creating the MX queue file. Please correct >= the problem and use MCP QUEUE CREATE to create the queue. >= I'm not sure what caused the error, but doing as it says (MCP QUEUE CREATE/MAX=5000) should get you going OK. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Sat, 02 Apr 1994 21:33:57 CST Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Successful upgrade to MX V4.0 Date: 3 Apr 1994 02:59:05 GMT Message-ID: <2nlbdp$t5d@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Hi, I have just completed upgrading from MX V3.3 to MX V4.0. The upgrade went very smoothly! Most questions read the old configuration for the defaults, and made the installation go fairly quickly. Just a note, I've only been running MX for about 5 weeks. The installation took about 15 minutes. I'd like to extend my thanks to Hunter for taking the time to make this so trouble-free, and for providing MX in the first place. Thanks Hunter! (And Matt for the original!) Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Sun, 03 Apr 1994 09:38:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wayne@tachyon.com (Wayne Sewell) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Successful upgrade to MX V4.0 Message-ID: <1994Apr3.074505.1309@tachyon.com> Date: 3 Apr 94 07:45:05 CDT To: MX-List@WKUVX1.WKU.EDU In article <2nlbdp$t5d@anchor.cc.umb.edu>, kismet@trantor.cc.umb.edu (Ted Corning) writes: > Hi, > > I have just completed upgrading from MX V3.3 to MX V4.0. The upgrade went > very smoothly! Most questions read the old configuration for the defaults, > and made the installation go fairly quickly. Just a note, I've only been > running MX for about 5 weeks. > > The installation took about 15 minutes. > My upgrade was just as easy. > I'd like to extend my thanks to Hunter for taking the time to make this so > trouble-free, and for providing MX in the first place. Thanks Hunter! (And > Matt for the original!) Hear, hear! It's the best PD software I have (and better than a lot of store-bought packages). -- ============================================================================== Wayne Sewell |INET: wayne@tachyon.com Tachyon Software Consulting |UUCP: uupsi!uupsi6!tachyon!wayne P. O. Box 550937, Dallas TX 75355-0937 |Voice: (214)-553-9760, Fax: -553-0077 ============================================================================= From Monty Python:"NOBODY expects the Spanish Inquisition!" ================================================================================ Archive-Date: Mon, 04 Apr 1994 06:09:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 4 Apr 94 14:04 JST From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 To: MX-List@WKUVX1.WKU.EDU Message-ID: <38B4059E27DF400322@HADASSAH.BITNET> > >Rick Stacks writes: >> >>MXers, >> >>I just tried to install MX V4.0 and received the following error... Does >>anyone have any idea what is wrong and what I need to do to fix it? Many >>TIA. MX V3.3 is installed, but I do NOT currently have MX running. >[...] >>=%MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... >>=%MCP-E-QCVTFAIL, error creating new system message queue >>=-RMS-F-ISI, invalid internal stream identifier (ISI) value >>= >>= An error occurred creating the MX queue file. Please correct >>= the problem and use MCP QUEUE CREATE to create the queue. >>= >I'm not sure what caused the error, but doing as it says (MCP QUEUE >CREATE/MAX=5000) should get you going OK. > >Hunter >------ >Hunter Goatley, VMS Systems Programmer, Western Kentucky University >goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) > hi. I came (and overcame ..) the same error. In my case, I found that the VMSINSTAL had gone thru the MX logicals and had MX logicals at both the system and process level. This not only generated the error reported by Rick, but prevented using the MCP. To trace it further, it seems that this i-logical situation prevented the instal-removal of FLQ_SHR. I solved it by: log off, and relogin to have only system level logicals (mx) go into instal and remove by hand the mx images. @sys$startup:mx_startup mcp que create/max Bye and good luck Najman Najman@hadassah.bitnet ================================================================================ Archive-Date: Mon, 04 Apr 1994 08:09:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 04 Apr 1994 08:56:52 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: kenny.kon@BIBLE.ACU.EDU CC: mx-list@wku.edu Message-ID: <0097C721.05C5B400.7825@swdev.si.com> Subject: RE: Strip headers for only one mail account Kenny Kon (kenny.kon@BIBLE.ACU.EDU) writes: >One of the users on this system is blind. He uses a screen reader to help >him with his work on the VAX. I would like to be able to define a logical >to strip the headers (the received lines) for all his incoming mail so that >he doesn't have to hear 20 lines worth of nothing to him before he gets to >his message. Is there a way to do this? Thanks. As one writer pointed out, you can move the headers to the bottom of the message (or eliminate them altogether) for everyone using MCP. However, if you want to retain the headers for most people, but eliminate them for specific individuals, you can pick up a copy of DELIVER from ftp.spc.edu:[.macro32.savesets] and other FTP sites. This allows you to process your incoming mail any way you please, altering it in any way you please. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Mon, 04 Apr 1994 12:34:54 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 04 Apr 1994 11:31:15 CST From: Kenny Kon Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C736.970A38E0.14344@bible.acu.edu> Subject: RE: Strip headers for only one mail account >> One of the users on this system is blind. He uses a screen reader to help >> him with his work on the VAX. I would like to be able to define a logical >> to strip the headers (the received lines) for all his incoming mail so that >> he doesn't have to hear 20 lines worth of nothing to him before he gets to >> his message. Is there a way to do this? Thanks. > >Move all the headers to the END of the message for ALL users... they will all >appreciate not having to wade through the stuf which only us techies really >use. Use the MCP SET LOCAL /HEADER=(TOP=NOALL,BOTTOM=ALL) command followed by >MCP RESET. Thanks for the response to my question. I tried it out and several of the users are very pleased. However 2 users who use popmail have complained that the headers at the bottom are messing their systems up. Can anyone with knowledge of popmail please explain the problem. Thanks. Kenny ----- Kenny Kon, Assistant Systems Manager College of Biblical Studies, Abilene Christian University E-Mail: kenny.kon@BIBLE.ACU.EDU, Postmaster@BIBLE.ACU.EDU ================================================================================ Archive-Date: Mon, 04 Apr 1994 14:21:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 4 Apr 94 14:14:38 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 To: mx-list@wkuvx1.wku.edu Message-ID: <0097C74D6A017A40.20200785@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > >> >>Rick Stacks writes: >>> >>>MXers, >>> >>>I just tried to install MX V4.0 and received the following error... Does >>[...] >>>=%MCP-I-QNEWQFL, creating new system message queue file for 5000 entries.... >>>=%MCP-E-QCVTFAIL, error creating new system message queue >>>=-RMS-F-ISI, invalid internal stream identifier (ISI) value >>>= >>>= An error occurred creating the MX queue file. Please correct >>>= the problem and use MCP QUEUE CREATE to create the queue. >>>= Hunter Goatley writes: >>I'm not sure what caused the error, but doing as it says (MCP QUEUE >>CREATE/MAX=5000) should get you going OK. >> >>Hunter >>------ >> > "Najman Kahana. Ext:7313" writes: > >hi. > I came (and overcame ..) the same error. > In my case, I found that the VMSINSTAL had gone thru the MX logicals >and had MX logicals at both the system and process level. This not only >generated the error reported by Rick, but prevented using the MCP. > To trace it further, it seems that this i-logical situation prevented >the instal-removal of FLQ_SHR. > > I solved it by: > log off, and relogin to have only system level logicals (mx) > go into instal and remove by hand the mx images. > @sys$startup:mx_startup > mcp que create/max > >Bye and good luck > >Najman >Najman@hadassah.bitnet Thanks so much for the replies... I intend to try what Najman and Hunter have suggested (probably this weekend). -- Rick +----------------------------------------------------------------------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: stacks@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | | |--------------------------------------+-------------------------------------| |- They that give up essential liberty to obtain a little temporary safety --| |- deserve neither liberty nor safety -- Benjamen Franklin, 1759 --| ================================================================================ Archive-Date: Mon, 04 Apr 1994 15:05:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 04 Apr 1994 15:03:38 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C754.42180308.7@ALPHA.WKU.EDU> Subject: MX V4.0 sources The sources for MX V4.0 are now available on ftp.wku.edu, segate.sunet.se (for European sites), and ftp.spc.edu. I think everything's all there.... They're also available from FILESERV@WKUVX1.WKU.EDU (SEND MX040_SRC). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 04 Apr 1994 15:48:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 04 Apr 1994 15:46:53 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C75A.4CE86362.17@ALPHA.WKU.EDU> Subject: Another ftp site for MX John Sandhoff has provided one of his systems as a Western U.S. mirror for the MX V4.0 files. You can find them on ftp.csus.edu in pub/mx. Thanks, John! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 04 Apr 1994 19:40:56 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: mdlcpgs@lhn.gns.cri.nz Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX without Date: Tue, 5 Apr 94 11:48:21 +1200 Message-ID: <2nq917$h5a@st-james.comp.vuw.ac.nz> To: MX-List@WKUVX1.WKU.EDU I have installed MX 3.3 on a system with CMUTEK 6.6.5a but havent been able to get it so actually send any mail yet. (everything sits READY in the queue). One possible problem is lack of a Domain Name server. Relying on NAMRES and a HOSTS.TXT file. Can MX SMTP use this mechanism? Phil ================================================================================ Archive-Date: Tue, 05 Apr 1994 01:29:47 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: MX without Date: 5 Apr 1994 06:22:01 GMT Message-ID: <2nr029$5ne@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2nq917$h5a@st-james.comp.vuw.ac.nz>, mdlcpgs@lhn.gns.cri.nz writes: =I have installed MX 3.3 on a system with CMUTEK 6.6.5a but havent been able =to get it so actually send any mail yet. (everything sits READY in the queue). = =One possible problem is lack of a Domain Name server. Relying on NAMRES =and a HOSTS.TXT file. Can MX SMTP use this mechanism? Yes. First: 1) Make sure the appropriate MX processes are running; 2) Define the appropriate logicals (you don't tell us what the queue entries actually are; you've obviously figured out how to use MCP to examine the queue. What led you to believe that the detailed information it gives you is irrelevant to your problem?) to enable debugging (it sounds as if you need to use MX_ROUTER_DEBUG and/or MX_SMTP_DEBUG), and get log files. 3) Post the output from the command: $ MCR MX_EXE:MCP SHOW ALL the queue information for a job that's not being delivered, and the log file[s] associated with that entry. Sheesh! You'd think that anybody who'd installed MX would have read the manual sufficiently to know enough to do the above. Some people seem to be driven to further expand the bounds of known idiocy, though. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Tue, 05 Apr 1994 12:16:42 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 05 Apr 1994 13:11:46 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mdlcpgs@lhn.gns.cri.nz, hardis@garnet.nist.gov Message-ID: <0097C80D.CC2DE940.8184@garnet.nist.gov> Subject: RE: MX without > I have installed MX 3.3 on a system with CMUTEK 6.6.5a but havent been > able to get it so actually send any mail yet. (everything sits READY in the > queue). Is the MX SMTP agent running? Or does it die immediately? If it dies immediately, in the IP_STARTUP.COM file, did you define the INTERNET_HOST_NAME (and uncomment the line)? - Jonathan ================================================================================ Archive-Date: Wed, 06 Apr 1994 03:10:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 05 Apr 1994 13:11:46 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mdlcpgs@lhn.gns.cri.nz, hardis@garnet.nist.gov Message-ID: <0097C80D.CC2DE940.8184@garnet.nist.gov> Subject: RE: MX without > I have installed MX 3.3 on a system with CMUTEK 6.6.5a but havent been > able to get it so actually send any mail yet. (everything sits READY in the > queue). Is the MX SMTP agent running? Or does it die immediately? If it dies immediately, in the IP_STARTUP.COM file, did you define the INTERNET_HOST_NAME (and uncomment the line)? - Jonathan ================================================================================ Archive-Date: Wed, 06 Apr 1994 07:30:54 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 08:27:11 EDT From: Stuart Cohnen Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C8AF.35210EE0.5@RUVMS2.ROCKEFELLER.EDU> Subject: User Restrictions 1) Got the upgrade to MX 4.0 with even breaking a sweat. Great job. Thanks guys! 2) Now for the question. The rationale behind this is quick long, but this is what I need to do. I would like to restrict a user from sending mail to mx%consult@popserver.mydomain.edu , but allow him to send mail to anyone else. Alternativally, this account should not receive mail from "consult@popserver but the mail to just forward it the postmaster Any ideas out there? Thanks SYS$MANAGER:[Stuart] +-----------------------------------------------+ |Stuart Cohnen | |Manager of Engineering and Technical Services | |The Rockefeller University/Computing Services | |1230 York Avenue | |New York, NY 10021 | |Voice: (212) 327-7509 Fax:(212) 327-8712 | | INTERNET COHNEN@ROCKVAX.ROCKEFELLER.EDU | | HEPNET ROCKUP::COHNEN | +-----------------------------------------------+ ================================================================================ Archive-Date: Wed, 06 Apr 1994 11:12:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 09:08:24 PST From: robert@dis.ucsf.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C8B4.F7024A60.10739@dis.ucsf.edu> Subject: RE: User Restrictions How about putting DEFINE "CONSULT@POPSERVER.MYDOMAIN.EDU" SYSTEM in the user's login.com? In my tests that directed all mail to that username to the system account. Of course, if the user has access to change her login.com file or redefine logicals this won't be reliable. The user would need to be locked into a menu in a captive account. Robert Weiner Manager, Development Information Systems robert@dis.ucsf.edu University of California, San Francisco > From: MX%"MX-List@WKUVX1.WKU.EDU" 6-APR-1994 06:56:37.49 > Subj: User Restrictions > > 2) Now for the question. The rationale behind this is quick long, but this is > what I need to do. > > I would like to restrict a user from sending mail to > mx%consult@popserver.mydomain.edu , but allow him to send mail to anyone else. > Alternativally, this account should not receive mail from "consult@popserver but > the mail to just forward it the postmaster > > Any ideas out there? > > Thanks > > SYS$MANAGER:[Stuart] > > +-----------------------------------------------+ > |Stuart Cohnen | > |Manager of Engineering and Technical Services | > |The Rockefeller University/Computing Services | > |1230 York Avenue | > |New York, NY 10021 | > |Voice: (212) 327-7509 Fax:(212) 327-8712 | > | INTERNET COHNEN@ROCKVAX.ROCKEFELLER.EDU | > | HEPNET ROCKUP::COHNEN | > +-----------------------------------------------+ > ================================================================================ Archive-Date: Wed, 06 Apr 1994 12:44:47 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) Subject: Re: Error during install of MX V4.0 Date: 6 Apr 1994 17:32:22 GMT Message-ID: <2nurn6$e69@jac.zko.dec.com> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Yeah, something's definitely hosed somewhere. I was doing a virgin install of 4.0 and got the RMS-F-ISI error during installation and then when trying to create the queue by hand (500 entries). I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, then create the queue. Didn't have time to track it down further. -- Jeff Needle Internet: needle@zk3.dec.com Unix Software Group Phone: 603-881-6199 Technology Partnerships -- -- Jeff Needle Internet: needle@zk3.dec.com Unix Software Group Phone: 603-881-6199 Technology Partnerships ================================================================================ Archive-Date: Wed, 06 Apr 1994 12:51:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 10:48:16 PDT From: digital dave Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: goppelt@SCFE.CHINALAKE.NAVY.MIL Message-ID: <0097C8C2.EA396670.61@SCFE.CHINALAKE.NAVY.MIL> Subject: MX V4.0 LOCAL process dying on AXP Does anybody know if there is a patch available from Digital to plug the memory leak in the MAILSHR routines for AXP? A while ago I applied a mandatory update kit and the MX Local process kept dying on the AXP. After posting this problem to this group, a few people suggested reinstalling the old MAILSHR and MAILSHRP programs. That did the trick. I've since updated MX to V4.0. Now my Local processes are dying with error status 1C278034 (which I cannot resolve). I tried installing the new MAILSHR{P} routines and reinstalling the MX AXP executables, but same problem. Any one else see this problem? I can provide more information if I you could tell me what to look for... dave -- David S. Goppelt Internet: goppelt@scfe.chinalake.navy.mil ================================================================================ Archive-Date: Wed, 06 Apr 1994 13:04:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 13:04:04 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C8D5.E30D2F72.4@ALPHA.WKU.EDU> Subject: Re: Error during install of MX V4.0 jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) writes: > >Yeah, something's definitely hosed somewhere. I was doing a virgin >install of 4.0 and got the RMS-F-ISI error during installation and then >when trying to create the queue by hand (500 entries). > >I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, >then create the queue. > >Didn't have time to track it down further. The process logicals were added to correct another problem. I would guess that it's because the new shareable image isn't getting INSTALLed right by VMSINSTAL or something. What I don't get is why it seems to work OK for most people (including all the MX beta sites). Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 06 Apr 1994 13:34:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 13:33:43 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097C8DA.07A4B0BD.5@ALPHA.WKU.EDU> Subject: RE: MX V4.0 LOCAL process dying on AXP digital dave writes: > >Does anybody know if there is a patch available from Digital to plug the memory >leak in the MAILSHR routines for AXP? A while ago I applied a mandatory update >kit and the MX Local process kept dying on the AXP. After posting this problem >to this group, a few people suggested reinstalling the old MAILSHR and MAILSHRP >programs. That did the trick. > As far as I know, there is no such patch, but the problem appears to have been resolved in T6.1-FT4. >I've since updated MX to V4.0. Now my Local processes are dying with error >status 1C278034 (which I cannot resolve). I tried installing the new >MAILSHR{P} routines and reinstalling the MX AXP executables, but same problem. > That's MX__MEMALLOC . How often does this happen? AXP$ set message mx_msg AXP$ write sys$output f$message(%xc278034) %MX-F-MEMALLOC, error allocating memory from zone !AS AXP$ >Any one else see this problem? > Not with V4.0, I think. >I can provide more information if I you could tell me what to look for... > Beats me. ;-) I'd guess that it's the callable mail memory leak, but it could be something in MX (although I've had no problems on V1.5). If it continues happening, I could try to supply you with a /DEBUG version of MX_LOCAL to run on a terminal to pinpoint just where it's happening. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 06 Apr 1994 15:11:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 13:07:35 PDT From: digital dave Reply-To: MX-List@WKUVX1.WKU.EDU To: goathunter@ALPHA.WKU.EDU CC: MX-List@WKUVX1.WKU.EDU, goppelt@SCFE.CHINALAKE.NAVY.MIL Message-ID: <0097C8D6.60B9B990.41@SCFE.CHINALAKE.NAVY.MIL> Subject: Re: MX V4.0 LOCAL process dying on AXP > That's MX__MEMALLOC . How > often does this happen? Fairly often. Each process stays up for only about 30-40 minutes. After they die the message entry stays at "INP". READY the entry and it gets delivered fine (either by a VAX process or a newly created or "backup" AXP process). Also, as I was typing this message, 2 out of 3 of the SMTP processes have just exited with status 1000000C (that one I know. ;-) ) on the AXP. And the single MX_SMTP on the VAX also died just after I "readied" a couple of the stuck "INP" entries. Help! :-0 Our MX environment is a APX 4000-600 machine (V1.5-1H1) with a VAX 8600 and 6620 (both at V5.5-2). The 8600 also runs MX, the 6620 does not. The VAXes are running UCX V2.0D and the AXP has UCX V3.0. I've started 3 MX_LOCAL processes, 3 MX_ROUTER, and 3 MX_SMTP processes. (Because we process a lot of mail and I thought it was neat that V4.0 could do that. ;-) ) The previous incarnation of this problem just happened to the MX_LOCAL process. But this is the first time I've seen the SMTP process die. And on the VAX too. dave -- David S. Goppelt Internet: goppelt@scfe.chinalake.navy.mil ================================================================================ Archive-Date: Wed, 06 Apr 1994 15:26:36 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 15:25:12 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C8E9.9A3F7DC7.26@ALPHA.WKU.EDU> Subject: Re: MX V4.0 LOCAL process dying on AXP digital dave writes: > >> That's MX__MEMALLOC . How >> often does this happen? > >Fairly often. Each process stays up for only about 30-40 minutes. After they >die the message entry stays at "INP". READY the entry and it gets delivered >fine (either by a VAX process or a newly created or "backup" AXP process). > >Also, as I was typing this message, 2 out of 3 of the SMTP processes have just >exited with status 1000000C (that one I know. ;-) ) on the AXP. And the single >MX_SMTP on the VAX also died just after I "readied" a couple of the stuck "INP" >entries. Help! :-0 > ??? Don't know what would cause that. How about enabling DEBUG on the SMTP processes; SET FILE/VERS=10 or something so that you don't get overwhelmed with logs. >Our MX environment is a APX 4000-600 machine (V1.5-1H1) I'll bet that that's the LOCAL problem. I'll bet that V1.5-1H1 includes the same files as the AXPMUP02 security patch. Do you have plain V1.5 MAILSHR.EXE around anywhere? If so, install that, and I'll bet your problems go away. >The previous incarnation of this problem just happened to the MX_LOCAL >process. But this is the first time I've seen the SMTP process die. And on >the VAX too. > That's strange---sounds like they got something they weren't expecting, but I can't imagine what. Start 'em up again with debug and let me know what happens. Actually, READY the INP entry and the debug log should show the problem right away, whatever it might be.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 06 Apr 1994 15:27:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 22:22:48 +0100 (CET) From: "Niek van Breederode, TNO Voeding" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: MX V4.0 LOCAL process dying on AXP To: MX-List@WKUVX1.WKU.EDU CC: breederode@voeding.TNO.NL Message-ID: <0097C923.F10230C0.1@hvva01.voeding.tno.nl> Content-Transfer-Encoding: 7BIT Hello, Hunter Goatley, writes: > > digital dave writes: > > > >Does anybody know if there is a patch available from Digital to plug the memory > >leak in the MAILSHR routines for AXP? A while ago I applied a mandatory update > >kit and the MX Local process kept dying on the AXP. After posting this problem > >to this group, a few people suggested reinstalling the old MAILSHR and MAILSHRP > >programs. That did the trick. > > > As far as I know, there is no such patch, but the problem appears to > have been resolved in T6.1-FT4. > > >I've since updated MX to V4.0. Now my Local processes are dying with error > >status 1C278034 (which I cannot resolve). I tried installing the new > >MAILSHR{P} routines and reinstalling the MX AXP executables, but same problem. > > > That's MX__MEMALLOC . How > often does this happen? > > AXP$ set message mx_msg > AXP$ write sys$output f$message(%xc278034) > %MX-F-MEMALLOC, error allocating memory from zone !AS > AXP$ > > >Any one else see this problem? > > > Not with V4.0, I think. Yes, I have the same problem. I'm using MX for a couple of weeks now and last weekend I installed MX V4.0. Things improved when I installed 2 local agents in stead of one. With only one agent the local agents died three or four times a dail, with two agents it only happens once a day. I'm running in a mixed environment of VAX VMS 5.5-2 and AXP VMS 1.5. All the agents are running on the AXP. Where can I find the status code? > > >I can provide more information if I you could tell me what to look for... > > > Beats me. ;-) I'd guess that it's the callable mail memory leak, but > it could be something in MX (although I've had no problems on V1.5). > If it continues happening, I could try to supply you with a /DEBUG > version of MX_LOCAL to run on a terminal to pinpoint just where it's > happening. > > Hunter > ------ > Hunter Goatley, VMS Systems Programmer, Western Kentucky University > goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) -- Niek ----------------------------------------------------------------------------- Niek van Breederode tel: +31 3404 44258 TNO Voeding fax: +31 3404 57224 breederode@voeding.tno.nl ----------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 06 Apr 1994 16:19:34 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 Date: 6 Apr 1994 20:57:04 GMT Message-ID: <2nv7n0$9i6@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Hunter Goatley, WKU (goathunter@ALPHA.WKU.EDU) wrote: : jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) writes: : > : >Yeah, something's definitely hosed somewhere. I was doing a virgin : >install of 4.0 and got the RMS-F-ISI error during installation and then : >when trying to create the queue by hand (500 entries). : > : >I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, : >then create the queue. : > : >Didn't have time to track it down further. : The process logicals were added to correct another problem. I would : guess that it's because the new shareable image isn't getting : INSTALLed right by VMSINSTAL or something. What I don't get is why it : seems to work OK for most people (including all the MX beta sites). : Hunter : ------ : Hunter Goatley, VMS Systems Programmer, Western Kentucky University : goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) I've run into similar error messages (RMS-F-ISI) with normal RMS operations (DCL COPY and BACKUP) on some of the larger disks (RA90/RA92). I seem to recall that it had something to do with some of the higher-numbered blocks. Sometimes re-trying the same operation works fine. Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Wed, 06 Apr 1994 17:44:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 06 Apr 1994 17:38:13 EDT From: Chris Olive Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: olive@sgi.siemens.com Message-ID: <0097C8FC.2F255A80.7@sgi.siemens.com> Subject: Re: MX V4.0 LOCAL process dying on AXP In article <0097C8E9.9A3F7DC7.26@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: >I'll bet that that's the LOCAL problem. I'll bet that V1.5-1H1 >includes the same files as the AXPMUP02 security patch. Yep Chris _______________________________________________________________________________ ___ ___ ___ _ _ ___ _ _ ___ /___ | |__ |\ /| |__ |\ | /___ Chris Olive, VMS Systems Consultant ___/ _|_ |___ | Y | |___ | \| ___/ Internet: olive@sgi.siemens.com Medical Systems, Inc. Voice: 708.304.7793 2501 N. Barrington Road. FAX: 708.304.7704 Hoffman Estates, IL 60195 CompuServe: 73740,1636 _______________________________________________________________________________ ================================================================================ Archive-Date: Wed, 06 Apr 1994 19:03:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: MX V4.0 LOCAL process dying on AXP Date: 6 Apr 1994 23:54:51 GMT Message-ID: <2nvi4b$m5i@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097C8C2.EA396670.61@SCFE.CHINALAKE.NAVY.MIL>, digital dave writes: =I've since updated MX to V4.0. Now my Local processes are dying with error =status 1C278034 (which I cannot resolve). $ SET MESSAGE MX_MSG $ WRITE SYS$OUTPUT F$MESSAGE(%X1C278034) %MX-F-MEMALLOC, error allocating memory from zone !AS -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 06 Apr 1994 19:21:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: RE: MX V4.0 LOCAL process dying on AXP Date: 7 Apr 1994 00:02:53 GMT Message-ID: <2nvijd$m5i@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097C923.F10230C0.1@hvva01.voeding.tno.nl>, "Niek van Breederode, TNO Voeding" writes: => AXP$ set message mx_msg => AXP$ write sys$output f$message(%xc278034) => %MX-F-MEMALLOC, error allocating memory from zone !AS => AXP$ => => >Any one else see this problem? => > => Not with V4.0, I think. = =Yes, I have the same problem. I'm using MX for a couple of weeks now and =last weekend I installed MX V4.0. =Things improved when I installed 2 local agents in stead of one. With only =one agent the local agents died three or four times a dail, with two agents =it only happens once a day. I'm running in a mixed environment of VAX VMS =5.5-2 and AXP VMS 1.5. All the agents are running on the AXP. = =Where can I find the status code? In the log files. =breederode@voeding.tno.nl =----------------------------------------------------------------------------- -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 06 Apr 1994 22:12:02 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: Summary: MX V4.0 LOCAL process dying on AXP Message-ID: <1994Apr6.153727.173@scff.chinalake.navy.mil> From: goppelt@scfe.chinalake.navy.mil (digital dave) Reply-To: MX-List@WKUVX1.WKU.EDU Date: 6 Apr 94 15:37:27 PST To: MX-List@WKUVX1.WKU.EDU Thanks to Hunter for quickly figuring out this problem. There were actually two problems. The MX_LOCAL problem on the AXP seemed to be the old memory leak problem in MAILSHR. Installing a V1.5 copy (we're at V1.5-1H1) of MAILSHR and MAILSHRP fixed MX_LOCAL from bombing. As Hunter pointed out to me, to decode the 1C278034 status code, do the following: $ SET MESSAGE MX_MSG $ WRITE SYS$OUTPUT F$MESSAGE(%X1C278034) %MX-F-MEMALLOC, error allocating memory from zone !AS The second problem was my fault. At this site we locally explode a few mailing lists. If a local node is down or unavailable to accept the mail, the messages will bounce to me, the MX Postmaster. I'll save those messages in a POSTMASTER mail folder until the node is available for mail again. Then I'll run a program that I wrote that will extract the messages from that folder, parse them, and use MX_ENTER to place them back into the queue for delivery. Worked great. Problem was, one of the addresses was on the order of : name%site.decnet@scfe.chinalake.navy.mil My routine mistakenly made this into: name"%"site.decnet@scfe.chinalake.navy.mil This cause the MX_ROUTER to hand the message off to MX_SMTP which didn't know what to do with it and exited with an access violation. So, I've got some debugging to do... ;-) I'm grateful to Hunter for his quick response in isolating this problem and his overall tireless efforts on MX. cheers, dave -- David S. Goppelt Internet: goppelt@scfe.chinalake.navy.mil ================================================================================ Archive-Date: Wed, 06 Apr 1994 23:58:38 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wayne@tachyon.com (Wayne Sewell) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 Message-ID: <1994Apr6.193840.1318@tachyon.com> Date: 6 Apr 94 19:38:40 CDT To: MX-List@WKUVX1.WKU.EDU In article <0097C8D5.E30D2F72.4@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: > jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) writes: >> >>Yeah, something's definitely hosed somewhere. I was doing a virgin >>install of 4.0 and got the RMS-F-ISI error during installation and then >>when trying to create the queue by hand (500 entries). >> >>I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, >>then create the queue. >> >>Didn't have time to track it down further. > > The process logicals were added to correct another problem. I would > guess that it's because the new shareable image isn't getting > INSTALLed right by VMSINSTAL or something. What I don't get is why it > seems to work OK for most people (including all the MX beta sites). > > Hunter In my case, I received the error messages during the install, but had no problems creating the queue file manually with mcp. This happened at two different sites, one running version 6 and the other 5.5. -- ============================================================================== Wayne Sewell |INET: wayne@tachyon.com Tachyon Software Consulting |UUCP: uupsi!uupsi6!tachyon!wayne P. O. Box 550937, Dallas TX 75355-0937 |Voice: (214)-553-9760, Fax: -553-0077 ============================================================================= From Monty Python:"NOBODY expects the Spanish Inquisition!" ================================================================================ Archive-Date: Thu, 07 Apr 1994 02:02:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: winter@vision.rs.ch (Martin Winter) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 Message-ID: <1994Apr7.004939.32@vision.rs.ch> Date: 7 Apr 94 00:49:39 +0200 To: MX-List@WKUVX1.WKU.EDU In article <2nurn6$e69@jac.zko.dec.com>, jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) writes: > > Yeah, something's definitely hosed somewhere. I was doing a virgin > install of 4.0 and got the RMS-F-ISI error during installation and then > when trying to create the queue by hand (500 entries). > > I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, > then create the queue. > > Didn't have time to track it down further. > -- > Jeff Needle Internet: needle@zk3.dec.com > Unix Software Group Phone: 603-881-6199 > Technology Partnerships > -- Don't investigate any further... it is just a small bug in the KITINSTAL.COM I found the real case and mailed all the information to Hunter. The error happens only during new Installations of MX 4.0 not upgrades. If you wan't a quick work-around then do $ DEFINE /SYSTEM/EXEC MX_FLQ_DIR SYS$SYSDEVICE:[MX.QUEUE] (assuming that you want to install your queue in the default directory) _BEFORE_ you call VMSINSTAL to install MX 4.0 Don't blame Hunter for this... blame me! (I'm one of the lousy Beta-Tester...) ---------------------------------------------------------------------------- Radio Suisse Ltd, Internet: winter@vision.rs.ch Laupenstrasse 18a postmaster@rs.ch & hostmaster@rs.ch 3008 Bern PSI-Mail: +22846431062::WINTER (public X.25) Switzerland X.400: C=CH; A=ARCOM; P=RS; O=DM; S=WINTER, G=MARTIN ---------------------------------------------------------------------------- ================================================================================ Archive-Date: Thu, 07 Apr 1994 06:57:24 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 7 Apr 94 06:52:36 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Error during install of MX V4.0 To: mx-list@wkuvx1.wku.edu Message-ID: <0097C96B28ECCBC0.20201972@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > >In article <2nurn6$e69@jac.zko.dec.com>, jmn@xyzzy.zk3.dec.com (Jeffrey M. Needle) writes: >> >> Yeah, something's definitely hosed somewhere. I was doing a virgin >> install of 4.0 and got the RMS-F-ISI error during installation and then >> when trying to create the queue by hand (500 entries). >> >> I had to deassign the process logicals, do an @SYS$STARTUP:MX_STARTUP, >> then create the queue. >> >> Didn't have time to track it down further. >> -- >> Jeff Needle Internet: needle@zk3.dec.com >> Unix Software Group Phone: 603-881-6199 >> Technology Partnerships >> -- winter@vision.rs.ch (Martin Winter) writes: > >Don't investigate any further... it is just a small bug in the KITINSTAL.COM >I found the real case and mailed all the information to Hunter. >The error happens only during new Installations of MX 4.0 not upgrades. > I was the one who originally posted this note and mine was NOT a new install, but an upgrade from 3.3 -- I did not have 3.3 running at the time and no logicals were defined, but 3.3 did exist on the disk and was replaced by 4.0 during the install. >If you wan't a quick work-around then do > $ DEFINE /SYSTEM/EXEC MX_FLQ_DIR SYS$SYSDEVICE:[MX.QUEUE] > (assuming that you want to install your queue in the default directory) >_BEFORE_ you call VMSINSTAL to install MX 4.0 > >Don't blame Hunter for this... blame me! (I'm one of the lousy Beta-Tester...) > No point in blaming anyone -- as the saying goes 'stuff happens' or something like that ;-) Thank goodness for mail lists and MX. -- Rick +----------------------------------------------------------------------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: stacks@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | | |--------------------------------------+-------------------------------------| |- They that give up essential liberty to obtain a little temporary safety --| |- deserve neither liberty nor safety -- Benjamen Franklin, 1759 --| ================================================================================ Archive-Date: Thu, 07 Apr 1994 08:58:58 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 07 Apr 1994 08:58:31 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097C97C.BFEE10A4.3@ALPHA.WKU.EDU> Subject: MX V4.0 OK. Thanks to Martin Winter, who correctly figured out what the problem was with the inability to create the queue during the post-install phase, I've come up with the solution I should have used when he first pointed out the initial problem. KITINSTAL.COM now does: $ @SYS$STARTUP:MX_STARTUP LOGICALS before creating the queue file. Duh---now everything is as it should be before it even attempts to create it. I've updated the MX V4.0 distributions everywhere to include this change to KITINSTAL.COM. THIS IS THE ONLY CHANGE IN THE KIT---THERE IS NO NEED TO GET THE ZIP FILE AGAIN. I would have just let it go, but I didn't want brand-new users to keep having the problem---so anybody that picks up from today on won't see it. AGAIN, THAT'S THE ONLY CHANGE THAT WAS MADE. Unfortunately, another bug was brought to my attention. This bug only affects sites using MLF to run mailing lists. One of the changes in MX V4.0 was that lists now go out with "owner-listname" as the Sender: and Errors-To: address. Bounces come back in to owner-listname, which MLF delivers to the /ERRORS_TO address for the "listname" list. All works fine and dandy except from *local* bounces. 8-( If your SMTP agents, for example, can't deliver a message and bounce it back to owner-listname, the bounce message is actually delivered to the SYSTEM_USERS, not the /ERRORS_TO address. The reason is that MLF has always forwarded messages from the local postmaster to the system users---it was never supposed to receive anything from the local postmaster. However, with the owner- change, it can and will receive such messages, only I didn't think of that in time. ;-) This will be fixed in the next release of MX. I don't know if it's severe enough to warrant the trouble of a V4.0-1 release so soon, but I'll probably do one if anything else shows up. Thanks to George Greenwade who spotted the behavior. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Thu, 07 Apr 1994 19:47:58 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: How to get MXserver to ignore signatures? Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Reply-To: MX-List@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 09:15:28 +1000 To: MX-List@WKUVX1.WKU.EDU Somewhere I recall reading that there is a convention (not rfc) for news and email that signatures start with a line consisting only of "-- " i.e., . Is this correct? Would it be possible to have email to the -request address of servers such as mxserver ignore signature lines. This would reduce the number of error messages sent unnecessarily. Iff there is such a convention, then perhaps the automatic signature inclusion routines could (optionally) insert the separator. -- David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Thu, 07 Apr 1994 20:27:15 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: wing@tgv.com (Dan Wing) Subject: Re: How to get MXserver to ignore signatures? Date: 8 Apr 1994 01:10:26 GMT Message-ID: <2o2au2$kj2@news.arc.nasa.gov> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article , bellamy@commerce.uq.edu.au (David Bellamy) writes: >Somewhere I recall reading that there is a convention (not rfc) for news >and email that signatures start with a line consisting only of "-- " i.e., >. Is this correct? > >Would it be possible to have email to the -request address of servers such >as mxserver ignore signature lines. This would reduce the number of error >messages sent unnecessarily. > >Iff there is such a convention, then perhaps the automatic signature >inclusion routines could (optionally) insert the separator. Sure, there's such a convention. But the people that know about it would also know how to prevent their signature from being (automatically) appended to a mail message they send to -request. ... Probably still a good idea to add "-- " as a synonym for the QUIT command. -Dan Wing, wing@tgv.com ================================================================================ Archive-Date: Thu, 07 Apr 1994 22:14:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 07 Apr 1994 20:10:22 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097C9DA.9B598DA0.319@Data.Basix.COM> Subject: Re: How to get MXserver to ignore signatures? > >Somewhere I recall reading that there is a convention (not rfc) for news > >and email that signatures start with a line consisting only of "-- " i.e., > >. Is this correct? > > > >Would it be possible to have email to the -request address of servers such > >as mxserver ignore signature lines. This would reduce the number of error > >messages sent unnecessarily. > > > Sure, there's such a convention. Well, *I* heard it was 5 dashes and NO space... Any other rumors? I don't suppose this is covered in an RFC anywhere, is it? > But the people that know about it would also know how to prevent their > signature from being (automatically) appended to a mail message they send > to -request. > > ... Probably still a good idea to add "-- " as a synonym for the QUIT command. How about ignoring ALL lines after ANY line containing two or more consecutive hyphens?! Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Adjunct Faculty, East Campus, RHarwood@Data.Basix.COM | Info@Data.Basix.COM | Pima Community College ================================================================================ Archive-Date: Fri, 08 Apr 1994 02:19:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: jcarey@cykick.infores.com (Jim Carey) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: MX V4.0 Message-ID: <1994Apr7.223035.107@cykick.infores.com> Date: 7 Apr 94 22:30:35 -0500 To: MX-List@WKUVX1.WKU.EDU In article <0097C97C.BFEE10A4.3@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: > Unfortunately, another bug was brought to my attention. This bug only > affects sites using MLF to run mailing lists. One of the changes in > MX V4.0 was that lists now go out with "owner-listname" as the Sender: > and Errors-To: address. Bounces come back in to owner-listname, which > MLF delivers to the /ERRORS_TO address for the "listname" list. All > works fine and dandy except from *local* bounces. 8-( If your SMTP > agents, for example, can't deliver a message and bounce it back to > owner-listname, the bounce message is actually delivered to the > SYSTEM_USERS, not the /ERRORS_TO address. The reason is that MLF has > always forwarded messages from the local postmaster to the system > users---it was never supposed to receive anything from the local > postmaster. However, with the owner- change, it can and will receive > such messages, only I didn't think of that in time. ;-) Might this explain why my disk was filled up with duplicate copies of a local bounce from my mailing list? I've got a list that I send out in digest form only. I sent a digest out right after upgrading to MX 4.0; two addresses were rejected by the SMTP agent. Details for those who care: The name of the list is "bread". I log on as a user named "bread" to actually post it. System users is set to postmaster, jcarey, and bread. The list is run using the MX digester software, with only the SITE alias set up to receive the non-digested version. Here are the important parts of a "show all": System (privileged) users: "POSTMASTER@CYKICK.INFORES.COM" "JCAREY@CYKICK.INFORES.COM" "BREAD@CYKICK.INFORES.COM" Mailing lists: Name: bread-digest Owner: "BREAD-mgr@CYKICK.INFORES.COM" Reply-to: NOList, Sender Archive: DKA100:[BREAD.ARCHIVE.BREAD-DIGEST] Add message: DKA100:[BREAD]MLIST_ADD_MESSAGE.TXT Remove message: DKA100:[BREAD]MLIST_REMOVE_MESSAGE.TXT Description: Bread Bakers Digest Errors-to: Bread-mgr@cykick.infores.com Return address: bread@cykick.infores.com Strip header: NOReceived, NOOther Private list: No Case sensitive: Yes Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RED,WORLD:RE) Name: bread-tmp Owner: "JCAREY@CYKICK.INFORES.COM" Reply-to: NOList, Sender Forwarded-to-owner message: DKA100:[BREAD]MLIST_FORWARD_MESSAGE.TXT Description: Bread Bakers list (undigested) Errors-to: bread-mgr@cykick.infores.com Strip header: NOReceived, NOOther Private list: No Case sensitive: Yes Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:W) Aliases: LocalName="Postmaster", Address="jcarey@cykick.infores.com" LocalName="POSTMAST", Address="jcarey@cykick.infores.com" LocalName="bread-mgr", Address="jcarey@cykick.infores.com" LocalName="bread-archive-mgr", Address="jcarey@cykick.infores.com" LocalName="bread", Address="bread-tmp@cykick.infores.com" LocalName="bread-request", Address="bread-digest-request@cykick.infores.com" ================================================================================ Archive-Date: Fri, 08 Apr 1994 05:13:50 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 12:09:44 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CA60.A0895CB6.157@uni-lj.si> Subject: RE: MX V4.0 > Unfortunately, another bug was brought to my attention. This bug only > affects sites using MLF to run mailing lists. One of the changes in > MX V4.0 was that lists now go out with "owner-listname" as the Sender: > and Errors-To: address. Bounces come back in to owner-listname, which > MLF delivers to the /ERRORS_TO address for the "listname" list. All > works fine and dandy except from *local* bounces. 8-( If your SMTP > agents, for example, can't deliver a message and bounce it back to > owner-listname, the bounce message is actually delivered to the > SYSTEM_USERS, not the /ERRORS_TO address. ... Exactely, but in my case the bounce was performed 79 times before I succeeded to STOP/ID Local agents which were so busy delivering that they did not notice my MCP SHUTDOWN LOCAL I have 9 SYSTEM_USERS, but I do not have the nerve to find out if 92th message will ever come... The only solution is then to find the offending message, MCP QUEUE CANCEL it, and restart the agents. Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Fri, 08 Apr 1994 07:29:30 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 14:25:43 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CA73.A018B818.16@uni-lj.si> Subject: RE: MX V4.0 Earlier I sent this: > > Unfortunately, another bug was brought to my attention. This bug only > > affects sites using MLF to run mailing lists. One of the changes in > > MX V4.0 was that lists now go out with "owner-listname" as the Sender: > > and Errors-To: address. Bounces come back in to owner-listname, which > > MLF delivers to the /ERRORS_TO address for the "listname" list. All > > works fine and dandy except from *local* bounces. 8-( If your SMTP > > agents, for example, can't deliver a message and bounce it back to > > owner-listname, the bounce message is actually delivered to the > > SYSTEM_USERS, not the /ERRORS_TO address. ... > > Exactely, but in my case the bounce was performed 79 times before I > succeeded to STOP/ID Local agents which were so busy delivering that they > did not notice my MCP SHUTDOWN LOCAL I have 9 SYSTEM_USERS, but I do not > have the nerve to find out if 92th message will ever come... > The only solution is then to find the offending message, MCP QUEUE CANCEL > it, and restart the agents. Well, in fact I did MCP SHUTDOWN MLF too; the bouncing was caused by the fact that one of the SYSTEM_USERS was, in effect, a mailing list too! Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Fri, 08 Apr 1994 07:32:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 07:32:27 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CA39.E4027E18.4@ALPHA.WKU.EDU> Subject: RE: MX V4.0 "Rok Vidmar, RCU Lj." writes: > > Exactely, but in my case the bounce was performed 79 times before I >succeeded to STOP/ID Local agents which were so busy delivering that they >did not notice my MCP SHUTDOWN LOCAL I have 9 SYSTEM_USERS, but I do not >have the nerve to find out if 92th message will ever come... > The only solution is then to find the offending message, MCP QUEUE CANCEL >it, and restart the agents. > Via e-mail with Rok, he found that it was local configuration error that was causing the repeated messages, not the MLF problem mentioned yesterday (though the problem was exploited by the MLF). Jim Carey wrote: > >Might this explain why my disk was filled up with duplicate copies of a local >bounce from my mailing list? I've got a list that I send out in digest form >only. I sent a digest out right after upgrading to MX 4.0; two addresses were >rejected by the SMTP agent. > I would suspect that this is also a local configuration error, exploited by the MLF bug. To find out for sure, you can enable debugging on the MLF and ROUTER. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 08 Apr 1994 07:48:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 08:43:06 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!mx-list@pubs22.si.com Message-ID: <0097CA43.C2D0EA40.12071@swdev.si.com> Subject: RE: How to get MXserver to ignore signatures? David Bellamy (bellamy@commerce.uq.edu.au) writes: >Somewhere I recall reading that there is a convention (not rfc) for news >and email that signatures start with a line consisting only of "-- " i.e., >. Is this correct? > >Would it be possible to have email to the -request address of servers such >as mxserver ignore signature lines. This would reduce the number of error >messages sent unnecessarily. > >Iff there is such a convention, then perhaps the automatic signature >inclusion routines could (optionally) insert the separator. Oh, come on! MX isn't your mother! ;-) Surely if you know you are sending to a -Request or xxserver address (and you do, because _you_ enter the address), then you also know enough to add /NOSIG or QUIT to the end of your message. What's six more little characters? I'd much rather Hunter spends his time adding in _important_ functionality or fixing bugs than worrying about whether you know how to type. Ray Harwood (RHarwood@Data.Basix.COM) writes: >How about ignoring ALL lines after ANY line containing two or more consecutive >hyphens?! How about simply ignoring all lines that aren't a -Request or xxServer command? If it doesn't parse, toss it out, no matter what it contains. -----------------------------+-------------------------------- Brian Tillman | Internet: tillman@swdev.si.com Smiths Industries, Inc. | tillman_brian@si.com 4141 Eastern Ave., MS129 | Hey, I said this stuff myself. Grand Rapids, MI 49518-8727 | My company has no part in it. -----------------------------+-------------------------------- ================================================================================ Archive-Date: Fri, 08 Apr 1994 12:34:59 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 8 Apr 1994 12:55:08 -0400 Message-ID: <9404081655.AA13679@genrad.com> From: dongray@genrad.com (Derek Dongray) Reply-To: MX-List@WKUVX1.WKU.EDU X-MX-Warning: Warning -- Invalid "To" header. To: "mx-list@wkuvx1.wku.edu" CC: Subject: Strange subscription entry and "From:" differs from "Reply-To:" Up until recently, we haven't had any direct mail connections (actually we still haven't ye), so I have not bothered previously to define the node names as FQDNs. After installing MX 4.0, and telling it that the network name was the FQDN, I now get the effect that the "From:" and "Reply-To:" addresses are different. For example... Received: from CD4000.GENRAD.CO.UK by CD4502.genrad.co.uk (MX V4.0 VAX) with SMTP; Fri, 08 Apr 1994 17:47:57 BST Received: by cd4000.genrad.co.uk (MX V4.0 VAX) id 25; Fri, 08 Apr 1994 17:47:54 BST Sender: dongray@cd4000 Date: Fri, 08 Apr 1994 17:47:53 BST From: Derek Dongray Reply-To: dongray@CD4000 To: applications-request@CD4502 Message-ID: <0097CA8F.DDA3E963.25@cd4000.genrad.co.uk> Also the entry on a subscribed list is... "dongray@cd4000" Rather than the expected... Derek Dongray The header problem seems to stem from the difference between the logicals MX_NODE_NAME and MX_VMSMAIL_NAME. "MX_NODE_NAME" = "cd4000.genrad.co.uk" "MX_VMSMAIL_LOCALHOST" = "@cd4000" It seems that the KITINSTAL.COM in MX 4.0 goes to the trouble of retaining any existing value for MX_VMSMAIL_LOCALHOST... ... $ VMI$CALLBACK ASK MX_NODE_NAME "Enter the MX network node name" - "''MX_DEF_MX_NODE'" SM $! $ MX_VMSMAIL_NAME = F$TRNLNM ("MX_VMSMAIL_LOCALHOST") $ IF MX_VMSMAIL_NAME .EQS. "" THEN MX_VMSMAIL_NAME = "@" + MX_NODE_NAME ... I assume to fix the problem I should edit the MX_LOGICALS.DAT file and restart MX, but I don't understand the subscription entries! As a further query, should UCX (2.0E) entries be FQDNs or simple node names? I couldn't find any indication in either the MX or DEC manuals. Derek. ---------------------------------------------------------- Derek Dongray, Systems Manager, GenRad Ltd., Cheshire, UK. E-mail : dongray@genrad.com or Derek.Dongray@GenRad.co.uk PSS : 234261600119::Dongray CompuServe : 70374,2745 ================================================================================ Archive-Date: Fri, 08 Apr 1994 13:29:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 13:27:47 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CA6B.87C5C4BB.13@ALPHA.WKU.EDU> Subject: RE: Strange subscription entry and "From:" differs from "Reply-To:" dongray@genrad.com (Derek Dongray) writes: > >Up until recently, we haven't had any direct mail connections (actually we >still haven't ye), so I have not bothered previously to define the node names >as FQDNs. After installing MX 4.0, and telling it that the network name was the >FQDN, I now get the effect that the "From:" and "Reply-To:" addresses are >different. For example... > [...] >The header problem seems to stem from the difference between the logicals >MX_NODE_NAME and MX_VMSMAIL_NAME. > > "MX_NODE_NAME" = "cd4000.genrad.co.uk" > "MX_VMSMAIL_LOCALHOST" = "@cd4000" > Yes, that's it. >It seems that the KITINSTAL.COM in MX 4.0 goes to the trouble of >retaining any existing value for MX_VMSMAIL_LOCALHOST... > If it's already there, yes. That's intentional, because they could be different. >I assume to fix the problem I should edit the MX_LOGICALS.DAT file >and restart MX, but I don't understand the subscription entries! > Yes, that'll fix it. MX always uses the From: address for subscription requests, not the Reply-To: address. That's done for list security reasons. >As a further query, should UCX (2.0E) entries be FQDNs or simple node >names? I couldn't find any indication in either the MX or DEC manuals. > The new NETLIB lets you specify them either way. Prior to V4.0, it had to be the FQDN for MX to work correctly. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 08 Apr 1994 13:43:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 08 Apr 1994 13:42:55 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097CA6D.A52B59E7.16@ALPHA.WKU.EDU> Subject: Another European ftp site for MX Massimo 'SleepyHead' Ianigro has provided another European ftp site for MX. The system is ftp.ba.cnr.it, the directory is /pub/software/mx. Thanks, Massimo! Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Sun, 10 Apr 1994 03:26:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 10 Apr 94 11:19 JST From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: variable return address To: MX-List@WKUVX1.WKU.EDU Message-ID: <34141842C6BF400291@HADASSAH.BITNET> Hi. I am using MX v4 on a VAX/VMS. I have a need for having multiple (at least 2) return addresses. that is, I want the FROM field to change depending on the TO:. I want the default to be "user@AAA.BITNET" I want to be "user@KKK.CCC" if sending to nodes under my domain. Is there any way to do this ? Thanks Najman Kahana Najman@hadassah.bitnet ================================================================================ Archive-Date: Mon, 11 Apr 1994 01:42:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 08:40:32 +0200 From: Herve Gilibert -CRITeR- Universite de St Etienne Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097CC9E.E6249E85.8236@stroph.univ-st-etienne.fr> Subject: Form oriented interface to VMS-MAIL. Does anybody has writen a screen oriented interface to VMS-MAIL (perhaps with pop-up menus), which could be used on VTxxx terminals ? I need that for occasional users. Thanks in advance. Herve. -- Herve GILIBERT UUUU UUUU CRITeR UUUU UUUU Universite Jean Monnet St-Etienne UUUU UUUU 23, Rue du Dr. P. Michelon UUUU UUUU 42023 ST ETIENNE Cedex 2 UUUU UUUU Tel : 33 77 42 15 79 UUUU UUUU Fax : 33 77 42 15 75 UUUUUUUUUUU RFC822: gilibert@univ-st-etienne.fr UUUUUUUUU ================================================================================ Archive-Date: Mon, 11 Apr 1994 08:46:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 15:27:03 +0300 From: syseng@sukair.cc.uob.bh Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097CCD7.B08A5600.1@sukair.cc.uob.bh> Subject: MX V4.0 Local Process Hi there, I upgraded to MX V4.0 and works fine now, but there is a different To: header format than the last version, now the MX Local process puts the complete user address instead of user ID only, and if the sender is a list it does not put the user ID at all. e.g. From : MX%"user@host.domain" To : MX%"localuser@local.host.domain" and From : MX%"MX-List@WKUVX1.WKU.EDU" To : MX%"MX-List@WKUVX1.WKU.EDU" Did any one saw this before, Is it the new version format or I missed something in installation or configuration ? Thanks in advance. Nader Nasry ================================================================================ Archive-Date: Mon, 11 Apr 1994 08:57:33 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 08:57:15 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CCA1.3C66C7D0.23@ALPHA.WKU.EDU> Subject: RE: MX V4.0 Local Process syseng@sukair.cc.uob.bh writes: > >Hi there, > I upgraded to MX V4.0 and works fine now, but there is a different > To: header format than the last version, now the MX Local process > puts the complete user address instead of user ID only, and if the > sender is a list it does not put the user ID at all. > > e.g. > From : MX%"user@host.domain" > To : MX%"localuser@local.host.domain" > > and > From : MX%"MX-List@WKUVX1.WKU.EDU" > To : MX%"MX-List@WKUVX1.WKU.EDU" > > Did any one saw this before, Is it the new version format or I missed > something in installation or configuration ? > It's new with MX V4.0. It was described in the release notes: 3.6 MX Local Enhancements o Incoming mail is now delivered with the VMS Mail ``To:'' and ``CC:'' lines containing the addresses from the RFC822 To: and CC: lines. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 11 Apr 1994 10:49:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 10:49:02 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097CCB0.DA25C778.27@ALPHA.WKU.EDU> Subject: MX V4.0-1 upgrade is now available An upgrade kit for MX V4.0-1 is now available. MX V4.0-1 offers the following enhancements and bug fixes over MX V4.0: o The MX MLF agent now correctly handles local bounce messages that are forwarded to owner-listname. A bug in MX V4.0 caused such messages to always be delivered to the MX system users instead of the list owners. o The MCP QUEUE READY command will now always notify the target agent that an entry has been marked READY. Previously, only the MX Router was notified when its entries were marked. o A memory leak in MAILQUEUE has been corrected. o The MCP command SHOW VERSION now reports the version as MX V4.0-1. ------------------------------------------------------------------------------- The MX040.ZIP kit has been updated on ftp.spc.edu, segate.sunet.se, and ftp.csus.edu to include the V4.0-1 changes. I assume the others will be once their maintainers read this. 8-) (Thanks!) If you've already installed MX V4.0, an upgrade kit is available on those sites as MX_REV1_UPGRADE040.ZIP. SEND MX_REV1_UPGRADE040 in the body of a mail message to FILESERV@WKUVX1.WKU.EDU will return the upgrade kit in 36 60-block files. MX040_SRC.ZIP will be updated soon. This is the last update planned for V4.0, barring some other major bug. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 11 Apr 1994 15:24:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 14:15:12 CST From: Kenny Kon Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CCCD.A6D2BDA0.21376@bible.acu.edu> Subject: RE: Form oriented interface to VMS-MAIL. >Does anybody has writen a screen oriented interface to VMS-MAIL (perhaps with >pop-up menus), which could be used on VTxxx terminals ? >I need that for occasional users. >Thanks in advance. >Herve. Yehavi Bourvine from Hebrew University has ported PINE over to VMS. You can get a beta copy from VMS.HUJI.AC.IL in the subdirectory [.LOCAL]. Kenny ----- Kenny Kon, Assistant Systems Manager College of Biblical Studies, Abilene Christian University E-Mail: kenny.kon@BIBLE.ACU.EDU, Postmaster@BIBLE.ACU.EDU ================================================================================ Archive-Date: Mon, 11 Apr 1994 19:04:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 11 Apr 1994 16:56:18 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: syssand@CCVAX.CCS.CSUS.EDU Message-ID: <0097CCE4.286F4660.31760@CCVAX.CCS.CSUS.EDU> Subject: re: PINE Mail for VMS Disclaimer: This is off the subject of MX-Mail and followup discussion should be directed to the comp.mail and other applicable groups... For convenience (and enhanced transfer speed!) we have placed the beta release of the Pine Mailer VMS port on ftp.csus.edu. (/pub/cmuip/contrib; you'll also need unzip.exe, see the readme file for how to use it). We have *not* tried compiling it yet and can offer no information as to how good it is. Pine replaces the VMS "user agent" (that is, VMSMail). It interfaces with the MAIL.MAI file, however there are several subtle differences between VMSMail and Pine (Pine does not use the wastebasket folder, for instance, and by default it checks 'inbox' rather than 'newmail' for new messages). However, Pine provides an arguably-much more friendly user interface to Mail. Yehavi Bourvine from Hebrew University is responsible for this port, and it was obtained from VMS.HUJI.AC.IL. John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Tue, 12 Apr 1994 00:26:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 08:16:00 +0300 From: syseng@sukair.cc.uob.bh Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD64.A390AB60.22@sukair.cc.uob.bh> Subject: RE: MX V4.0 Local Process Hi Hunter, Thank you for your reply, this is the message header I received : From: MX%"MX-List@WKUVX1.WKU.EDU" 11-APR-1994 17:20:59.24 To: MX%"MX-List@WKUVX1.WKU.EDU" CC: Subj: RE: MX V4.0 Local Process From: "Hunter Goatley, WKU" To: MX-List@WKUVX1.WKU.EDU Subject: RE: MX V4.0 Local Process Actually I read that Incoming mail is now delivered with the VMS Mail ``To:'' and ``CC:'' lines containing the addresses from the RFC822 To: and CC: lines. But I saw the address format is not simple as you see, Is it better ?. I prefere VMS Mail To: contains the local user ID not the RFC822 format as it is not useful for the user and it confused with the list address as you see. Is it possible to modify the local process to put local user ID instead, if so can you help me doing so, as I have not all the source compilers unless it is written in MACRO. Thanks in advance. Nader Nasry ================================================================================ Archive-Date: Tue, 12 Apr 1994 01:27:15 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: henrym@sacto.mp.usbr.gov Subject: Re: MX V4.0-1 upgrade is now available Message-ID: <0097CD10.1028BB28@sacto.mp.usbr.gov> Date: Tue, 12 Apr 1994 05:10:35 GMT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097CCB0.DA25C778.27@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: >An upgrade kit for MX V4.0-1 is now available. MX V4.0-1 offers the >following enhancements and bug fixes over MX V4.0: > > o The MX MLF agent now correctly handles local bounce > messages that are forwarded to owner-listname. A > bug in MX V4.0 caused such messages to always be > delivered to the MX system users instead of the > list owners. > > o The MCP QUEUE READY command will now always notify > the target agent that an entry has been marked > READY. Previously, only the MX Router was notified > when its entries were marked. > > o A memory leak in MAILQUEUE has been corrected. > > o The MCP command SHOW VERSION now reports the > version as MX V4.0-1. > >------------------------------------------------------------------------------- >The MX040.ZIP kit has been updated on ftp.spc.edu, segate.sunet.se, >and ftp.csus.edu to include the V4.0-1 changes. I assume the others >will be once their maintainers read this. 8-) (Thanks!) > >If you've already installed MX V4.0, an upgrade kit is available on >those sites as MX_REV1_UPGRADE040.ZIP. > >SEND MX_REV1_UPGRADE040 in the body of a mail message to >FILESERV@WKUVX1.WKU.EDU will return the upgrade kit in 36 60-block >files. > >MX040_SRC.ZIP will be updated soon. > >This is the last update planned for V4.0, barring some other major >bug. > >Hunter >------ >Hunter Goatley, VMS Systems Programmer, Western Kentucky University >goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) Now avaliable on SACUSR.MP.USBR.GOV in the [.MX040] directory. -HWM ---------- Henry W. Miller Assistant Systems and Network Manager U.S. Bureau of Reclamation, Mid Pacific Region 2800 Cottage Way MP1130 Sacramento, CA 95825 (916) 978-5108 ================================================================================ Archive-Date: Tue, 12 Apr 1994 04:35:01 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 11:31:47 +0300 (MET-DST) From: Massimo 'SleepyHead' Ianigro Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <940412113147.21400128@astrba.ba.cnr.it> Subject: Re: MX V4.0-1 upgrade is now available ~ In article <0097CCB0.DA25C778.27@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: ~ >An upgrade kit for MX V4.0-1 is now available. MX V4.0-1 offers the ~ >following enhancements and bug fixes over MX V4.0: ~ > ~ > o The MX MLF agent now correctly handles local bounce ~ > messages that are forwarded to owner-listname. A ~ > bug in MX V4.0 caused such messages to always be ~ > delivered to the MX system users instead of the ~ > list owners. ~ > ~ > o The MCP QUEUE READY command will now always notify ~ > the target agent that an entry has been marked ~ > READY. Previously, only the MX Router was notified ~ > when its entries were marked. ~ > ~ > o A memory leak in MAILQUEUE has been corrected. ~ > ~ > o The MCP command SHOW VERSION now reports the ~ > version as MX V4.0-1. ~ > ~ >------------------------------------------------------------------------------- ~ >The MX040.ZIP kit has been updated on ftp.spc.edu, segate.sunet.se, ~ >and ftp.csus.edu to include the V4.0-1 changes. I assume the others ~ >will be once their maintainers read this. 8-) (Thanks!) ~ > ~ >If you've already installed MX V4.0, an upgrade kit is available on ~ >those sites as MX_REV1_UPGRADE040.ZIP. ~ > ~ >SEND MX_REV1_UPGRADE040 in the body of a mail message to ~ >FILESERV@WKUVX1.WKU.EDU will return the upgrade kit in 36 60-block ~ >files. ~ > ~ >MX040_SRC.ZIP will be updated soon. ~ > ~ >This is the last update planned for V4.0, barring some other major ~ >bug. ~ > ~ >Hunter ~ >------ ~ >Hunter Goatley, VMS Systems Programmer, Western Kentucky University ~ >goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ~ Now avaliable on SACUSR.MP.USBR.GOV in the [.MX040] directory. Also available on FTP.BA.CNR.IT in /pub/software/mx040 (Italy) Massimo -- ----------------------------------------------------------------------------- | Massimo Ianigro | E-write at : ianigro@astrba.ba.cnr.it | | CNR - IESI | | | Via Amendola, 166/5 | | | 70126 BARI ITALY | Fax : 39 80 5484311 Voice : 39 80 5481969 | ---------------------------------------------------------------------------- ================================================================================ Archive-Date: Tue, 12 Apr 1994 05:43:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: nike@indirect.com (Laurence Canter) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Green Card Lottery- Final One? Date: 12 Apr 1994 08:23:28 GMT Message-ID: <2odlq0$4t3@herald.indirect.com> To: MX-List@WKUVX1.WKU.EDU Green Card Lottery 1994 May Be The Last One! THE DEADLINE HAS BEEN ANNOUNCED. The Green Card Lottery is a completely legal program giving away a certain annual allotment of Green Cards to persons born in certain countries. The lottery program was scheduled to continue on a permanent basis. However, recently, Senator Alan J Simpson introduced a bill into the U. S. Congress which could end any future lotteries. THE 1994 LOTTERY IS SCHEDULED TO TAKE PLACE SOON, BUT IT MAY BE THE VERY LAST ONE. PERSONS BORN IN MOST COUNTRIES QUALIFY, MANY FOR FIRST TIME. The only countries NOT qualifying are: Mexico; India; P.R. China; Taiwan, Philippines, North Korea, Canada, United Kingdom (except Northern Ireland), Jamaica, Domican Republic, El Salvador and Vietnam. Lottery registration will take place soon. 55,000 Green Cards will be given to those who register correctly. NO JOB IS REQUIRED. THERE IS A STRICT JUNE DEADLINE. THE TIME TO START IS NOW!! For FREE information via Email, send request to cslaw@indirect.com -- ***************************************************************** Canter & Siegel, Immigration Attorneys 3333 E Camelback Road, Ste 250, Phoenix AZ 85018 USA cslaw@indirect.com telephone (602)661-3911 Fax (602) 451-7617 ================================================================================ Archive-Date: Tue, 12 Apr 1994 05:47:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 03:42:38 -0700 (PDT) From: Paul Havinden Reply-To: MX-List@WKUVX1.WKU.EDU Subject: SMTP process keeps aborting To: MX-List@WKUVX1.WKU.EDU Message-ID: <01HB2NL8VRKI004C2C@UG.EDS.COM> MIME-Version: 1.0 Content-Transfer-Encoding: 7BIT I have just upgraded to MX version 4.0 from 3.3. However the SMTP process seems to keep aborting. The following is the entry in the logfile:- SNOOPY$ type MX_SMTP_SNOOPY.LOG;16 12-APR-1994 11:20:52.64: MX SMTP (pid 5EC00466) starting 12-APR-1994 11:20:54.10: MX SMTP (pid 5EC00466) exiting, status = 1000000C Sometimes after restarting it will run for quiet a while and process mail fine. Can soeone tell me what the status means, or what to look for. I turned on debugging for SMTP but no output is produced for this problem. Thanks Paul Havinden Graphic Data Systems ================================================================================ Archive-Date: Tue, 12 Apr 1994 06:16:16 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 13:13:04 +0300 (MET-DST) From: Massimo 'SleepyHead' Ianigro Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <940412131304.21400128@astrba.ba.cnr.it> Subject: A question from a newbie Hi Mx-friends, first of all, sorry for my long and error-prone mail, but my English is not very good.. I have a question about the configuration of MX. In my BIND configuration files, i have set up three MX resource records for each machine. This is an example of how i have done this: astrba 40 astrba.ba.cnr.it astrba 50 wsie05.ba.cnr.it astrba 60 icnucevx.cnuce.cnr.it When astrba is up, it is able to receive mail via SMTP. When astrba is down, then mails go to wsie05 (correctly) and after a certain period (depending on MX logicals setting) they try to go again to astrba. But astrba is down and so they go to icnucevx (the third MX resource...) and then stay there until astrba goes up. (icnucevx is running PMDF) Now the question is: since i have installed MX on wsie05 to avoid icnucevx.cnuce.cnr to get all our mails what can i do to store messages on wsie05 avoiding forward on icnucevx? I know that it would be sufficient to use only two MX records like: astrba 40 astrba.ba.cnr.it astrba 50 wsie05.ba.cnr.it but i would like to have a backup when wsie05 is down. There is a way to do that in mcp? Do i have to set up BIND config. as follows? astrba 40 astrba.ba.cnr.it astrba 50 wsie05.ba.cnr.it wsie05 10 wsie05.ba.cnr.it wsie05 30 icnucevx.cnuce.cnr.it This is an example of what happens. The header is from a mail i received: CNUCE is a DECnet alias for icnucevx.cnuce.cnr.it The destination address was ianigro@astrba.ba.cnr.it ~ From: CNUCE::IN%"MX-List@WKUVX1.WKU.EDU" 7-APR-1994 09:03:38.65 ~ To: IN%"MX-List@WKUVX1.WKU.EDU" ~ CC: ~ Subj: RE: MX V4.0 LOCAL process dying on AXP ~ Return-path: ~ Received: from wsie05.ba.cnr.it by icnucevx.cnuce.cnr.it (PMDF V4.2-14 #4369) ~ id <01HAVMLPBZB4HW9VB8@icnucevx.cnuce.cnr.it>; Thu, 7 Apr 1994 02:58:26 MET ~ Received: from wkuvx1.wku.edu by wsie05.ba.cnr.it (MX V3.3 AXP) with SMTP; Thu, ~ 07 Apr 1994 02:55:38 WET ~ Date: Wed, 06 Apr 1994 23:54:51 +0000 (GMT) ~ From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) ~ Subject: RE: MX V4.0 LOCAL process dying on AXP ~ Sender: owner-mx-list@WKUVX1.WKU.EDU ~ To: MX-List@WKUVX1.WKU.EDU ~ Errors-to: owner-mx-list@WKUVX1.WKU.EDU ~ Warnings-to: <> ~ Reply-to: MX-List@WKUVX1.WKU.EDU ~ Message-id: <2nvi4b$m5i@gap.cco.caltech.edu> ~ Organization: HST Wide Field/Planetary Camera ~ Content-transfer-encoding: 7BIT ~ X-ListName: Message Exchange Discussion List ~ X-Newsgroups: vmsnet.mail.mx ~ Lines: 15 ~ Distribution: world ~ NNTP-Posting-Host: sol1.gps.caltech.edu ~ X-Gateway-Source-Info: USENET Thanks a lot and sorry again to bother you, Massimo -- ----------------------------------------------------------------------------- | Massimo Ianigro | E-write at : ianigro@astrba.ba.cnr.it | | CNR - IESI | | | Via Amendola, 166/5 | | | 70126 BARI ITALY | Fax : 39 80 5484311 Voice : 39 80 5481969 | ---------------------------------------------------------------------------- ================================================================================ Archive-Date: Tue, 12 Apr 1994 06:16:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 06:16:17 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD53.E9B6871F.5@ALPHA.WKU.EDU> Subject: RE: MX V4.0 Local Process syseng@sukair.cc.uob.bh writes: > [...] >Actually I read that Incoming mail is now delivered with the VMS Mail >``To:'' and ``CC:'' lines containing the addresses from the RFC822 To: >and CC: lines. > >But I saw the address format is not simple as you see, Is it better ?. A lot of people think so, yes. I didn't like it at first, but have since grown to like it a lot. It causes all (most) recipients to show on the VMS Mail To: line, and it lets you do things like SELECT NEWMAIL/TO=OWNER to select certain messages. >I prefere VMS Mail To: contains the local user ID not the RFC822 format >as it is not useful for the user and it confused with the list address >as you see. > This is expected behavior---the From: line is the list address, and the message was sent to the list, so the To: also shows the list. >Is it possible to modify the local process to put local user ID instead, >if so can you help me doing so, as I have not all the source compilers >unless it is written in MACRO. > The code is in BLISS. I suppose I can make this a configurable option in the next version of MX. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 12 Apr 1994 06:47:41 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 14:30:17 +0300 From: syseng@sukair.cc.uob.bh Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD98.ECAA0EC0.20@sukair.cc.uob.bh> Subject: RE: MX V4.0 Local Process Hi Hunter, Thank you very much for your reply, I think the configurable option is the best solution to give choices. Thanks again. Nader Nasry ================================================================================ Archive-Date: Tue, 12 Apr 1994 07:28:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 17:21:33 +1000 From: bellamy@commerce.uq.edu.au Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <0097CDB0.D9D6EA94.3@covax.commerce.uq.oz.au> Subject: Re: How to get MXserver to ignore signatures? Relay-Version: ANU News - V6.1 08/24/93 VAX/VMS; site covax Path: test1.commerce.uq.oz.au!user Newsgroups: comp.mail.mx Subject: Re: How to get MXserver to ignore signatures? Message-ID: From: bellamy@commerce.uq.edu.au (David Bellamy) Date: Tue, 12 Apr 1994 16:58:08 +1000 Followup-To: comp.mail.mx References: <0097CA43.C2D0EA40.12071@swdev.si.com> Distribution: local Organization: The University of Queensland Nntp-Posting-Host: test1.commerce.uq.oz.au Lines: 69 In article <0097CA43.C2D0EA40.12071@swdev.si.com>, "Brian Tillman" wrote: > David Bellamy (bellamy@commerce.uq.edu.au) writes: > > >Somewhere I recall reading that there is a convention (not rfc) for news > >and email that signatures start with a line consisting only of "-- " i.e., > >. Is this correct? > > The answer seems to be a few yeses and a couple of maybes (or I thought it was @#$%). > >Would it be possible to have email to the -request address of servers such > >as mxserver ignore signature lines. This would reduce the number of error > >messages sent unnecessarily. > > > >Iff there is such a convention, then perhaps the automatic signature > >inclusion routines could (optionally) insert the separator. > > Oh, come on! MX isn't your mother! ;-) Surely if you know you are sending to a > -Request or xxserver address (and you do, because _you_ enter the address), then > you also know enough to add /NOSIG or QUIT to the end of your message. What's > six more little characters? I'd much rather Hunter spends his time adding in > _important_ functionality or fixing bugs than worrying about whether you know > how to type. > Sorry for making the suggestion! It's not for me, well at least not directly. I know about QUIT. However I have **lots** of users that are about to be let loose on our mlf (undergrad students, or even worse staff). I cannot do much about external people who take an interest in our list server, except if there is a Usenet convention to use "-- ", then that would be great - some of them might even use it :-). However, I do not look forward to receiving a heap of messages about signatures in subscribe/signoff commands. If we can modify the default signature included in our email to commence with "-- " or whatever the agreed 'convention' is, then I can save myself and our users lots of time. If there is a convention, then I see no harm in making such a feature available. I note that probably the most used NNTP client in the Mac world, John Norstad's, NewsWatcher will automatically include "-- " at the start of the signature. I'm very appreciative of Hunter's and Matt's time in developing MX and certainly would not want to burden them (or the code) with trivia, but to me at least it would be useful. I though perhaps that others might also find it a useful feature. > Ray Harwood (RHarwood@Data.Basix.COM) writes: > > >How about ignoring ALL lines after ANY line containing two or more consecutive > >hyphens?! > > How about simply ignoring all lines that aren't a -Request or xxServer command? > If it doesn't parse, toss it out, no matter what it contains. That would also cause problems. If a user send a request and it disappears into a black hole - no subscription and no response, then they are less like to try again. -- David Bellamy. Deparment of Commerce. The University of Queensland. Australia. Internet: bellamy@commerce.uq.edu.au ================================================================================ Archive-Date: Tue, 12 Apr 1994 07:34:43 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 07:34:11 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD5E.CC325ACE.23@ALPHA.WKU.EDU> Subject: Re: How to get MXserver to ignore signatures? bellamy@commerce.uq.edu.au writes: > [...] >It's not for me, well at least not directly. I know about QUIT. However I >have **lots** of users that are about to be let loose on our mlf (undergrad >students, or even worse staff). > >I cannot do much about external people who take an interest in our list >server, except if there is a Usenet convention to use "-- ", then that >would be great - some of them might even use it :-). However, I do not >look forward to receiving a heap of messages about signatures in >subscribe/signoff commands. If we can modify the default signature >included in our email to commence with "-- " or whatever the agreed >'convention' is, then I can save myself and our users lots of time. > Just to clear up something here---the list owner will not receive any messages about invalid commands. The users will, but if they will bother to read the message, they'll figure out what it's talking about. Of course, *I* know they won't do that and so they'll bug you about the errors they got.... >If there is a convention, then I see no harm in making such a feature >available. I note that probably the most used NNTP client in the Mac >world, John Norstad's, NewsWatcher will automatically include "-- " at the >start of the signature. > Until now, I had never heard of any such convention. >I'm very appreciative of Hunter's and Matt's time in developing MX and >certainly would not want to burden them (or the code) with trivia, but to >me at least it would be useful. I though perhaps that others might also >find it a useful feature. > It's on the wish list now, but I can't say if or when.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 12 Apr 1994 09:01:42 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 09:41:12 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: Message-ID: <0097CD70.8ADA42A0.4455@nscvax.princeton.edu> Subject: RE: SMTP process keeps aborting Paul Havinden writes: >I have just upgraded to MX version 4.0 from 3.3. However the SMTP process seems >to keep aborting. The following is the entry in the logfile:- > >SNOOPY$ type MX_SMTP_SNOOPY.LOG;16 >12-APR-1994 11:20:52.64: MX SMTP (pid 5EC00466) starting >12-APR-1994 11:20:54.10: MX SMTP (pid 5EC00466) exiting, status = 1000000C > > >Sometimes after restarting it will run for quiet a while and process mail fine. >Can soeone tell me what the status means, or what to look for. >I turned on debugging for SMTP but no output is produced for this problem. > The status is "Access violation"! It sounds very much like a bug! Hunter will have to tell you how to procede from herre. ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 12 Apr 1994 10:16:43 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 10:15:40 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD75.5AD38238.2@ALPHA.WKU.EDU> Subject: RE: SMTP process keeps aborting Mighty Firebreather writes: > > Paul Havinden writes: > >>I have just upgraded to MX version 4.0 from 3.3. However the SMTP process seems >>to keep aborting. The following is the entry in the logfile:- >> >>SNOOPY$ type MX_SMTP_SNOOPY.LOG;16 >>12-APR-1994 11:20:52.64: MX SMTP (pid 5EC00466) starting >>12-APR-1994 11:20:54.10: MX SMTP (pid 5EC00466) exiting, status = 1000000C >> >> >>Sometimes after restarting it will run for quiet a while and process mail fine. >>Can soeone tell me what the status means, or what to look for. >>I turned on debugging for SMTP but no output is produced for this problem. >> > > The status is "Access violation"! It sounds very much like a bug! >Hunter will have to tell you how to procede from herre. > My experience has been that these are almost always caused my a malformed address. I'd check your rewrite rules carefully. Also, you can use MCP SHOW QUEUE/IN to find the INPROG entry that caused the failure---SHOW QUEUE/FULL on that entry would show the target address. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 12 Apr 1994 10:28:53 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 09:57 BSC (-0300 C) From: Joseph Max Cohenca Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Problem with MX 4.0 To: MX-List@WKUVX1.WKU.EDU Message-ID: <732A4C84E0017864@fpsp.fapesp.br> References: ANSP network HEPnet SPAN Bitnet Internet gateway Yesterday we installed MX V4.0. Everything seemed working OK. When we arrived today there were more than 300 messages in the queue and all processes except the Routers where hibernating. It does not make a difference to shutdown MX and start it again. Any body has a clue of what is occurring?. This is the output of the SHOW SYSTEM command: 2760586E MX FLQ Manager HIB 6 1857 0 00:00:05.70 211 366 2760586F MX Router CUR 1 4 743 0 00:11:20.17 580 765 27605771 MX Router#2 CUR 3 4 384 0 00:12:08.22 491 682 27605972 MX Local HIB 5 2063 0 00:00:07.51 708 922 27604F73 MX Local#2 HIB 5 1934 0 00:00:06.87 671 881 27605874 MX DNSMTP HIB 5 1105 0 00:00:03.64 189 318 27604376 MX SMTP HIB 5 1314 0 00:00:04.67 539 988 27604E78 MX SMTP#2 HIB 5 1250 0 00:00:04.53 524 981 2760547A MX SMTP#3 HIB 5 1214 0 00:00:04.59 465 970 27604C7B MX SMTP#4 HIB 5 1216 0 00:00:04.61 622 811 27604E7C MX SMTP Server HIB 5 930 0 00:00:07.90 488 954 2760577D MX X.25-SMTP HIB 4 1106 0 00:00:03.73 189 322 2760537E MX MLF HIB 5 1107 0 00:00:03.83 227 423 +-----------------------------------------------------------------------------+ ! Joseph Max Cohenca ! Hepnet: uspif::mcohenca ! ! Centro de Computacao ! Hepnet: 47602::mcohenca ! ! Instituto de Fisica da USP ! Renpac: psi%11187031::mcohenca ! ! Caixa Postal 20516 ! Internet: mcohenca@uspif.if.usp.br ! ! 01498- Sao Paulo ! Fone: (011) 818-6810 ! ! BRASIL ! FAX : (011) 814-0503 ! +-----------------------------------------------------------------------------+ ================================================================================ Archive-Date: Tue, 12 Apr 1994 10:32:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: chris@csvax1.ucc.ie (Chris Higgins - System Administrator) Subject: Re: MX V4.0-1 upgrade is now available Message-ID: Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 15:05:18 GMT To: MX-List@WKUVX1.WKU.EDU > ~ In article <0097CCB0.DA25C778.27@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: > ~ >An upgrade kit for MX V4.0-1 is now available. MX V4.0-1 offers the > ~ >following enhancements and bug fixes over MX V4.0: > Also available on csvax1.ucc.ie [.VMS] Chris. + J.C. Higgins, + Chris@csvax1.ucc.ie + If you love something, set it + + VMS Sys. Admin, + Chris@cs.ucc.ie + free. If it doesn't come back + + Comp.Sc.Dept. + Chris@odyssey.ucc.ie + to you, hunt it down and + + UCC, Ireland + C.Higgins@bureau.ucc.ie + KILL it. + ================================================================================ Archive-Date: Tue, 12 Apr 1994 10:35:49 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 10:35:15 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD78.17653B3D.1@ALPHA.WKU.EDU> Subject: RE: Problem with MX 4.0 Joseph Max Cohenca writes: > >Yesterday we installed MX V4.0. Everything seemed working OK. When we arrived >today there were more than 300 messages in the queue and all processes except >the Routers where hibernating. It does not make a difference to shutdown MX >and start it again. Any body has a clue of what is occurring?. > This is the output of the SHOW SYSTEM command: Off-hand, no. Have you enabled debugging on the Router? If not, you should to see what it's doing. You might do the same for the others too. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 12 Apr 1994 11:09:31 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 12:06:14 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: goathunter@alpha.wku.edu Message-ID: <0097CD84.CD9FFB20.4502@nscvax.princeton.edu> Subject: RE: SMTP process keeps aborting "Hunter Goatley, WKU" writes: >Mighty Firebreather writes: >> >> Paul Havinden writes: >> >>>I have just upgraded to MX version 4.0 from 3.3. However the SMTP process seems >>>to keep aborting. The following is the entry in the logfile:- >>> >>>SNOOPY$ type MX_SMTP_SNOOPY.LOG;16 >>>12-APR-1994 11:20:52.64: MX SMTP (pid 5EC00466) starting >>>12-APR-1994 11:20:54.10: MX SMTP (pid 5EC00466) exiting, status = 1000000C >>> >>> >>>Sometimes after restarting it will run for quiet a while and process mail fine. >>>Can soeone tell me what the status means, or what to look for. >>>I turned on debugging for SMTP but no output is produced for this problem. >>> >> >> The status is "Access violation"! It sounds very much like a bug! >>Hunter will have to tell you how to procede from herre. >> >My experience has been that these are almost always caused my a >malformed address. I'd check your rewrite rules carefully. Also, you >can use MCP SHOW QUEUE/IN to find the INPROG entry that caused the >failure---SHOW QUEUE/FULL on that entry would show the target address. > Hunter, I'm sure that Paul did something wrong that triggered it but is an access violation a correct response to an error? One would hope that the program would detect the error, issue a meaningful message, and continue with its work. OK, the message can't be sent to an invalid address; how about: a. drop it in the bit bucket or, b. put it in a "dead letter" queue or, c. return to sender. "I can't go on like this! Farewell cruel world!" seems a little extreme. :-) -- ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 12 Apr 1994 11:14:02 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 11:13:01 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: DRAGON@NSCVAX.PRINCETON.EDU Message-ID: <0097CD7D.5E368918.20@ALPHA.WKU.EDU> Subject: RE: SMTP process keeps aborting Mighty Firebreather writes: > > I'm sure that Paul did something wrong that triggered it but is an >access violation a correct response to an error? One would hope that the >program would detect the error, issue a meaningful message, and continue >with its work. I agree. Unfortunately, I haven't tracked down all the cases where the accvio can occur. I'm working on it though. MX V4.0 is better about that than previous versions. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 12 Apr 1994 11:48:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 12:18:49 EDT From: "Brian Tillman" Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!mx-list@pubs22.si.com Message-ID: <0097CD86.8F484920.14929@swdev.si.com> Subject: Re: How to get MXserver to ignore signatures? David Bellamy (bellamy@commerce.uq.edu.au) writes: >In article <0097CA43.C2D0EA40.12071@swdev.si.com>, "Brian Tillman" > wrote: >... >> How about simply ignoring all lines that aren't a -Request or xxServer >> command? >> If it doesn't parse, toss it out, no matter what it contains. > >That would also cause problems. If a user send a request and it disappears >into a black hole - no subscription and no response, then they are less >like to try again. I didn't mean throw the message out. I meant ignore the line that isn't understood. If no line is understood, then an error can be returned to the requester. There is no "--" USENET convention for separating signatures from body, by the way. Some very common mailers use this method, but it's by no means universal or even the majority. ================================================================================ Archive-Date: Tue, 12 Apr 1994 11:54:23 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 12 Apr 1994 11:50:30 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CD82.9A935B20.183@SHSU.edu> Subject: RE: MX V4.0-1 upgrade is now available On Mon, 11 Apr 1994 10:49:02 CDT, "Hunter Goatley, WKU" posted: > An upgrade kit for MX V4.0-1 is now available. MX V4.0-1 offers the > following enhancements and bug fixes over MX V4.0: >.... > If you've already installed MX V4.0, an upgrade kit is available on those > sites as MX_REV1_UPGRADE040.ZIP. > > SEND MX_REV1_UPGRADE040 in the body of a mail message to > FILESERV@WKUVX1.WKU.EDU will return the upgrade kit in 36 60-block files. SEND MX_REV1_UPGRADE040 in the body of a mail message to FILESERV@Niord.SHSU.edu will retrieve this in 26 80-block files and I've updated the FILESERV'able MX040 set (134 80-block files) here as well for retrieval from our FILESERV (SEND MX040 to FILESERV@Niord.SHSU.edu to fetch them). As far as the ZIP sets for these, they are available for anonymous ftp retrieval from Niord.SHSU.edu in [FILESERV.MX040.ZIPSETS]; as far as the VMSINSTALlable backup savesets included in these ZIP sets, look in [FILESERV.MX] on Niord. Many thanks to Hunter and everyone else involved in getting together 4.0 and the 4.0-1 upgrade. --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Internet: bed_gdg@SHSU.edu Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 Sam Houston State University FAX: (409) 294-3612 Huntsville, TX 77341-2118 USA %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Tue, 12 Apr 1994 14:23:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: ken@dmsman.dom.uab.edu (Ken Beaudrie) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Mail Notification Message-ID: Date: Tue, 12 Apr 1994 19:34:33 GMT To: MX-List@WKUVX1.WKU.EDU I'm going to ask about something that popped up a while back at our site and I haven't seen discussed here. Our PC people use Pathworks mail for all their mail traffic. If someone sends them a message from either a local or remote vax using VMS mail, they receive a notification of new mail. But foreign mail, like MX% stuff never gets notified. I checked this out on three Pathworks servers and a half-dozen different PCs. Has anyone else seen this? Can anyone say notification to PCs works with MX? If so did you have to do anything, or did it just work? Thanks in advance for any help on this problem. I'm stumped. ================================================================================ Archive-Date: Tue, 12 Apr 1994 17:53:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: re: PINE Mail for VMS Message-ID: <1994Apr12.133708.21889@oxvaxd> Date: 12 Apr 94 13:37:08 BST To: MX-List@WKUVX1.WKU.EDU In article <0097CCE4.286F4660.31760@CCVAX.CCS.CSUS.EDU>, "John F. Sandhoff" writes: > > Disclaimer: This is off the subject of MX-Mail and followup discussion > should be directed to the comp.mail and other applicable groups... > > For convenience (and enhanced transfer speed!) we have placed the beta > release of the Pine Mailer VMS port on ftp.csus.edu. (/pub/cmuip/contrib; > you'll also need unzip.exe, see the readme file for how to use it). We > have *not* tried compiling it yet and can offer no information as to > how good it is. > > Pine replaces the VMS "user agent" (that is, VMSMail). It interfaces with > the MAIL.MAI file, however there are several subtle differences between > VMSMail and Pine (Pine does not use the wastebasket folder, for instance, > and by default it checks 'inbox' rather than 'newmail' for new messages). > However, Pine provides an arguably-much more friendly user interface to > Mail. > > Yehavi Bourvine from Hebrew University is responsible for this port, and > it was obtained from VMS.HUJI.AC.IL. > > John F. Sandhoff, University Network Support > California State University, Sacramento - USA > sandhoff@csus.edu > I've managed to get it working under UCX (you'll need NETLIB to do it though). If anybody manages to get Pine's IMAPD to work under UCX please let me know! Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Tue, 12 Apr 1994 19:11:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 10:05:30 +1000 From: Powell HEUER Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: powell@syd.dwt.csiro.au Message-ID: <0097CE3D.19B183E0.169@syd.dwt.CSIRO.AU> Subject: RE: Mail Notification ken@dmsman.dom.uab.edu (Ken Beaudrie) writes: > I'm going to ask about something that popped up a while back at our site >and I haven't seen discussed here. Our PC people use Pathworks mail for all >their mail traffic. If someone sends them a message from either a local or >remote vax using VMS mail, they receive a notification of new mail. But >foreign mail, like MX% stuff never gets notified. I checked this out on >three Pathworks servers and a half-dozen different PCs. Has anyone else >seen this? Can anyone say notification to PCs works with MX? If so did you >have to do anything, or did it just work? >Thanks in advance for any help on this problem. I'm stumped. We had a similar problem. The background is that the broadcast used for Pathworks mail notification is not a normal DECNET broadcast as generated by REPLY but can only be done by a Pathworks server. In our case only one node of the cluster is a Pathworks server but nodes other than this also run MX processes. Our system is configured with the logical MAIL$SYSTEM_FLAGS = 7 for cluster wide mail. If MX receives mail and it is processed (by LOCAL I think) on a node other than the Pathworks server, the Pathworks broadcast can't be generated and so no notification is made. Notification is done via a forwarding address. The "solution" is to change the forwarding address for all Pathworks users who want notification from addresses like PCSA%"PC_nodename$username" to Pathworks_host_node_number::PCSA%"PC_nodename$username" where Pathworks_host_node_number is the DECnet address of your Pathworks server (eg if the DECnet node number of your Pathworks server is 1.4 the required address is (1*1024)+4, ie 1028). It has to be the number rather than the node name to fool Mail into forwarding the message via DECnet. If you use the name it will recognise that the node is part of the same cluster and so because of the behaviour set by the the value of MAIL$SYSTEM_FLAGS no forwarding to the required node will happen. The change can't be done from Pathworks mail but has to be done from VMS mail. You can make the change for users by using the SET FORWARD/USER=name address command in MAIL. I logged the result of a SHOW FORWARD/USER=* command and edited this create a command file that made the change for all present users. Hope this helps. --------------------------------------------------------------------- Powell Heuer E-Mail: P.Heuer@syd.dwt.csiro.au CSIRO Division of Wool Technology Phone : +61 2 809 9444 PO Box 7 Fax : +61 2 809 9476 Ryde NSW 2112 AUSTRALIA ================================================================================ Archive-Date: Tue, 12 Apr 1994 21:02:01 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: dunnett@mala.bc.ca (Malcolm Dunnett) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Mail Notification Message-ID: <1994Apr12.185128.3961@malins.mala.bc.ca> Date: 12 Apr 94 18:51:28 -0700 To: MX-List@WKUVX1.WKU.EDU In article <0097CE3D.19B183E0.169@syd.dwt.CSIRO.AU>, Powell HEUER writes: > > We had a similar problem. > The background is that the broadcast used for Pathworks mail notification is not > a normal DECNET broadcast as generated by REPLY but can only be done by a > Pathworks server. > ... > > Notification is done via a forwarding address. The "solution" is to change the > forwarding address for all Pathworks users who want notification from addresses > like > PCSA%"PC_nodename$username" to > Pathworks_host_node_number::PCSA%"PC_nodename$username" > where Pathworks_host_node_number is the DECnet address of your > Pathworks server (eg if the DECnet node number of your Pathworks server is 1.4 > the required address is (1*1024)+4, ie 1028). > Another approach is to run the NETBIOS component of Pathworks on all nodes in the cluster. Since Pathworks ( at least pre V5 ) licensing is client based there's no licensing issue with doing this, and if you're running Pathworks on one node presumably the files are available to all nodes ( or can be made available ). It does require a process entry slot for the NETBIOS process. -- ============================================================================= Malcolm Dunnett Malaspina University-College Email: dunnett@mala.bc.ca Computer Services Nanaimo, B.C. CANADA V9R 5S5 Tel: (604)755-8738 ================================================================================ Archive-Date: Wed, 13 Apr 1994 02:03:31 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 07:59:44 BST From: "John Hill, Cavendish Lab, Cambridge Univ. (0223-337243)" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CE2B.87F9A047.5243@hep.phy.cam.ac.uk> Subject: RE: Mail Notification One can also use the __nodename syntax to force the use of DECnet in an homogeneous cluster. Just in case the _ gets shredded on its trip round the world, if one prepends two underscore characters in front of the nodename, this forces the use of DECnet, even ================================================================================ Archive-Date: Wed, 13 Apr 1994 02:09:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 08:02:03 BST From: "John Hill, Cavendish Lab, Cambridge Univ. (0223-337243)" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CE2B.DB1FA307.5245@hep.phy.cam.ac.uk> Subject: RE: Mail Notification One can also use the __nodename syntax to force the use of DECnet in an homogeneous cluster. Just in case the _ gets shredded on its trip round the world, if one prepends two underscore characters in front of the nodename, this forces the use of DECnet, even if MAIL$SYSTEM_FLAGS is set to 7. John Hill [Sorry about the truncated message just sent - I'm using an unfamiliar window system at the moment] ================================================================================ Archive-Date: Wed, 13 Apr 1994 09:45:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: desroches@woods.uml.edu Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Why is %am.mrgate in return address??? Date: 13 Apr 94 10:22:28 -0500 Message-ID: <1994Apr13.102228.1@woods.uml.edu> To: MX-List@WKUVX1.WKU.EDU Recently our return address for all email going out through MX changed all by itself. Suddenly, for no reason we know of, the string "%am.mrgate" is being inserted into the address so that my return address comes out as: desroches%am.mrgate@woods.uml.edu There are a lot of problems with this format since most listservers and many unix email systems cannot respond to this address. I suspect this is a problem with DEC's Message Router software. However, the CSC has not been any help at all and as soon as I mention MX they say it's not their problem and they won't talk to me any more. Does anybody have any ideas on how I can fix this? Thanks, Dick Desroches ================================================================================ Archive-Date: Wed, 13 Apr 1994 09:58:53 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: FLQ Manager process very slow Message-ID: <1994Apr13.132616.21923@oxvaxd> Date: 13 Apr 94 13:26:16 BST To: MX-List@WKUVX1.WKU.EDU Hi, Is anybody running the MX FLQ Manager that came with MX 4.0? On our system it seems to take ages to get rid of FINISHed entries and their associated files. Anybody else seen this? Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Wed, 13 Apr 1994 10:10:23 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 10:08:46 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CE3D.8E9110DB.13@ALPHA.WKU.EDU> Subject: RE: FLQ Manager process very slow daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) writes: > >Hi, > >Is anybody running the MX FLQ Manager that came with MX 4.0? On our system it >seems to take ages to get rid of FINISHed entries and their associated files. >Anybody else seen this? > The MX FLQ Manager uses the exact same code as the MX Router for finding and deleting entries. If the MX disk is heavily I/O bound, then the deletion of the files can be slowed down quite a bit. That's one of the downsides to the new queue file: it's so efficient, the agents can do more searching than before, which can increase the I/O load on the disk. That's one reason the MX FLQ Manager can be useful---without it, one of your Routers would be delayed from routing during that time. You can also define the following FLQ logicals to cause scans to happen more frequently and to delete FIN entries sooner: MX_FLQ_MGR_WAKEUP_INTERVAL Defaults to "0 00:02:00" Amount of time it sleeps before waking up MX_FLQ_CHECK_WAIT Defaults to "0 00:10:00" Amount of time that must elapse before it'll actually scan for entries MX_FLQ_PURGE_WAIT Defaults to "0 00:15:00" Amount of time a FIN entry will be left in the queue You could try changing the MX_FLQ_CHECK_WAIT to "0 00:01:00", which will cause it to scan every time it wakes up.... Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 13 Apr 1994 10:55:00 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 17:47:46 +0100 From: Juan Altmayer Pizzorno Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CE7D.AE0A5816.23@vms.gmd.de> Subject: RE: Problem with MX 4.0 [...] >2760586E MX FLQ Manager HIB 6 1857 0 00:00:05.70 211 366 >2760586F MX Router CUR 1 4 743 0 00:11:20.17 580 765 >27605771 MX Router#2 CUR 3 4 384 0 00:12:08.22 491 682 >27605972 MX Local HIB 5 2063 0 00:00:07.51 708 922 [...] TWO processed marked "current" in a SHOW SYSTEM command? I didn't think this was possible... .. Juan ================================================================================ Archive-Date: Wed, 13 Apr 1994 11:00:24 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 10:57:12 EST From: koenig@CVAX.IPFW.INDIANA.EDU Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CE44.528ED760.17354@CVAX.IPFW.INDIANA.EDU> Subject: RE: Problem with MX 4.0 >From: MX%"MX-List@WKUVX1.WKU.EDU" 13-APR-1994 10:54:21.64 >Subj: RE: Problem with MX 4.0 >[...] >>2760586E MX FLQ Manager HIB 6 1857 0 00:00:05.70 211 366 >>2760586F MX Router CUR 1 4 743 0 00:11:20.17 580 765 >>27605771 MX Router#2 CUR 3 4 384 0 00:12:08.22 491 682 >>27605972 MX Local HIB 5 2063 0 00:00:07.51 708 922 >[...] > >TWO processed marked "current" in a SHOW SYSTEM command? I didn't think >this was possible... It's a multi-processor VAX, I'd guess. Simple, huh? :-) >.. Juan ---Greg --------------------------------------------------------------------------- Greg Koenig koenig@cvax.ipfw.indiana.edu Systems Programmer koenig@ipfwcvax.bitnet Indiana University - Purdue University koenig@smtplink.ipfw.indiana.edu Fort Wayne, Indiana (219) 481-6031 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 13 Apr 1994 13:28:17 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 13 Apr 1994 13:22:34 EDT From: Chris Olive Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: olive@sgi.siemens.com Message-ID: <0097CE58.A18C9D20.22@sgi.siemens.com> Subject: RE: Problem with MX 4.0 In article <0097CE7D.AE0A5816.23@vms.gmd.de>, Juan Altmayer Pizzorno writes: >[...] >>2760586E MX FLQ Manager HIB 6 1857 0 00:00:05.70 211 366 >>2760586F MX Router CUR 1 4 743 0 00:11:20.17 580 765 >>27605771 MX Router#2 CUR 3 4 384 0 00:12:08.22 491 682 >>27605972 MX Local HIB 5 2063 0 00:00:07.51 708 922 >[...] > >TWO processed marked "current" in a SHOW SYSTEM command? I didn't think >this was possible... It is if one has more than one CPU. This one apparently has at least 3 (if past memory serves me correctly). Chris _______________________________________________________________________________ ___ ___ ___ _ _ ___ _ _ ___ /___ | |__ |\ /| |__ |\ | /___ Chris Olive, VMS Systems Consultant ___/ _|_ |___ | Y | |___ | \| ___/ Internet: olive@sgi.siemens.com Medical Systems, Inc. Voice: 708.304.7793 2501 N. Barrington Road. FAX: 708.304.7704 Hoffman Estates, IL 60195 CompuServe: 73740,1636 _______________________________________________________________________________ ================================================================================ Archive-Date: Thu, 14 Apr 1994 08:04:09 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 14 Apr 1994 13:57:28 EDT From: "Andy Harper, KCL Systems Manager" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: udaa055@bay.cc.kcl.ac.uk Message-ID: <0097CF26.AC3A0720.5@bay.cc.kcl.ac.uk> Subject: Adding extra headers on outbound mail I've scanned the MX 4.0-1 docs and can;t see this (apologies if i've missed it)... Sometime back I asked if it was possible for MX to have additional headers inserted by privileged users (E.G. X-organisation: ...) when mail is sent out. I recall that the answer was `it's planned for the next release...'. Did it make it into 4.0-x? If so, how is it accomplished; if not, when? Regards, Andy Harper Kings College London ================================================================================ Archive-Date: Thu, 14 Apr 1994 08:12:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 14 Apr 1994 08:09:28 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CEF6.0EBE4E2D.13@ALPHA.WKU.EDU> Subject: RE: Adding extra headers on outbound mail "Andy Harper, KCL Systems Manager" writes: > >I've scanned the MX 4.0-1 docs and can;t see this (apologies if i've missed >it)... > >Sometime back I asked if it was possible for MX to have additional headers >inserted by privileged users (E.G. X-organisation: ...) when mail is sent out. >I recall that the answer was `it's planned for the next release...'. Did it >make it into 4.0-x? If so, how is it accomplished; if not, when? > No, that didn't make it in MX V4.0. After we discussed the various methods, I got busy with the new queueing subsystem and, basically, forgot to do anything about it. 8-( I'll make that a high priority for MX V4.1. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Thu, 14 Apr 1994 11:16:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: szgyula@skysrv.pha.jhu.edu (Gyula Szokoly) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Adding extra headers on outbound mail Date: 14 Apr 1994 15:19:55 GMT Message-ID: <2ojmurINNajo@jhunix.hcf.jhu.edu> To: MX-List@WKUVX1.WKU.EDU In article <0097CF26.AC3A0720.5@bay.cc.kcl.ac.uk>, Andy Harper, KCL Systems Manager wrote: >I've scanned the MX 4.0-1 docs and can;t see this (apologies if i've missed >it)... > >Sometime back I asked if it was possible for MX to have additional headers >inserted by privileged users (E.G. X-organisation: ...) when mail is sent out. >I recall that the answer was `it's planned for the next release...'. Did it >make it into 4.0-x? If so, how is it accomplished; if not, when? A more specific question: can I add a 'Return-receipt-to: ....' line to the header somehow? I was stupid enough to trust the UCX SMTP mailer. There were mails lost, etc. Now I converted to MX (over UCX). So far it seems to be great. However the prejudice sticks to the VMS mailers here. If somebody does not respond to a mail in 2 minutes, the user comes and complains that the mailer is broken again. I'd like to add this return receipt stuff centrally to the header if possible (only for a week or two -- to convience the users that it's not the mailer; the adresee just does not respond). Any idea, any reasonable hack, etc.? If it's in the manual, say so. I've just installed MX in panic (serious crash of UCX SMTP) so I did not read the whole manual yet. Thanks, Gyula -- Gyula P. Szokoly (szgyula@skysrv.pha.jhu.edu) -------------------------------\ | When I am weaker than you, I ask you for freedom because that is according| |to your principles; when I am stronger than you, I take away your freedom| |because that is according to my principles. -- Frank Herbert| ================================================================================ Archive-Date: Thu, 14 Apr 1994 18:51:56 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 14 Apr 1994 16:39:02 PDT From: "John F. Sandhoff" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: ianigro@astrba.ba.cnr.it, syssand@CCVAX.CCS.CSUS.EDU Message-ID: <0097CF3D.3E20CA00.16082@CCVAX.CCS.CSUS.EDU> Subject: RE: A question from a newbie I may be way off base in understanding the problem here, but on the off chance that the answer is really this easy... > In my BIND configuration files, i have set up three MX resource records for > each machine. This is an example of how i have done this: > > astrba 40 astrba.ba.cnr.it > astrba 50 wsie05.ba.cnr.it > astrba 60 icnucevx.cnuce.cnr.it The format of lines in most BIND implementations requires some additional fields; namely in this case the field saying it's an MX record: astrba IN MX 40 astrba.ba.cnr.it IN MX 50 wsie05.ba.cnr.it IN MX 60 icnucevx.cnuce.cnr.it Now, I do believe that there's something wrong with your name server records; querying astrba.ba.cnr.it returns MX records for itself and wsie05, but no MX pointing to icnucevx so I have no idea how the mail is getting passed off to icnucevx. However, trying to query icnucevx.cnuce.cnr.it causes my version of nslookup to crash; this is a pretty good indication that there's some faulty data on your end. So that's where I'd start the search. Good luck. John F. Sandhoff, University Network Support California State University, Sacramento - USA sandhoff@csus.edu ================================================================================ Archive-Date: Thu, 14 Apr 1994 21:02:32 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 14 Apr 1994 21:56:07 EDT From: Jeff Finlay Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <0097CF69.89C4C980.20092@ycvax.york.cuny.edu> help ================================================================================ Archive-Date: Fri, 15 Apr 1994 01:16:17 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kramer@fragile.termfrost.org (Mike Andrews) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: (possible FAQ/RTFM?) MX 4.0 and DNS Mail Exchange records Message-ID: Date: Fri, 15 Apr 1994 05:06:29 GMT To: MX-List@WKUVX1.WKU.EDU Advance apologies; I'm a MX newbie. That said, I just installed MX 4.0-1 (though creating the queue was a bit of a hassle as mentioned before, I did finally get it going)... Right now I'm trying to run it in outbound-only mode for testing (we don't want to replace our Jnet and SMTP servers just YET) and it seems pretty impressive, except I've got two fairly big problems (one with Jnet that will probably solve itself when I actually start MX before Jnet like I'm supposed to, but like I said, I'm trying to do it outbound-only) ANYWAY, my real problem: I don't seem to be able to mail to hosts specified in the DNS as Mail Exchange aliases (MX records). For example: wittenberg.edu = 136.227.1.2 (VAX 4300, VMS 5.5-2, Wollongong Pathway) fragile.termfrost.org = 136.227.1.128 (NeXT connected via SLIP) termfrost.org = DNS mail exchange record, pointing at fragile, with preference 0. No IP address of its own. Mail to root@fragile.termfrost.org from the VAX works, but mail to root@termfrost.org gets stuck in the queue running up a lot of DNS errors (%MX-F-NOHOST, no such host) The Management Guide didn't have much to say besides "check the Netlib release notes", and they weren't a lot of help, except for suggesting that I make a NETLIB_NAMESERVERS logical (without much hint as to how to specify multiple nameservers). Perhaps the fact that the DNS server is running on the LOCAL machine (wittenberg.edu) is messing it up? I tried defining NETLIB_NAMESERVERS with the address of our secondary nameserver, though (first hostname, then ip number) and it didn't seem to help. Any ideas, or am I just stupid and missing something really obvious in the docs? Thanks... -- Mike Andrews "This guy's pretty bizarre, Gus." root@fragile.termfrost.org [NeXTmail OK] - Primus kramer@wittenberg.edu (school) kramer@mik.uky.edu (hometown) ================================================================================ Archive-Date: Fri, 15 Apr 1994 02:32:35 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Apr 1994 17:27:50 +1000 From: Powell HEUER Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: powell@syd.dwt.csiro.au Message-ID: <0097D00D.398B6CE0.354@syd.dwt.CSIRO.AU> Subject: RE: (possible FAQ/RTFM?) MX 4.0 and DNS Mail Exchange records kramer@fragile.termfrost.org (Mike Andrews) writes: >... >ANYWAY, my real problem: I don't seem to be able to mail to hosts specified >in the DNS as Mail Exchange aliases (MX records). >... I've found Matt Madison's NSQUERY utility very useful to allow me to query my nameservers to check proper operation. --------------------------------------------------------------------- Powell Heuer E-Mail: P.Heuer@syd.dwt.csiro.au CSIRO Division of Wool Technology Phone : +61 2 809 9444 PO Box 7 Fax : +61 2 809 9476 Ryde NSW 2112 AUSTRALIA ================================================================================ Archive-Date: Fri, 15 Apr 1994 03:36:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Apr 1994 10:36:35 EDT From: "Jean Xech - S.I.U.P." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: xech@univ-perp.fr Message-ID: <0097CFD3.C6505BD9.31@gala.univ-perp.fr> Subject: MX 4.0 on a mixed cluster ... Hi, I have just installed MX 4.0 on a mixed cluster. I stopped the MX 3.3 server on the VAX node (SYSPO) to start the AXP server (node GALA), then run MX_startup.com(4.0) on all nodes. The messages are sent correctly, but received messages are not distribued to the local VAX users and disappear from the queue ... Where is the mistake ???!!! A badly defined cluster logical ? PLEASE REPLY to : XECH@NAXOS.UNICE.FR Best regards --Jean Xech ------------------------------------------------------ Here are the VAX logicals "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "$1$DKA200:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[EXE]" "MX_FLQ_CHECK_WAIT" = "0 00:10:00" "MX_FLQ_DIR" = "GALA$DUA0:[MX.QUEUE]" "MX_FLQ_MGR_WAKEUP_INTERVAL" = "0 00:02:00" "MX_FLQ_NODE_NAME" = "GALA" "MX_FLQ_PURGE_WAIT" = "0 00:01:00" "MX_FLQ_RECLAIM_WAIT" = "0 02:00:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "gala.univ-perp.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "4" "MX_VMSMAIL_LOCALHOST" = "@univ-perp.fr" -------------------------------------------------------------- Here are the AXP logicals "MX_ALIAS_HELPLIB" = "MX_DIR:MX_ALIAS_HELPLIB" "MX_DEVICE" = "$1$DKA200:" "MX_DIR" = "MX_DEVICE:[MX]" "MX_DOC" = "MX_ROOT:[DOC]" "MX_EXAMPLES_DIR" = "MX_ROOT:[EXAMPLES]" "MX_EXE" = "MX_ROOT:[ALPHA_EXE]" "MX_FLQ_CHECK_WAIT" = "0 00:10:00" "MX_FLQ_DIR" = "GALA$DUA0:[MX.QUEUE]" "MX_FLQ_MGR_WAKEUP_INTERVAL" = "0 00:02:00" "MX_FLQ_NODE_NAME" = "GALA" "MX_FLQ_PURGE_WAIT" = "0 00:01:00" "MX_FLQ_SHR" = "MX_EXE:MX_FLQ_SHR" "MX_LOCAL_DIR" = "MX_ROOT:[LOCAL]" "MX_MAILSHR" = "MX_EXE:MX_MAILSHR" "MX_MAILSHRP" = "MX_EXE:MX_MAILSHRP" "MX_MCP_HELPLIB" = "MX_DIR:MX_MCP_HELPLIB" "MX_MLF_DIR" = "MX_ROOT:[MLF]" "MX_MLIST_DIR" = "MX_ROOT:[MLF.MAILING_LISTS]" "MX_MSG" = "MX_EXE:MX_MSG" "MX_NODE_NAME" = "gala.univ-perp.fr" "MX_ROOT" = "MX_DEVICE:[MX.]" "MX_ROUTER_DIR" = "MX_ROOT:[ROUTER]" "MX_SHR" = "MX_EXE:MX_SHR" "MX_SITE_DIR" = "MX_ROOT:[SITE]" "MX_SITE_DOM_EXPANSION" = "MX_EXE:DOMAIN_EXPANSION" "MX_SMTP_DIR" = "MX_ROOT:[SMTP]" "MX_SMTP_SERVER_THREADS" = "4" "MX_VMSMAIL_LOCALHOST" = "@univ-perp.fr" ------------------------------------------------------ the process on the node GALA (AXP node) 23400218 MX FLQ Manager HIB 6 4150 0 00:00:03.61 58 74 23400219 MX Router HIB 4 1893 0 00:00:01.65 89 118 2340029A MX Local HIB 4 8471 0 00:00:12.59 2634 586 2340029B MX SMTP HIB 4 1886 0 00:00:01.12 90 117 2340029C MX SMTP Server HIB 5 398 0 00:00:00.48 80 109 2340029D MX MLF HIB 4 565 0 00:00:00.41 58 64 2340009F UCX$INET_ACP HIB 8 2918 0 00:00:02.46 139 81 234000A1 UCX$INET_ROUTED LEF 6 44 0 00:00:00.10 104 84 S ------------------------------------------------------ The command MCP QUEUE SHOW /brief : .......................................... 13 INP 135 MX_ROUTER 14 RDY 135 MX_LOCAL .......................................... ------------------------------------------------------ Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;1 MX version id is: MX V4.0-1 AXP Domain-to-path mappings: Domain="gala.univ-perp.fr", Path=Local Domain="siup.univ-perp.fr", Path=Local Domain="cri.univ-perp.fr", Path=Local Domain="univ-perp.fr", Path=Local Domain="gala", Path=Local Domain="siup", Path=Local Domain="cri", Path=Local Domain="*.BITNET", Path=SMTP, Route="frmop11.cnusc.fr" Domain="*.UUCP", Path=SMTP, Route="uunet.uu.net" Domain="*", Path=SMTP Aliases: LocalName="Postmaster", Address="xech@univ-perp.fr" LocalName="POSTMAST", Address="xech@univ-perp.fr" SMTP agent settings: SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: disabled Default router: (none) LOCAL agent settings: DECnet delivery retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. Multiple VMS Mail From: addresses allowed. Local delivery errors are not CC'ed to local Postmaster. Delivery to MultiNet MM disallowed. Top headers: FROM,SENDER,TO,RESENT_TO,CC,RESENT_CC,BCC,RESENT_BCC,MESSAGE_ID, RESENT_MESSAGE_ID,IN_REPLY_TO,REFERENCES,KEYWORDS,SUBJECT, ENCRYPTED,DATE,REPLY_TO,RECEIVED,RESENT_REPLY_TO,RESENT_FROM, RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER Bottom headers: (none) ROUTER agent settings: Automatic percent-hack handling: enabled Sender header for outgoing VMS Mail messages: included if necessary JNET agent settings: Automatic percent-hack handling: enabled BSMTP replies: disabled Accounting: disabled Lenient about gatewaying mail: no No mailer username set. DECnet_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. SITE agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 X25_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. ------------------------------------------------------------- Here is MX_STARTUP_INFO.DAT 001NETLIB:* 002FLQ_MGR:GALA 002ROUTER:GALA=1 003LOCAL:GALA=1 004SMTP:GALA=1 004SMTP_SERVER:GALA 005MLF:GALA --------------------------------------------------------------- J. Xech - Service Informatique - Université de PERPIGNAN 52 Avenue de Villeneuve, 66860 PERPIGNAN Cedex --------------------------------------------------------------- PYRENEUS CATALANES LES PYRENEES CATALANES - LES PYRENEES DU SOLEIL KIND REGARDS FROM THE SUNNY PYRENEES ================================================================================ Archive-Date: Fri, 15 Apr 1994 05:40:18 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 15 Apr 1994 05:39:03 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: XECH@NAXOS.UNICE.FR Message-ID: <0097CFAA.357D6C3D.44@ALPHA.WKU.EDU> Subject: RE: MX 4.0 on a mixed cluster ... "Jean Xech - S.I.U.P." writes: > >Hi, > >I have just installed MX 4.0 on a mixed cluster. >I stopped the MX 3.3 server on the VAX node (SYSPO) to start the >AXP server (node GALA), then run MX_startup.com(4.0) on all nodes. > >The messages are sent correctly, but received messages are not >distribued to the local VAX users and disappear from the queue ... > >Where is the mistake ???!!! A badly defined cluster logical ? > I saw nothing immediately wrong with your setup. The next step is to enable debugging for MX Router and MX Local; the debug logs will be created, by default, in MX_ROUTER_DIR: and MX_LOCAL_DIR:. $ define/sys/exec mx_router_debug true $ define/sys/exec mx_local_debug true Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 15 Apr 1994 09:44:54 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <199404151358.AA04841@interlock.jci.com> Date: Fri, 15 Apr 1994 08:39:27 -0600 From: arlen.walker@jci.com (Arlen P. Walker) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Help To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7BIT Jeff Finlay wrote: >help We're sorry, Jeff, but according to the General Omnipotence Act of the year 0000AC , you must be more specific. The Generally Omnipotent Deity [under the Uniform Information Monopoly Act of -7145 AC] requires that you expend some effort towards the identification of the nature of the help you seek. Have Fun, Arlen arlen.walker@jci.com --------------------------------------------------- This mail message contains 100% recycled electrons --------------------------------------------------- ================================================================================ Archive-Date: Fri, 15 Apr 1994 14:55:56 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: Digest not creating .input file Message-ID: <1994Apr15.150827@lucy.merrimack.edu> From: rand@lucy.merrimack.edu () Date: Fri, 15 Apr 94 15:08:27 EST Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU I'm setting up MX_DIGEST for the first time. I can't figure out why the SITE delivery agent isn't creating a .input file. When it kicks off the .LOG file looks like this: 15-APR-1994 12:55:34.32 Processing queue entry number 64. 15-APR-1994 12:55:40.13 DELIVER: Delivering... 15-APR-1994 12:55:40.20 DELIVER_FILE: Command: @MX_EXE:SITE_DELIVER - 15-APR-1994 12:55:40.25 DELIVER_FILE: "DIGEST" - 15-APR-1994 12:55:40.26 DELIVER_FILE: MX_ROOT:[SITE]SITE_MSG_31805CC0 _0097CFE7_24200573.TMP;1 - 15-APR-1994 12:55:40.33 DELIVER_FILE: MX_ROOT:[SITE]SITE_ADR_31805CC0 _0097CFE7_24200573.TMP;1 - 15-APR-1994 12:55:40.36 DELIVER_FILE: "" 15-APR-1994 12:55:43.73 DELIVER_FILE: Subprocess says: MX_DIGEST: Opening mes sage file.... 15-APR-1994 12:55:43.90 DELIVER_FILE: Subprocess says: MX_DIGEST: Opening rec ipients file.... 15-APR-1994 12:55:43.98 DELIVER_FILE: Subprocess says: MX_DIGEST: Using sende r address 15-APR-1994 12:55:44.07 DELIVER_FILE: Subprocess says: MX_DIGEST: Looking for DIGEST recipient.... 15-APR-1994 12:55:44.12 DELIVER_FILE: Subprocess says: MX_DIGEST: All done! 15-APR-1994 12:55:44.45 DELIVER_FILE: Subprocess says: EXIT:00000001 Presto! No .input file. Any ideas? And where'd the " Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097CFFA.3A8D7BBE.3@ALPHA.WKU.EDU> Subject: RE: Digest not creating .input file rand@lucy.merrimack.edu () writes: > >I'm setting up MX_DIGEST for the first time. I can't figure out why >the SITE delivery agent isn't creating a .input file. When it kicks off >the .LOG file looks like this: > [...] >15-APR-1994 12:55:44.07 DELIVER_FILE: Subprocess says: MX_DIGEST: Looking >for DIGEST recipient.... >15-APR-1994 12:55:44.12 DELIVER_FILE: Subprocess says: MX_DIGEST: All done! >15-APR-1994 12:55:44.45 DELIVER_FILE: Subprocess says: EXIT:00000001 > It didn't find the "@DIGEST" address in the recipient list. The address *has* to be {user}@DIGEST.SITE (actually, {x}@DIGEST{whatever}) for MAKE_DIGEST to find the recipient. Check your REWRITE_RULES, etc., to make sure that's what you're using. >Presto! No .input file. Any ideas? And where'd the "from? I never noticed that before I upgraded to 4.0. > From the MX V4.0 release notes: o All outgoing mailing list mail now shows the sender as ``owner-listname''. When mail is received for such an address, it is automatically delivered to the user defined to receive errors for that list (/ERRORS_TO on the MCP command DEFINE LIST). Like the listname-server support, that was added to follow the precedent (soon to be standard?) set by Eric Thomas's LISTSERV. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 15 Apr 1994 16:27:35 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kramer@fragile.termfrost.org (Mike Andrews) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: (possible FAQ/RTFM?) MX 4.0 and DNS Mail Exchange records Message-ID: Date: Fri, 15 Apr 1994 20:37:22 GMT To: MX-List@WKUVX1.WKU.EDU Powell HEUER writes: >kramer@fragile.termfrost.org (Mike Andrews) writes: >>... >>ANYWAY, my real problem: I don't seem to be able to mail to hosts specified >>in the DNS as Mail Exchange aliases (MX records). >>... >I've found Matt Madison's NSQUERY utility very useful to allow me to query my >nameservers to check proper operation. Yes, but it was happening with hosts outside my domain too. (for example, "aol.com") At any rate, I found a workaround: explicitly define NETLIB_NAMESERVERS to point to the local host (and one outside nameserver). Netlib is supposed to use the TCP/IP transport's logicals to figure that out, but since we were running named on the local host, we didn't have any logicals defined for that. Makes sense, but it's just slightly obscure. Anyway, it works now, so thanks for listening anyway. ;-) -- Mike Andrews "This guy's pretty bizarre, Gus." root@fragile.termfrost.org [NeXTmail OK] - Primus kramer@wittenberg.edu (school) kramer@mik.uky.edu (hometown) ================================================================================ Archive-Date: Sat, 16 Apr 1994 14:09:57 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: M.Czapski@unsw.EDU.AU (Michael Czapski, Manager, Information Systems) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Security issues Message-ID: Date: Thu, 14 Apr 1994 02:51:20 GMT To: MX-List@WKUVX1.WKU.EDU This site is just starting to connect to the Internet, and we are (justifiably or not) very concerned about security issues. I've taken a copy of MX, and we are very impressed with its functionality and ease of installation, but we need some assurance that the SMTP server in MX isn't going to introduce any holes in our 'firewall' system. SMTP will be the only traffic allowed into the hospital from the outside world, and is the only potential hole in the system. I guess the ultimate answer is to read the source (and I will), but I'd like to know whether anyone has experienced any breakins a-la the 'sendmail' bug (etc). -- Michael Czapski, Manager, Information Systems St.Vincent's Hospital Sydney Limited 83 Boundary Street, Darlinghurst, NSW, 2010, Australia Phone : +61 2 361-2403, Facsimile : +61 2 332-1316 ================================================================================ Archive-Date: Sun, 17 Apr 1994 09:33:22 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sun, 17 Apr 1994 16:29:02 CET From: Hans-Joachim Koch Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: sys_hjk@LISSY1.lif.de Message-ID: <0097D197.57972860.8@LISSY1.LIF.DE> Subject: SMTP accounting with _real_ To:-adress? First of all: I just made the update from 3.3 to 4.0-1 - NO PROBLEMS! Thanks to Hunter for this *very* *great* job! Just one question: the smtp accounting got one additional information. I hoped to see the REAL adress there, unfortunately it is equal to the smtp gateway. Is this intended or what could be wrong here? Our VAX loads all smtp mail to our Sparc gateway, which in turn is connected to the outside world. Therefore the smtp path has the last line for "*" with route=this_sparc. In the VAX smtp accounting I would like to see the _real_ target adress instead of always the route to host=this_sparc. Is it possible? Thank you. Hans. -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Mon, 18 Apr 1994 05:26:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 05:26:25 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D203.F0E2EDE9.2@ALPHA.WKU.EDU> Subject: RE: SMTP accounting with _real_ To:-adress? Hans-Joachim Koch writes: > >First of all: I just made the update from 3.3 to 4.0-1 - NO PROBLEMS! >Thanks to Hunter for this *very* *great* job! > Thanks. >Just one question: the smtp accounting got one additional information. I >hoped to see the REAL adress there, unfortunately it is equal to the smtp >gateway. Is this intended or what could be wrong here? > That's intended. For sites like yours, the new info is less than useful. For others, the "HOST" and "SENT-TO" info shows the target host and the actual host to which the message was sent. >In the VAX smtp accounting I would like to see the _real_ target adress >instead of always the route to host=this_sparc. Is it possible? > If you modify the sources, yes. In V4.0-1, no. There have been enough complaints about this that I guess I'll change that in MX V4.1. I had always thought of it as an invasion of users' privacy, but the MX Local accounting shows the same info, so I guess it's no big deal. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 18 Apr 1994 05:31:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 05:31:10 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D204.9AD7B6DB.24@ALPHA.WKU.EDU> Subject: RE: Security issues M.Czapski@unsw.EDU.AU (Michael Czapski, Manager, Information writes: > >This site is just starting to connect to the Internet, and we are >(justifiably or not) very concerned about security issues. > >I've taken a copy of MX, and we are very impressed with its >functionality and ease of installation, but we need some assurance >that the SMTP server in MX isn't going to introduce any holes in our >'firewall' system. SMTP will be the only traffic allowed into the >hospital from the outside world, and is the only potential hole in >the system. > >I guess the ultimate answer is to read the source (and I will), but I'd >like to know whether anyone has experienced any breakins a-la the >'sendmail' bug (etc). > I can assure you that there are no trap-doors, etc., in the MX SMTP Server. VMS is not UNIX, and problems like the "sendmail" bug can't happen in the MX SMTP Server. The worst case that I can think of is that someone could cause the SMTP Server to generate an access violation, which would cause it to terminate. MX SMTP Server does not have an interactive debug mode, nor does it have any ability to specify that any program be run by the server. It accepts a handful of RFC821 commands, and that's it. Note that there is no way to prevent people (inside or outside) from sending fake mail via SMTP. This is, of course, not a failing of MX---*all* SMTP servers can be used to fake mail. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 18 Apr 1994 08:48:54 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: SMTP accounting with _real_ To:-adress? Message-ID: <1994Apr18.133617.22028@oxvaxd> Date: 18 Apr 94 13:36:17 BST To: MX-List@WKUVX1.WKU.EDU In article <0097D197.57972860.8@LISSY1.LIF.DE>, Hans-Joachim Koch writes: > Just one question: the smtp accounting got one additional information. I > hoped to see the REAL adress there, unfortunately it is equal to the smtp > gateway. Is this intended or what could be wrong here? > > Our VAX loads all smtp mail to our Sparc gateway, which in turn is > connected to the outside world. Therefore the smtp path has the last > line for "*" with route=this_sparc. > > In the VAX smtp accounting I would like to see the _real_ target adress > instead of always the route to host=this_sparc. Is it possible? > > Thank you. > Hans. I asked about this during MX 4.0 beta testing, because we have a similar setup to you and it would be very useful to see the real target address in SMTP accounting records. Any chance of implementing it in 4.1, Hunter? Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Mon, 18 Apr 1994 10:16:13 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 10:45:20 EST From: "Wheeler, Daniel A" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU CC: manager@maple.lemoyne.edu Message-ID: <0097D230.7EB28180.29033@maple.lemoyne.edu> Subject: intermittent v3.3 smtp send problem? I've been getting intermittent (1/1000 messages per week) problems with SMTP mail transmissions with as yet no identified common ground. The messages appear to be sent correctly, once. They then appear to be processed again (under separate queue entries) but with the local node as the SMTP destination. After 10 tries the message bombs and the sender gets a postmaster response as included below. I've only been able to track a couple of these and am relatively sure that the messages are received correctly once, but the error messages are sure confusing my users. Any quick solutions or directions for me to search? --dan --------------------------------------------------------------------------- Dan Wheeler Senior Support Analyst & VMS System Manager Office of Information Systems, Le Moyne College, Syracuse NY 13214-1399 Phone 315.445.4565 (Home 315.655.8193) wheeler@maple.lemoyne.edu --------------------------------------------------------------------------- My config: vms 5.5-2/mx3.3/ucx 2.0 Examples and configs (MX and UCX hosts) below: This is long!!!! *************************************************************************** (Note: example is from a local mailing list but problem *not* limited to MLF) >From: MX%"Postmaster@maple.lemoyne.edu" 17-APR-1994 19:07:33.82 >To: MANAGER >CC: >Subj: SMTP delivery error > >Date: Sun, 17 Apr 1994 19:07:27 EST >From: SMTP delivery agent > >Note: this message was generated automatically. > >A problem occurred during SMTP delivery of your message. > >Error occurred sending to the following user(s): > (via STU.ADMIN.SUFCA.EDU): > %MX_SMTP-F-TRANSACTION_FAI, transaction failed > > Transcript: > Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:24 EST > Sent: HELO maple.lemoyne.edu > Rcvd: 250 Hello, maple.lemoyne.edu > Sent: MAIL FROM: > Rcvd: 250 MAIL command accepted. > Sent: RCPT TO: > Rcvd: 250 Recipient okay (at least in form) > Sent: DATA > Rcvd: 354 Start mail input; end with . > Rcvd: 554 Received too many times by this host. > Sent: QUIT > Rcvd: 221 maple.lemoyne.edu Service closing transmission channel >======================================================================== > >Message follows. > >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:07:20 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:07:15 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:07:09 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:07:04 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:06:58 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:06:53 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:06:47 EST >Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; Sun, 17 Apr 1994 19:06:42 EST >Received: by maple.lemoyne.edu (MX V3.3 VAX) id 26818; Sun, 17 Apr 1994 19:06:08 EST >Date: Sun, 17 Apr 1994 19:06:08 EST >Sender: Postmaster@maple.lemoyne.edu >Errors-To: Postmaster@maple.lemoyne.edu >Warnings-To: <> >From: MX mailing list processor >To: user_name@STU.ADMIN.SUFCA.EDU >Subject: Subscription to mailing list jesu_net > >You have been added to mailing list jesu_net@maple.lemoyne.edu. > >Further administrative requests regarding this list should be sent to > <...message text removed...> > >(This message was generated automatically.) >-------------------------------------------------------------------------------- >Return-Path: <> >To: *************************************************************************** The SMTP DEBUG Log entries look like: The first (the sucessful) entry: >17-APR-1994 19:05:41.99 Processing queue entry number 26815 on node NEWKID >17-APR-1994 19:05:42.19 Recipient: , route=STU.ADMIN.USFCA.EDU >17-APR-1994 19:05:42.19 SMTP_SEND: looking up host name STU.ADMIN.USFCA.EDU >17-APR-1994 19:05:43.23 SMTP_SEND: Attempting to start session with STU.ADMIN.USFCA.EDU [138.202.3.2] >17-APR-1994 19:05:43.82 SMTP_SEND: Connected >17-APR-1994 19:05:46.54 SMTP_SEND: Rcvd: 220 STU.ADMIN.USFCA.EDU TGV MultiNet V3.2 Rev C SMTP service ready at Sun, 17 Apr 1994 16:04:56 -0700 (PDT) >17-APR-1994 19:05:46.56 SMTP_SEND: Sent: HELO maple.lemoyne.edu >17-APR-1994 19:05:47.58 SMTP_SEND: Rcvd: 250 STU.ADMIN.USFCA.EDU ; Hello maple.lemoyne.edu, pleased to meet you. >17-APR-1994 19:05:47.58 SMTP_SEND: Sent: MAIL FROM: >17-APR-1994 19:05:48.37 SMTP_SEND: Rcvd: 250 OK >17-APR-1994 19:05:48.37 SMTP_SEND: Sent: RCPT TO: >17-APR-1994 19:05:50.62 SMTP_SEND: Rcvd: 250 ... ok - delivered as >17-APR-1994 19:05:50.63 SMTP_SEND: Sent: DATA >17-APR-1994 19:05:51.24 SMTP_SEND: Rcvd: 354 Start mail input; end with . >17-APR-1994 19:05:51.24 SMTP_SEND: Sent: Received: by maple.lemoyne.edu (MX V3.3 VAX) id 26814; Sun, 17 Apr 1994 >17-APR-1994 19:05:51.24 SMTP_SEND: Sent: 19:05:40 EST >17-APR-1994 19:05:51.25 SMTP_SEND: Sent: Date: Sun, 17 Apr 1994 19:05:35 EST >17-APR-1994 19:05:51.25 SMTP_SEND: Sent: From: "RAY user, S.J." >17-APR-1994 19:05:51.25 SMTP_SEND: Sent: To: user_name@STU.ADMIN.USFCA.EDU >17-APR-1994 19:05:51.26 SMTP_SEND: Sent: Message-ID: <0097D1AD.366A69C0.26814@maple.lemoyne.edu> >17-APR-1994 19:05:51.26 SMTP_SEND: Sent: Subject: RE: Virtual Recroom >17-APR-1994 19:05:51.26 SMTP_SEND: Sent: >17-APR-1994 19:05:51.26 SMTP_SEND: Sent: >17-APR-1994 19:05:51.31 SMTP_SEND: Sent: . >17-APR-1994 19:05:51.31 SMTP_SEND: will wait 00:10:30.00 for reply. >17-APR-1994 19:05:54.01 SMTP_SEND: Rcvd: 250 OK ; Job SMTP-NETMAIL (queue SMTP_STU, entry 294) started on SMTP_STU >17-APR-1994 19:05:54.02 SMTP_SEND: Sent: QUIT >17-APR-1994 19:05:55.07 SMTP_SEND: Rcvd: 221 STU.ADMIN.USFCA.EDU TGV MultiNet V3.2 Rev C SMTP service complete at Sun, 17 Apr 1994 16:05:05 -0700 (PDT) >17-APR-1994 19:05:55.30 Recipient status=00000001 for >17-APR-1994 19:05:55.34 Entry now completely processed, no retries needed. >17-APR-1994 19:05:55.38 *** End of processing pass *** The final (rejected) entry: >17-APR-1994 19:07:24.11 Processing queue entry number 26839 on node NEWKID >17-APR-1994 19:07:24.34 Recipient: , route=STU.ADMIN.SUFCA.EDU >17-APR-1994 19:07:24.34 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU >17-APR-1994 19:07:24.51 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] >17-APR-1994 19:07:24.54 SMTP_SEND: Connected >17-APR-1994 19:07:24.81 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:24 EST >17-APR-1994 19:07:24.89 SMTP_SEND: Sent: HELO maple.lemoyne.edu >17-APR-1994 19:07:24.95 SMTP_SEND: Rcvd: 250 Hello, maple.lemoyne.edu >17-APR-1994 19:07:24.95 SMTP_SEND: Sent: MAIL FROM: >17-APR-1994 19:07:25.38 SMTP_SEND: Rcvd: 250 MAIL command accepted. >17-APR-1994 19:07:25.38 SMTP_SEND: Sent: RCPT TO: >17-APR-1994 19:07:25.40 SMTP_SEND: Rcvd: 250 Recipient okay (at least in form) >17-APR-1994 19:07:25.41 SMTP_SEND: Sent: DATA >17-APR-1994 19:07:25.79 SMTP_SEND: Rcvd: 354 Start mail input; end with . >17-APR-1994 19:07:25.79 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.79 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:07:20 EST >17-APR-1994 19:07:25.79 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.79 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:07:15 EST >17-APR-1994 19:07:25.80 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:07:09 EST >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:07:04 EST >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:06:58 EST >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:06:53 EST >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:06:47 EST >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Received: from maple.lemoyne.edu by maple.lemoyne.edu (MX V3.3 VAX) with SMTP; >17-APR-1994 19:07:25.81 SMTP_SEND: Sent: Sun, 17 Apr 1994 19:06:42 EST >17-APR-1994 19:07:25.82 SMTP_SEND: Sent: Received: by maple.lemoyne.edu (MX V3.3 VAX) id 26818; Sun, 17 Apr 1994 >17-APR-1994 19:07:25.82 SMTP_SEND: Sent: 19:06:08 EST >17-APR-1994 19:07:25.84 SMTP_SEND: Sent: Date: Sun, 17 Apr 1994 19:06:08 EST >17-APR-1994 19:07:25.84 SMTP_SEND: Sent: Sender: Postmaster@maple.lemoyne.edu >17-APR-1994 19:07:25.84 SMTP_SEND: Sent: Errors-To: Postmaster@maple.lemoyne.edu >17-APR-1994 19:07:25.84 SMTP_SEND: Sent: Warnings-To: <> >17-APR-1994 19:07:25.85 SMTP_SEND: Sent: From: MX mailing list processor >17-APR-1994 19:07:25.86 SMTP_SEND: Sent: To: user_name@STU.ADMIN.SUFCA.EDU >17-APR-1994 19:07:25.86 SMTP_SEND: Sent: Subject: Subscription to mailing list jesu_net >17-APR-1994 19:07:25.86 SMTP_SEND: Sent: >17-APR-1994 19:07:25.98 SMTP_SEND: Sent: (This message was generated automatically.) >17-APR-1994 19:07:26.00 SMTP_SEND: Sent: . >17-APR-1994 19:07:26.00 SMTP_SEND: will wait 00:10:30.00 for reply. >17-APR-1994 19:07:26.71 SMTP_SEND: Rcvd: 554 Received too many times by this host. >17-APR-1994 19:07:26.71 SMTP_SEND: Sent: QUIT >17-APR-1994 19:07:26.72 SMTP_SEND: Rcvd: 221 maple.lemoyne.edu Service closing transmission channel >17-APR-1994 19:07:26.82 SMTP send failed, sts=0C2680AC, sts2=0C2680AC >17-APR-1994 19:07:26.82 Recipient status=0C2680AC for >17-APR-1994 19:07:29.06 Entry now completely processed, no retries needed. >17-APR-1994 19:07:29.23 *** End of processing pass *** ****************************** SMTP DEBUG Logs headers for multiple entries: DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1723 17-APR-1994 19:07:24.11 Processing queue entry number 26839 on node NEWKID 17-APR-1994 19:07:24.34 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:24.34 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:24.51 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:07:24.54 SMTP_SEND: Connected 17-APR-1994 19:07:24.81 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:24 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1722 17-APR-1994 19:07:18.35 Processing queue entry number 26837 on node NEWKID 17-APR-1994 19:07:18.59 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:18.59 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:18.80 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:07:18.82 SMTP_SEND: Connected 17-APR-1994 19:07:19.09 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:18 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1721 17-APR-1994 19:07:13.19 Processing queue entry number 26834 on node NEWKID 17-APR-1994 19:07:13.48 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:13.48 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:13.66 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:07:13.68 SMTP_SEND: Connected 17-APR-1994 19:07:13.87 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:13 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1720 17-APR-1994 19:07:07.73 Processing queue entry number 26832 on node NEWKID 17-APR-1994 19:07:08.03 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:08.03 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:08.32 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:07:08.33 SMTP_SEND: Connected 17-APR-1994 19:07:08.47 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:08 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1719 17-APR-1994 19:07:03.07 Processing queue entry number 26830 on node NEWKID 17-APR-1994 19:07:03.33 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:03.33 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:07:03.54 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:07:03.55 SMTP_SEND: Connected 17-APR-1994 19:07:03.66 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:07:03 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1717 17-APR-1994 19:06:56.78 Processing queue entry number 26828 on node NEWKID 17-APR-1994 19:06:56.93 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:56.93 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:57.26 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:06:57.28 SMTP_SEND: Connected 17-APR-1994 19:06:57.44 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:06:57 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1716 17-APR-1994 19:06:50.92 Processing queue entry number 26826 on node NEWKID 17-APR-1994 19:06:51.20 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:51.20 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:51.64 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:06:51.66 SMTP_SEND: Connected 17-APR-1994 19:06:51.90 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:06:51 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1715 17-APR-1994 19:06:45.13 Processing queue entry number 26824 on node NEWKID 17-APR-1994 19:06:45.46 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:45.46 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:46.59 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:06:46.62 SMTP_SEND: Connected 17-APR-1994 19:06:46.74 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:06:46 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1714 17-APR-1994 19:06:11.32 Processing queue entry number 26819 on node NEWKID 17-APR-1994 19:06:11.79 Recipient: , route=STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:11.79 SMTP_SEND: looking up host name STU.ADMIN.SUFCA.EDU 17-APR-1994 19:06:42.26 SMTP_SEND: Attempting to start session with lemoyne.edu. [192.231.122.100] 17-APR-1994 19:06:42.28 SMTP_SEND: Connected 17-APR-1994 19:06:42.34 SMTP_SEND: Rcvd: 220 maple.lemoyne.edu MX V3.3 VAX SMTP server ready at Sun, 17 Apr 1994 19:06:42 EST ****************************** DISK$APPS:[MANAGER.TEMPORARY]SMTP_DEBUG.LOG;1713 17-APR-1994 19:05:41.99 Processing queue entry number 26815 on node NEWKID 17-APR-1994 19:05:42.19 Recipient: , route=STU.ADMIN.USFCA.EDU 17-APR-1994 19:05:42.19 SMTP_SEND: looking up host name STU.ADMIN.USFCA.EDU 17-APR-1994 19:05:43.23 SMTP_SEND: Attempting to start session with STU.ADMIN.USFCA.EDU [138.202.3.2] 17-APR-1994 19:05:43.82 SMTP_SEND: Connected 17-APR-1994 19:05:46.54 SMTP_SEND: Rcvd: 220 STU.ADMIN.USFCA.EDU TGV MultiNet V3.2 Rev C SMTP service ready at Sun, 17 Apr 1994 16:04:56 -0700 (PDT) *************************************************************************** Configuration file: MX_DEVICE:[MX]MX_CONFIG.MXCFG;72 MX version id is: MX V3.3 VAX Mailing lists: Name: odcase-l Owner: "oconnor@MAPLE.LEMOYNE.EDU" Reply-to: List, NOSender Archive: MLF_ROOT:[ODCASE-L] Add message: MLF_ROOT:[ODCASE-L]ODCASE.WELCOME Description: Organizational Development - CASE Western Reserve University Errors-to: oconnor@maple.lemoyne.edu Strip header: NOReceived Private list: No Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWED,WORLD:WE) Name: jesu_net Owner: "user@MAPLE.LEMOYNE.EDU" "manager@MAPLE.LEMOYNE.EDU" Reply-to: List, NOSender Archive: MLF_ROOT:[ARCHIVES.JESU_NET] Description: Jesuit General Chatter Newsgroup Errors-to: user@maple.lemoyne.edu Strip header: NOReceived Private list: Yes Protection: (SYSTEM:RWED,OWNER:RWED,GROUP:RWD,WORLD) Address-rewriting rules: Rewrite "<{u}@lemoyne>" => "<{u}@lemoyne>" Rewrite "<{u}@lemoyne.BITNET>" => "<{u}@lemoyne>" Rewrite "<{u}@maple.lemoyne.edu>" => "<{u}@lemoyne>" Rewrite "<{folder}@BULLETIN>" => "<{folder}@BULLETIN>" Rewrite "<@{stuff}:{user}@{host}.UUCP>" => "<{user}%{host}%uunet.uu.net@INTERBIT.BITNET>" Rewrite "<{user}@{host}.UUCP>" => "<{user}%{host}%uunet.uu.net@INTERBIT.BITNET>" Rewrite "<@{stuff}:{user}@{host}.CSNET>" => "<{user}%{host}.CSNET%relay.cs.net@INTERBIT.BITNET>" Rewrite "<{user}@{host}.CSNET>" => "<{user}%{host}.CSNET%relay.cs.net@INTERBIT.BITNET>" Rewrite "<@{route}:{user}@{host}.BITNET>" => "<{user}@{host}.BITNET>" Rewrite "<{user}@{host}.BITNET>" => "<{user}@{host}.BITNET>" Rewrite "<@{route}:{user}@{host}>" => "<{user}%{host}@INTERBIT.BITNET>" Rewrite "<{U}@SOCRATES>" => "<{U}@LEMOYNE>" Rewrite "<{U}@MAPLE>" => "<{U}@LEMOYNE>" Rewrite "<{U}@admin1>" => "<{U}@oak>" Rewrite "<{U}@wpgate>" => "" Rewrite "<{U}%wpgate@lemoyne>" => "" Domain-to-path mappings: Domain="[192.231.122.100]", Path=Local Domain="maple", Path=Local Domain="lemoyne", Path=Local Domain="lemoyne.edu", Path=Local Domain="maple.lemoyne.edu", Path=Local Domain="BULLETIN", Path=Site Domain="oak", Path=SMTP Domain="bamboo", Path=SMTP Domain="lemoyne.bitnet", Path=Local Domain="socrates", Path=Local Domain="lmccsc", Path=Local Domain="*.bitnet", Path=Jnet Domain="*.uucp", Path=SMTP, Route="uunet.uu.net" Domain="*.*", Path=SMTP File servers: Name: jesu_fs, Manager: user@maple.lemoyne.edu Root: NEWKID$DKA200:[MX.MAILING_LISTS.ARCHIVES.] Linked to mailing list: jesu_net Delay threshold: 0 Send period: 17:00 - 08:00 Daily limits: Server: 0 Host: 0 User: 0 SMTP agent settings: Retry interval: 0 00:15:00.00 Maximum number of retries: 96 Number of DNS failure retries: 12 Accounting: enabled Default router: (none) LOCAL agent settings: DECnet delivery retry interval: 0 00:05:00.00 Maximum number of retries: 96 Accounting enabled. Multiple VMS Mail From: addresses allowed. Top headers: FROM,DATE,REPLY_TO Bottom headers: SENDER,TO,RESENT_TO,CC,BCC,MESSAGE_ID,RESENT_MESSAGE_ID, IN_REPLY_TO,REFERENCES,KEYWORDS,ENCRYPTED,RECEIVED,RESENT_REPLY_TO, RESENT_FROM,RESENT_SENDER,RESENT_DATE,RETURN_PATH,OTHER ROUTER agent settings: Automatic percent-hack handling: enabled JNET agent settings: Automatic percent-hack handling: disabled BSMTP replies: disabled Accounting: enabled Lenient about gatewaying mail: yes Primary mailer username: MXMAILER DECnet_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. SITE agent settings: Retry interval: 0 00:01:00.00 Maximum number of retries: 96 X25_SMTP agent settings: Retry interval: 0 00:30:00.00 Maximum number of retries: 96 Accounting disabled. *************************************************************************** UCX SHOW HOSTS: LOCAL database Host address Host name 192.34.82.2 192.231.122.20 ASH, ash 192.231.122.120 BAMBOO, bamboo 192.33.4.10 DNSP, dnsp 192.35.82.2 DNSS, dnss 192.77.176.110 JANE 127.0.0.1 LOCALHOST, localhost 192.231.122.10 OAK, oak, admin1, ADMIN1 192.77.176.100 OLDVAX 192.231.122.1 PINE, pine, porky 192.231.122.111 PRINTER, printer 192.231.122.100 maple.lemoyne.edu, maple, socrates, MAPLE, MAPLE.LEMOYNE.EDU 192.77.176.150 plato, PLATO, LMCCSC, lmccsc, MVAX ================================================================================ Archive-Date: Mon, 18 Apr 1994 11:28:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 11:24:08 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D235.EA0C8DE0.23@uwwvax.uww.edu> Subject: mx4.0 and a question We are site hadling 4000-6000 mail messages a day which brought MX3.3 to it knees. MX4.0 is handling the load very well and no one should hesitate to install it. Question: I would like to enforce quotas on a users MAIL. Can it be done? What the implications? Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Mon, 18 Apr 1994 12:36:05 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 11:30:59 MDT From: Bill Dailey (303) 490-8324 Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list%wkuvx1.bitnet@ulkyvm.louisville.edu CC: dailey@gpsrv1.gpsr.colostate.edu Message-ID: <0097D236.DF2F6040.6835@gpsrv1.gpsr.colostate.edu> Subject: UCX question Hi MX-list Sorry for asking an UCX question on the MX-list, but here goes. I installed Open VMS 6.0, and UCX 2.0E over the weekend, when I startup UCX I get a error stating that BGDRIVER.EXE has a version mismatch with OPEN VMS 6.0. Is Digital still using UCX with OPEN VMS 6.0? Has anyone else had this problem? Thanks William J. Dailey, GPSR Systems Analyst ------------------------------------------------------------------------------ USDA-ARS-NPA Great Plains Systems Res. TEL: 303-490-8324 P.O. Box E FAX: 303-490-8310 303 South Howes Rm. 227 FTS2000: A03RLGPSR Fort Collins, CO 80522 INTERNET: dailey@gpsrv1.gpsr.colostate.edu ------------------------------------------------------------------------------ ================================================================================ Archive-Date: Mon, 18 Apr 1994 13:00:16 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 12:59:02 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D243.2C30C69D.27@ALPHA.WKU.EDU> Subject: RE: UCX question Bill Dailey (303) 490-8324 writes: > >I installed Open VMS 6.0, and UCX 2.0E over the weekend, when I startup >UCX I get a error stating that BGDRIVER.EXE has a version mismatch >with OPEN VMS 6.0. > Have you tried the new REGISTER facility? I've never done it, but it sounds like it would solve the problem. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 18 Apr 1994 13:02:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 13:00:21 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D243.5AD5ABCB.31@ALPHA.WKU.EDU> Subject: RE: mx4.0 and a question hunterl@uwwvax.uww.edu writes: > >We are site hadling 4000-6000 mail messages a day which brought MX3.3 >to it knees. MX4.0 is handling the load very well and no one should >hesitate to install it. > Good deal! 8-) >Question: I would like to enforce quotas on a users MAIL. Can it be >done? What the implications? > If you take EXQUOTA away from the username under which MX Local runs, that should do it, as long as there are no quotas on the MX_LOCAL_DIR: and MX_FLQ_DIR: disks. I think---I've never done it, so I don't know for sure if there will be any problems from doing that. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Mon, 18 Apr 1994 13:07:58 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: RE: Digest not creating .input file Message-ID: <1994Apr18.132303@lucy.merrimack.edu> From: rand@lucy.merrimack.edu () Date: Mon, 18 Apr 94 13:23:03 EST Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097CFFA.3A8D7BBE.3@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: >rand@lucy.merrimack.edu () writes: >> >>I'm setting up MX_DIGEST for the first time. I can't figure out why >>the SITE delivery agent isn't creating a .input file. >It didn't find the "@DIGEST" address in the recipient list. The address >*has* to be {user}@DIGEST.SITE (actually, {x}@DIGEST{whatever}) for >MAKE_DIGEST to find the recipient. Check your REWRITE_RULES, etc., to make >sure that's what you're using. Ah, once I compensated for my habit of downcasing everthing, it worked :-) Thanks, rand ================================================================================ Archive-Date: Mon, 18 Apr 1994 13:22:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 11:18:41 MST From: kish@DRWHO.IAC.HONEYWELL.COM Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D235.27517725.26383@DRWHO.IAC.HONEYWELL.COM> Subject: RE: UCX question RE BGDRIVER MISMATCH: Ther is a driver command procedure which I believe is SYS$COMMON:[SYSMGR]UCX$REGISTER.COM It was late at night when i called the "springs and I forgot to put it in my log. But I am fairly shure... Karl KISH@DRWHO.IAC.HONEYWELL.COM ================================================================================ Archive-Date: Mon, 18 Apr 1994 14:22:23 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 94 14:15:15 C*T From: Rick Stacks Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: RE: mx4.0 and a question To: mx-list@wkuvx1.wku.edu Message-ID: <0097D24DD2227F60.20201F05@adpce.lrk.ar.us> Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT > >hunterl@uwwvax.uww.edu writes: >> >>Question: I would like to enforce quotas on a users MAIL. Can it be >>done? What the implications? >> "Hunter Goatley, WKU" writes: >If you take EXQUOTA away from the username under which MX Local runs, >that should do it, as long as there are no quotas on the MX_LOCAL_DIR: >and MX_FLQ_DIR: disks. I think---I've never done it, so I don't know >for sure if there will be any problems from doing that. > I think I need some clarification on the question... Is the original intent to limit the amount of disk space used by an individual? OR to limit the number of email messages received by an individual? I believe the answer given above by Hunter G. will work if you are trying to limit the disk usage. Trying to limit the number of email messages may require changes to the MX source code -- again this will have to be answered by Hunter G.. Sorry for the misunderstanding; but I could not tell if the answer given actually fit the question posed... -- Rick +----------------------------------------------------------------------------+ | Rick Stacks, Sr. Programmer Analyst | voice: 501-570-2174 | | Ark Dept Pollution Control & Ecology | fax: 501-562-4632 | | 8001 National Dr. / POB 8913 | email: stacks@adpce.lrk.ar.us | | Little Rock, AR 72219 USA | | |--------------------------------------+-------------------------------------| |- They that give up essential liberty to obtain a little temporary safety --| |- deserve neither liberty nor safety -- Benjamin Franklin, 1759 --| ================================================================================ Archive-Date: Mon, 18 Apr 1994 14:48:43 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <0097D252.5565B6F4.15@ALPHA.WKU.EDU> Return-Path: Date: Mon, 18 Apr 1994 15:19:00 -0400 (EDT) From: "Patrick Perini (614)466-0335" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: UCX question To: owner-mx-list MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Regarding the UCX and VMS 6.0 concerns, you should note that VMS 6.0 requires CSCPAT_1113010 for UCX. This can be downloaded from DEC's DSNLINK service (a "freebie" if you have a support contract and a spare modem and phone line). ================================================================================ Archive-Date: Mon, 18 Apr 1994 15:14:49 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 15:03:35 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D254.922FC8C0.145@uwwvax.uww.edu> Subject: Re: RE: mx4.0 and a question => >hunterl@uwwvax.uww.edu writes: => >> => >>Question: I would like to enforce quotas on a users MAIL. Can it be => >>done? What the implications? => >> => => "Hunter Goatley, WKU" writes: => => >If you take EXQUOTA away from the username under which MX Local runs, => >that should do it, as long as there are no quotas on the MX_LOCAL_DIR: => >and MX_FLQ_DIR: disks. I think---I've never done it, so I don't know => >for sure if there will be any problems from doing that. => > => => I think I need some clarification on the question... Is the original => intent to limit the amount of disk space used by an individual? OR to limit => the number of email messages received by an individual? I believe the => answer given above by Hunter G. will work if you are trying to limit the => disk usage. Trying to limit the number of email messages may require => changes to the MX source code -- again this will have to be answered by => Hunter G.. => => Sorry for the misunderstanding; but I could not tell if the answer given => actually fit the question posed... => => -- Rick Hunter is correct, I want to limit the disk space to established allocation Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Mon, 18 Apr 1994 15:19:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: system@faxcsl.dcrt.nih.gov (Ramon L. Tate) Subject: Public Key Digital Signatures in the works - Please!? Message-ID: <1994Apr18.194052.4785@alw.nih.gov> Reply-To: MX-List@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 19:40:52 GMT To: MX-List@WKUVX1.WKU.EDU Just a little something for the wish list - digital signatures. Now that RSA has released the tools for doing this for free, are there plans to put this into MX? We would love to see it.... ------------------------------------------------------------------------------- Ramon L. Tate | "Is it not strange that sheeps' guts should hale DSB, DCRT | souls out of men's bodies?" Nat.Insts. of Health | - Act II, scene 3, Much Ado About Nothing Bethesda, MD 20892 | Wm. Shakspere tate@faxcsl.dcrt.nih.gov | ================================================================================ Archive-Date: Mon, 18 Apr 1994 16:46:50 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 18 Apr 1994 17:40:35 EDT From: "Jonathan E. Hardis" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: hardis@garnet.nist.gov Message-ID: <0097D26A.81566C00.9539@garnet.nist.gov> Subject: RE: (possible FAQ/RTFM?) MX 4.0 and DNS Mail Exchange records > I don't seem to be able to mail to hosts specified in the DNS as Mail > Exchange aliases (MX records). > Any ideas, or am I just stupid and missing something really obvious in > the docs? You didn't mention which IP transport you were using. This strikes me as an IP driver level problem, not an MX problem. - Jonathan ================================================================================ Archive-Date: Tue, 19 Apr 1994 06:19:46 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 07:11:00 -0400 (EDT) From: "Patrick Perini (614)466-0335" Reply-To: MX-List@WKUVX1.WKU.EDU Subject: VMS 6.0 and UCX 2.0D/E To: mx-list@wkuvx1.wku.edu Message-ID: <01HBCN3HBNAU002HEF@mr.ohio.gov> MIME-Version: 1.0 Content-Type: MULTIPART/MIXED; BOUNDARY="Boundary (ID 2c/vsN5HsA4hdKIF1FS4/A)" --Boundary (ID 2c/vsN5HsA4hdKIF1FS4/A) Content-type: TEXT/PLAIN; CHARSET=US-ASCII Is this readable? --Boundary (ID 2c/vsN5HsA4hdKIF1FS4/A) Content-type: MESSAGE/RFC822 Date: Tue, 19 Apr 1994 07:09:00 EDT From: "Patrick Perini"@mr.ohio.gov Subject: ucX Content-type: TEXT/PLAIN; CHARSET=US-ASCII Posting-date: Tue, 19 Apr 1994 00:00:00 EDT A1-format: A1-type: DOCUMENT Regarding the UCX and VMS 6.0 concerns, you should note that VMS 6.0 requires CSCPAT_1113010 for UCX 2.0D (and I assume for 2.0E also). This can be downloaded from DEC's DSNLINK service (a "freebie" if you have a support contract and a spare modem and phone line). --Boundary (ID 2c/vsN5HsA4hdKIF1FS4/A)-- ================================================================================ Archive-Date: Tue, 19 Apr 1994 08:10:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: mcscs1cfsi@zippy.dct.ac.uk (Herbie Akira) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Mail-list server., Message-ID: <1994Apr19.140110.2491@zippy.dct.ac.uk> Date: 19 Apr 94 14:01:10 +0100 To: MX-List@WKUVX1.WKU.EDU Does anyone know where I can get a copy of a mailing-list server programme??? -- | | | _) \ | _) Nothing is __ | -_) _| _ \ | -_) _ \ | / | _| _` | All is True _| _\___|_| _.__/_\___| _/ _\_|\_\_|_| \__,_| permitted Herbie@zippy.dct.ac.uk ================================================================================ Archive-Date: Tue, 19 Apr 1994 09:36:31 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <199404191346.AA10421@interlock.jci.com> Date: Tue, 19 Apr 1994 09:29:28 -0500 (CDT) From: arlen.walker@jci.com (Arlen P. Walker) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Mail-list server., To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7BIT >Does anyone know where I can get a copy of a mailing-list server programme??? > Certainly. ftp.wku.edu, look for MX 4.0. ;{>} Have Fun, Arlen arlen.walker@jci.com --------------------------------------------------- This mail message contains 100% recycled electrons --------------------------------------------------- ================================================================================ Archive-Date: Tue, 19 Apr 1994 10:25:10 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 10:56:55 -0400 (EDT) From: PERINI@pucvms.decnet.ohio.gov Reply-To: MX-List@WKUVX1.WKU.EDU Subject: UCX and VMS6.0 To: mx-list@wkuvx1.wku.edu Message-ID: <01HBCUT3QSZ6002FEQ@gosip.net.ohio.gov> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Content-Transfer-Encoding: 7BIT Regarding the UCX and VMS 6.0 concerns, VMS 6.0 requires CSCPAT_1113010 for UCX 2.0D (and I assume for 2.0E also). This can be downloaded from DEC's DSNLINK service (a "freebie" if you have a support contract and a spare modem and phone line). ================================================================================ Archive-Date: Tue, 19 Apr 1994 13:56:53 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: torobin@svs6.svh.unsw.edu.au (Robin Garner) Subject: RE: UCX question Message-ID: <1994Apr19.045800.417@usage.csd.unsw.OZ.AU> Reply-To: MX-List@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 04:58:00 GMT To: MX-List@WKUVX1.WKU.EDU In article <0097D243.2C30C69D.27@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: >Bill Dailey (303) 490-8324 writes: >> >>I installed Open VMS 6.0, and UCX 2.0E over the weekend, when I startup >>UCX I get a error stating that BGDRIVER.EXE has a version mismatch >>with OPEN VMS 6.0. >> >Have you tried the new REGISTER facility? I've never done it, but it >sounds like it would solve the problem. > In fact, the release notes tell you to run SYS$MANAGER:UCX$REGISTER.COM, which registers both UCX$INETACP and BGDRIVER. -Robin ================================================================================ Archive-Date: Tue, 19 Apr 1994 14:08:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU To: mail-mx-list@coranto.ucs.mun.ca From: randy@kean.ucs.mun.ca Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: FLQ Manager process very slow Date: 19 Apr 94 16:26:02 -0330 NST Message-ID: <1994Apr19.162602.1@leif> References: <0097CE3D.8E9110DB.13@ALPHA.WKU.EDU> In article <0097CE3D.8E9110DB.13@ALPHA.WKU.EDU>, goathunter@ALPHA.WKU.EDU (Hunte r Goatley, WKU) writes: > daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) writes: >> >>Hi, >> >>Is anybody running the MX FLQ Manager that came with MX 4.0? On our system it >>seems to take ages to get rid of FINISHed entries and their associated files. >>Anybody else seen this? >> > The MX FLQ Manager uses the exact same code as the MX Router for > finding and deleting entries. If the MX disk is heavily I/O bound, > then the deletion of the files can be slowed down quite a bit. That's > one of the downsides to the new queue file: it's so efficient, the > agents can do more searching than before, which can increase the I/O > load on the disk. > > That's one reason the MX FLQ Manager can be useful---without it, one > of your Routers would be delayed from routing during that time. > > You can also define the following FLQ logicals to cause scans to > happen more frequently and to delete FIN entries sooner: > > MX_FLQ_MGR_WAKEUP_INTERVAL Defaults to "0 00:02:00" > Amount of time it sleeps before waking up > > MX_FLQ_CHECK_WAIT Defaults to "0 00:10:00" > Amount of time that must elapse before it'll actually > scan for entries > > MX_FLQ_PURGE_WAIT Defaults to "0 00:15:00" > Amount of time a FIN entry will be left in the queue > > You could try changing the MX_FLQ_CHECK_WAIT to "0 00:01:00", which > will cause it to scan every time it wakes up.... > Since installing the released V4, I've had a problem keeping the queue directories clean. The Beta-test software worked ok, but now it seems that the flq_manager process isn't cleaning up the Finished files. I'm running out of queue entry space daily (10,000 entries). I've set the logicals as suggested above, but the debug log file keeps saying : 19-APR-1994 15:32:05.66 %FLQ_CLEANUP, time to check for cleanups 19-APR-1994 15:32:05.71 %FLQ_CLEANUP, time to make a purge pass 19-APR-1994 15:32:05.94 %FLQ_CLEANUP, PURGE: final FLQ_SEARCH status =0001827A 19-APR-1994 15:32:05.99 %FLQ_CLEANUP, EXPIRE: final FLQ_SEARCH status =0001827A and 19-APR-1994 15:30:17.03 %FLQ_CLEANUP: Checking lock, resnam= FLQ_LOCK_xxxx_RQC 19-APR-1994 15:30:17.06 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. Is this a problem only for high-volume mail sites, or have I done something stupid ?? I'm using the patched V4.0-1 MX release, by the way. -- Randy Dodge, Manager Technical Support Group, Computing & Communications Memorial University, St. John's, Newfoundland Canada randy@kean.ucs.mun.ca ================================================================================ Archive-Date: Tue, 19 Apr 1994 14:54:36 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 14:50:35 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D31B.EBEE86DB.1@ALPHA.WKU.EDU> Subject: RE: FLQ Manager process very slow randy@kean.ucs.mun.ca writes: > >Since installing the released V4, I've had a problem keeping the queue >directories clean. The Beta-test software worked ok, but now it seems >that the flq_manager process isn't cleaning up the Finished files. I'm >running out of queue entry space daily (10,000 entries). > Maybe one of your Routers is still doing it. The MX FLQ Manager process *has* to be started before the Router processes in order for it to do the work (I'll try to address that in V4.1). You might stop the router and FLQ manager and restart them by hand to see if that helps. >Is this a problem only for high-volume mail sites, or have I done something >stupid ?? I'm using the patched V4.0-1 MX release, by the way. > You are the third site that's reported similar problems (all extra-heavy duty sites). Setting the logicals appears to have helped the other two. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Tue, 19 Apr 1994 17:13:02 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 00:02:42 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D369.0D27F222.375@uni-lj.si> Subject: RE: Digest not creating .input file Whenever something shows up in a list, I get hit somehow ;-) From MX_DEVICE:[MX]MX_DELIVER_DIGESTS.LOG: Digest name to process is FRACTAL.... $ mx_make_digest FRACTAL %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC =000713E0, PSL=03C00004 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 201C0000 Name = 0000000C 00000000 00000000 201C0000 00000000 00000007 000713E0 7FEBAD74 03C00004 000017FD 00085130 00085BD3 00000200 00000001 Register dump R0 = 00000000 R1 = 00085BD3 R2 = 00000000 R3 = 00000000 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R8 = 7FFECA4C R9 = 7FFECC54 R10= 7FFED7D4 R11= 7FFE2BDC AP = 7FEBACF8 FP = 7FEBACB8 SP = 7FEBAD34 PC = 000713E0 PSL= 03C00004 $ digest_file = f$search("MX_SITE_DIR:FRACTAL-DIGEST.OUTPUT") $ if digest_file.nes."" $ else say "No OUTPUT file found!!!" No OUTPUT file found!!! The start od FRACTAL-DIGEST.PROCESS looks like: From-MX-SITE--- Resent-Date: Sun, 17 Apr 1994 05:12:57 +0100 Resent-From: Resent-To: Received: by uni-lj.si (MX V4.0 VAX) with SITE; Sun, 17 Apr 1994 05:12:45 +0100 ... The only thing changed is MX: from V3.3 to V4.0-1. Does the case of "DIGEST" matter now? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Tue, 19 Apr 1994 17:20:34 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Problem with MX V4.0? Date: 19 Apr 1994 21:34:33 GMT Message-ID: <2p1ip9$b8o@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Hi, I've been running MX V4.0 for a couple of weeks now and have had no problems until today. Several users have reported that they have received multiple copies of the same message, and my Mail Queue has not been getting cleaned of finished entries since a little before 9:00am this morning. I am running separate FLQ Manager processes, and when I checked, they were in the HIB state. I have shut down MX and restarted only one FLQ Manager process, and it seemed to do its job. I am just worried that it might happen again, and I have no idea what caused it, as I was out of the office today. Any ideas would be greatly appreciated. Next time I will gather more info. Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 17:50:47 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 1:43 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:16:03 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5352; Tue, 19 Apr 1994 18:15:53 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:15:51 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 00:02:42 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D369.0D27F222.375@uni-lj.si> Subject: RE: Digest not creating .input file Whenever something shows up in a list, I get hit somehow ;-) From MX_DEVICE:[MX]MX_DELIVER_DIGESTS.LOG: Digest name to process is FRACTAL.... $ mx_make_digest FRACTAL %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC =000713E0, PSL=03C00004 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 201C0000 Name = 0000000C 00000000 00000000 201C0000 00000000 00000007 000713E0 7FEBAD74 03C00004 000017FD 00085130 00085BD3 00000200 00000001 Register dump R0 = 00000000 R1 = 00085BD3 R2 = 00000000 R3 = 00000000 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R8 = 7FFECA4C R9 = 7FFECC54 R10= 7FFED7D4 R11= 7FFE2BDC AP = 7FEBACF8 FP = 7FEBACB8 SP = 7FEBAD34 PC = 000713E0 PSL= 03C00004 $ digest_file = f$search("MX_SITE_DIR:FRACTAL-DIGEST.OUTPUT") $ if digest_file.nes."" $ else say "No OUTPUT file found!!!" No OUTPUT file found!!! The start od FRACTAL-DIGEST.PROCESS looks like: From-MX-SITE--- Resent-Date: Sun, 17 Apr 1994 05:12:57 +0100 Resent-From: Resent-To: Received: by uni-lj.si (MX V4.0 VAX) with SITE; Sun, 17 Apr 1994 05:12:45 +0100 ... The only thing changed is MX: from V3.3 to V4.0-1. Does the case of "DIGEST" matter now? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Tue, 19 Apr 1994 18:11:51 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 17:25:25 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D331.8CDC11C0.327@SHSU.edu> Subject: RE: FLQ Manager process very slow On Tue, 19 Apr 1994 14:50:35 CDT, "Hunter Goatley, WKU" posted: > You are the third site that's reported similar problems (all extra-heavy > duty sites). Setting the logicals appears to have helped the other two. We're what I thought was an "extra-heavy duty" site but we haven't seen this problem and I thought Hunter (and even Matt before him!) designed everything so we always found the bugs. 8-) I feel kinda left out -- NOT! 8-) We're using all the defaults for everything as best as I can tell, with UCX and MultiNet (different nodes, obviously) on VAX/OpenVMS 6.0. If you want to compare configurations to try and track any of this down, let me know and I will give you whatever information you might want. --George ================================================================================ Archive-Date: Tue, 19 Apr 1994 18:16:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:10 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:19:04 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5407; Tue, 19 Apr 1994 18:18:34 -0400 Received: from wkuvx2.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:18:33 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU X-Newsgroups: vmsnet.mail.mx Subject: Problem with MX V4.0? Date: 19 Apr 1994 21:34:33 GMT Organization: University of Massachusetts at Boston Lines: 22 Message-ID: <2p1ip9$b8o@anchor.cc.umb.edu> NNTP-Posting-Host: trantor.cc.umb.edu X-Newsreader: TIN [version 1.2 PL2] To: MX-List@WKUVX1.WKU.EDU X-Gateway-Source-Info: USENET Hi, I've been running MX V4.0 for a couple of weeks now and have had no problems until today. Several users have reported that they have received multiple copies of the same message, and my Mail Queue has not been getting cleaned of finished entries since a little before 9:00am this morning. I am running separate FLQ Manager processes, and when I checked, they were in the HIB state. I have shut down MX and restarted only one FLQ Manager process, and it seemed to do its job. I am just worried that it might happen again, and I have no idea what caused it, as I was out of the office today. Any ideas would be greatly appreciated. Next time I will gather more info. Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 18:25:19 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 16:18:29 PST From: robert@dis.ucsf.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D328.336F6500.12893@dis.ucsf.edu> Subject: RE: Problem with MX V4.0? Are these duplicated messages completely local to your system? I've been seeing duplicated messages from a bitnet listserver intermittently for a few weeks. It started happening again yesterday. I'm not the only subscriber getting duplicate messages (generally 2 copies, as many as 7, but not every message is duplicated). But not all subscribers are getting them. It seems to be something out of whack elsewhere on the net. Anyway, it may not be your system. ------------------------------------------------------------------------------- Robert Weiner Manager, Development Information Systems robert@dis.ucsf.edu University of California, San Francisco > > Hi, > > I've been running MX V4.0 for a couple of weeks now and have had no problems > until today. Several users have reported that they have received multiple > copies of the same message, and my Mail Queue has not been getting cleaned > of finished entries since a little before 9:00am this morning. > > I am running separate FLQ Manager processes, and when I checked, they were > in the HIB state. > > I have shut down MX and restarted only one FLQ Manager process, and it > seemed to do its job. I am just worried that it might happen again, and I > have no idea what caused it, as I was out of the office today. > > Any ideas would be greatly appreciated. Next time I will gather more info. > > Ted > -- > Ted Corning > UMass/Boston > Computing Services > kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 18:42:51 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:36 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:50:26 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 6024; Tue, 19 Apr 1994 18:50:06 -0400 Received: from wkuvx1.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:50:04 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 1:43 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is:( Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:16:03 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5352; Tue, 19 Apr 1994 18:15:53 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:15:51 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 00:02:42 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D369.0D27F222.375@uni-lj.si> Subject: RE: Digest not creating .input file Whenever something shows up in a list, I get hit somehow ;-) From MX_DEVICE:[MX]MX_DELIVER_DIGESTS.LOG: Digest name to process is FRACTAL.... $ mx_make_digest FRACTAL %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC =000713E0, PSL=03C00004 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 201C0000 Name = 0000000C 00000000 00000000 201C0000 00000000 00000007 000713E0 7FEBAD74 03C00004 000017FD 00085130 00085BD3 00000200 00000001 Register dump R0 = 00000000 R1 = 00085BD3 R2 = 00000000 R3 = 00000000 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R8 = 7FFECA4C R9 = 7FFECC54 R10= 7FFED7D4 R11= 7FFE2BDC AP = 7FEBACF8 FP = 7FEBACB8 SP = 7FEBAD34 PC = 000713E0 PSL= 03C00004 $ digest_file = f$search("MX_SITE_DIR:FRACTAL-DIGEST.OUTPUT") $ if digest_file.nes."" $ else say "No OUTPUT file found!!!" No OUTPUT file found!!! The start od FRACTAL-DIGEST.PROCESS looks like: From-MX-SITE--- Resent-Date: Sun, 17 Apr 1994 05:12:57 +0100 Resent-From: Resent-To: Received: by uni-lj.si (MX V4.0 VAX) with SITE; Sun, 17 Apr 1994 05:12:45 +0100 ... The only thing changed is MX: from V3.3 to V4.0-1. Does the case of "DIGEST" matter now? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Tue, 19 Apr 1994 18:45:24 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:36 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:12:11 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 6472; Tue, 19 Apr 1994 19:10:41 -0400 Received: from wkuvx1.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:10:40 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 17:25:25 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D331.8CDC11C0.327@SHSU.edu> Subject: RE: FLQ Manager process very slow On Tue, 19 Apr 1994 14:50:35 CDT, "Hunter Goatley, WKU" posted: > You are the third site that's reported similar problems (all extra-heavy > duty sites). Setting the logicals appears to have helped the other two. We're what I thought was an "extra-heavy duty" site but we haven't seen this problem and I thought Hunter (and even Matt before him!) designed everything so we always found the bugs. 8-) I feel kinda left out -- NOT! 8-) We're using all the defaults for everything as best as I can tell, with UCX and MultiNet (different nodes, obviously) on VAX/OpenVMS 6.0. If you want to compare configurations to try and track any of this down, let me know and I will give you whatever information you might want. --George ================================================================================ Archive-Date: Tue, 19 Apr 1994 19:13:29 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 3:05 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:25:12 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 0428; Tue, 19 Apr 1994 19:24:38 -0400 Received: from wkuvx1.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:24:25 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 16:18:29 PST From: robert@dis.ucsf.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D328.336F6500.12893@dis.ucsf.edu> Subject: RE: Problem with MX V4.0? Are these duplicated messages completely local to your system? I've been seeing duplicated messages from a bitnet listserver intermittently for a few weeks. It started happening again yesterday. I'm not the only subscriber getting duplicate messages (generally 2 copies, as many as 7, but not every message is duplicated). But not all subscribers are getting them. It seems to be something out of whack elsewhere on the net. Anyway, it may not be your system. ------------------------------------------------------------------------------- Robert Weiner Manager, Development Information Systems robert@dis.ucsf.edu University of California, San Francisco > > Hi, > > I've been running MX V4.0 for a couple of weeks now and have had no problem s > until today. Several users have reported that they have received multiple > copies of the same message, and my Mail Queue has not been getting cleaned > of finished entries since a little before 9:00am this morning. > > I am running separate FLQ Manager processes, and when I checked, they were > in the HIB state. > > I have shut down MX and restarted only one FLQ Manager process, and it > seemed to do its job. I am just worried that it might happen again, and I > have no idea what caused it, as I was out of the office today. > > Any ideas would be greatly appreciated. Next time I will gather more info. > > Ted > -- > Ted Corning > UMass/Boston > Computing Services > kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 19:14:20 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 3:05 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:19:27 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 7869; Tue, 19 Apr 1994 19:19:18 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:18:52 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:10 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is:( Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:19:04 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5407; Tue, 19 Apr 1994 18:18:34 -0400 Received: from wkuvx2.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:18:33 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU X-Newsgroups: vmsnet.mail.mx Subject: Problem with MX V4.0? Date: 19 Apr 1994 21:34:33 GMT Organization: University of Massachusetts at Boston Lines: 22 Message-ID: <2p1ip9$b8o@anchor.cc.umb.edu> NNTP-Posting-Host: trantor.cc.umb.edu X-Newsreader: TIN [version 1.2 PL2] To: MX-List@WKUVX1.WKU.EDU X-Gateway-Source-Info: USENET Hi, I've been running MX V4.0 for a couple of weeks now and have had no problems until today. Several users have reported that they have received multiple copies of the same message, and my Mail Queue has not been getting cleaned of finished entries since a little before 9:00am this morning. I am running separate FLQ Manager processes, and when I checked, they were in the HIB state. I have shut down MX and restarted only one FLQ Manager process, and it seemed to do its job. I am just worried that it might happen again, and I have no idea what caused it, as I was out of the office today. Any ideas would be greatly appreciated. Next time I will gather more info. Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 19:41:53 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 3:35 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:48:14 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5929; Tue, 19 Apr 1994 19:43:48 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:43:33 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:36 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is:( Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:50:26 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 6024; Tue, 19 Apr 1994 18:50:06 -0400 Received: from wkuvx1.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:50:04 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 1:43 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is:( Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 01:16:03 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 5352; Tue, 19 Apr 1994 18:15:53 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 18:15:51 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 00:02:42 +0100 From: "Rok Vidmar, RCU Lj." Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D369.0D27F222.375@uni-lj.si> Subject: RE: Digest not creating .input file Whenever something shows up in a list, I get hit somehow ;-) From MX_DEVICE:[MX]MX_DELIVER_DIGESTS.LOG: Digest name to process is FRACTAL.... $ mx_make_digest FRACTAL %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=00000000, PC =000713E0, PSL=03C00004 Improperly handled condition, image exit forced. Signal arguments Stack contents Number = 00000005 201C0000 Name = 0000000C 00000000 00000000 201C0000 00000000 00000007 000713E0 7FEBAD74 03C00004 000017FD 00085130 00085BD3 00000200 00000001 Register dump R0 = 00000000 R1 = 00085BD3 R2 = 00000000 R3 = 00000000 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R4 = 00000000 R5 = 00000810 R6 = 7FEBAD60 R7 = 00000760 R8 = 7FFECA4C R9 = 7FFECC54 R10= 7FFED7D4 R11= 7FFE2BDC AP = 7FEBACF8 FP = 7FEBACB8 SP = 7FEBAD34 PC = 000713E0 PSL= 03C00004 $ digest_file = f$search("MX_SITE_DIR:FRACTAL-DIGEST.OUTPUT") $ if digest_file.nes."" $ else say "No OUTPUT file found!!!" No OUTPUT file found!!! The start od FRACTAL-DIGEST.PROCESS looks like: From-MX-SITE--- Resent-Date: Sun, 17 Apr 1994 05:12:57 +0100 Resent-From: Resent-To: Received: by uni-lj.si (MX V4.0 VAX) with SITE; Sun, 17 Apr 1994 05:12:45 +0100 ... The only thing changed is MX: from V3.3 to V4.0-1. Does the case of "DIGEST" matter now? Regards, Rok Vidmar inet: rok.vidmar@uni-lj.si UCC, University of Ljubljana x.400: S=vidmar;G=rok;O=uni-lj;P=ac;A=mail;C=si Kardeljeva pl. 17 phone: +386 61 1686439 <-- Changed! 61000 Ljubljana fax: +386 61 1686358 <-- Changed! Slovenia ================================================================================ Archive-Date: Tue, 19 Apr 1994 19:42:19 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 3:35 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is: Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:48:36 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 6184; Tue, 19 Apr 1994 19:46:37 -0400 Received: from wkuvx3.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:46:32 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 94 2:36 +0300 From: Automatic answer system Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Subject: Problems delivering a message Your message could not be delivered to some or all of its recipients. The problem is:( Address not found in table or nameserver. The erronous address was: NAJMAN@MAIL.HADASSAH.HUJI.AC.IL If you have problems locating your addressee, try writing to POSTMASTER@HUJIVMS or INFO@HUJIVMS ----------------------------------- Received: by HUJIVMS via NJE (HUyMail-V6l); Wed, 20 Apr 94 02:12:11 +0300 Received: from UKCC (NJE origin SMTP@UKCC) by UKCC.UKY.EDU (LMail V1.1d/1.7f) with BSMTP id 6472; Tue, 19 Apr 1994 19:10:41 -0400 Received: from wkuvx1.wku.edu by UKCC.uky.edu (IBM VM SMTP V2R2) with TCP; Tue, 19 Apr 94 19:10:40 EDT X-ListName: Message Exchange Discussion List Warnings-To: <> Errors-To: owner-mx-list@WKUVX1.WKU.EDU Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 19 Apr 1994 17:25:25 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D331.8CDC11C0.327@SHSU.edu> Subject: RE: FLQ Manager process very slow On Tue, 19 Apr 1994 14:50:35 CDT, "Hunter Goatley, WKU" posted: > You are the third site that's reported similar problems (all extra-heavy > duty sites). Setting the logicals appears to have helped the other two. We're what I thought was an "extra-heavy duty" site but we haven't seen this problem and I thought Hunter (and even Matt before him!) designed everything so we always found the bugs. 8-) I feel kinda left out -- NOT! 8-) We're using all the defaults for everything as best as I can tell, with UCX and MultiNet (different nodes, obviously) on VAX/OpenVMS 6.0. If you want to compare configurations to try and track any of this down, let me know and I will give you whatever information you might want. --George ================================================================================ Archive-Date: Tue, 19 Apr 1994 20:58:11 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Problem with MX V4.0? Date: 20 Apr 1994 01:15:10 GMT Message-ID: <2p1vmu$hnb@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Here's one of the FLQ Log files: 19-APR-1994 21:10:14.20 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC 19-APR-1994 21:10:14.48 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. 19-APR-1994 21:10:36.99 %FLQ_CLEANUP, time to check for cleanups 19-APR-1994 21:10:37.12 %FLQ_CLEANUP, time to make a purge pass 19-APR-1994 21:10:37.37 %FLQ_CLEANUP, PURGE: final FLQ_SEARCH status = 0001827A 19-APR-1994 21:10:37.55 %FLQ_CLEANUP, EXPIRE: final FLQ_SEARCH status = 0001827A 19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC 19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. 19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC 19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. 19-APR-1994 21:12:37.70 %FLQ_CLEANUP, time to check for cleanups Hope this makes things a little clearer. -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Tue, 19 Apr 1994 21:14:19 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: kismet@trantor.cc.umb.edu (Ted Corning) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Problem with MX V4.0? Date: 20 Apr 1994 01:30:26 GMT Message-ID: <2p20ji$i1v@anchor.cc.umb.edu> To: MX-List@WKUVX1.WKU.EDU Here's the next piece of the puzzle. My queue directories are all full with files that should have been delivered over the past few days. I don't know if they have been delivered and didn't get removed, or if they got lost somehow. It appears that each subdirectory has about 1600 to 1700 files. Is there a way to tell the status of the messages? Help! Ted -- Ted Corning UMass/Boston Computing Services kismet@trantor.cc.umb.edu ================================================================================ Archive-Date: Wed, 20 Apr 1994 05:00:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: Problem with MX V4.0? Date: 20 Apr 1994 09:36:43 GMT Message-ID: <2p2t3b$v1@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <2p20ji$i1v@anchor.cc.umb.edu>, kismet@trantor.cc.umb.edu (Ted Corning) writes: =Here's the next piece of the puzzle. Perhaps even the most crucial one, but not the one you think. =My queue directories are all full with =files that should have been delivered over the past few days. I don't know =if they have been delivered and didn't get removed, or if they got lost =somehow. It appears that each subdirectory has about 1600 to 1700 files. = =Is there a way to tell the status of the messages? RTFM!!!!!!!!!!!!!! Do you mean to tell us that you installed MX and you couldn't be bothered to invest enough time to even learn about the QUEUE SHOW command to MCP! Given that you've apparently installed the product blind, there are any of a number of things which you might, in your abysmal and wholly self-imposed, ignorance, have screwed up royally. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 20 Apr 1994 05:06:04 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 05:05:26 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D393.5741F33D.19@ALPHA.WKU.EDU> Subject: Re: Problem with MX V4.0? kismet@trantor.cc.umb.edu (Ted Corning) writes: > >Here's one of the FLQ Log files: > >19-APR-1994 21:10:14.20 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC >19-APR-1994 21:10:14.48 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. >19-APR-1994 21:10:36.99 %FLQ_CLEANUP, time to check for cleanups >19-APR-1994 21:10:37.12 %FLQ_CLEANUP, time to make a purge pass >19-APR-1994 21:10:37.37 %FLQ_CLEANUP, PURGE: final FLQ_SEARCH status = 0001827A >19-APR-1994 21:10:37.55 %FLQ_CLEANUP, EXPIRE: final FLQ_SEARCH status = 0001827A >19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC >19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. >19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC >19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. >19-APR-1994 21:12:37.70 %FLQ_CLEANUP, time to check for cleanups > >Hope this makes things a little clearer. > I'm not sure why no entries were purged above, unless none were older than 15 minutes. In any case, the other messages are coming from the MX Router process(es): they all use the same log file, and when one process has the lock, the others just report that someone else is doing the cleanups. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 20 Apr 1994 07:57:56 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: daveh@vax.oxford.ac.uk (Dave Hastings, OUCS) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Re: Problem with MX V4.0? Message-ID: <1994Apr20.123653.22095@oxvaxd> Date: 20 Apr 94 12:36:53 GMT To: MX-List@WKUVX1.WKU.EDU In article <2p1vmu$hnb@anchor.cc.umb.edu>, kismet@trantor.cc.umb.edu (Ted Corning) writes: > Here's one of the FLQ Log files: > > 19-APR-1994 21:10:14.20 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC > 19-APR-1994 21:10:14.48 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. > 19-APR-1994 21:10:36.99 %FLQ_CLEANUP, time to check for cleanups > 19-APR-1994 21:10:37.12 %FLQ_CLEANUP, time to make a purge pass > 19-APR-1994 21:10:37.37 %FLQ_CLEANUP, PURGE: final FLQ_SEARCH status = 0001827A > 19-APR-1994 21:10:37.55 %FLQ_CLEANUP, EXPIRE: final FLQ_SEARCH status = 0001827A > 19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC > 19-APR-1994 21:11:37.15 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. > 19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Checking lock, resnam=FLQ_LOCK_UMBSKY_RQC > 19-APR-1994 21:11:38.72 %FLQ_CLEANUP: Someone else is doing the cleanups. Bye. > 19-APR-1994 21:12:37.70 %FLQ_CLEANUP, time to check for cleanups > > Hope this makes things a little clearer. > > -- > Ted Corning > UMass/Boston > Computing Services > kismet@trantor.cc.umb.edu It looks as though you've got the same problem as us, which is that the FLQ Manager can't delete finished messages quickly enough. You might want to try reducing the values of MX_FLQ_CHECK_WAIT and MX_FLQ_MGR_WAKEUP_INTERVAL to quite small values: I've set both of them to 45 seconds which has improved the situation. There doesn't seem to be much point in running two FLQ Manager processes, since only one of them can actually purge the queue at any time. Hunter said that there will be an 'autopurge' option in MX 4.1. Dave -- David Hastings | "There's nothing wrong with my sense VAX Systems Programmer | of reality - I have it thoroughly Oxford University Computing Services| serviced once a fortnight" - DNA daveh@vax.oxford.ac.uk | ================================================================================ Archive-Date: Wed, 20 Apr 1994 09:21:52 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 07:20:15 PDT From: "Brian R. Kuhn" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3A6.2CB99220.6@SD68.NANAIMO.BC.CA> Subject: REPLY-TO, "From:" field, etc. I've got a mailing list set up with the REPLY-TO set to List. When messages are sent to the list, the sender's return address is placed in the "From:" header field - thus a REPLY command sends a reply message to the sender and not the list. What am I missing here? thanks, Brian ----------------------------------------------------------------------- Brian R. Kuhn, Co-ordinator of Information Systems VOICE: 604 741 5289 School District No. 68 (Nanaimo), FAX: 604 754 6511 British Columbia, Canada DATA: 604 754 3630 TELNET: crc.sd68.nanaimo.bc.ca (guest) *(bbs --> guest)* EMAIL: bkuhn@sd68.nanaimo.bc.ca Compuserve: 75430,3250 ------------------------------------------------------------------------ ================================================================================ Archive-Date: Wed, 20 Apr 1994 09:59:50 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 09:56:21 EST From: koenig@CVAX.IPFW.INDIANA.EDU Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3BB.FB673860.11408@CVAX.IPFW.INDIANA.EDU> Subject: RE: REPLY-TO, "From:" field, etc. >From: "Brian R. Kuhn" >Subj: REPLY-TO, "From:" field, etc. >I've got a mailing list set up with the REPLY-TO set to List. When >messages are sent to the list, the sender's return address is placed in >the "From:" header field - thus a REPLY command sends a reply message to >the sender and not the list. What am I missing here? Did you modify an already-existing list? If so, did you remember to do a "$ RESET/CLUSTER ROUTER,MLF" command to reset the router and mailing list agents? I've forgotten to do this a few times in the past myself. >thanks, > >Brian >----------------------------------------------------------------------- >Brian R. Kuhn, Co-ordinator of Information Systems VOICE: 604 741 5289 >School District No. 68 (Nanaimo), FAX: 604 754 6511 >British Columbia, Canada DATA: 604 754 3630 >TELNET: crc.sd68.nanaimo.bc.ca (guest) *(bbs --> guest)* >EMAIL: bkuhn@sd68.nanaimo.bc.ca Compuserve: 75430,3250 >------------------------------------------------------------------------ ---Greg --------------------------------------------------------------------------- Greg Koenig koenig@cvax.ipfw.indiana.edu Systems Programmer koenig@ipfwcvax.bitnet Indiana University - Purdue University koenig@smtplink.ipfw.indiana.edu Fort Wayne, Indiana (219) 481-6031 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 20 Apr 1994 10:09:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 11:05:01 EDT From: "Michael H. Spence, Eastman Chemical Company, (615-229-2220)" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3C5.936E3380.9@stc150.kpt.emn.com> Subject: Subscribe SUBSCRIBE ================================================================================ Michael H. Spence (mspence@emn.com) | "I'm still the apple of my ECCR Computing & Telecommunication Services | mama's eye. I'm my daddy's Eastman Chemical Company | worst fears realized..." Kingsport, TN | Steve Earle ================================================================================ ================================================================================ Archive-Date: Wed, 20 Apr 1994 10:13:14 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 08:09:18 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097D3AD.06F48480.10811@Data.Basix.COM> Subject: RE: REPLY-TO, "From:" field, etc. > I've got a mailing list set up with the REPLY-TO set to List. When > messages are sent to the list, the sender's return address is placed in > the "From:" header field - thus a REPLY command sends a reply message to > the sender and not the list. What am I missing here? Look at the headers from your posting to the MX-List: > Sender: owner-mx-list@WKUVX1.WKU.EDU > From: "Brian R. Kuhn" > Reply-To: MX-List@WKUVX1.WKU.EDU Any GOOD mail user agent (MUA) will use the REPLY-TO as the default address for REPLY command. Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Internet training & consulting RHarwood@Data.Basix.COM | Info@Data.Basix.COM | DEC small-system management ================================================================================ Archive-Date: Wed, 20 Apr 1994 10:49:48 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 11:46:04 EDT From: "Michael H. Spence, Eastman Chemical Company, (615-229-2220)" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3CB.4F0D42C0.6@stc150.kpt.emn.com> Subject: MXAlias Problems I am having problems trying to get the mxalias database to work. Without MX% set as a default transport the mx%alias address is not translating correctly. Here are the error messages that I am receiving: ============================================================================== MAIL> send To: mx%ada20 %MAIL-E-USERSPEC, invalid user specification '%"ada20@csvaxsrv.east-tenn-st.edu" MAIL> set transport mx% MAIL> send To: ada20 MX rewrote ada20@csvaxsrv.east-tenn-st.edu as Reply-To: MX-List@WKUVX1.WKU.EDU To: WKUVX1.WKU.EDU!mx-list@pubs22.si.com Message-ID: <0097D3CE.F560E200.21749@swdev.si.com> Subject: RE: REPLY-TO, "From:" field, etc. Ray Harwood (RHarwood@Data.Basix.COM) writes: >Look at the headers from your posting to the MX-List: > >> Sender: owner-mx-list@WKUVX1.WKU.EDU >> From: "Brian R. Kuhn" >> Reply-To: MX-List@WKUVX1.WKU.EDU > >Any GOOD mail user agent (MUA) will use the REPLY-TO as the default address for >REPLY command. Unless the transport mungs the addresses. All of my Reply-To headers come out looking like this: X-MX-Warning: Warning -- Invalid "Reply-To" header. Reply-To: uunet!WKUVX1.WKU.EDU!MX-List Thus I can _never_ reply to a list message and expect it to go to the Reply-To address. I always wind up replying to the Return-Path address, which we've been able to have our mail router rewrite like this: Return-Path: where pubs22 is our UUCP mail router. How I *wish* I could just reply to a list! -- Brian Tillman tillman_brian@si.com ================================================================================ Archive-Date: Wed, 20 Apr 1994 12:53:25 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: REPLY-TO, "From:" field, etc. Date: 20 Apr 1994 16:55:20 GMT Message-ID: <2p3mpo$bl6@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097D3A6.2CB99220.6@SD68.NANAIMO.BC.CA>, "Brian R. Kuhn" writes: =I've got a mailing list set up with the REPLY-TO set to List. When =messages are sent to the list, the sender's return address is placed in =the "From:" header field - thus a REPLY command sends a reply message to =the sender and not the list. What am I missing here? You're missing a mailer at the other end that's capable of proprely processing the headers: The mail really IS from the person who sent it. When there's a Reply-To: field in the headers, the remote mail agent is supposed to use that when generating replies. Apparently, the mailer on the system that reports the problem has a brain-dead mailer. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 20 Apr 1994 13:52:55 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 13:46:36 CST From: hunterl@uwwvax.uww.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D3DC.26153920.14@uwwvax.uww.edu> Subject: mx_logicals.dat What is the corrct syntax for adding an entry to mx_logicals.dat mx_flq_purge_wait\/system\""0 00:01:00"" or mx_flq_purge_wait\/system\"'0 00:01:00'" or something else mx_flq_purge_wait\/system\"0 00:01:00" does not work Outside of mx_logicals.dat def/sys mx_flq_purge_wait "0 00:01:00" works Lyle Hunter Computer Center University Wisconsin-Whitewater hunterl@uwwvax.uww.edu ================================================================================ Archive-Date: Wed, 20 Apr 1994 14:02:45 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 14:01:58 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3DE.4B4090C1.20@ALPHA.WKU.EDU> Subject: RE: mx_logicals.dat hunterl@uwwvax.uww.edu writes: > >What is the corrct syntax for adding an entry to mx_logicals.dat >mx_flq_purge_wait\/system\""0 00:01:00"" >or >mx_flq_purge_wait\/system\"'0 00:01:00'" >or something else > >mx_flq_purge_wait\/system\"0 00:01:00" does not work > >Outside of mx_logicals.dat > def/sys mx_flq_purge_wait "0 00:01:00" works > Just use: MX_FLQ_PURGE_WAIT\/SYSTEM/EXEC\0 00:01:00 Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 20 Apr 1994 16:24:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 14:17:25 PST From: robert@dis.ucsf.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097D3E0.7433DCC0.13238@dis.ucsf.edu> Subject: duplicate mail Someone complained about duplicate email coming into his site, and I want to provide an example. This has been happening to me intermittently for weeks. Here are headers from two messages that look like exact duplicates -- at least the text is identical. I've received duplicates from listservers and from individuals, from both internet and bitnet sites. I know I'm not the only one getting them, and don't think they're caused by MX (BTW, I'm still running 3.3). But if anyone knows what's going on I'd appreciate being enlightened. HERE'S THE HEADER OF THE 1ST MESSAGE RECEIVED: From: MX%"FUNDLIST%JHUVM.bitnet@uccvma.ucop.edu" 20-APR-1994 12:36:34.07 To: ROBERT CC: Subj: Subscribe Return-Path: <@UCCVMA.UCOP.EDU:owner-fundlist@JHUVM.HCF.JHU.EDU> Received: from uccvma.ucop.edu by DIS.UCSF.EDU (MX V3.3 VAX) with SMTP; Wed, 20 Apr 1994 12:36:28 PST Received: from UCCVMA.UCOP.EDU by uccvma.ucop.edu (IBM VM SMTP V2R2) with BSMTP id 1307; Wed, 20 Apr 94 12:36:51 PDT Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU (LMail V1.1d/1.7f) with BSMTP id 0040; Wed, 20 Apr 1994 12:36:50 -0700 Date: Wed, 20 Apr 1994 10:12:59 EST Reply-To: "List for the discussion of university fund raising issues." Sender: "List for the discussion of university fund raising issues." From: DEVSANDG@AMBER.INDSTATE.EDU Subject: Subscribe X-To: fundlist@jhuvm.hcf.jhu.edu To: Multiple recipients of list FUNDLIST HERE'S THE HEADER OF THE 2ND MESSAGE RECEIVED: From: MX%"FUNDLIST%JHUVM.bitnet@uccvma.ucop.edu" 20-APR-1994 12:55:07.19 To: ROBERT CC: Subj: Subscribe Return-Path: <@UCCVMA.UCOP.EDU:owner-fundlist@JHUVM.HCF.JHU.EDU> Received: from uccvma.ucop.edu by DIS.UCSF.EDU (MX V3.3 VAX) with SMTP; Wed, 20 Apr 1994 12:55:03 PST Received: from UCCVMA.UCOP.EDU by uccvma.ucop.edu (IBM VM SMTP V2R2) with BSMTP id 9133; Wed, 20 Apr 94 12:55:25 PDT Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU (LMail V1.1d/1.7f) with BSMTP id 0468; Wed, 20 Apr 1994 12:55:23 -0700 Date: Wed, 20 Apr 1994 10:12:59 EST Reply-To: "List for the discussion of university fund raising issues." Sender: "List for the discussion of university fund raising issues." From: DEVSANDG@AMBER.INDSTATE.EDU Subject: Subscribe X-To: fundlist@jhuvm.hcf.jhu.edu To: Multiple recipients of list FUNDLIST ------------------------------------------------------------------------------- Robert Weiner Manager, Development Information Systems robert@dis.ucsf.edu University of California, San Francisco ================================================================================ Archive-Date: Wed, 20 Apr 1994 16:40:37 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 16:39:56 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D3F4.5D0B3020.15@ALPHA.WKU.EDU> Subject: RE: duplicate mail robert@dis.ucsf.edu writes: > >Someone complained about duplicate email coming into his site, and I >want to provide an example. This has been happening to me >intermittently for weeks. Here are headers from two messages that >look like exact duplicates -- at least the text is identical. I've >received duplicates from listservers and from individuals, from both >internet and bitnet sites. I know I'm not the only one getting them, >and don't think they're caused by MX (BTW, I'm still running 3.3). They're not. >But if anyone knows what's going on I'd appreciate being enlightened. > The only thing I can tell from the headers is that UCCVMA.UCOP.EDU is resending it. Note the date & time (12:36:50): >Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU > (LMail V1.1d/1.7f) with BSMTP id 0040; Wed, 20 Apr 1994 12:36:50 -0700 >Date: Wed, 20 Apr 1994 10:12:59 EST And from the second message: >Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU > (LMail V1.1d/1.7f) with BSMTP id 0468; Wed, 20 Apr 1994 12:55:23 -0700 >Date: Wed, 20 Apr 1994 10:12:59 EST Note that it was received again at 12:55:23. The LISTSERV@UCCVMA sent it out again for some reason. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Wed, 20 Apr 1994 17:05:06 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: duplicate mail Date: 20 Apr 1994 21:44:05 GMT Message-ID: <2p47n5$itp@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097D3E0.7433DCC0.13238@dis.ucsf.edu>, robert@dis.ucsf.edu writes: =Someone complained about duplicate email coming into his site, and I =want to provide an example. This has been happening to me =intermittently for weeks. Here are headers from two messages that =look like exact duplicates -- at least the text is identical. I've =received duplicates from listservers and from individuals, from both =internet and bitnet sites. I know I'm not the only one getting them, =and don't think they're caused by MX (BTW, I'm still running 3.3). It doesn't take a genius to figure that out: From the first message: =Received: from uccvma.ucop.edu by DIS.UCSF.EDU (MX V3.3 VAX) with SMTP; Wed, 20 = Apr 1994 12:36:28 PST =Received: from UCCVMA.UCOP.EDU by uccvma.ucop.edu (IBM VM SMTP V2R2) with BSMTP = id 1307; Wed, 20 Apr 94 12:36:51 PDT =Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU = (LMail V1.1d/1.7f) with BSMTP id 0040; Wed, 20 Apr 1994 12:36:50 -0700 =Date: Wed, 20 Apr 1994 10:12:59 EST From the second message: =Received: from uccvma.ucop.edu by DIS.UCSF.EDU (MX V3.3 VAX) with SMTP; Wed, 20 = Apr 1994 12:55:03 PST =Received: from UCCVMA.UCOP.EDU by uccvma.ucop.edu (IBM VM SMTP V2R2) with BSMTP = id 9133; Wed, 20 Apr 94 12:55:25 PDT =Received: from UCCVMA.UCOP.EDU (NJE origin LISTSERV@UCCVMA) by UCCVMA.UCOP.EDU = (LMail V1.1d/1.7f) with BSMTP id 0468; Wed, 20 Apr 1994 12:55:23 -0700 =Date: Wed, 20 Apr 1994 10:12:59 EST Please note that UCCVMA.UCOP.EDU (the machine on which the message originated, as far as we're concerned), claims to have received the first message from itself as 12:36:50, and the second at 12:55:23. Clearly, it's the LISTSERV on the IBM machine which is causing the problem. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Wed, 20 Apr 1994 17:42:26 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: blake@ntupub.ntu.edu (Blake Stewart) Reply-To: MX-List@WKUVX1.WKU.EDU Message-ID: <9404202236.AA15883@ntupub.ntu.edu> Subject: To: mx-list@wkuvx1.wku.edu Date: Wed, 20 Apr 1994 16:36:24 -0600 (MDT) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit SUBSCRIBE ================================================================================ Archive-Date: Wed, 20 Apr 1994 21:03:40 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 20 Apr 1994 21:00:44 CDT From: "DANIAN LIU ;->" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D418.CBA99020.3675@BEAVER.HS.Bemidji.MSUS.edu> Subject: sign off... Please sign me off Danian Liu ================================================================================ Archive-Date: Wed, 20 Apr 1994 23:36:17 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: meregalli@cesi.it Reply-To: MX-List@WKUVX1.WKU.EDU Subject: SYSLCK required for QUEUE SHOW? Message-ID: <1994Apr20.115924.472@cesi.it> Date: 20 Apr 94 11:59:24 +0200 To: MX-List@WKUVX1.WKU.EDU Hello! (I've already posted, but I'm afraid nobody has seen it.) I have upgraded to MX 4.0. Now if I try to see the entries in the queue I get this message $ mcp que show %MCP-E-QOPENERR, error occurred opening system message queue -SYSTEM-F-NOSYSLCK, operation requires SYSLCK privilege Is this intended behaviour? The management guide doesn't mention any privilege in the description of the command! --------------------------------------------------------------------------- Alberto Meregalli, SIC tel. +39 2 2125 249 CESI, Centro Elettrotecnico Sperimentale Italiano fax +39 2 2125 520 Via Rubattino, 54 - I 21034 Milano E-mail: meregalli@cesi.it ================================================================================ Archive-Date: Wed, 20 Apr 1994 23:36:43 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: meregalli@cesi.it Reply-To: MX-List@WKUVX1.WKU.EDU Subject: QUEUE SHOW inconsistencies? Message-ID: <1994Apr20.120022.474@cesi.it> Date: 20 Apr 94 12:00:22 +0200 To: MX-List@WKUVX1.WKU.EDU (I'm trying again to post this text) On MX 4.0 I'm looking at queue entries: $ mcp que show/all Entry# Status Size Source Agent Entry# Status Size ------ ------ ------- ------ ------- ------ ------ ------- 81 FINISH 39 MAIL 83 FINISH 1576 LOCAL ^^^^^^^^^^^^^^^^ 84 FINISH 777 LOCAL 1 FINISH 33 UUCP plath@cesi.it %MCP-I-QENTRIES, total matching entries: 4 Now I look in detail at one of the entries $ mcp que show/full 83 Entry: 83, Origin: [Local] ^^^^^^^^^^^^^^^^^^ Status: FINISHED, size: 1576 bytes Created: 12-APR-1994 09:23:39.07, expires 12-MAY-1994 09:23:39.07 Last modified 12-APR-1994 09:23:57.05 Recipient #1: Are the underlined items correct? Why are they different? Thank you --------------------------------------------------------------------------- Alberto Meregalli, SIC tel. +39 2 2125 249 CESI, Centro Elettrotecnico Sperimentale Italiano fax +39 2 2125 520 Via Rubattino, 54 - I 21034 Milano E-mail: meregalli@cesi.it ================================================================================ Archive-Date: Thu, 21 Apr 1994 02:12:46 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 09:09:24 +0100 From: Juan Altmayer Pizzorno Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D47E.9714054F.26@vms.gmd.de> Subject: RE: Problem with MX V4.0? > I've been running MX V4.0 for a couple of weeks now and have had no problems > until today. Several users have reported that they have received multiple > copies of the same message, and my Mail Queue has not been getting cleaned > of finished entries since a little before 9:00am this morning. Just after MX 4.0 was released there was a discussion about how to empty the queues so that you could have a new queue file created without loosing messages. The suggested trick included READYing the main (i.e., router) entries of the messages, so that the agent entries got routed differently. This works fine if your message has only one recipient, but if it has two or more, and some of the recipients had already received the message when the main entry was READYed, these will receive the message for a second time. This might have caused the duplicate messages you mention. .. Juan ================================================================================ Archive-Date: Thu, 21 Apr 1994 02:43:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 10:36:05 EDT From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU CC: najman%hadassah@VMS.HUJI.AC.IL Message-ID: <0097D48A.B2A45AC0.8@HADASSAH.HUJI.AC.IL> Subject: V4.n SMTP process dies Hi. I seem to remmember talk about this problem, but I cannot find it in the archives. So please forgive if covered, and help. I have MX installed on 6500 Vax and it works like a charm I installed a second copy on a MicroVax and the SMTP process dies as soon as it starts processing an entry. The vms-accounting indicates that the problem is an access violation.: access violation mask=0 virt add=00 pc=3758 psl 3c0004 module smtp_out routine smtp_send line 205 I tried both v4.0 and v4.1. The result is identical. Any help would be appreciated. Najman Kahana Najman@hadassah.bitnet +----------+------------------+------------------------------+---------------+ ! !\ ! / ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! ! \ !/\ ! najman@HADASSAH. ! Jerusalem, Israel ! we have our ! ! ! \! \ ! BITNET ! (visit our capital soon) ! own viruses ! +----------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Thu, 21 Apr 1994 06:42:17 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 06:41:43 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D469.F56AFBF5.40@ALPHA.WKU.EDU> Subject: RE: SYSLCK required for QUEUE SHOW? meregalli@cesi.it writes: > >Hello! (I've already posted, but I'm afraid nobody has seen it.) > No, it didn't make it. >I have upgraded to MX 4.0. > >Now if I try to see the entries in the queue I get this message > >$ mcp que show >%MCP-E-QOPENERR, error occurred opening system message queue >-SYSTEM-F-NOSYSLCK, operation requires SYSLCK privilege > >Is this intended behaviour? The management guide doesn't mention any >privilege in the description of the command! > Yes, SYSLCK is required in MX V4.0+. SYSPRV (or BYPASS) is also needed, but the SYSLCK requirement is new in MX V4.0. That's because MX is now doing it's own record locking and *not* using RMS record locking. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Thu, 21 Apr 1994 06:46:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 06:45:55 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D46A.8B85AC02.42@ALPHA.WKU.EDU> Subject: RE: QUEUE SHOW inconsistencies? meregalli@cesi.it writes: > >On MX 4.0 I'm looking at queue entries: [...] > 83 FINISH 1576 LOCAL > ^^^^^^^^^^^^^^^^ [...] >Now I look in detail at one of the entries > >$ mcp que show/full 83 > >Entry: 83, Origin: [Local] > ^^^^^^^^^^^^^^^^^^ [...] >Are the underlined items correct? Why are they different? > Yes, they are. The first is information stored in the MX queue file; it reflects the actual From: address. The second is stored in the .SRC_INFO file for that entry and reflects the Sender: address. Normally, they're the same address, but this is an example where they're different. When coding the new MLF, I thought that using the From: address in SHOW QUEUE would be more useful, as several things can produce messages with "Postmaster" as the address. For example, all bounce messages from SMTP, LOCAL, etc., are from the postmaster. This way, you can see at a glance that it was actually MXserver. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Thu, 21 Apr 1994 06:49:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 06:48:31 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097D46A.E82B8F62.23@ALPHA.WKU.EDU> Subject: SYSLCK required for DECnet and X.25 network objects! Ralph Kloess and Martin Winter (thanks!) pointed out that the X.25 (and DECnet-SMTP) network objects also need SYSLCK in MX V4.0+. I forgot about that when updating the manuals. If you're using X.25 and/or DECSMTP, you *must* use AUHTORIZE to grant the SYSLCK privilege to the account(s) used by those network objects. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (WKUVX1 is leaving BITNET in May!) ================================================================================ Archive-Date: Thu, 21 Apr 1994 06:52:22 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 21 Apr 1994 06:52:12 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D46B.6C14822A.31@ALPHA.WKU.EDU> Subject: RE: V4.n SMTP process dies "Najman Kahana. Ext:7313" writes: > > I installed a second copy on a MicroVax and the SMTP process dies >as soon as it starts processing an entry. The vms-accounting indicates that >the problem is an access violation.: > > access violation mask=0 virt add=00 pc=3758 psl 3c0004 > > module smtp_out > routine smtp_send > line 205 > This problem was discovered and reported to me by Andy Harper a couple of days ago. The problem is most likely a bad address. In the example Andy forwarded to me, the bad address had a leading "." after the "@" sign, for example, "goathunter@.alpha.wku.edu". This will be corrected soon in a -2 update. Enabling MX_SMTP_DEBUG should show you the bad address. You should also check your rewrite rules to make sure they're not responsible for the bad address. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Thu, 21 Apr 1994 17:33:05 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: SYSLCK also required for MX-NEWS-GATEWAY Message-ID: <1994Apr21.161422@mccall.com> From: tp@mccall.com (Terry Poot) Date: Thu, 21 Apr 1994 16:14:22 CDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Another place SYSLCK is required that isn't mentioned in the instructions.txt file is the news -> mail portion of the MX-NEWS-GATEWAY contributed software. If the process running newsskim doesn't have SYSLCK, mx_site_in exits with an appropriate status, but gatenews doesn't report it. There is no indication in any log files anywhere I could find that the message didn't get mailed out. NEWSSKIM-FRAG.COM should be updated to turn on SYSLCK, and the account you're running NEWSSKIM under should be updated to have the privilege. With the DECUS UUCP setup, NEWSMGR already has setprv, but I don't know about other setups. I modified it such that the two lines containing the gatenews and delete commands were replaced by: $ oldprv = f$setprv("SYSLCK") $ if .not. f$privilege("SYSLCK") $ then $ say "Insufficient privilege!" $ else $ gatenews 'file 'list_add 'list_add $ delete 'file $ endif $ oldprv = f$setprv(oldprv) This one's annoying because it leaves no tracks (gatenews doesn't check the return status of the subprocess running mx_site_in), and the other direction, mail to news, works fine, so you don't immediately realize there's a problem. -- Terry Poot The McCall Pattern Company Phone/Fax: (800)255-2762, (913)776-4041 615 McCall Road Manhattan, KS 66502, USA ================================================================================ Archive-Date: Thu, 21 Apr 1994 18:05:39 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: system@condor.navsses.navy.mil (Mike Jacobi; CDNSWC 3582; Vax System Manager) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: SYSLCK required for QUEUE SHOW? Message-ID: <1994Apr21.101537.1321@condor> Date: 21 Apr 94 10:15:37 -0600 To: MX-List@WKUVX1.WKU.EDU In article <0097D469.F56AFBF5.40@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: > Yes, SYSLCK is required in MX V4.0+. SYSPRV (or BYPASS) is also > needed, but the SYSLCK requirement is new in MX V4.0. That's because > MX is now doing it's own record locking and *not* using RMS record > locking. > Is it safe to install MCP or MLFAKE with SYSLCK? If not, could that be added to the to-do list? thanks -- Mike Jacobi NAVSSES VAXCluster system manager System@Eagle.Navsses.Navy.Mil System@Condor.Navsses.Navy.Mil Disclaimer - I speak for myself. No-one else. ================================================================================ Archive-Date: Fri, 22 Apr 1994 05:20:08 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 05:19:55 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D527.B2948B07.13@ALPHA.WKU.EDU> Subject: RE: SYSLCK required for QUEUE SHOW? system@condor.navsses.navy.mil (Mike Jacobi; CDNSWC 3582; Vax System writes: > >In article <0097D469.F56AFBF5.40@ALPHA.WKU.EDU>, "Hunter Goatley, WKU" writes: >> Yes, SYSLCK is required in MX V4.0+. SYSPRV (or BYPASS) is also >> needed, but the SYSLCK requirement is new in MX V4.0. That's because >> MX is now doing it's own record locking and *not* using RMS record >> locking. >> >Is it safe to install MCP or MLFAKE with SYSLCK? If not, could that be added >to the to-do list? > Yes, it's safe. At least, I can think of nothing that would be unsafe about it. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) ================================================================================ Archive-Date: Fri, 22 Apr 1994 05:21:28 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Subject: SYSLSLSack tSack tSaroblerfor MX-NEWS-GATEWAY Message-ID: <1994Apr21.161422@m@m@.com> From: tp@mccall.com (Terry Poot) Date: Thu, 21 Apr 1994 16:14:22 CDT Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Another place lace lLCK is ris ried that isn't mentioned in the in the ng-eg-egWWWATEWAYion: Tgributed software. If the process running newsskim doesn't have SYSYSY, mx_site_in ere yfts with an appropriate status, but gatenews doesn't ifee it.hole hhole hho indication cation c log files anywhere I could 2 Pa that the message didn't get mailed out. NEWS.com)PIM-FRAG.COM should be upge c omputourn on on CKcompa?entereunt you're 're ' NE NE With the DECAYiUUCP setup, N, N,MGR already has setprv, but I don't know about other setups. I modif) Subait such that the two lines containing the ng the nk w nd delete co.Y?ds graph replaAWCaby: $ oldoldo = f$f$frv("S"S"CK") ) ) if .not. f$privilegeegee$ thenthent say "Inetuy wrofent pent pelege!" " " elseelsee ws ''''list_add 'listlistlddddd delete e eile ile i endififi rvrvr f$setete(oldldl) This one's annoying because ie (=aves no tracks ( ( s doesn't check the retretrstat= fing copubprocess ss sdirection, mail to news, works fine, so you you mmediaS3Fa realize there's a 5jsMathe Terrerreot Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 01:21:16 CET Subject: RE: duplicate mail Message-ID: <445D6747BC@aszi.sztaki.hu> Hunter writes: > robert@dis.ucsf.edu writes: > > > >Someone complained about duplicate email coming into his site, and I > >want to provide an example. This has been happening to me > >intermittently for weeks. Here are headers from two messages that > >look like exact duplicates -- at least the text is identical. I've > >received duplicates from listservers and from individuals, from both > >internet and bitnet sites. I know I'm not the only one getting them, > >and don't think they're caused by MX (BTW, I'm still running 3.3). > > They're not. More precisely: in Robert's example they are not. In theory SMTP messages can get duplicated anytime. The "message received and queued" message which approves the receipt can get lost for some reason, resulting in a retransmission of the message. (Recipient thinks transmission was ok, sender thinks it was not). Regards, Miklos ==================================================================== Pa'sztor Miklo's | E-mail: pasztor@hugbox.bitnet MTA SZTAKI/ASZI Budapest Victor H. u. 18-22 | Phone: (36)-(1)-149-75-32 Institute for Computation and Automation, Hungarian Academy of Sciences ==================================================================== ================================================================================ Archive-Date: Fri, 22 Apr 1994 09:42:21 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 10:37:46 EDT From: hone@ouvaxa.cats.ohiou.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097D554.19BA06A0.4238@ouvaxa.cats.ohiou.edu> Subject: protocol error Ohio University Electronic Communication Date: 22-Apr-1994 10:37am EST To: Remote Addressee ( _mx%"MX-List@WKUVX1.WKU.EDU" ) From: Donald Hone Dept: CaTS HONE Tel No: 614-593-0247 Subject: protocol error Our VAX is having trouble sending mail to a specific Unix machine. I have recieved 2 different rejections notices. One is a protocol error with the error cannot open /usr/lib/aliases. The other is an All-in-1 error message invalid alternate MTS address and probably should be asked of that group instead. VMS 5.5-2, DEC TCP/IP V2.0E, MX 3.3, All-in-1 3.0A, Message Router 3.2 Thanks in advance. -Don $ mcp queue show/full 578 Entry: 576, Origin: [Local] Status: IN-PROGRESS, size: 2016 bytes Created: 21-APR-1994 19:27:35.63, expires 21-MAY-1994 19:27:35.63 Last modified 22-APR-1994 09:49:04.18 SMTP entry #578, status: READY, size: 2016 bytes, waiting for retry until 22-APR-1994 10:19:05.69 Created: 21-APR-1994 19:27:52.39, expires 21-MAY-1994 19:27:35.63 Last modified 22-APR-1994 09:49:05.70 Recipient #1: , Route=pslsun.psl.msu.edu Error count=28 Last error: %MX-E-PROTOERR, protocol error? mx_smtp_dir:mx_smtp_log.log 22-APR-1994 09:49:03.96 Processing queue entry number 578 on node OUVAXA 22-APR-1994 09:49:04.29 Recipient: , route=pslsun.psl.msu.edu 22-APR-1994 09:49:04.29 SMTP_SEND: looking up host name pslsun.psl.msu.edu 22-APR-1994 09:49:04.60 SMTP_SEND: Attempting to start session with pslsun.psl.msu.edu. [35.8.148.2] 22-APR-1994 09:49:04.65 SMTP_SEND: Connected 22-APR-1994 09:49:04.99 SMTP_SEND: Rcvd: cannot open database /usr/lib/aliases 22-APR-1994 09:49:05.19 SMTP send failed, sts=0C27804A, sts2=0C278042 22-APR-1994 09:49:05.19 Recipient status=0C27804A for 22-APR-1994 09:49:05.69 1 rcpts need retry, next try 22-APR-1994 10:19:05.69 22-APR-1994 09:49:05.72 *** End of processing pass *** ------------------------ Date: 21-Apr-1994 03:28pm EST To: Donald Hone ( HONE ) From: Mail Postmaster Dept: CaTS POSTMASTER Tel No: Subject: Delivery Failure Report ALL-IN-1 was unable to deliver your message dated 21-Apr-1994 03:28pm to _mx"lori@pslsun.psl.msu.edu" - Recipient has invalid alternate MTS address; on node OUVAXA The subject of the message was : test of mail from OU Received: 21-Apr-1994 04:23pm ------------------------------------ $ ty MX_STARTUP_INFO.DAT;7 001NETLIB:* 002ROUTER:OUVAXA=4 003LOCAL:OUVAXA=4 004SMTP:OUVAXA=2 004SMTP_SERVER:OUVAXA 005MLF:OUVAXA $ ty MX_LOGICALS.DAT;8 MX_FLQ_NODE_NAME\/SYSTEM/EXEC\OUVAX MX_NODE_NAME\/SYSTEM/EXEC\ouvaxa.cats.ohiou.edu MX_VMSMAIL_LOCALHOST\/SYSTEM/EXEC\@ouvaxa.cats.ohiou.edu MX_FLQ_DIR\/SYSTEM/EXEC\$1$DUA4:[MX.QUEUE] MX_FLQ_RECLAIM_WAIT\/SYSTEM/EXEC\0 00:30:00 MX_ROUTER_DIR\/SYSTEM/EXEC\MX_ROOT:[ROUTER] MX_LOCAL_DIR\/SYSTEM/EXEC\MX_ROOT:[LOCAL] MX_MCP_HELPLIB\/SYSTEM\MX_DIR:MX_MCP_HELPLIB MX_ALIAS_HELPLIB\/SYSTEM\MX_DIR:MX_ALIAS_HELPLIB Received: 22-Apr-1994 10:37am ================================================================================ Archive-Date: Fri, 22 Apr 1994 09:56:49 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 09:53:50 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D54D.F6458BC8.3@ALPHA.WKU.EDU> Subject: RE: protocol error hone@ouvaxa.cats.ohiou.edu writes: > >Our VAX is having trouble sending mail to a specific Unix machine. >I have recieved 2 different rejections notices. > >One is a protocol error with the error cannot open /usr/lib/aliases. >The other is an All-in-1 error message invalid alternate MTS address and >probably should be asked of that group instead. > [...] >$ mcp queue show/full 578 [...] > Recipient #1: , Route=pslsun.psl.msu.edu > Error count=28 > Last error: %MX-E-PROTOERR, protocol error? [...] >22-APR-1994 09:49:04.99 SMTP_SEND: Rcvd: cannot open database /usr/lib/aliases That's coming from the UNIX system, which means it's a problem on that system. Welcome to the world of UNIX, where messages like this are the norm. >22-APR-1994 09:49:05.19 SMTP send failed, sts=0C27804A, sts2=0C278042 >22-APR-1994 09:49:05.19 Recipient status=0C27804A for This is just MX reporting what it received; it shows up in the retry as a protocol error, because that's what it is: an SMTP protocol error. $ set mess mx_msg $ write sys$output f$message(%X0C27804A) %MX-E-NOCOMPLETE, message transmission could not be completed $ write sys$output f$message(%X0C278042) %MX-E-PROTOERR, protocol error? $ Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Fri, 22 Apr 1994 14:20:07 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 14:28:38 CST From: Ian Vaz Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@RPIECSVX.BITNET Message-ID: <0097D574.5A6992E0.46@mars.senecac.on.ca> Subject: MX 4.0 List Server anomaly. Hi, I have a list with protections (s:rwed,o:rwed,g,w), and not case sensitive. The list is supposed to be a uni-directional one, i.e., the owners can send messages but nobody is permitted to individually subscribe, signoff or send messages. I am the list owner as well as a SYSTEM_USER. When I send mail to: listname-request@address with a body of: add listname username@address Absolutely nothing happens. No user gets added. BTW, I do not even see an entry in the queue when I do: MCP queue show. Is there something I have missed? Thanks for any help. Regards, Ian Vaz ================================================================================ Archive-Date: Fri, 22 Apr 1994 14:39:56 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 14:35:27 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D575.4DD5B972.7@ALPHA.WKU.EDU> Subject: RE: MX 4.0 List Server anomaly. Ian Vaz writes: > >When I send mail to: >listname-request@address > >with a body of: >add listname username@address > >Absolutely nothing happens. No user gets added. BTW, I do not >even see an entry in the queue when I do: >MCP queue show. > You should see the entry, in any case. But your format is wrong. When sent to the -request address, the command should look like one of the following: ADD "Hunter Goatley" or ADD goathunter@ALPHA.WKU.EDU Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Fri, 22 Apr 1994 15:20:22 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 15:02:30 CST From: "George D. Greenwade" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: ian@mars.senecac.on.ca Message-ID: <0097D579.15496640.83@SHSU.edu> Subject: RE: MX 4.0 List Server anomaly. On Fri, 22 Apr 1994 14:28:38 CST, Ian Vaz posted: > I have a list with protections (s:rwed,o:rwed,g,w), and not case sensitive. > The list is supposed to be a uni-directional one, i.e., the owners can send > messages but nobody is permitted to individually subscribe, signoff or send > messages. I am the list owner as well as a SYSTEM_USER. > > When I send mail to: > listname-request@address > with a body of: > add listname username@address > Absolutely nothing happens. No user gets added. BTW, I do not even see an > entry in the queue when I do: MCP queue show. > > Is there something I have missed? Thanks for any help. If you use the listname-request@server-site, the proper syntax is add "subscriber's personal name" --George %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% George D. Greenwade, Ph.D. Internet: bed_gdg@SHSU.edu Department of Economics and Business Analysis THEnet: SHSU::BED_GDG College of Business Administration Voice: (409) 294-1266 Sam Houston State University FAX: (409) 294-3612 Huntsville, TX 77341-2118 USA %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Fri, 22 Apr 1994 16:09:20 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 22 Apr 1994 13:53:32 EDT From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D56F.72C04B40.1@HADASSAH.HUJI.AC.IL> Subject: RE: V4.n SMTP process dies Subj: RE: V4.n SMTP process dies >> >> I installed a second copy on a MicroVax and the SMTP process dies >>as soon as it starts processing an entry. The vms-accounting indicates that >>the problem is an access violation.: >> >> access violation mask=0 virt add=00 pc=3758 psl 3c0004 >> >> module smtp_out >> routine smtp_send >> line 205 >> >This problem was discovered and reported to me by Andy Harper a couple >of days ago. The problem is most likely a bad address. In the >example Andy forwarded to me, the bad address had a leading "." after >the "@" sign, for example, "goathunter@.alpha.wku.edu". This will be >corrected soon in a -2 update. > >Enabling MX_SMTP_DEBUG should show you the bad address. You should >also check your rewrite rules to make sure they're not responsible for >the bad address. > >Hunter >------ >Hunter Goatley, VMS Systems Programmer, Western Kentucky University >goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.BITNET) Thank you. Following your advice, I found the offending entry. After I emptied the Q, the problem went away. Najman +----------+------------------+------------------------------+---------------+ ! !\ ! / ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! ! \ !/\ ! najman@HADASSAH. ! Jerusalem, Israel ! we have our ! ! ! \! \ ! BITNET ! (visit our capital soon) ! own viruses ! +----------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Fri, 22 Apr 1994 20:53:24 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 23 Apr 1994 02:47:59 BST From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D5DB.A30866E0.3@hicom.lut.ac.uk> Subject: RE: SYSLCK also required for MX-NEWS-GATEWAY Archive-Date: Sun, 23 Jan 1994 13:10:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sun, 23 Jan 1994 19:05:07 GMT From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00978FAB.3B163600.1@hicom.lut.ac.uk> Subject: Some Comments on MX V3.4-BETA-1 Archive-Date: Sun, 23 Jan 1994 13:10:20 CST Sender: list-mgr@WKUVX1.WKU.EDU Date: Sun, 23 Jan 1994 19:05:07 GMT From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <00978FAB.3B163600.1@hicom.lut.ac.uk> Subject: Some Comments on MX V3.4-BETA-1 Hi. Well, I installed V3.4-BETA-1 on friday (as a 'new' installation - i.e. I renamed the V3.3 tree to something else, instead of 'upgrading' it). Here are a few initial comments : 1) MX_SITE_IN now requires SYSLCK to work, but didn't in V3.3. I didn't notice this mentioned in V3.4 installation notes (but forgive me if I missed it) ================================================================================ Archive-Date: Fri, 22 Apr 1994 21:01:00 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 23 Apr 1994 02:55:51 BST From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D5DC.BC5C5C40.2@hicom.lut.ac.uk> Subject: RE: SYSLCK also required for MX-NEWS-GATEWAY I'm going to be obnoxious now, and quote something I posted in January :-) : => ================================================================================ => Archive-Date: Sun, 23 Jan 1994 13:10:20 CST => Sender: list-mgr@WKUVX1.WKU.EDU => Date: Sun, 23 Jan 1994 19:05:07 GMT => From: "Jamie Jones, HICOM Operations" => Reply-To: MX-List@WKUVX1.WKU.EDU => To: mx-list@wkuvx1.wku.edu => Message-ID: <00978FAB.3B163600.1@hicom.lut.ac.uk> => Subject: Some Comments on MX V3.4-BETA-1 => => => Hi. Well, I installed V3.4-BETA-1 on friday (as a 'new' installation - i.e. => I renamed the V3.3 tree to something else, instead of 'upgrading' it). => Here are a few initial comments : => => 1) MX_SITE_IN now requires SYSLCK to work, but didn't in V3.3. I didn't => notice this mentioned in V3.4 installation notes (but forgive me if I => missed it) => [ ... ] Sorry, it's been a long day! Jamie ================================================================================ Archive-Date: Fri, 22 Apr 1994 21:13:16 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Sat, 23 Apr 1994 03:08:06 BST From: "Jamie Jones, HICOM Operations" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D5DE.72622640.6@hicom.lut.ac.uk> Subject: for the wish list ? Spurned on by Juan's message, I would like to mention a command which I would have liked to have for quite a while. : How about something along the lines of : MCP> queue kick which only restarts those entries that have not been delivered. So, that if a message was originally sent to many people (such as with a mailing list) the only entries to be retried are the ones that are requeing/undelivered. This avoids duplicate messages being received by some people, when you use the "queue ready" command. Also, if possible, how about an optional "/route" qualifier which overrides the smtp path for that particular message only. For example : I want to shutdown the system for scheduled mainenance. There is a queue entry still in progress (but requeuing) - 2 of the recipients have temporarily unavalible hosts - the other 40 or so members have received the message. Without needing to ready the message (so sending it to all people again) along with changing "define path "*" smtp/route=another.local.site temporarily; saving; resetting; readying; then putting it back to define path "*" smtp , I'd like to be able to simply do : MCP. queue kick 23/route=another.local.site which will send the 2 requeuing entries only; in this case via node 'another.local.site' Is this possible ? thanks, jamie ================================================================================ Archive-Date: Mon, 25 Apr 1994 00:36:52 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 08:32:26 EDT From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: najman%hadassah@VMS.HUJI.AC.IL Message-ID: <0097D79E.16DE96C0.5@HADASSAH.HUJI.AC.IL> Subject: MXAlias. System-wide ? Hi. I find the MXAlias utility very useful. Since I have a very large number of users, I am interested in setting up a "general" (system-wide) alias table, as well as allowing the users the use of private ones. Is there a way of setting this up ? Does anyone have a utility which allows this ? I want the user to "see" these entries on a DIR command, but be able to maintain them on a system level. Thanks Najman Kahana Najman@hadassah.bitnet +----------+------------------+------------------------------+---------------+ ! !\ ! / ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! ! \ !/\ ! najman@HADASSAH. ! Jerusalem, Israel ! we have our ! ! ! \! \ ! BITNET ! (visit our capital soon) ! own viruses ! +----------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Mon, 25 Apr 1994 07:30:22 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 07:29:31 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D795.4C2F4A8A.29@ALPHA.WKU.EDU> Subject: RE: MXAlias. System-wide ? "Najman Kahana. Ext:7313" writes: > > I find the MXAlias utility very useful. Since I have a very large >number of users, I am interested in setting up a "general" (system-wide) >alias table, as well as allowing the users the use of private ones. > > Is there a way of setting this up ? Does anyone have a utility >which allows this ? I want the user to "see" these entries on a DIR command, >but be able to maintain them on a system level. > No, there's not currently, but I plan to include that (optional) ability in MX V4.1. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 25 Apr 1994 07:36:31 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 07:36:01 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D796.34B24866.16@ALPHA.WKU.EDU> Subject: RE: for the wish list ? "Jamie Jones, HICOM Operations" writes: > >How about something along the lines of : > >MCP> queue kick > >which only restarts those entries that have not been delivered. > >So, that if a message was originally sent to many people (such as >with a mailing list) the only entries to be retried are the ones >that are requeing/undelivered. > >This avoids duplicate messages being received by some people, when you >use the "queue ready" command. > This won't happen if you QUEUE READY the correct entry. For example, if you have the following entries: 10 INPROG 6120 LOCAL SMTP 15 READY 51 (waiting until 25-APR-1994 07:49:26.39) Doing a QUEUE READY 15 will cause a delivery attempt *only* for the recipients scheduled for RETRY. READYing 10 could cause a redelivery to everyone on the list. >Also, if possible, how about an optional "/route" qualifier which >overrides the smtp path for that particular message only. > I'll add that to the wish list. >Without needing to ready the message (so sending it to all people again) Again, if you READY the right one, that won't happen. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 25 Apr 1994 09:34:25 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 10:30:10 EDT From: George Weitzel Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D7AE.89220AE0.59@ube.ubalt.edu> Subject: Incoming JNET files not processed All incoming JNET files are remaining in the READY state. Outgoing JNET files appear to go ok. The MX_JNET_LOG.LOG file contains the following: 25-APR-1994 05:51:05.96 Processing incoming message, entry number 78 25-APR-1994 05:51:06.04 File not quite there yet...couldn't find the input file. The [MX.QUEUE.n] directory only contains the *.JNET_INPUT files. I recently upgraded to MX 4.0 but this *was* working ok after the upgrade. Any ideas? Thanks, George Weitzel ================================================================== George H. Weitzel BITNET: george@UBE Network Services Manager Internet: george@ube.ubalt.edu Academic Computing Center Voice: (410) 837-5486 University of Baltimore FAX: (410) 837-4860 1420 North Charles Street Baltimore, Maryland, USA 21201 ================================================================== ================================================================================ Archive-Date: Mon, 25 Apr 1994 09:45:47 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 09:44:43 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D7A8.2F5B8FE1.2@ALPHA.WKU.EDU> Subject: RE: Incoming JNET files not processed George Weitzel writes: > > >All incoming JNET files are remaining in the READY state. Outgoing JNET >files appear to go ok. The MX_JNET_LOG.LOG file contains the following: > >25-APR-1994 05:51:05.96 Processing incoming message, entry number 78 >25-APR-1994 05:51:06.04 File not quite there yet...couldn't find the > input file. > > >The [MX.QUEUE.n] directory only contains the *.JNET_INPUT files. I recently >upgraded to MX 4.0 but this *was* working ok after the upgrade. > Hmmm.... The message shown above only comes when the MX Jnet interface can't find the .JNET_INPUT file for each entry. You're sure the file is there for entry 78? Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 25 Apr 1994 10:41:44 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 08:36:20 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST%WKUVX1.BITNET@ULKYVM.LOUISVILLE.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097D79E.A1DB0880.14896@Data.Basix.COM> Subject: SMTP-Server and Local dying I've got a VMS 5.5, UCX 2.0, MX 3.3 system where the SMTP-Server and Local processes are starting to die regularly. (Upgrading to MultiNet AND MX 4.0 are scheduled for right after the semester is over.) I've enabled debugging with MX_SMTP_SERVER_DEBUG and MX_LOCAL_DEBUG, and there's nothing unusual in the *LOG.LOG files, and the SMTP_SERVER_EAST.LOG file has two lines, one for "starting" and one for "exiting", but there's no indication of error or anything like that. What else should I look for? I'm stuck! Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Internet training & consulting RHarwood@Data.Basix.COM | Info@Data.Basix.COM | DEC small-system management ================================================================================ Archive-Date: Mon, 25 Apr 1994 11:12:33 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: MXAlias. System-wide ? Date: 25 Apr 1994 16:01:08 GMT Message-ID: <2pgpg4$9m7@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097D79E.16DE96C0.5@HADASSAH.HUJI.AC.IL>, "Najman Kahana. Ext:7313" writes: =Hi. = = I find the MXAlias utility very useful. Since I have a very large =number of users, I am interested in setting up a "general" (system-wide) =alias table, as well as allowing the users the use of private ones. = = Is there a way of setting this up ? Does anyone have a utility =which allows this ? I want the user to "see" these entries on a DIR command, =but be able to maintain them on a system level. Use the MCP command "DEFINE ALIAS." Users can check the system-wide aliases via the command: $ MCR MX_EXE:MCP SHOW ALIAS -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 25 Apr 1994 13:13:06 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 13:07:31 EDT From: "Stanley J. McCaslin" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D7C4.845DA300.32462@psccs1.peru.edu> Subject: RE: SMTP-Server and Local dying I had a similar problem. There is no assurance they are the same cause, but our SMTP process dying was an early symptom which appeared in other processes later on, and which we traced to having too small a value in the GBLPAGFIL sysgen parameter. Stanley J. McCaslin Inet: mccaslin@psccs1.peru.edu Assistant Professor, Computer Science Phone:402/872-2208 Peru State College, Peru, NE 68421 Home: 402/872-7595 ================================================================================ Archive-Date: Mon, 25 Apr 1994 13:40:28 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 14:34:50 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: mccaslin@psccs1.peru.edu Message-ID: <0097D7D0.B7385200.6768@nscvax.princeton.edu> Subject: RE: SMTP-Server and Local dying "Stanley J. McCaslin" writes: > I had a similar problem. There is no assurance they are the same >cause, but our SMTP process dying was an early symptom which appeared in other >processes later on, and which we traced to having too small a value in the >GBLPAGFIL sysgen parameter. > GBLPAGFIL????? I've heard of GBLSECTIONS and GBLPAGES.... -- ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Mon, 25 Apr 1994 14:54:35 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: RE: SMTP-Server and Local dying Date: 25 Apr 1994 19:34:53 GMT Message-ID: <2ph60t$iun@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097D7D0.B7385200.6768@nscvax.princeton.edu>, Mighty Firebreather writes: = "Stanley J. McCaslin" writes: = => I had a similar problem. There is no assurance they are the same =>cause, but our SMTP process dying was an early symptom which appeared in other =>processes later on, and which we traced to having too small a value in the =>GBLPAGFIL sysgen parameter. => = = GBLPAGFIL????? = = I've heard of GBLSECTIONS and GBLPAGES.... $ MCR SYSGEN HELP PAR GBLPAGFIL Parameters GBLPAGFIL Global page file limit - establishes the maximum number of global pages with page file backing store that can be created. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Mon, 25 Apr 1994 15:15:34 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 13:08:51 -0700 From: "Ray Harwood -- Data Basix: (602)721-1988" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: rharwood@Data.Basix.COM Message-ID: <0097D7C4.B43BF860.15365@Data.Basix.COM> Subject: RE: SMTP-Server and Local dying > > I had a similar problem. There is no assurance they are the same > >cause, but our SMTP process dying was an early symptom which appeared in other > >processes later on, and which we traced to having too small a value in the > >GBLPAGFIL sysgen parameter. > GBLPAGFIL????? > I've heard of GBLSECTIONS and GBLPAGES.... In fact, my dying SMTP Server and Local processes were due to not being able to create files due to the index file being full... enabling DEBUG only WORSENED the problem, since that sucked up even more file headers. Off to install DEC's DFG, I suppose... Ray ----- Ray Harwood | Data Basix | DEC Pro Networking Editor Voice: (602)721-1988 | PO Box 18324 | "Internet Resource Guide" FAX: (602)721-7240 | Tucson, AZ 85731 | Internet training & consulting RHarwood@Data.Basix.COM | Info@Data.Basix.COM | DEC small-system management ================================================================================ Archive-Date: Mon, 25 Apr 1994 15:37:53 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 13:32:52 EDT From: Trevor Johnson Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: trevor@hepnsf.csudh.edu Message-ID: <0097D7C8.0ECA9EA0.5@hepnsf.csudh.edu> Subject: RE: SMTP-Server and Local dying >> I had a similar problem. There is no assurance they are the same >>cause, but our SMTP process dying was an early symptom which appeared in other >>processes later on, and which we traced to having too small a value in the >>GBLPAGFIL sysgen parameter. >> > > GBLPAGFIL????? > > I've heard of GBLSECTIONS and GBLPAGES.... GBLPAGFIL here (VAXstation 3100, VMS 5.5-1, CMU-IP) is set to 6024, up from the default value of 1024. Yes, it does exist. ================================================================================ Archive-Date: Mon, 25 Apr 1994 16:16:40 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 17:04:34 EDT From: George Weitzel Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D7E5.A1F9E2E0.34@ube.ubalt.edu> Subject: RE: Incoming JNET files not processed >>All incoming JNET files are remaining in the READY state. Outgoing JNET >>files appear to go ok. The MX_JNET_LOG.LOG file contains the following: >> >>25-APR-1994 05:51:05.96 Processing incoming message, entry number 78 >>25-APR-1994 05:51:06.04 File not quite there yet...couldn't find the >> input file. >> >> >>The [MX.QUEUE.n] directory only contains the *.JNET_INPUT files. I recently >>upgraded to MX 4.0 but this *was* working ok after the upgrade. >> >Hmmm.... The message shown above only comes when the MX Jnet >interface can't find the .JNET_INPUT file for each entry. You're sure >the file is there for entry 78? Well, ah, actually no. I'd swear that is was there yesterday though. Stranger things are happening though. MCP QUE SHO /FULL 78 returned and entry 63! I CANcelled 78 and had it working for a while, 'till it got back around to entry 78 (acording to MX_JNET_LOG.LOG, can remember exactly but I think entry 78 had returned). I CANcelled 78 and 63 and now this happens: $ mcp/nofile que sho/full 78 %MCP-I-QENTRIES, total matching entries: 0 $ mcp/nofile que sho/full 63 %MCP-E-QREADERR, error reading queue entry number 63 -FLQ-E-NOSUCHENT, entry number does not exist %MCP-I-QENTRIES, total matching entries: 0 I'm seeing the same message in MX_JNET_LOG.LOG as above again. It's seems to be stuck here repeating the same message in each new MX_JNET_LOG.LOG file, which are created two or three a second. I shutdown and restarted JNET and ROUTER and it's working again. I imagine it will get stuck when it gets back around to entry 78. George ================================================================== George H. Weitzel BITNET: george@UBE Network Services Manager Internet: george@ube.ubalt.edu Academic Computing Center Voice: (410) 837-5486 University of Baltimore FAX: (410) 837-4860 1420 North Charles Street Baltimore, Maryland, USA 21201 ================================================================== ================================================================================ Archive-Date: Mon, 25 Apr 1994 17:09:38 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <199404252122.AA10455@interlock.jci.com> Date: Mon, 25 Apr 1994 17:06:03 -0500 (CDT) From: arlen.walker@jci.com (Arlen P. Walker) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: Mail List addressing problem To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7BIT A lot of our mailers add a "personal name" in front of the address. When I created a new mailing list, the pele I added to the list couldn't post to it, because of the personal name. Since the personal is subject to change on a more frequent basis than the address, I'd like MX to ignore it, and just use the address. Example: Address I added to list:thomas.mccullough@jci.com This person cannot post to the list, gets permission denied. He subscribed to the list and I did a review and his added address was: Tom at 228-2929 Is there some way I can convince MX to ignore the personal phrase at the front and take only the part within angle brackets? Incidentally, when this kind of address is replied to through a different mailer (we haven't tried feeding it through MX yet) the mailer finds the correct address in that string and sends it out correctly. Have Fun, Arlen arlen.walker@jci.com --------------------------------------------------- This mail message contains 100% recycled electrons --------------------------------------------------- ================================================================================ Archive-Date: Mon, 25 Apr 1994 17:16:32 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 17:15:32 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D7E7.29EE260B.19@ALPHA.WKU.EDU> Subject: RE: Mail List addressing problem arlen.walker@jci.com (Arlen P. Walker) writes: > >A lot of our mailers add a "personal name" in front of the address. When I >created a new mailing list, the pele I added to the list couldn't post to >it, because of the personal name. Since the personal is subject to change >on a more frequent basis than the address, I'd like MX to ignore it, and >just use the address. Example: > MX doesn't pay any attention to the personal name. >Address I added to list:thomas.mccullough@jci.com > >This person cannot post to the list, gets permission denied. He subscribed >to the list and I did a review and his added address was: > >Tom at 228-2929 > >Is there some way I can convince MX to ignore the personal phrase at the >front and take only the part within angle brackets? Incidentally, when this >kind of address is replied to through a different mailer (we haven't tried >feeding it through MX yet) the mailer finds the correct address in that >string and sends it out correctly. > It's not the personal name, it's (probably) the case on the e-mail address. Unless the list or the entry is marked /NOCASE_SENSITIVE, then any e-mail from Tom *must* show a From: address of to work. Note the capital "T" and "M". Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Mon, 25 Apr 1994 19:03:58 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Mon, 25 Apr 1994 20:00:06 EDT From: Mighty Firebreather Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: carl@sol1.gps.caltech.edu Message-ID: <0097D7FE.27E827A0.6824@nscvax.princeton.edu> Subject: RE: SMTP-Server and Local dying carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) writes: >In article <0097D7D0.B7385200.6768@nscvax.princeton.edu>, Mighty Firebreather writes: >= "Stanley J. McCaslin" writes: >= >=> I had a similar problem. There is no assurance they are the same >=>cause, but our SMTP process dying was an early symptom which appeared in other >=>processes later on, and which we traced to having too small a value in the >=>GBLPAGFIL sysgen parameter. >=> >= >= GBLPAGFIL????? >= >= I've heard of GBLSECTIONS and GBLPAGES.... > > >$ MCR SYSGEN HELP PAR GBLPAGFIL > >Parameters > > GBLPAGFIL > > > Global page file limit - establishes the maximum number of global pages > with page file backing store that can be created. > Under VMS 5.4, at least, MCR SYSGEN SHOW GBL* turns up GBLSECTIONS. Only! SHOW GBLPAGES will show the parameter. I guess I just didn't look hard enough. I should have gotten suspicious when GBLPAGES didn't show as a result of SHOW GBL*. -- ************************************************************************* * Here, there be dragons! * * dragon@nscvax.princeton.edu * * * * I'm job hunting. Any offers or leads will be appreciated. * * Thanks! * * Richard B. Gilbert * ************************************************************************* ================================================================================ Archive-Date: Tue, 26 Apr 1994 06:41:09 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 13:39:54 EDT From: "Bj|rn Skeppner MTA/F, Huddinge Hosp" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-LIST@WKUVX1.WKU.EDU Message-ID: <0097D892.34B65B20.3@bimd01.hs.sll.se> Subject: Eudora-Mx Hi! I'm using Eudora on Macintosh. My problem is: I have 2 VAX-computers. On one I have Multinet installed, on the other I'm using CMU-IP (ver 6.6-5) and MX ver 4.0. -When i configure Eudora to use the VAX with CMU-IP (as the SMTP-server) it VERY often hangs when i attach a file to the message. After a few minutes it says, that it (MacTCP) has lost connection with my VAX. -If I configure Eudora to use the VAX witch I have multinet installed, as a SMTP-server it works! Is there any thing to to in configuration with CMU-IP or what? Any hints? PS: Sorry for my bad english.... but I do my very best! --------------------------------------------------------------------------- From: Bj|rn Skeppner /SM0OCV/ MTA/F69 Huddinge Hospital S-141 86 HUDDINGE SWEDEN bjsk@bimd01.hs.sll.se ================================================================================ Archive-Date: Tue, 26 Apr 1994 09:35:41 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <199404261349.AA06389@interlock.jci.com> Date: Tue, 26 Apr 1994 09:33:21 -0500 (CDT) From: arlen.walker@jci.com (Arlen P. Walker) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Mail List addressing problem To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7BIT >MX doesn't pay any attention to the personal name. > I guess I gt confused because it listed it in the address on the REVIEW response. Sorry. >It's not the personal name, it's (probably) the case on the e-mail >address. Unless the list or the entry is marked /NOCASE_SENSITIVE, I see how an individual address is listed as /nocase. How can the list be marked as /nocase? Have Fun, Arlen arlen.walker@jci.com --------------------------------------------------- This mail message contains 100% recycled electrons --------------------------------------------------- ================================================================================ Archive-Date: Tue, 26 Apr 1994 09:39:01 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 09:38:28 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D870.7A2F7A2D.7@ALPHA.WKU.EDU> Subject: RE: Mail List addressing problem arlen.walker@jci.com (Arlen P. Walker) writes: > >I see how an individual address is listed as /nocase. How can the list be >marked as /nocase? > MX V4.0-1 provides the ability to specify that a list should be case-insensitive when it's DEFINEd using DEFINE LIST/NOCASE_SENSITIVE. Note that any addresses already on the list will have to be individually REMOVEd and re-ADDed. The /NOCASE qualifier does not apply to addresses already on the list. Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Tue, 26 Apr 1994 09:41:31 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 11:37:07 ADT From: Greg Bishop Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu Message-ID: <0097D881.0D7A2AC0.7@ac.nsac.ns.ca> Subject: MCP SHUTDOWN not shutting down DNSMTP MCP shutdown is not stopping the DNSMTP process on our site. MX seems to get a bit confused every couple of weeks or so. Our usual solution is to execute an MCP SHUTDOWN command and submit the MX_STARTUP procedure. Since we've installed version 4.0, this hasn't been working for us. After a bit of monitoring with log files, etc, I noticed that the DNSMTP process was not disappearing from the SHOW SYSTEM output, whereas all the other MX processes were. So I did a STOP/PROCESS on it and got things to work. Is this a bug in version 4? Greg Greg Bishop Internet: GBISHOP@AC.NSAC.NS.CA System Manager Voice: (902) 893-6693 Nova Scotia Agricultural College Fax: (902) 895-4547 Truro, Nova Scotia CANADA B2N 5E3 ================================================================================ Archive-Date: Tue, 26 Apr 1994 11:09:31 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Message-ID: <199404261521.AA11830@interlock.jci.com> Date: Tue, 26 Apr 1994 11:05:44 -0500 (CDT) From: arlen.walker@jci.com (Arlen P. Walker) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: RE: Mail List addressing problem To: MX-List@WKUVX1.WKU.EDU MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7BIT >MX V4.0-1 provides the ability to specify that a list should be >case-insensitive when it's DEFINEd using DEFINE LIST/NOCASE_SENSITIVE. 4.0-1? But I've got 4.0-1 and it ("modify list/nocase") didn't work. I brought 4.0-1 down and put it up last w...... oops! Sorry about that, chief! ;{>} Have Fun, Arlen arlen.walker@jci.com --------------------------------------------------- This mail message contains 100% recycled electrons --------------------------------------------------- ================================================================================ Archive-Date: Tue, 26 Apr 1994 11:27:06 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 09:59:22 EDT From: "Mark geib@vistanm.com" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: geib@vistanm.com Message-ID: <0097D873.65C57A58.1501@vistanm.com> Subject: File tools for OpenVMS/AXP Does anyone know where zip, unzip, and maybe kermit or c-kermit can be acquired for OpenVMS/AXP. I can Email or FTP to get them. Thanks. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Mark D. Geib | "The most likely way for the world to be Vista Control Systems, Inc. | destroyed, most experts agree, is by accident. Los Alamos, NM | That's where we come in; we're computer Email: geib@vistanm.com | professionals. We cause accidents." Voice:505.662.2484 | -Nathaniel Borenstein FAX:505.662.3956 | %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% ================================================================================ Archive-Date: Tue, 26 Apr 1994 11:33:34 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 11:32:54 CDT From: "Hunter Goatley, WKU" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D880.76D63C62.1@ALPHA.WKU.EDU> Subject: RE: File tools for OpenVMS/AXP "Mark geib@vistanm.com" writes: > >Does anyone know where zip, unzip, and maybe kermit or c-kermit can be acquired >for OpenVMS/AXP. I can Email or FTP to get them. > All of these, and many more, can be found on ftp.spc.edu in [.MACRO32.SAVESETS]. See [.MACRO32]BRIEF.DESCRIPTION for a brief description of each package there. You can get them via e-mail from FILESERV@WKUVX1.WKU.EDU. Send the following commands in the body of a mail message to FILESERV for more info: DIR ALL HELP Hunter ------ Hunter Goatley, VMS Systems Programmer, Western Kentucky University goathunter@ALPHA.WKU.EDU (or goathunter@WKUVX1.WKU.EDU) ================================================================================ Archive-Date: Tue, 26 Apr 1994 11:56:04 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: doug@grinch.hcf.jhu.edu (Douglas W. O'Neal) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX / NETLIB not resolving names Date: 26 Apr 1994 16:36:41 GMT Message-ID: <2pjfupINNnjr@jhunix.hcf.jhu.edu> To: MX-List@WKUVX1.WKU.EDU I am running MX V4.0-1 with NETLIB V1.6 and UCX 2.0 on a VAXstation 3100 running VMS 6.0. My problem is that if I send mail repeatly to an address, about one message in four will not be delivered. Mailqueue will list the last error as "%MX-F-NOHOST, no such host" and increment the DNS errors count after each retry. Usually, the mail will be delivered after a half dozen retries. Other times, the mail will go through on the first try. I have loaded NSQUERY and tested looking up addresses. I have not been able to get nsquery to fail for any valid lookup. I have also turned on debugging for the named process on our nameserver. Whenever mail is delivered successfully, named logs a normal query. Whenever there is a DNS failure by MX, named does not log *any* connection from the vaxstation. I have defined/system NETLIB_NAMESERVERS to point specifically to our primary nameserver so I know which nameserver is being queried. None of the ucx clients have any problems with resolving names. The addresses I am testing are local to my domain although the problem also occurs with machines outside my domain. Does anyone have an idea of what is going on? My users are getting a little annoyed with have mail fail this way. Thanks for any suggestions. Doug -- Doug O'Neal, Distributed Systems Programmer, Johns Hopkins University doug@jhuvms.bitnet, doug@jhuvms.hcf.jhu.edu, mimsy!aplcen!jhunix!doug ================================================================================ Archive-Date: Tue, 26 Apr 1994 12:34:53 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 10:28:29 PST From: robert@dis.ucsf.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D877.77400060.14161@dis.ucsf.edu> Subject: RE: File tools for OpenVMS/AXP Kermit is at kermit.columbia.edu (used to be watsun.columbia.edu, and that still works). The entries below are from the VAX LIST, a list of VMS freeware. You can get the list as follows: The VAX Software List NOTE: A current version of this file may be obtained via anonymous ftp from pomona.claremont.edu (134.173.4.160). Please try to restrict ftp usage to times other than weekdays 10am-10pm, PST (GMT-0800). If you must ftp during these hours, please use acme.claremont.edu (134.173.4.162). It is also available by sending e-mail to VMSSERV@POMONA.CLAREMONT.EDU with the command SEND VAX_LIST.PACKAGE in the body of the message. On BITNET, the address is VMSSERV@POMONA, and either e-mail or an interactive message will do the trick. If you use an interactive message and you are on a VMS system running JNET, you should use VMSDUMP in place of SEND. ZIP-UNZIP Zip v1.9 and UnZip v5.0 for VMS. Sources available as package ZIP-UNZIP. Executables available as package ZIP_EXE for sites without a C compiler. Availability: F11, S16 F11 FTP.SPC.EDU S16 FILESERV@WKUVX1.BITNET Accepts HELP, DIR, SEND package. ------------------------------------------------------------------------------- Robert Weiner Manager, Development Information Systems robert@dis.ucsf.edu University of California, San Francisco > Does anyone know where zip, unzip, and maybe kermit or c-kermit can be acquired > for OpenVMS/AXP. I can Email or FTP to get them. > > Thanks. > Mark D. Geib | "The most likely way for the world to be > Vista Control Systems, Inc. | destroyed, most experts agree, is by accident. > Los Alamos, NM | That's where we come in; we're computer > Email: geib@vistanm.com | professionals. We cause accidents." > Voice:505.662.2484 | -Nathaniel Borenstein > FAX:505.662.3956 | > ================================================================================ Archive-Date: Tue, 26 Apr 1994 15:38:45 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: RE: Mail List addressing problem Date: 26 Apr 1994 20:21:03 GMT Message-ID: <2pjt3f$53t@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <199404261349.AA06389@interlock.jci.com>, arlen.walker@jci.com (Arlen P. Walker) writes: =>MX doesn't pay any attention to the personal name. => =I guess I gt confused because it listed it in the address on the REVIEW =response. Sorry. = =>It's not the personal name, it's (probably) the case on the e-mail =>address. Unless the list or the entry is marked /NOCASE_SENSITIVE, = =I see how an individual address is listed as /nocase. How can the list be =marked as /nocase? With the DEFINE LIST/NOCASE or MOD LIST/NOCASE command to MCP. At least under MX v4.0-1: $ MCR MX_EXE:MCP HELP DEF LIST/CASE DEFINE LIST /CASE_SENSITIVE /CASE_SENSITIVE (default) /NOCASE_SENSITIVE Enables or disables case-sensitivity with regard to mailing list subscribers. By default, MX treats the left-hand side of subscriber addresses in a case-sensitive manner with regard to SIGNOFF and SET commands. If a list is defined /NOCASE_SENSITIVE, then the case of subscriber addresses will be ignored. -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Tue, 26 Apr 1994 15:50:08 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Tue, 26 Apr 1994 15:44:29 CST From: chanaka@bible.acu.edu Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU Message-ID: <0097D8A3.9C4D75A0.4140@bible.acu.edu> Subject: RE: Mail List addressing problem Date sent: 26-APR-1994 15:44:24 >From: MX%"MX-List@WKUVX1.WKU.EDU" 26-APR-1994 12:04:15.08q >To: CHANAKA >CC: >Subj: RE: Mail List addressing problem > >Return-Path: >Sender: owner-mx-list@WKUVX1.WKU.EDU >Date: Tue, 26 Apr 1994 11:05:44 -0500 (CDT) >From: arlen.walker@jci.com (Arlen P. Walker) >Reply-To: MX-List@WKUVX1.WKU.EDU >Subject: RE: Mail List addressing problem >To: MX-List@WKUVX1.WKU.EDU > >>MX V4.0-1 provides the ability to specify that a list should be >>case-insensitive when it's DEFINEd using DEFINE LIST/NOCASE_SENSITIVE. > >4.0-1? But I've got 4.0-1 and it ("modify list/nocase") didn't work. I >brought 4.0-1 down and put it up last w...... [walker.to-do]>oops! Sorry about that, chief! ;{>} > > >Have Fun, >Arlen > >arlen.walker@jci.com >--------------------------------------------------- >This mail message contains 100% recycled electrons >--------------------------------------------------- > > --------------------------------------------------------------------------- Chanaka Dooldeniya "Fix the Problem, Not the Blame" chanaka@BIBLE.ACU.EDU "Make Corrections, Not Excuses" cpd58431@ACUVAX.ACU.EDU ZSCDOOLDENIY@ACUADM.ACU.EDU "TAKE RESPONSIBILITY" Phon WK:674 2132 --------------------------------------------------------------------------- ================================================================================ Archive-Date: Wed, 27 Apr 1994 09:42:01 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Wed, 27 Apr 1994 16:26:00 EDT From: "Eberhard Mater,German Aerospace Research Establishment (DLR)" Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@WKUVX1.WKU.EDU Message-ID: <0097D972.939C4420.3@grzap1.rz.go.dlr.de> Subject: Q: Mailing list address Hallo, how can i define an address like: decnetnode::mx%"userid@node.dlr.de" in your mailing list?? Thank's Eberhard mfg +-----------------------------------------------------------------------+ | Eberhard Mater, German Aerospace Research Establishment (DLR) | | D-37073 Goettingen, Bunsenstr.10 | | Phone: +49 551 709-2453 ! FAX: +49 551 709-2169 | | Internet: system@grzap1.rz.go.dlr.de | | DECnet : grzap1::system | +-----------------------------------------------------------------------+ ================================================================================ Archive-Date: Thu, 28 Apr 1994 06:59:53 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 28 Apr 1994 13:54:22 CET From: Hans-Joachim Koch Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: sys_hjk@LISSY1.lif.de Message-ID: <0097DA26.8ED2C860.17@LISSY1.LIF.DE> Subject: no rewrite tooks place, why? Hello, I have a small problem with a rewrite rule. We are just setting up our complete routing and we have some temporary problemes. Just in this case we have to rewrite a name with an ip address, because the nameserver does not know this subnet (don't ask why :-) Thats the rewrite rule, its on top of the list: > DEFINE REWRITE_RULE "<{U}@BB001.{D}>" "<{U}@[149.233.195.2]>" But no rewrite takes place, why? mx_router_log shows: > 28-APR-1994 13:42:11.97 %PROCESS, Recipient #0: > 28-APR-1994 13:42:11.97 %REWRITE, No rewrite rules matched > 28-APR-1994 13:42:11.97 %FINDPATH, Site-spec expand on bb001.lif.de err=00000000 Any ideas? Thanks, Hans. -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Thu, 28 Apr 1994 10:08:35 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Thu, 28 Apr 1994 10:03:04 EDT From: Chris Olive Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: sys_hjk@LISSY1.lif.de, olive@sgi.siemens.com Message-ID: <0097DA06.3F0D3C40.14@sgi.siemens.com> Subject: RE: no rewrite tooks place, why? In article <0097DA26.8ED2C860.17@LISSY1.LIF.DE>, Hans-Joachim Koch writes: >I have a small problem with a rewrite rule. We are just setting up our >complete routing and we have some temporary problemes. Just in this case >we have to rewrite a name with an ip address, because the nameserver >does not know this subnet (don't ask why :-) > >Thats the rewrite rule, its on top of the list: >> DEFINE REWRITE_RULE "<{U}@BB001.{D}>" "<{U}@[149.233.195.2]>" > >But no rewrite takes place, why? mx_router_log shows: >> 28-APR-1994 13:42:11.97 %PROCESS, Recipient #0: >> 28-APR-1994 13:42:11.97 %REWRITE, No rewrite rules matched >> 28-APR-1994 13:42:11.97 %FINDPATH, Site-spec expand on bb001.lif.de err=00000000 > >Any ideas? Did you remember to reset the router? Chris _______________________________________________________________________________ ___ ___ ___ _ _ ___ _ _ ___ /___ | |__ |\ /| |__ |\ | /___ Chris Olive, VMS Systems Consultant ___/ _|_ |___ | Y | |___ | \| ___/ Internet: olive@sgi.siemens.com Medical Systems, Inc. Voice: 708.304.7793 2501 N. Barrington Road. FAX: 708.304.7704 Hoffman Estates, IL 60195 CompuServe: 73740,1636 _______________________________________________________________________________ ================================================================================ Archive-Date: Fri, 29 Apr 1994 03:03:44 EDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: carl@SOL1.GPS.CALTECH.EDU (Carl J Lydick) Subject: Re: no rewrite tooks place, why? Date: 29 Apr 1994 07:39:16 GMT Message-ID: <2pqdj4$7r5@gap.cco.caltech.edu> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097DA26.8ED2C860.17@LISSY1.LIF.DE>, Hans-Joachim Koch writes: =I have a small problem with a rewrite rule. We are just setting up our =complete routing and we have some temporary problemes. Just in this case =we have to rewrite a name with an ip address, because the nameserver =does not know this subnet (don't ask why :-) = =Thats the rewrite rule, its on top of the list: => DEFINE REWRITE_RULE "<{U}@BB001.{D}>" "<{U}@[149.233.195.2]>" = =But no rewrite takes place, why? mx_router_log shows: => 28-APR-1994 13:42:11.97 %PROCESS, Recipient #0: => 28-APR-1994 13:42:11.97 %REWRITE, No rewrite rules matched => 28-APR-1994 13:42:11.97 %FINDPATH, Site-spec expand on bb001.lif.de err=00000000 Have you RESET the router process? (Please note: Under some versions of MX, you might have to shut down the agent processes and restart them for some changes to take effect; I don't know whether this is one such case). -------------------------------------------------------------------------------- Carl J Lydick | INTERnet: CARL@SOL1.GPS.CALTECH.EDU | NSI/HEPnet: SOL1::CARL Disclaimer: Hey, I understand VAXen and VMS. That's what I get paid for. My understanding of astronomy is purely at the amateur level (or below). So unless what I'm saying is directly related to VAX/VMS, don't hold me or my organization responsible for it. If it IS related to VAX/VMS, you can try to hold me responsible for it, but my organization had nothing to do with it. ================================================================================ Archive-Date: Fri, 29 Apr 1994 06:48:03 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 29 Apr 1994 07:10:43 EDT From: Rich Hill Reply-To: MX-List@WKUVX1.WKU.EDU To: mx-list@wkuvx1.wku.edu CC: rich_h@simusa.sim.org Message-ID: <0097DAB7.55DE2040.12363@mailhub.sim.org> Subject: Help with MX and Pegasus Mail This may be slightly off topic, but since it involves e-mail and MX, here goes: If anyone could help point me in the right direction, I am interested in using Pegasus Mail on our in-house PCs that are networked with our VAX using PathWorks. I have been using MX V3.3 (it is a great product Hunter, thanks) for the last couple of months along with DECUS UUCP V2.0. While the mail utility that comes with PathWorks does work, it would ben much better if I could use Pegasus. What do I need to make this work? How do I configure the client PCs? Do I need any additional protocol support on my VAX? I would appreciate any help or pointers that anyone may be able to give me. Also, if anyone knows of any mailing lists that relate to PathWorks or P-Mail, I would appreciate getting an address for them. Thanks, Rich Hill -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Rich Hill S I M rich_h@simusa.sim.org Systems Administrator b y EasyLink: 62923838 SIM USA, Inc. P r a y e r Phone: 1-704-587-1462 Charlotte, NC since 1893 FAX: 1-704-587-1518 -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- ================================================================================ Archive-Date: Fri, 29 Apr 1994 10:46:57 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU Date: Fri, 29 Apr 1994 18:41:57 EDT From: "Najman Kahana. Ext:7313" Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU CC: najman%hadassah@VMS.HUJI.AC.IL Message-ID: <0097DB17.E647B960.23@HADASSAH.HUJI.AC.IL> Subject: RE: Help with MX and Pegasus Mail Subj: Help with MX and Pegasus Mail >If anyone could help point me in the right direction, I am interested in >using Pegasus Mail on our in-house PCs that are networked with our VAX >using PathWorks. I have been using MX V3.3 (it is a great product Hunter, >thanks) for the last couple of months along with DECUS UUCP V2.0. > >While the mail utility that comes with PathWorks does work, it would ben >much better if I could use Pegasus. What do I need to make this work? >How do I configure the client PCs? Do I need any additional protocol >support on my VAX? > >I would appreciate any help or pointers that anyone may be able to give me. >Also, if anyone knows of any mailing lists that relate to PathWorks or >P-Mail, I would appreciate getting an address for them. > >Thanks, > >Rich Hill HI. I have had problems setting up Mercury too. The Mercury guru is David Harris. He really knows his stuff, and has helped me solve my problems. I am enclosing his address. Najman Kahana Najman@hadassah.bitnet ------------------------------------------------------------------ ------------------- David Harris -+- Pegasus Mail -------------------- Box 5451, Dunedin, New Zealand | e-mail: david@pmail.gen.nz +64 3 4536880/Fax +64 3 4536612 | CIS: >internet:david@pmail.gen.nz +----------+------------------+------------------------------+---------------+ ! !\ ! / ! NAJMAN KAHANA ! Hadassah University Hospital ! thanks, ! ! ! \ !/\ ! najman@HADASSAH. ! Jerusalem, Israel ! we have our ! ! ! \! \ ! BITNET ! (visit our capital soon) ! own viruses ! +----------+------------------+------------------------------+---------------+ ================================================================================ Archive-Date: Fri, 29 Apr 1994 19:26:57 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: sys_hjk@lissy1.lif.de (Hans-Joachim Koch) Subject: RE: no rewrite tooks place, why? Date: 29 Apr 1994 09:21:49 GMT Message-ID: <2pqjjd$hh6@sunny.lif.de> Reply-To: MX-List@WKUVX1.WKU.EDU To: MX-List@WKUVX1.WKU.EDU In article <0097DA06.3F0D3C40.14@sgi.siemens.com>, Chris Olive writes: > Did you remember to reset the router? Sure! many times... -- Hans-Joachim Koch, Computer department of Lahmeyer International Lyoner Strasse 22, D-60528 Frankfurt, Germany Phone: +49 (69) 6677-642, Fax: +49 (69) 6677-388, Tx: 413478 li d ================================================================================ Archive-Date: Fri, 29 Apr 1994 19:28:27 CDT Sender: owner-mx-list@WKUVX1.WKU.EDU From: brodie@fps.mcw.edu (Kent C Brodie) Reply-To: MX-List@WKUVX1.WKU.EDU Subject: MX 4.0, decus uucp, and REWRITE rules? Message-ID: <1994Apr29.160321.816@fps.mcw.edu> Date: 29 Apr 94 16:03:21 CST To: MX-List@WKUVX1.WKU.EDU Hi. Does anyone know if there are special re-write rules needed to handle UUCP in MX 4.0...? In order to handle "!" addresses correctly, Matt had given me the following a long time ago: DEFINE REWRITE "<@{route}:{host}!{user}@fps.mcw.edu>" - "<@{route}:{host}!{user}@fps.mcw.edu>" ! i.e., no-op DEFINE REWRITE "<{host}!{user}@fps.mcw.edu>" "<{user}@{host}.UUCP>" ! DEFINE PATH *.UUCP UUCP ...are rules like these obsolete now? -- Kent C. Brodie - Sr. Systems Manager InterNet: brodie@fps.mcw.edu Faculty Physicians & Surgeons uucpNet: fps!brodie Medical College of Wisconsin MaBellNet: +1 414 266 5080 "The UEO is VERY upset that a scientist was able to fire all those torpedoes.."