| Date | Commit message (Collapse) |
|---|
|
Replies are only direct replies, but followups could be any message
further down the thread. The latter is more useful.
|
|
We will not require Search::Xapian to be installed.
|
|
Quick-and-dirty wiring up of to Subject: paths.
This may prove more memorizable and easier-to-share than
/t/$MESSAGE_ID.html links, but less strict.
This changes our schema version to 1, since we now
use lower-case subject paths.
|
|
This will relieve callers of the need to decode the data
we store internally in Xapian
|
|
This shall allow us to search for replies/threads more easily.
|
|
This fixes a minor test failure in t/cgi.t
Tested with perl 5.18.2-2ubuntu1 on Ubuntu 14.04.3 LTS
|
|
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.
|
|
This is probably more compliant, and saves us a few bytes
on the uncompressed HTML.
|
|
Sometimes people send HTML email and I forget to fixup in my
MUA during moderation. Automatically strip out HTML portions
instead.
|
|
This hopefully allows easier setup.
|
|
Unix line endings are LF-only, so do not introduce or preserve
CRLF line endings when reading from lynx.
|
|
It's important to keep HTML source readable to folks who prefer
to read raw HTML. This should improve readability of the HTML
source by keeping line length in check without wasting bytes.
|
|
12 lines is half an 80x24 terminal, so it is probably a reasonable
amount to quote. Often 5 lines was not enough for context. This
feature is mainly to reduce scrolling necessary to view pages.
|
|
We need to ensure the HTML output is not mangled, either.
|
|
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.
|
|
Oops.
|
|
These views are not OO, so the "as_" prefix makes little sense
and "as_html" conflicts with Hval, which is OO.
|
|
This should allow us to more-easily test with Plack.
|
|
This mimics functionality found in -learn. Originally the design
allowed for only one address per-list, but when migrating/hijacking
existing mailing lists, having multiple addresses map to the same
inbox is useful.
|
|
For each feed element, we'll just use the link since there's
currently no suitable URN.
|
|
Hopefully this simplifies and corrects our usage of Perl encoding
APIs.
|
|
We already depend on IPC::Run, so just use it our tests.
|
|
We need to ensure this works
This follows commit bd8fd095067b79a0d2a40bbca2b27b923d02b3f8
("feed: fix address when multiple addresses exist")
|
|
One of my dev machines did not have XML::Feed so things were
not tested sufficiently.
|
|
Ugh, at least this has a test...
|
|
Do not repeat ourselves, just use the same description file
gitweb uses to avoid surprising users.
|
|
This is not a blog. All posts, whether replies or not,
carry equal weight.
|
|
It should be common for a single users to be subscribed to multiple
addresses/lists, so we must use the address before alias expansion.
This partially reverts commit b949afc9edf89dd494cac6255c78b124d58e11a5
|
|
We will be combining common code between -learn and -mda
|
|
The emergency destination may be Maildir. A Maildir emergency
destination is better for volatile data which is written to
and deleted-from frequently.
|
|
This allows WWW readers to slowly page through the entire history
of the mailing list.
|
|
Breaking up short quote messages at 1 line is too disconcerting,
try 5 lines as proper quotes shouldn't be too long.
|
|
CGI mounts should probably handle this internally. We're reverting
this since it adds too much potential for abuse with fake/extra
prefixes in the URL. We also need to reorder our redirect handling
as a result.
This reverts commit c394de9f2c91c2c5ed1f7832a5a7cc0206120b7f.
|
|
We may be breaking some parsers or allowing more breakage
to slip through without quotes. We waste some bytes, though.
|
|
"bugs" might confuse and limit the discussion, so "meta" it is!
|
|
This may be useful for generating List-Id headers and HTML pages.
|
|
We do not have all messages in the top-level index
(and we need to adjust the test while we're at it).
|
|
It is common to type upper-level URLs without the slash,
redirect users to the correct page for usability.
|
|
Not sure what I was thinking...
|
|
MIDs may have strange characters in them, so we need to handle
escaping/unescaping properly to avoid broken links or worse.
|
|
We may have something like /foo.cgi/m/$MID.html in there.
|
|
This makes it easier to configure for systems which
determine a script is a CGI script based on suffix.
|
|
This makes it possible to gradually migrate to new address in case
of list name changes, and is one step closer to operating in
"stealth hijack mode" :)
|
|
This is essential for integrating into my inotify-based
spam training setup.
|
|
These need better tests and verification, but it's something
for now.
|
|
Code should be consistent with the design docs
(and we will need better tests).
|
|
This prevents ambiguity when switching URLs between static
file servers and CGI.
The /$LISTNAME/index.html URL appearing in the wild is inevitable
because of our static file server support. Worst yet, there's
no easy/consistent way to get all installations detect and 301
them to the shorter /$LISTNAME/. So we make the CGI support
/$LISTNAME/index.html.
The downside of this is the potential duplicate entry in all caches.
|
|
This is essential when telling people to use something like:
curl $URL | git am
|
|
Remove the specified /all.html while we're at it, we only have
/all.atom.xml because it's convenient for feed readers.
|
|
We did not test as well as we should have.
|