Date | Commit message (Collapse) |
|
We will be reusing the config parsing code for the CGI
script, too.
|
|
We will also be using the RECIPIENT env in the future, since
that takes aliases into account.
Reducing the possible callsites to check ENV means we can more
easily update the code in the future.
|
|
|
|
This should be safer than running file(1), which has had its share
of vulnerabilities this year (early 2014) We really only care about
diffs and maybe short log files, here.
|
|
We may keep PGP signatures for messages we do not modify.
However, we have no way of verifying them on the server-side.
|
|
|
|
Some mailers do not correctly detect/set the Content-Type header; so
attempt to keep messages based on our server-detected MIME type if
application/octet-stream was specified.
|
|
|
|
This should make it easier for non-ssoma users to follow.
|
|
Valid emails should not arrive without a Message-ID.
|
|
This is to keep content accessible to search engines.
|
|
We may add more checks before we go to spamc.
|
|
|
|
We'll be using git config files after all...
|
|
Due to the higher latency of a pull-based email, we want to
encourage the use of reply-to-all for public-inbox.
|
|
SpamAssassin doesn't seem to have this heuristic, but the lack of
the intended email address in To:/Cc: headers cannot be a good
sign (especially when this is a _public_ inbox).
|
|
|
|
Unfortunately we slurp, but expect our MTA to provide its own
limit on message sizes.
|
|
Just use $0 for now, since I suck at naming things.
|
|
We generate them when publishing.
|
|
|
|
|
|
|