Email Error Too Many Hops
Contents |
does the "too many hops" error mean when an email message I send fails? When you send an email message over a network, it is transferred to and through several computers before it gets to its destination. Each transfer between error too many hops (in reply to end of data command) computers is called a hop. The "too many hops" error message means there are too many too many hops error message transfers between you and your recipient. To prevent mail forwarding loops, most mail delivery systems limit the number of hops they will process 5.4 0 error too many hops before stopping a delivery attempt. There is little you can do to correct a "too many hops" mail return. If you think a mail forwarding loop is causing the error, you can contact the person with the loop 554 5.4 0 error too many hops through a method other than the email address causing the error. If you know a mail forwarding loop is not causing the error, ask your system administrator to increase the maximum number of hops allowed. Mail forwarding loops A mail forwarding loop can occur when you set up mail forwarding on two accounts so that the first account forwards all its mail to the second, and the second account forwards mail back to the first. If
Too Many Hops 26 (25 Max)
your mail delivery system had no limit on hops, your message could be bounced back and forth between these two accounts indefinitely. Frequently, when a message you sent returns to you with the "too many hops" error message, it means the recipient has set up a mail forwarding loop. Distribution lists If you are an owner of a distribution list and your list gets the "too many hops" error message, you may have more difficulty identifying the sender because the error message typically does not include the exact email address(es) causing the problem. Here is an example of the delivery error message: | ---------- Forwarded message ---------- | Date: 11 Jul 2003 15:28:10 -0500 | From: Mail Delivery Subsystem
Contact us Having Spam Issues? Go here for troubleshooting steps. Error 554 Too many hops: psmtp indicates mail loop This Help Center article is for Postini, a suite of Google services that's now discontinued. If you're searching for instructions related to Google Apps, see the Google Apps Help Center. For instructions related to Google Apps Vault, see
Too Many Hops Traceroute
the Vault Help Center. Issue: Notifications, Alerts, and Message Center deliveries are quarantined. Symptoms: too many hops pmtu 1500 Messages bounce with the SMTP error code "554 Too many hops -psmtp" Resolution: There is a loop in the delivery too many hops gmail logic for the domain. The most likely source of this type of issue is that the message security service always checks the DNS MX entries for a machine name before delivery and routes mail to https://kb.iu.edu/d/beha the highest priority MX record. Depending on DNS configuration, this could cause the security service to deliver to its own servers. This solution applies to all e-mails which are sent from the message security service's outgoing mail servers: Welcome Notifications Junk Email Notifications Alias Creation Confirmations All Quarantined Emails delivered from the Message Center Wireless Activation Notifications (External, Internal) Alerts Messages delivered from spool. Check the Server Configuration and https://support.google.com/postini/answer/139416?hl=en DNS MX entries to ensure that there is no MX entry for the fully qualified machine name for the mail server: Select the email config from the Choose Org pull-down list. Go to Inbound Servers > Delivery Manager. Click Edit in the dark gray bar above the graph. Look at the configured mail server (e.g. mail.mydomain.com). Do a dig on the MX entries for the mail server. (On UNIX/Linux, the command is: dig mail.mydomain.com mx) If the dig returns MX entries pointing to the message security service such as: mail.mydomain.com. 10M IN MX 100 mail.mydomain.com.sNa1.psmtp.com. mail.mydomain.com. 10M IN MX 200 mail.mydomain.com.sNa2.psmtp.com. mail.mydomain.com. 10M IN MX 300 mail.mydomain.com.sNb1.psmtp.com. mail.mydomain.com. 10M IN MX 400 mail.mydomain.com.sNb2.psmtp.com. then this is the source of the loop. RFC 821 requires that a SMTP server do an MX record lookup a domain before delivery, and since that MX record points to message security servers, the message will be delivered from the message security service directly back to the service. To correct this, do one of the following: Remove the MX entries for mail.mydomain.com. Entries should already exist for mydomain.com pointing to the message security service. Configure the Delivery Manager of the Admin Console with the actual IP for your mail server into
AfterSuburban Landscape Management: Before and AfterYoung Electric: Before and AfterCitizens Bank of Kansas: Before and AfterSmart Teeth: Before and AfterLeading Edge Aerospace: Before and AfterPrairie Homestead https://www.penpublishing.com/support/emailerrors/understandingemailerrors Senior Living: Before and AfterKS Assoc. of Community Action: Before and AfterSentry International: Before and After Contact Our Design Staff Mobile Web SitesWebsite HostingSearch Engine Optimization (SEO)Content Management Systems (CMS)Social MediaPay-Per-Click (PPC)Email Services Anti-Virus ScanningAdvanced Spam FilteringRelay ServicesWebmailZixCorp eMail Marketing Pen eMail Marketing Manager AuthorizeNet Support DNS SupportVirusesFAQ Billing FAQ'sE-mail FAQ'sDomain too many Name FAQ's Email Setup iPhone & iPadMac Mail Email Errors Dealing With Email ErrorsUnderstanding Email Errors Troubleshooting TipseMarketing Newsletter Manager Contact Sales & MarketingSubmit A Support RequestMapPaperless BillingOnline Bill PayAccounting HomeAbout The BasicsThe Pen BlogTestimonialsCommunity InvolvementCareersLegalPrivacy Statement Services Website Design & Copywriting Web Design Samples Center for Reproductive Medicine: Before and too many hops AfterSuburban Landscape Management: Before and AfterYoung Electric: Before and AfterCitizens Bank of Kansas: Before and AfterSmart Teeth: Before and AfterLeading Edge Aerospace: Before and AfterPrairie Homestead Senior Living: Before and AfterKS Assoc. of Community Action: Before and AfterSentry International: Before and After Contact Our Design Staff Mobile Web SitesWebsite HostingSearch Engine Optimization (SEO)Content Management Systems (CMS)Social MediaPay-Per-Click (PPC)Email Services Anti-Virus ScanningAdvanced Spam FilteringRelay ServicesWebmailZixCorp eMail Marketing Pen eMail Marketing Manager AuthorizeNet Support DNS SupportVirusesFAQ Billing FAQ'sE-mail FAQ'sDomain Name FAQ's Email Setup iPhone & iPadMac Mail Email Errors Dealing With Email ErrorsUnderstanding Email Errors Troubleshooting TipseMarketing Newsletter Manager Contact Sales & MarketingSubmit A Support RequestMapPaperless BillingOnline Bill PayAccounting Home > Support > Email Errors > Understanding Email Errors Understanding Email Errors and Error Messages Email error messages can be broken down into three groups. Look for the error message that most closely matches the one you received. User Error Messages Mailbox is full Message exceeds size limit Improper for