thh/yapfaq
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Activity

Update POD.

Browse source 
Signed-off-by: Thomas Hochstein <thh@thh.name>
This commit is contained in:
Thomas Hochstein 2026-02-07 19:21:03 +01:00
parent cc881f7897
commit 66435ceda0
2 changed files with 11 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

12
bin/yapfaq.pl
View file

@ -761,7 +761,14 @@ files need to be in B<datadir>.
Needs to have at least I<From:>, I<Subject:> and I<Newsgroups:> and
can contain all other headers that the posting should have. Headers
must conform to RFC 5536 and RFC 5322 and use MIME encoded words for
8bit characters. B<yapfaq> won't convert headers.
8bit characters. B<yapfaq> won't convert headers, but will warn of
unencoded 8bit characters in B<--debug> mode. Longer headers should
be folded; B<yapfaq> won't fold headers.
The headers file must not contain any of the following headers:
I<Date:>, I<User-Agent:>, I<X-Newsreader:>, I<X-Mailer:>,
I<Injection-Date:>, I<Injection-Info:>, I<NNTP-Posting-Date:>,
I<NNTP-Posting-Host:> or I<X-Trace:>.
I<Subject:> may contain a I<%LM> placeholder that will be replaced
with the I<Last-modified:> pseudo-header from the text file
@ -823,7 +830,8 @@ I<Last-modified:> and I<Posting-frequency> will be evaluated by
B<yapfaq>.
If your content contains 8bit characters, you'll need suitable MIME
headers in your headers file.
headers in your headers file. B<yapfaq> will warn of unencoded 8bit
characters with missung MIME headers in B<--debug> mode.
B<Example text file with pseudo-headers>