<?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: SMTP_EXCMAXHOP in Operating System - OpenVMS</title>
    <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916079#M51528</link>
    <description>It has occured again today, but just produced 15 such errors and was then quiet again. No chance to trace this.</description>
    <pubDate>Tue, 14 Feb 2006 05:35:44 GMT</pubDate>
    <dc:creator>Edwin Gersbach_2</dc:creator>
    <dc:date>2006-02-14T05:35:44Z</dc:date>
    <item>
      <title>SMTP_EXCMAXHOP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916075#M51524</link>
      <description>In a TCPIP$SMTP_LOGFILE I was made aware of the following error entry:&lt;BR /&gt;%TCPIP-E-EXCMAXHOP, maximum number of hops exceeded; mail loop suspected&lt;BR /&gt;&lt;BR /&gt;Is there any way to get some information about the problem? I perfectly understand what has happened here, but in order to narrow down the problem I guess I should at least know what the mail destination was. Not even a timestamp is in the logfile which would allow to check for systems down or the like.&lt;BR /&gt;&lt;BR /&gt;I've just sent several test mails without any problems and the error was logged only on one node of a two-node cluster. It can therefore not be a general problem.&lt;BR /&gt;&lt;BR /&gt;Is there any way to get more information - if not for this occurence so at least for the next time?&lt;BR /&gt;&lt;BR /&gt;Edwin</description>
      <pubDate>Thu, 04 Aug 2005 02:17:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916075#M51524</guid>
      <dc:creator>Edwin Gersbach_2</dc:creator>
      <dc:date>2005-08-04T02:17:54Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP_EXCMAXHOP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916076#M51525</link>
      <description>It will be hard to trace it down, but it may be worth a try:&lt;BR /&gt;&lt;BR /&gt;1. $ @sys$manager:TCPIP$DEFINE_COMMANDS.COM&lt;BR /&gt;setus up a number of commands. VERY helpful...&lt;BR /&gt;2. Determine the address of the intended receiving machine. $ TCPIP PING may work, but it will fail if the domain has no DNS entry (purely MX-based). Consider NSLOOKUP or, for MX records, DIG to get this data.&lt;BR /&gt;3. Now run TRACEROUTE &lt;ADDRESS&gt; and look for a loop. It might be it won't show the IP address or name of routers, but perhaps it will.&lt;BR /&gt;&lt;BR /&gt;(All these (Unix) based commands have a load on options, these are covered under TCPIP&amp;gt; HELP &lt;FACILITY&gt;, than choose FLAGS. (As so many, I'm still waiting for a decent, VMS-like DCL interface and HELP for all these TCPIP commands...) &lt;BR /&gt;&lt;BR /&gt;Check route and default gateway on the node where the problem occurs.&lt;/FACILITY&gt;&lt;/ADDRESS&gt;</description>
      <pubDate>Fri, 05 Aug 2005 01:39:55 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916076#M51525</guid>
      <dc:creator>Willem Grooters</dc:creator>
      <dc:date>2005-08-05T01:39:55Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP_EXCMAXHOP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916077#M51526</link>
      <description>Edwin,&lt;BR /&gt;&lt;BR /&gt;to capture more information - should this error happen again - would mean to enable SMTP logging. See chapter 18.5.1 in the TCPIP Mgmt guide:&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h71000.www7.hp.com/doc/732final/6526/6526pro_039.html#logicals_sec" target="_blank"&gt;http://h71000.www7.hp.com/doc/732final/6526/6526pro_039.html#logicals_sec&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;To reduce logfile size, consider to enable shapshot logging.&lt;BR /&gt;&lt;BR /&gt;Volker.</description>
      <pubDate>Fri, 05 Aug 2005 02:16:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916077#M51526</guid>
      <dc:creator>Volker Halle</dc:creator>
      <dc:date>2005-08-05T02:16:21Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP_EXCMAXHOP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916078#M51527</link>
      <description>Willem,&lt;BR /&gt;&lt;BR /&gt;As I mentioned, this is not a permanent problem - it occured only once so far. As I don't know the mail destination I can neither ping or trace.&lt;BR /&gt;&lt;BR /&gt;Volker,&lt;BR /&gt;&lt;BR /&gt;I had some hope that such information is logged somewhere by default. Well then, if/when this problem occures again I will enable snapshot logging.&lt;BR /&gt;&lt;BR /&gt;Many thanks&lt;BR /&gt;Edwin</description>
      <pubDate>Fri, 05 Aug 2005 02:40:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916078#M51527</guid>
      <dc:creator>Edwin Gersbach_2</dc:creator>
      <dc:date>2005-08-05T02:40:53Z</dc:date>
    </item>
    <item>
      <title>Re: SMTP_EXCMAXHOP</title>
      <link>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916079#M51528</link>
      <description>It has occured again today, but just produced 15 such errors and was then quiet again. No chance to trace this.</description>
      <pubDate>Tue, 14 Feb 2006 05:35:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-openvms/smtp-excmaxhop/m-p/4916079#M51528</guid>
      <dc:creator>Edwin Gersbach_2</dc:creator>
      <dc:date>2006-02-14T05:35:44Z</dc:date>
    </item>
  </channel>
</rss>

