/$INBOX/new.atom -> Atom feed
#### Optional, relies on Search::Xapian
/$INBOX/new.atom -> Atom feed
#### Optional, relies on Search::Xapian
anchors:
#u location of $MESSAGE_ID in URL
#m<SHA-1> per-message links, where <SHA-1> is of the Message-ID
of each message (stable)
#s<NUM> relative numeric position of message in thread (unstable)
anchors:
#u location of $MESSAGE_ID in URL
#m<SHA-1> per-message links, where <SHA-1> is of the Message-ID
of each message (stable)
#s<NUM> relative numeric position of message in thread (unstable)
/$INBOX/$MESSAGE_ID/t.atom -> Atom feed for thread
/$INBOX/$MESSAGE_ID/t.mbox.gz -> gzipped mbox of thread
/$INBOX/$MESSAGE_ID/t.atom -> Atom feed for thread
/$INBOX/$MESSAGE_ID/t.mbox.gz -> gzipped mbox of thread
* No graphics, images, or icons at all. We tolerate, but do not
encourage the use of GUIs.
* No graphics, images, or icons at all. We tolerate, but do not
encourage the use of GUIs.
* We only use CSS for one reason: wrapping pre-formatted text
This is necessary because unfortunate GUI browsers tend to be
prone to layout widening from unwrapped mailers.
* We only use CSS for one reason: wrapping pre-formatted text
This is necessary because unfortunate GUI browsers tend to be
prone to layout widening from unwrapped mailers.
However, we will try to make it easy for users to supply their
own colors via user-side CSS.
CSS classes (for user-supplied CSS)
-----------------------------------
However, we will try to make it easy for users to supply their
own colors via user-side CSS.
CSS classes (for user-supplied CSS)
-----------------------------------