| Date | Commit message (Collapse) |
|---|
|
By converting to using ourt git-fast-import-based Import
module. This should allow us to be more easily installed.
|
|
Followup-to commit 5a590bcb6813
("filter: preserve Mail-Followup-To and Mail-Reply-To")
|
|
Allow users to do wacky things here if they really wish...
It's bad practice, but at least allow other readers to
mock users of these headers :P
|
|
Hopefully this gives new hackers a better overview of
how the components relate to each other.
|
|
Improve error messages and use a better regexp for detecting
printable characters in attachments.
|
|
While we're at it, reject non-plain-text top-level messages,
too. They probably do not exist in practice, but we cannot
afford to scrub given policies implemented by overzealous
mail providers.
While we're at it, update the comment for strip_multipart.
|
|
It's often part of idiotic policies to prevent mailing lists
from working at all.
|
|
Apparently, my mental model of Perl internals is still incorrect
after all these years. I am but a simple *nix programmer:
everything is a bag of bytes to me.
This fixes a problem with UTF-8 headers from Xapian (via
"XHDR Subject [range]") triggering partial writes and writing an
extra newline to the outputs.
|
|
Filter and View should reject X?HTML the same way.
|
|
In the future, it should be possible to use this:
git ls-files | UPDATE_COPYRIGHT_HOLDER='all contributors' \
UPDATE_COPYRIGHT_USE_INTERVALS=2 \
xargs /path/to/gnulib/build-aux/update-copyright
|
|
Perl does not currently optimize for this.
ref (from p5p):
http://mid.gmane.org/D5C27970-9176-4C7A-8B99-7D78360E67A2@pobox.com
|
|
Might as well be strict about it for new lists.
Importing old archives might be more of a challenge, though.
|
|
part_type still contains the filename, unfortunately, so
PGP signatures were truly stripped. Oh well, nobody cares
to verify PGP signatures anyways.
|
|
This should hopefully reduce the delay between when a user fails
to send plain-text to when an admin such as myself notices the
HTML mail in a sea of spam.
Unfortunately, this can lead to backscatter, so avoid doing it
until its passed through spamc, at least.
|
|
Some mailers may omit the Content-Type header entirely,
so do detection and try to get the message through.
|
|
Unix line endings are LF-only, so do not introduce or preserve
CRLF line endings when reading from lynx.
|
|
HTML clients also tend to send quoted-printable crap in
their plain-text parts, preserve that so it's displayed
correctly for all QP-capable handlers.
|
|
Hopefully this simplifies and corrects our usage of Perl encoding
APIs.
|
|
I often forget the subtleties of Perl regexps and newlines,
so I suspect others do, too. Use explicit capture so it's
more familiar to users of non-Perl regexps.
|
|
We may occasionally encounter horrid HTML which lynx cannot
handle, so improve error reporting.
|
|
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.
|
|
Due to the higher latency of a pull-based email, we want to
encourage the use of reply-to-all for public-inbox.
|
|
|