Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
6 changed files
with
90 additions
and
3 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,31 @@ | ||
# This is an example map file for the sigh milter | ||
# | ||
# The file may contain comments starting at the beginning of a line. Also | ||
# blank lines are allowed. The format of this file is a two column syntax. | ||
# The first column is a key and the second a value. Key and value are devided | ||
# by one or more whitespace characters. It is important to NOT put whitspaces | ||
# in the value column! | ||
# | ||
# The key is simply an email address without angle braces. The value has the | ||
# following form: | ||
# | ||
# <cert> ':' /path/to/cert.pem ',' <key> ':' /path/to/key.pem | ||
# | ||
# <cert> and <key> are keywords. It doesn't matter, if you define the key | ||
# first and the cert second. The certificate file may not only contain the | ||
# pure certificate. You may also concatenate furthe intermediate certificates. | ||
# For both, the certificate and the key, the files must be in PEM format. See | ||
# the OpenSSL documentation how to convert it, if you got them in a different | ||
# format. Furthermore, the key must be in unencrypted. Make sure, you adopt | ||
# the privileges to restrict access only to the milter. | ||
# | ||
# Path names must be absolute and not relative paths! | ||
# | ||
# If you make changes to this file, you must send a SIGHUP signal to the milter | ||
# in order to reload this table. | ||
|
||
# Example: | ||
c@roessner.co cert:/some/path/cert.pem,key:/some/path/key.pem | ||
|
||
# Another example | ||
test@example.com key:/another/path/key.pem,cert:/another/path/cert.pem |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,42 @@ | ||
[Milter] | ||
|
||
# The milter will run as the given user | ||
# | ||
# Default: milter | ||
;user = milter | ||
|
||
# The milter will be run with this group | ||
# | ||
# Default: milter | ||
;group = milter | ||
|
||
# A PID file for the process | ||
# | ||
# Default: | ||
pidfile = /run/sigh.pid | ||
|
||
# This is the map file which maps email addresses to S/MIME certificates. You | ||
# must specify a valid file here in order to have a working setup. | ||
# | ||
# Default: | ||
mapfile = /etc/sigh/mapfile.txt | ||
|
||
# The milter socket. Three definitions are possible. | ||
# | ||
# For IPv4: | ||
# inet:portnumber@address, example: inet:5678@127.0.0.1 | ||
# | ||
# For IPv6: | ||
# inet6:portnumber@[address], example: inet6:5678@[::1] | ||
# | ||
# For a unix socket: | ||
# unix:/pat/to/unix/listener | ||
# | ||
# Default: inet:4000@127.0.0.1 | ||
;socket = inet6:4000@[::1] | ||
|
||
# The milter creates temporary files for each mail. You should create a | ||
# directory with proper permissions and set the path here. | ||
# | ||
# Default: /tmp | ||
;tmpdir = /var/lib/sigh |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters