This is an automated email from the ASF dual-hosted git repository. btellier pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/james-project.git
commit 419819851622834dc44f6dc04bc324f30836161f Author: Benoit Tellier <[email protected]> AuthorDate: Wed Oct 30 10:23:01 2019 +0700 JAMES-2904 Remove some uneeded files from docker configuration --- .../jpa/destination/conf/managesieve.help.txt | 112 --------------------- .../memory/destination/conf/batchsizes.properties | 10 -- 2 files changed, 122 deletions(-) diff --git a/dockerfiles/run/guice/jpa/destination/conf/managesieve.help.txt b/dockerfiles/run/guice/jpa/destination/conf/managesieve.help.txt deleted file mode 100644 index f45c78d..0000000 --- a/dockerfiles/run/guice/jpa/destination/conf/managesieve.help.txt +++ /dev/null @@ -1,112 +0,0 @@ -managesieve implements the commands defined by RFC 5804 ((http://tools.ietf.org/html/rfc5804) to manage sieve scripts via mail messages. A mail is sent to the managesieve user with the command and parameters in the subject header. Sieve scripts are exchanged as mail attachments. - -Consult your mail administrator for the name of the managesieve user configured for your installation. - -Users MUST be SMTP authenticated to execute all except the CAPABILITY and HELP commands (see note (1) below). - -Commands are executed and answered within the namespace of the sending user as denoted by the sender header of the mail. Thus, a command such as LISTSCRIPTS lists the scripts within namespace of the user identified by the sender header. - -The supported commands are summarised in "Command Summary" below. Generally the responses are self describing. For full details see RFC 5804 - Commands (http://tools.ietf.org/html/rfc5804#section-2). - -In these descriptions the following keywords apply: - -- sieve-name - The name of a sieve script enclosed in parentheses, eg: "my script". An empty name is not allowed. -- active-sieve-name - As sieve-name, except an empty name, eg: "", is allowed. -- old-sieve-name - As sieve-name -- new-sieve-name - As sieve-name -- sieve-script - A mail attachment recognised as a sieve script. This is the first attachment in a mail satisfying any of these characteristics: - - A MIME type of "application/sieve" - - A filename with the suffix ".sieve" - - A filename with the suffix ".siv" - Returned sieve-scripts always have the MIME type of "application/sieve" - -Command Summary ---------------- - -CAPABILITY - Subject: - CAPABILITY - Attachments: - none -Answers the capabilities of the underlying sieve inplementation. - -CHECKSCRIPT - Subject: - CHECKSCRIPT - Attachments: - sieve-script -Verifies the attached sieve-script without storing it on the server. - -DELETESCRIPT - Subject: - DELETESCRIPT sieve-name - Attachments: - none -Deletes the named sieve script. - -GETACTIVE - Subject: - GETACTIVE - Attachments: - none -Answers the active sieve script as an attachment. - -GETSCRIPT - Subject: - GETSCRIPT sieve-name - Attachments: - none -Answers the named sieve script as an attachment. - -HAVESPACE - Subject: - HAVESPACE sieve-name number - Attachments: - none -Answers OK if there is available space to store a script with the given name of the given size, else NO. - -HELP - Subject: - HELP - Attachments: - none -Answers this text. - -LISTSCRIPTS - Subject: - LISTSCRIPTS - Attachments: - none -Answers a list of the sieve scripts stored on the server, indicating which, if any, is the active script. - -PUTSCRIPT - Subject: - PUTSCRIPT sieve-name - Attachments: - sieve-script -Verifies the attached sieve-script and if there are no errors stores it on the server using the given name. - -RENAMESCRIPT - Subject: - RENAMESCRIPT old-sieve-name new-sieve-name - Attachments: - none -Renames the script stored on the server named old-sieve-name to new-sieve-name. - -SETACTIVE - Subject: - SETACTIVE active-sieve-name - Attachments: - none -Sets the active script on the server to the given name. Use an empty string, "", to deactivate all scripts. - -Notes ------ -1) Some mail servers optionally allow configurations that enable local clients to post without SMTP authentication, such configurations will fail as managesieve requires SMTP authentication in all circumstances. To repeat, users MUST be SMTP authenticated to execute all except the CAPABILITY and HELP commands. - - diff --git a/dockerfiles/run/guice/memory/destination/conf/batchsizes.properties b/dockerfiles/run/guice/memory/destination/conf/batchsizes.properties deleted file mode 100644 index 47da2c5..0000000 --- a/dockerfiles/run/guice/memory/destination/conf/batchsizes.properties +++ /dev/null @@ -1,10 +0,0 @@ -# Those properties let you configure the number of messages queried at the same time. -# IMAP FETCH command -fetch.metadata=200 -fetch.headers=200 -fetch.body=100 -fetch.full=50 -# IMAP COPY command -copy=100 -# IMAP MOVE command -move=100 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
