<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: Email address being blocked? in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7057095#M104742</link>
    <description>&lt;P&gt;&amp;gt; How can I see the activity that might show why this email is not being&lt;BR /&gt;&amp;gt; received? [...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I don't know.&amp;nbsp; Most of the available diagnostics deal with receiving,&lt;BR /&gt;not sending (TCPIP$SMTP_RECV_TRACE, for example).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I don't use "@list" mail distribution lists, so I know nothing, but I&lt;BR /&gt;can't see what's in yours, and the HELP says that you should 'enclose&lt;BR /&gt;this construction in quotation marks (").'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; What happens if you manually specify the problem address from that&lt;BR /&gt;list?&amp;nbsp; (Is the problem with the address or with the list?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcpip show version&lt;/P&gt;</description>
    <pubDate>Wed, 31 Jul 2019 20:21:08 GMT</pubDate>
    <dc:creator>Steven Schweda</dc:creator>
    <dc:date>2019-07-31T20:21:08Z</dc:date>
    <item>
      <title>Email address being blocked?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7056830#M104740</link>
      <description>&lt;P&gt;I'm sending an email from an Itanium server to a distribution list.&amp;nbsp; I am in the list and another email address is in the list that goes to a Nagios server as a service check.&amp;nbsp; I receive the email but the Nagios server does not.&amp;nbsp; Both addresses are in the same domain.&amp;nbsp; This does work on a different Itanium server.&lt;/P&gt;&lt;P&gt;MAIL/SUBJECT="CUST FROM CUSTTN (CUST) SUCCESS" MAIL.BODY @MAIL2.DIS&lt;/P&gt;&lt;P&gt;How can I see the activity that might show why this email is not being received?&amp;nbsp; The .log file indicated by tcpip&amp;gt;show config smtp is empty.&amp;nbsp; The other log files in that directory don't have any data from today.&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;Steve&lt;/P&gt;</description>
      <pubDate>Mon, 29 Jul 2019 20:48:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7056830#M104740</guid>
      <dc:creator>HudsonRecords</dc:creator>
      <dc:date>2019-07-29T20:48:04Z</dc:date>
    </item>
    <item>
      <title>Re: Email address being blocked?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7056867#M104741</link>
      <description>&lt;P&gt;It's not clear from your post how big the distribution list is, but one thing I have found is that if the list is approximately 1024 characters in size, then beyond a certain address, it will be truncated (this is due to processing by the DCL CLI when it parses the "@dislistname"), so I would check first of all that your list size isn't hovering around that size (you also need to take into account carriage returns, line feeds, and potentially other stuff like length-encoding byte/word) - it may appear to work on another system because the order of addresses in the DL is different, so it's actually a different address at which the truncation occurs).&lt;/P&gt;&lt;P&gt;Beyond that, there are some logical names that you can define which may help with your analysis.&lt;/P&gt;&lt;P&gt;I spent some time a while ago extrapolating logical names from an - even then - old copy of the Compaq TCP/IP Services for OpenVMS Management V5.1 manual (AA-LU50L-TE, JAN-2001).&lt;/P&gt;&lt;P&gt;I won't go into detail as to what the various logical names do, and what type/value of equivalence name they need (Boolean, integer etc.) - it's left as an exercise for the the reader once you've found/downloaded a copy of the manual (or a more up-to-date copy for your version).&lt;/P&gt;&lt;P&gt;TCPIP$SMTP_8BITMIME_HACK&lt;BR /&gt;TCPIP$SMTP_ALTGATE_ALWAYS&lt;BR /&gt;TCPIP$SMTP_COMMON&lt;BR /&gt;TCPIP$SMTP_INBOUND_NOXVMS&lt;BR /&gt;TCPIP$SMTP_JACKET_LOCAL&lt;BR /&gt;TCPIP$SMTP_LOCAL_ALIAS_ONLY&lt;BR /&gt;TCPIP$SMTP_LOG_LEVEL&lt;BR /&gt;TCPIP$SMTP_LOG_LINE_NUMBERS&lt;BR /&gt;TCPIP$SMTP_MIME_HACK&lt;BR /&gt;TCPIP$SMTP_MTS_ALLIN1&lt;BR /&gt;TCPIP$SMTP_MX_IF_NOALTGATE&lt;BR /&gt;TCPIP$SMTP_NO_MX&lt;BR /&gt;TCPIP$SMTP_NO_SUBS_DOMAIN_INBOUND&lt;BR /&gt;TCPIP$SMTP_NOSEY&lt;BR /&gt;TCPIP$SMTP_POSTMASTER_ALIAS&lt;BR /&gt;TCPIP$SMTP_PROHIBIT_USER_HEADERS&lt;BR /&gt;TCPIP$SMTP_RECV_TRACE&lt;BR /&gt;TCPIP$SMTP_RECV_DEBUG&lt;BR /&gt;TCPIP$SMTP_RECV_SNAPSHOT_BLOCKS&lt;BR /&gt;TCPIP$SMTP_REWRITE_MTS_FROM&lt;BR /&gt;TCPIP$SMTP_SFF_REQUIRES_PRIV&lt;BR /&gt;TCPIP$SMTP_SYMB_SNAPSHOT_BLOCKS&lt;BR /&gt;TCPIP$SMTP_SYMB_TRACE&lt;BR /&gt;TCPIP$SMTP_VMSDEF_TO&lt;BR /&gt;TCPIP$SMTP_VMSMAIL_PARSE&lt;BR /&gt;TCPIP$SMTP_VMSMAIL_SEND&lt;/P&gt;&lt;P&gt;Of course, there may be more logical names that have since been added, or some of the above have become obsolete/deprecated.&lt;/P&gt;&lt;P&gt;This reminds me that whilst housekeeping my directory on a test system recently, I found some (IIRC) TRACE.TXT files in my own directory, which were generated by SMTP as a result of me having defined one or more of these logicals (or the UCX equivalent) whilst trying to get to the bottom of email problems I was having (truncation of email addresses as I alluded to, and callable mail routines hanging on a test system when specifying an internet-style address (the SMTP symbiont was attempting DNS translation of the "@domain" part for each address;&amp;nbsp; the test system is on a closed network with no gateway &amp;amp; no DNS server, and the DL was full of internet-style addresses, making the process that was calling the callable mail routines appear to be stuck)).&lt;/P&gt;&lt;P&gt;Hopefully one or ''tother of these suggestions will help.&lt;/P&gt;&lt;P&gt;If you do find the cause, please do come back and let us all know;&amp;nbsp; you never know when someone else will suffer from the same problem in future.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;</description>
      <pubDate>Tue, 30 Jul 2019 06:43:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7056867#M104741</guid>
      <dc:creator>Mark_Corcoran</dc:creator>
      <dc:date>2019-07-30T06:43:43Z</dc:date>
    </item>
    <item>
      <title>Re: Email address being blocked?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7057095#M104742</link>
      <description>&lt;P&gt;&amp;gt; How can I see the activity that might show why this email is not being&lt;BR /&gt;&amp;gt; received? [...]&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I don't know.&amp;nbsp; Most of the available diagnostics deal with receiving,&lt;BR /&gt;not sending (TCPIP$SMTP_RECV_TRACE, for example).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; I don't use "@list" mail distribution lists, so I know nothing, but I&lt;BR /&gt;can't see what's in yours, and the HELP says that you should 'enclose&lt;BR /&gt;this construction in quotation marks (").'&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp; What happens if you manually specify the problem address from that&lt;BR /&gt;list?&amp;nbsp; (Is the problem with the address or with the list?)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; tcpip show version&lt;/P&gt;</description>
      <pubDate>Wed, 31 Jul 2019 20:21:08 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7057095#M104742</guid>
      <dc:creator>Steven Schweda</dc:creator>
      <dc:date>2019-07-31T20:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Email address being blocked?</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7057775#M104745</link>
      <description>&lt;P&gt;$ DEFINE/SYSTEM&amp;nbsp;&lt;SPAN&gt;TCPIP$SMTP_LOG_LEVEL&lt;/SPAN&gt; 3&lt;/P&gt;&lt;P&gt;stop and start SMTP&lt;/P&gt;&lt;P&gt;you should now get useful information in the SMTP log file.&lt;/P&gt;</description>
      <pubDate>Tue, 06 Aug 2019 15:43:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/email-address-being-blocked/m-p/7057775#M104745</guid>
      <dc:creator>Ian Miller.</dc:creator>
      <dc:date>2019-08-06T15:43:54Z</dc:date>
    </item>
  </channel>
</rss>

