• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Resolved MSmtp Relay to many recipients

Heppi75

Basic Pleskian
Hi,

I have a problem with sending more than 50 mails over a second plesk server which is used as MSmtp Relay on the other plesk server.

After 50 emails the following message is generated:

Code:
Apr 17 10:45:54 merkur msmtp: host=mailserver.host tls=off auth=on [email protected] [email protected] [email protected] smtpstatus=450 smtpmsg='450 4.7.1 Error: too many recipients from ipv6address' errormsg='recipient address [email protected] not accepted by the server' exitcode=EX_UNAVAILABLE

The user which is used for the relay doesn't have a restriction. Could anyone help me where I could configure this limit on the mailserver?
 
Maybe found it on my own - I think this postfix config should do the trick - smtpd_client_recipient_rate_limit ...
 
Back
Top