• 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 smtpd_timeout set too high

obendev

Basic Pleskian
User name: lkdvc

TITLE

smtpd_timeout set too high

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian v18.0.28_build1800200720.10 os_Ubuntu 18.04

PROBLEM DESCRIPTION

As @mr-wolf said in his post (Issue - smtpd_timeout = 3600s, why is Plesk so anxious to make that entry in main.cf???), the postfix configuration smtpd_timeout is unnecessarily high or there’s no real reason why it should be set this high.
I'd like to quote @mr-wolf here:
The Internet was already a bad place with all those spammers 10 years ago, but it only got worse.
A timeout of an hour is way too long nowadays to let them hog your resources.
And this is true.

The post configuration manual (Postfix Configuration Parameters) states that the default value is 300 seconds and that really should be by far enough.

STEPS TO REPRODUCE

Check /etc/postfix/main.cf

ACTUAL RESULT

It is set to 3600s (≙ 1 hour)

EXPECTED RESULT

The default value of 300s (≙ 5 minutes) should be high enough.

ANY ADDITIONAL INFORMATION


Amavis point of view
https://web.archive.org/web/20200729094849/https://www.ijs.si/software/amavisd/release-notes.txt
amavisd-new-2.4.0 release notes, April 3, 2006
introduced new configuration variable $smtpd_timeout (default 8*60 seconds)
which controls the amount of time we are willing to wait for slow/idle client
during incoming SMTP session before disconnecting a session. Previously the
$child_timeout was covering complete elapsed time, both our processing and
waiting for client, now the $child_timeout only still limits our processing,
and $smtpd_timeout only limits waiting time. With Postfix after-queue setup
the $smtpd_timeout should be higher than Postfix setting max_idle (default
100s). Some other setups (like a pre-queue setup) may demand substantially
higher $smtpd_timeout values; inflexibility pointed out by Martin Schmitt;

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Last edited:
Thank you.
After investigating original reasons for such customization in Plesk developers filed PPPM-12236 to address this issue.
 
Fixed in Plesk 18.0.32:

Plesk no longer specifies excessively large smtpd_proxy_timeout and smtpd_timeout values in Postfix configuration files during Plesk installation or whenever the plesk repair mail command is run. (PPPM-12236)

 
Back
Top