[exim] A bunch of documentation bug reports from Debian

Kezdőlap
Üzenet törlése
Válasz az üzenetre
Szerző: Marc Haber
Dátum:  
Címzett: exim-users
CC: Marc Haber
Tárgy: [exim] A bunch of documentation bug reports from Debian
Hi,

this is a bunch of documentation bugs. The bug progress reports can be
seen on http://bugs.debian.org/cgi-bin/pkgreport.cgi?src=eximdoc4

Greetings
Marc

----- Forwarded message from Ross Boylan <ross@???> -----

> From: Ross Boylan <ross@???>
> Subject: exim4-doc-info: Some hyperlinks do not function properly
> Date: Tue, 22 Jul 2003 18:09:34 -0700
>
> In the infoized help file, some, but not all, of the table of contents
> links do not respond properly when you hit enter in emacs 21.
>
> example: -bh for the "Command line options page"
> When I position cursor on the line and hit enter I get
> "No such anchor in tag table or node in tag tabel or file: -bh <IP address>"
>
> But if I then hit space I go on to the node.


----- End forwarded message -----



----- Forwarded message from Ross Boylan <RossBoylan@???> -----

> From: Ross Boylan <RossBoylan@???>
> Subject: exim4-doc-info: missing or damaged index entries
> Date: Fri, 20 Feb 2004 11:16:53 -0800
>
> In emacs21 I tried looking for index entries for match, matches,
> begins. None of these turned up the documentation on the string
> comparison commands in the exim4-filter doc, which documents them.
>
> While looking for this, I noticed some other problems.
>
> In the main exim4 doc, if I look for (i.e., hit "i" and then type the
> entry I want) an index entry for filter, my CPU goes to 100% for about
> a minute. Finally it drops me in the index and says "No such anchor
> in tag table or node in tag table or file: enabling use of:
> allow_filter (redirect)".
>
> If I then go to
> *filter:introduction: User filters
> in the index, position on the *, and hit enter, the CPU again maxes
> out. It finishes with an error similar to that above, only this time
> on "introduction: User filters".
>
> Finally, still in the main doc, if ask for the index entry for if, I
> go to a page. Then I hit "," (see next entry) and after a bit get
> "No such anchor in tag table or node in tag table or file: for client,
> location of: tls_certificate (smtp)".


----- End forwarded message -----



----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim-daemon-heavy: [info] File and database lookups - add chapter link
> Date: Mon, 13 Sep 2004 22:06:59 +0300
>
> Info page node: File and database lookups
>
>   2. Lists of domains, hosts, and email addresses can contain lookup
>      requests as a way of avoiding excessively long linear lists. In
>      this case, the data that is returned by the lookup is often (but
>      not always) discarded; whether the lookup succeeds or fails is
>      what really counts. These kinds of list are described in chapter
>      "Domain, host, address, and local part lists".

>
> Info pages can have hyuperlinks, so please add link pointing to
> the indicated chapter "Domain, host, address, and local part lists"


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info [add hyperlink] File and database lookups
> Date: Mon, 13 Sep 2004 22:13:03 +0300
>
> Hyperlinks are missing from infor node: File and database lookups
> Add those to all location where "chapter" is referred to.
>
>   2. Lists of domains, hosts, and email addresses can contain lookup
>      requests as a way of avoiding excessively long linear lists. In
>      this case, the data that is returned by the lookup is often (but
>      not always) discarded; whether the lookup succeeds or fails is
>      what really counts. These kinds of list are described in chapter
> >>   "Domain, host, address, and local part lists".

