summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorPeter Wu <lekensteyn@gmail.com>2013-07-11 12:15:10 +0200
committerPeter Wu <lekensteyn@gmail.com>2013-07-11 12:15:10 +0200
commit1fbf8946fdab8bfdf60751bdd0c53afc50d34a58 (patch)
tree6ee445edf8509a3f496ff1e59d63e2e7ed0a2446 /README.md
parentcac24b714c2fd65a0df1ec3da490941f0bc84a6b (diff)
downloadfemtomail-1fbf8946fdab8bfdf60751bdd0c53afc50d34a58.tar.gz
Insert From and Date headers if missing
cron is not inserting a `Date` header which is confusing for the mail client. As a side-effect, `From` will be calculated from the user sending the mail if no `-f` option was specified.
Diffstat (limited to 'README.md')
-rw-r--r--README.md10
1 files changed, 6 insertions, 4 deletions
diff --git a/README.md b/README.md
index f58c2a2..89b1b04 100644
--- a/README.md
+++ b/README.md
@@ -14,7 +14,8 @@ The workflow of femtomail:
1. Change the process user and group.
2. Create a new file with a [unique filename][2] in the mail directory.
- 3. Write a `Received` header to the file.
+ 3. Write a `Received` header to the file. If `From` and `Date` headers are
+ missing, then they will also be appended to the headers.
4. Pass data from standard input to the file.
5. Exit.
@@ -61,9 +62,10 @@ directory):
Bugs
----
Not much validation is done for the address specified with the `-f` option or
-the recipient address. The mail headers and its body is passed unprocessed. If
-femtomail is invoked without specifying mail contents, an empty message will be
-created.
+the recipient address. The mail body is passed unprocessed. If femtomail is
+invoked without specifying mail contents, an empty message will be created. If
+the mail does not contain headers, `Date` and `From` headers will be appended
+anyway.
Other bugs can be reported at &lt;lekensteyn@gmail.com&gt;.