formail | Début | Suivant | Sommaire | Préc.page.lue | Accueil |
NAME | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
SYNOPSIS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
DESCRIPTION | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
If formail is supposed to determine the sender of the mail, but is unable to find any, it will substitute `foo@bar'.
If formail is started without any command line options, it will force any mail coming from stdin into mailbox format and will escape all bogus `From ' lines with a `>'.
OPTIONS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
NOTES | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
By default, when generating an auto-reply header procmail selects the envelope sender from the input message. This is correct for vacation messages and other automatic replies regarding the routing or delivery of the original message. If the sender is expecting a reply or the reply is being generated in response to the contents of the original message then the -t option should be used.
RFC822, the original standard governing the format of Internet mail messages, did not specify whether Resent header fields (those that begin with `Resent-', such as `Resent-From:') should be considered when generating a reply. Since then, the recommended usage of the Resent headers has evolved to consider them as purely informational and not for use when generating a reply. This has been codified in RFC2822, the new Internet Message Format standard, which states in part:
While formail now ignores Resent headers when generating header replies, versions of formail prior to 3.14 gave such headers a high precedence. If the old behavior is needed for established applications it can be specified by calling formail with the option `-a Resent-' in addition to the -r and -t options. This usage is deprecated and should not be used in new applications.
ENVIRONMENT | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
EXAMPLES | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
To remove all Received: fields from the header:
To remove all fields except From: and Subject: from the header:
To supersede the Reply-To: field in a header you could use:
To convert a non-standard mailbox file into a standard mailbox file you can use:
Or, if you have a very tolerant mailer:
To extract the header from a message:
To extract the body from a message:
SEE ALSO | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
DIAGNOSTICS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
WARNINGS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
In the tradition of UN*X utilities, formail will do exactly what you ask it to, even if it results in a non-RFC822 compliant message. In particular, formail will let you generate header fields whose name ends in a space instead of a colon. While this is correct for the leading `From ' line, that line is not a header field so much as the message separator for the mbox mailbox format. Multiple occurrences of such a line or any other colonless header field will be considered by many mail programs, including formail itself, as the beginning of a new message. Others will consider the message to be corrupt. Because of this, you should not use the -i option with the `From ' line as the resulting renamed line, `Old-From ', will probably not do what you want it to. If you want to save the original `From ' line, rename it with the -R option to a legal header field such as `X-From_:'.
BUGS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
If formail is instructed to delete or rename the leading `From ' line, it will not automatically regenerate it as usual. To force formail to regenerate it in this case, include -a 'From '.
If formail is not called as the first program in a pipe and it is told to split up the input in several messages, then formail will not terminate until the program it receives the input from closes its output or terminates itself.
If formail is instructed to generate an autoreply mail, it will never put more than one address in the `To:' field.
MISCELLANEOUS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
When formail has to determine the sender's address, every RFC822 conforming mail address is allowed. Formail will always strip down the address to its minimal form (deleting excessive comments and whitespace).
The regular expression that is used to find `real' postmarks is:
If a Content-Length: field is found in a header, formail will copy the number of specified bytes in the body verbatim before resuming the regular scanning for message boundaries (except when splitting digests or Berkeley mailbox format is assumed).
Any header lines immediately following the leading `From ' line that start with `>From ' are considered to be a continuation of the `From ' line. If instructed to rename the `From ' line, formail will change each leading `>' into a space, thereby transforming those lines into normal RFC822 continuations.
NOTES | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
SOURCE | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
MAILINGLIST | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
AUTHORS | Début | Précédent | Suivant | Sommaire | Préc.page.lue | Accueil |
Sommaire | Début | Suivant | Sommaire | Préc.page.lue | Accueil |
Table des mots clés | Début | Suivant | Sommaire | Préc.page.lue | Accueil |
-b | OPTIONS |
-c | OPTIONS |
-d | OPTIONS |
-e | OPTIONS |
-f | OPTIONS |
-k | OPTIONS |
-l folder | OPTIONS |
-q | OPTIONS |
-r | OPTIONS |
-s | OPTIONS |
-t | OPTIONS |
-v | OPTIONS |
-Y | OPTIONS |
-z | OPTIONS |
FILENO | ENVIRONMENT |