>
>   [...]
>     The first uses a string expansion, the result of which must be a domain
> >>  list.  String expansions are described in detail in chapter "String
> >>  expansions". The expansion takes place first, and the file that is
>     searched could contain lines like this:


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: [add hyperlink] Address batching in local transports
> Date: Tue, 14 Sep 2004 16:37:02 +0300
>
> Please add hyperlink to node: "Address batching in local transports"
> and point where "section" and "chapters" is referred to:
>
>     [...]
>     when batched SMTP is in use. A full description of the batch SMTP
>     mechanism is given in section "Outgoing batched SMTP" in chapter "SMTP
>     processing". The "lmtp" transport does not have a "use_bsmtp" option,
>     because it always delivers using the SMTP protocol.


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info [add hyperlink] use_bsmtp (pipe) option
> Date: Tue, 14 Sep 2004 16:40:53 +0300
>
> At node "use_bsmtp (pipe) option" please add hyperlink where
> chapter is referred to:
>
>     If this option is set true, the "pipe" transport writes messages in
>     `batch SMTP' format, with the envelope sender and recipient(s) included
>     as SMTP commands. If you want to include a leading HELO command with
>     such messages, you can do so by setting the "message_prefix" option.
> >>  See section "Outgoing batched SMTP" in chapter "SMTP processing" for
>     details of batch SMTP.


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: [clarify] log_output (pipe) option
> Date: Tue, 14 Sep 2004 16:59:12 +0300
>
> Please add note to the following info nodes:
>
>         log_fail_output (pipe) option
>         log_output (pipe) option

>
> that only of of the options can be active, not both.


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: clarify node 'Address lists'
> Date: Sat, 25 Sep 2004 03:06:17 +0300
>
> The documentation in node 'Address lists' is very technical. Please
> provide more examples for cases. Consider also moving the "normal"
> case to the top of explanationa and only then describing the
> exceptions for patterns starting with "^" and "@".
>
> Details:
>
>    * If (after expansion) a pattern starts with `^', a regular

>
> Please give better example. The one using \N is not typical, just
> show cuple of some ^.*this.*@???' examples as well.
>
>    * If a pattern is not one of the above syntax forms, that is, if a

>
> There is no examples at all. Please provide examples that are
> technically worded in the paragraph.


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: [add hyperlink] Address lists
> Date: Sun, 26 Sep 2004 10:27:58 +0300
>
> Please add hyperlink to node "Address lists":
>
>      The lookup may be a partial one, and/or one involving a search for
> >>   a default keyed by `*' (see section "Default values in single-key
> >>   lookups" in chapter "File and database lookups"). The local part
>      patterns that are looked up can be regular expressions or begin
>      with `*', or even be further lookups. They may also be
>      independently negated. For example, with


----- End forwarded message -----




----- Forwarded message from Dan Jacobson <jidanni@???> -----

> From: Dan Jacobson <jidanni@???>
> Subject: exim4-doc-info: some links broken
> Date: Wed, 06 Oct 2004 05:06:31 +0800
>
> Do
> $ info exim4
> goto the Concept Index
> put the cursor on e.g.,
> * customizing: Received header:          receive_timeout.
> * customizing:`cannot route' message:    cannot_route_message (router).
> and hit RET. One gets an error that it can't go to ....


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: [add hyperlink] Handling an incoming message
> Date: Sun, 10 Oct 2004 15:55:46 +0300
>
> Please add hyperlinks to the info node "Handling an incoming message"
>
>     ...

>
>     status of the message includes a list of recipients who have already
>     received the message. The format of the first spool file is described
> =>  in chapter "Format of spool files".

>
>     Address rewriting that is specified in the rewrite section of the
> =>  configuration (see chapter "Address rewriting") is done once and for
>     all on incoming addresses, both in the header lines and the envelope,
>     at the time the message is accepted.  If during the course of delivery
>     additional addresses are generated (for example, via aliasing), these
>     new addresses are rewritten as soon as they are generated. At the time
>     a message is actually delivered (transported) further rewriting can
>     take place; because this is a transport option, it can be different for
>     different forms of delivery. It is also possible to specify the
>     addition or removal of certain header lines at the time the message is
> =>  delivered (see chapters "Generic options for routers" and "Generic
>     options for transports").


----- End forwarded message -----




----- Forwarded message from Jari Aalto <jari.aalto@???> -----

> From: Jari Aalto <jari.aalto@???>
> Subject: exim4-doc-info: [add hyperlink] 15 Generic options for routers
> Date: Thu, 03 Feb 2005 07:49:25 +0200
>
> Hyperlinks are missing from chapter 15:
>
>     This chapter describes the generic options that apply to all routers,
>     identifying those that are preconditions. For a general description of
> >>  how a router operates, see sections "Running an individual router" in
> >>  chapter "How Exim receives and delivers mail" and "Router
> >>  preconditions" in chapter "How Exim receives and delivers mail". The
>     second of these sections specifies the order in which the preconditions
>     are tested.  The order of expansion of the options that provide data
>     for a transport is: "errors_to", "headers_add", "headers_remove",
>     "transport".

>
> Please add those cross references for easier navigation.


----- End forwarded message -----

-- 
-----------------------------------------------------------------------------
Marc Haber         | "I don't trust Computers. They | Mailadresse im Header
Mannheim, Germany  |  lose things."    Winona Ryder | Fon: *49 621 72739834
Nordisch by Nature |  How to make an American Quilt | Fax: *49 621 72739835