• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • 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!
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

Resolved spamassassin cli error: option "max-mail-size" is incorrect

enduser

Basic Pleskian
Username:

TITLE

spamassassin cli error: option "max-mail-size" is incorrect

PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE

Plesk Obsidian 18.0.48
Windows 2022

PROBLEM DESCRIPTION

Just tested that below command returns error in new version 18.0.48, however it should be working in older version.

C:\Users\Administrator>plesk bin spamassassin --update-server -max-mail-size 10
option "max-mail-size" is incorrect

exit status 1

STEPS TO REPRODUCE

  1. Fresh install Plesk with spamassassin
  2. plesk bin spamassassin --update-server -max-mail-size 10

ACTUAL RESULT

option "max-mail-size" is incorrect

exit status 1

EXPECTED RESULT

Server-wide spam filtering settings were updated

ANY ADDITIONAL INFORMATION

(DID NOT ANSWER QUESTION)

YOUR EXPECTATIONS FROM PLESK SERVICE TEAM

Confirm bug
 
Thank you.
The bug was confirmed and submitted as PPPM-13793
The only workaround is to adjust this value using UI.
 
Back
Top