The translation is temporarily closed for contributions due to maintenance, please come back later.
The translation was automatically locked due to following alerts: Could not merge the repository.
Zen

Source string Source string

656/10000 · 656

This translation is currently locked.

English Actions
For example, lines in a user's `~/.procmailrc` file may look like this:
MAILDIR=$HOME/Msgs
INCLUDERC=$MAILDIR/lists.rc
INCLUDERC=$MAILDIR/spam.rc
To turn off Procmail filtering of email lists but leaving spam control in place, comment out the first [command]#INCLUDERC# line with a hash sign (`#`). Note that it uses paths relative to the current directory.
[command]#LOCKSLEEP# — Sets the amount of time, in seconds, between attempts by Procmail to use a particular lockfile. The default is 8 seconds.
[command]#LOCKTIMEOUT# — Sets the amount of time, in seconds, that must pass after a lockfile was last modified before Procmail assumes that the lockfile is old and can be deleted. The default is 1024 seconds.
[command]#LOGFILE# — The file to which any Procmail information or error messages are written.
[command]#MAILDIR# — Sets the current working directory for Procmail. If set, all other Procmail paths are relative to this directory.
[command]#ORGMAIL# — Specifies the original mailbox, or another place to put the messages if they cannot be placed in the default or recipe-required location.
By default, a value of [command]#/var/spool/mail/$LOGNAME# is used.
[command]#SUSPEND# — Sets the amount of time, in seconds, that Procmail pauses if a necessary resource, such as swap space, is not available.
[command]#SWITCHRC# — Allows a user to specify an external file containing additional Procmail recipes, much like the [command]#INCLUDERC# option, except that recipe checking is actually stopped on the referring configuration file and only the recipes on the [command]#SWITCHRC#-specified file are used.
[command]#VERBOSE# — Causes Procmail to log more information. This option is useful for debugging.
Other important environmental variables are pulled from the shell, such as [command]#LOGNAME#, the login name; [command]#HOME#, the location of the home directory; and [command]#SHELL#, the default shell.
A comprehensive explanation of all environments variables, and their default values, is available in the `procmailrc` man page.
Procmail Recipes
indexterm:[Procmail,recipes] New users often find the construction of recipes the most difficult part of learning to use Procmail. This difficulty is often attributed to recipes matching messages by using _regular expressions_ which are used to specify qualifications for string matching. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, see xref:Mail_Servers.adoc#s3-email-procmail-recipes-examples[Recipe Examples].
Procmail recipes take the following form:
:0 pass:quotes[_flags_] : pass:quotes[_lockfile-name_]
* pass:quotes[_condition_1_special-condition-character_] pass:quotes[_condition_1_regular_expression_]
* pass:quotes[_condition_2_special-condition-character_] pass:quotes[_condition-2_regular_expression_]
* pass:quotes[_condition_N_special-condition-character_] pass:quotes[_condition-N_regular_expression_]
pass:quotes[_special-action-character_]
pass:quotes[_action-to-perform_]
The first two characters in a Procmail recipe are a colon and a zero. Various flags can be placed after the zero to control how Procmail processes the recipe. A colon after the [command]#pass:attributes[{blank}]_flags_pass:attributes[{blank}]# section specifies that a lockfile is created for this message. If a lockfile is created, the name can be specified by replacing [command]#pass:attributes[{blank}]_lockfile-name_pass:attributes[{blank}]#.
A recipe can contain several conditions to match against the message. If it has no conditions, every message matches the recipe. Regular expressions are placed in some conditions to facilitate message matching. If multiple conditions are used, they must all match for the action to be performed. Conditions are checked based on the flags set in the recipe's first line. Optional special characters placed after the asterisk character ([command]#*#) can further control the condition.
The [command]#pass:attributes[{blank}]_action-to-perform_pass:attributes[{blank}]# argument specifies the action taken when the message matches one of the conditions. There can only be one action per recipe. In many cases, the name of a mailbox is used here to direct matching messages into that file, effectively sorting the email. Special action characters may also be used before the action is specified. See xref:Mail_Servers.adoc#s3-email-procmail-recipes-special[Special Conditions and Actions] for more information.
Delivering vs. Non-Delivering Recipes
indexterm:[Procmail,recipes,delivering]indexterm:[Procmail,recipes,non-delivering] The action used if the recipe matches a particular message determines whether it is considered a _delivering_ or _non-delivering_ recipe. A delivering recipe contains an action that writes the message to a file, sends the message to another program, or forwards the message to another email address. A non-delivering recipe covers any other actions, such as a _nesting block_. A nesting block is a set of actions, contained in braces [command]#{# [command]#}#, that are performed on messages which match the recipe's conditions. Nesting blocks can be nested inside one another, providing greater control for identifying and performing actions on messages.
When messages match a delivering recipe, Procmail performs the specified action and stops comparing the message against any other recipes. Messages that match non-delivering recipes continue to be compared against other recipes.
Flags
indexterm:[Procmail,recipes,flags] Flags are essential to determine how or if a recipe's conditions are compared to a message. The [application]*egrep* utility is used internally for matching of the conditions. The following flags are commonly used:
[command]#A# — Specifies that this recipe is only used if the previous recipe without an [command]#A# or [command]#a# flag also matched this message.
[command]#a# — Specifies that this recipe is only used if the previous recipe with an [command]#A# or [command]#a# flag also matched this message *and* was successfully completed.
[command]#B# — Parses the body of the message and looks for matching conditions.
[command]#b# — Uses the body in any resulting action, such as writing the message to a file or forwarding it. This is the default behavior.
[command]#c# — Generates a carbon copy of the email. This is useful with delivering recipes, since the required action can be performed on the message and a copy of the message can continue being processed in the `rc` files.

Loading…

User avatar None

String added in the repository
indexterm:[Procmail,recipes] New users often find the construction of recipes the most difficult part of learning to use Procmail. This difficulty is often attributed to recipes matching messages by using _regular expressions_ which are used to specify qualifications for string matching. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, see xref:Mail_Servers.adoc#s3-email-procmail-recipes-examples[Recipe Examples].
indexterm:[Procmail,recipes] New users often find the construction of recipes the most difficult part of learning to use Procmail. This difficulty is often attributed to recipes matching messages by using _regular expressions_ which are used to specify qualifications for string matching. However, regular expressions are not very difficult to construct and even less difficult to understand when read. Additionally, the consistency of the way Procmail recipes are written, regardless of regular expressions, makes it easy to learn by example. To see example Procmail recipes, see xref:Mail_Servers.adoc#s3-email-procmail-recipes-examples[Recipe Examples].
7 months ago
Browse all string changes

Things to check

Long untranslated

The string has not been translated for a long time

Reset

Glossary

English English
No related strings found in the glossary.

String information

Source string description
type: Plain text
Flags
read-only
Source string location
./pages/servers/Mail_Servers.adoc:785
String age
7 months ago
Last updated
7 months ago
Source string age
7 months ago
Translation file
pot/f40/pages/servers/Mail_Servers.pot, string 291