Bobcares

How to fix “554 Too many recipients” email error

by | Oct 4, 2018

Here at Bobcares.com, we provide Outsourced Tech Support to web hosting providers. As part of our service, we resolve email errors posted by hosting users.

A common email bounce error we see in VPS and Shared servers is:

The rejected e-mail address was 'user@domain.com'. Subject 'My mail subject', Server Error: 554, Server Response: 554 Too many recipients, Server: 'mx.sender.com', Windows Live Mail Error ID: 0x800CCC79, Protocol: SMTP, Port: 587, Secure(SSL): No

This error is seen when people attempt to send group mails with a large CC or BCC list.

 

What is the error “554 Too many recipients”?

Every mail server places a limit on the number of recipients that can be placed in To, CC and BCC combined.

This limit is placed to:

  • Keep a control on memory usage
  • Prevent mail server abuse

If there’s no limit, malicious scripts can send spam to thousands of email IDs in just one mail transaction. This will make spam infections hard to detect and mitigate.

We’ve seen hosting providers keep recipient limits as low as 10 per mail, and up to 500 per mail.

When this limit is exceeded, the mail bounces with the error 554 Too many recipients.

 

How to fix “554 Too many recipients”

Many mail servers such as Postfix and Exim keep the default recipient limit as 50. This should be enough for all normal mail communications.

So, changing this limit is not recommended, especially in shared servers.

However, there can be exceptions based on the web hosts’s market segment. Here are two ways in which we tackle it in our customer servers.

 

1. Increase the Max recipients limit

The recipient limit can be changed by modifying these settings:

  • Exim – Default limit is 0 (unlimited), but many vendors such as cPanel & DirectAdmin set it to 50. Edit the value recipients_max to change it.
  • Postfix – Default value is 1000, but many vendors set it to 50. Edit smtp_destination_recipient_limit to change it.
  • MailEnable – 300 is the default setting. Go to MailEnable MMC –> SMTP Connector [Right Click] –> Properties –> Security –> Maximum Number of Recipients, to change the limit.
  • Sendmail – In Sendmail v8.10 and above the default limit is set as 0 (unlimited), but service providers set it to lower values.  Edit MaxRecipientsPerMessage to change it.
  • Zimbra – Zimbra uses Postfix as its mail server. Edit smtpd_recipient_limit in Postfix configuration file to change the limit

 

2. Setup a mailing list app

The ideal way to resolve this is to setup a mailing list software.

A mailing list will send individual mails to everyone in the list. This will give each recipient a personalized feel, and keeps the server safe by staying under the recipient limit.

Some common open source mailing lists we setup include Dada Mail, phpList, Sympa, mlmmj, etc.

Note : When setting up mailing lists, you must upgrade the app religiously. If not, attackers can exploit vulnerabilities to send spam, and get your IP blacklisted.

 

Conclusion

Hosting providers set limits on number of recipients per mail in an effort to prevent abuse, and to reduce resource usage. When that limit is exceeded, mails will fail with the error 554 Too many recipients. Today we’ve seen two ways in which our Support Engineers resolve this issue.

 

 

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

SEE SERVER ADMIN PLANS

var google_conversion_label = "owonCMyG5nEQ0aD71QM";

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Never again lose customers to poor
server speed! Let us help you.

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie
_clck, _clsk, CLID, ANONCHK, MR, MUID, SM

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

_reb2bgeo - The visitor's geographical location

_reb2bloaded - Whether or not the script loaded for the visitor

_reb2bref - The referring URL for the visit

_reb2bsessionID - The visitor's RB2B session ID

_reb2buid - The visitor's RB2B user ID

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid
_reb2bgeo, _reb2bloaded, _reb2bref, _reb2bsessionID, _reb2buid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF