ai-pl9.1, Fidogate 4.3a3, 24 Jun 1998, Andy Igoshin <ai@vsu.ru>


    The present archive is an adaptation of patch fidogate-4.2.9-ai-pl9.0
to fidogate-4.3a3. The current version is fidogate-4.3.a3-ai-pl9.1.

    The differences between pl9.0 and pl9.1 are:
    - UNICODE support was removed, because fidogate-4.3a3 contains another
mechanisms for re-encoding of messages.
    - Re-encoding tables for Russian language were added: { koi8-r, iso-8859-5,
cp1251 } <-> cp866. The corresponding aliases koi8-u, x-cp866, x-cp1251 are
also supported.
    - Sample configuration files (used at fido.vsu.ru site) were added.


				    Andy Igoshin  <ai@vsu.ru>

ai-pl9.0, Fidogate 4.2.9, 12 Jun 1998, Andy Igoshin <ai@vsu.ru>

Source is available at:
ftp://ftp.vsu.ru/pub/linux/system/fido/fidogate-4.2.9-ai-pl9.0.tar.gz


 0. All changes are delimitered with corresponding #define's, which
    allows one to switch separate features. This also makes the
    changes localized and more clear.

 1. Added `-a' key to hosts file (see example). This key is necessary
    in situations when a message from internet address, for which there
    is a mapping in a `hosts' file to some fidonet address, is being sent
    to fidonet area, the ^AREPLYTO and Origin fields should contain "real"
    fidonet address, but not a gate's address. ^AMSGID is also generated
    if Message-Id is absent in the original message, using "real" fidonet
    address.
    To switch this on, `#define AI_1' in config.h.

 2. Fixed alias problem in ftn2rfc.c module.
    Fixed alias problem in aliases.c module.
    Added extended aliases. New format of aliases file is backward
    compatible with original format, i.e. the behavior for old configs
    is exactly as for unmodified algorithm (as far as I was able to test :).
    See README.ai.alias for more information.
    To switch this on, `#define AI_2' in config.h.

 3. Added `DeleteSeenBy' and `DeletePath' variables to config.main file
    (see example).
    To switch this on, `#define AI_3' in config.h.

 4. Added UNICODE patch from Alexander E. Pevzner <pzz@pzz.msk.ru>.
    Fixed UNICODE quoted-printable bug in message.c (Andy Igoshin <ai@vsu.ru>).
    Fixed quoted-printable bug (added processing of Soft Line Breaks
    (Rule #5 of RFC1521) - `=' at the end of QP-line) in rfc2ftn.c, mime.c,
    unicode.c (Andy Igoshin <ai@vsu.ru>). To switch this on, `#define AI_9' in
    config.h.
    Fixed a bug of processing 8bit characters in `CHRS:' kludge in unicode.c
    (these 8bit chars are illegal there, but without a fix ftn2rfc would crash
    on some PKTs which have this broken CHRS). (Andy Igoshin <ai@vsu.ru>).

 5. Added check on 8bit in subject, origin and tearline.
    To switch this on, `#define AI_5' in config.h.

 6. Added `AddressIsLocalForXPost' variable in config.common file
    (see example). In this variable one can specify wildcards to determine
    which users are allowed to crosspost to areas marked with `-l' flag
    in `areas' file.
    To switch this on, `#define AI_6' in config.h.

 7. Added `UseXMailerForTearline', `UseUseragentForTearline' and
    `UseXNewsreaderForTearline' variables to config.gate file (see example).
    This allows generation of `Tearline' field in .pkt files from field
    `User-Agent:' or `X-Newsreader:' contained in RFC message (like
    `X-FTN-Tearline:' header). Priority is: `X-FTN-Tearline:', `User-Agent:',
    `X-Newsreader:' for news messages and `X-FTN-Tearline:', `X-Mailer:' for
    mail messages. If these variables are not present in config.gate, we do
    not process the corresponding fields in RFC message.
    To switch this on, `#define AI_7' in config.h.

 8. Added ACL support. This feature allows one to describe the correspondence
    between sender's email address and newsgroups to which this sender is
    allowed to write. One can use wildcards as email and newsgroups. The
    newsgroups list is in INN like style. See the comments in `acl' file in
    the `examples' directory for further information.
    To switch this on, `#define AI_8' in config.h.


				    Andy Igoshin  <ai@vsu.ru>

ai-pl9.0, Fidogate 4.2.9, 12 Jun 1998, Andy Igoshin <ai@vsu.ru>

Source is available at:
ftp://ftp.vsu.ru/pub/linux/system/fido/fidogate-4.2.9-ai-pl9.0.tar.gz


    Extended aliases are supported. This means that it is not necessary from
now to map a node or point address _all_ internet domain. A transparent mapping
of Fidonet <-> Internet addresses is performed.

    The presence of full domain name `user@do.main' in the LHS in `aliases' file
means that this rule will be processed by the `extended' aliasing algorithm.
First, an `original' aliasing algorithm is executed; if it fails, then `extended'
aliasing algorithm is used. One exception from this rule is in the case when
one particular domain is present in both `aliases' file (as extended alias) and
in `hosts' file. In this case, rules in `aliases' have higher priority, if, of
course, the search using extended aliases succeeds.

    For example, if we have the following rule in the `aliases' file,

aliases:
vk@crk.vgts.ru	2:5025/8.32		"Vladislav Kuleshenko"

and there will be nothing about these addresses in the `hosts' file, then it
will mean that in messages from `vk@crk.vgts.ru' to Fidonet, this address
will be substituted with `Vladislav Kuleshenko @ 2:5025/8.32'. And vice versa,
for messages from Fidonet to Internet.
It is allowed to specify several rules:

aliases:
vk@crk.vgts.ru	2:5025/8.32		"Vladislav Kuleshenko"
vk@crk.vgts.ru	2:5025/8.32		"Sysop"

I.e., we mapped this point address _only_ to a _user_ of `crk.vgts.ru' domain,
but not to the whole domain, as it has been if we have used `hosts' file. If
there are no more rules for these addresses, then all the rest addresses of
`crk.vgts.ru' domain will be mapped to the address of the default gate.

    One can add arbitrary number of such rules to the `aliases' file.

    The following example is very interesting, because it demonstrates the
reasons of extensions to Fidogate's aliases. :)

aliases:
vk@crk.vgts.ru	2:5025/8.32		"Vladislav Kuleshenko"
vk@crk.vgts.ru	2:5025/8.32		"Sysop"
reb@ctrl.vsu.ru	2:5025/8.32		"Eugene Ryzhkov"
pk		2:5025/74		"Paul Koltakov"

hosts:
2:5025/74	crk.vgts.ru.		-a
2:5025/127	ctrl.vsu.ru.		-a

In this case, if a message will be from any user under `@crk.vgts.ru' domain,
except `vk', then it's address after gating to Fidonet will be set to `2:5025/74';
but `vk@crk.vgts.ru' will be transformed to `2:5025/8.32'. Naturally, nothing stops
one to add more lines to the `aliases' file, which describe rules for other users
of domen/node crk.vgts.ru - 2:5025/74. For domen/node ctrl.vsu.ru - 2:5025/127
in the above example, all is analogous. Let's repeat once again that Fidonet ->
Internet transformation also uses these these algorithms. Note: the description
of the `-a' option is in the first n. in the README.ai.

    I'd like to stress that nothing stops one to use an `original' and `extended'
models of aliasing together, as it is shown, in particular, in the above example.


				    Andy Igoshin  <ai@vsu.ru>