The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

Strange Email Error

Discussion in 'E-mail Discussions' started by mickalo, Sep 24, 2006.

  1. mickalo

    mickalo Well-Known Member

    Joined:
    Apr 16, 2002
    Messages:
    765
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    N.W. Iowa
    Hello,

    what hoping someone could explain this email error. I've never come accross an error message like this before:
    Code:
    The original message was received at Sun, 24 Sep 2006 06:23:49 -0400 from
    srv04.futurepoint.com [67.15.8.86]
    
       ----- The following addresses had permanent fatal errors -----
    <admin@uk.schools.ac>
        (reason: 554 5.4.6 Too many hops)
    
       ----- Transcript of session follows -----
    554 5.4.6 Too many hops 26 (25 max): from <schools_ac@schools.ac> via
    localhost, to <admin@uk.schools.ac>
    
    what exactly does the "hops" refer too here ?

    Mickalo
     
  2. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    hops are the number of Received: header lines. The protcol governing the relaying of email allows for an email to be dropped if it relayed through too many servers to avoid infinite loops. e.g. A forwards to B forwards to C forwards to A etc
     
  3. mickalo

    mickalo Well-Known Member

    Joined:
    Apr 16, 2002
    Messages:
    765
    Likes Received:
    2
    Trophy Points:
    18
    Location:
    N.W. Iowa
    thanks Chirpy, that helps explain it.

    a missing or no MX record, could this possible cause the same type of problem ?

    Mickalo
     
  4. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    I guess so, if the domain is missing an MX record the smtp server will usually check the A record, and if that isn't where email should be delivered, then it could start looping about.
     
Loading...

Share This Page