[exim] Fidonet...

Pàgina inicial
Delete this message
Reply to this message
Autor: Marco Gaiarin
Data:  
A: exim-users
Assumpte: [exim] Fidonet...

[if you don't know fidonet, consider it some sort of uucp, a bit
stranger... ;]

...yes, it is somewhat still alive. ;)

I've just converted my Fidonet BBS system from exim3 to exim4, doing a
rather brute force conversion.
I've still some culprit.

I'm 2:333/1016, and i've also some downlink (2:333/1018) and clearly
some point (2:333/1016.2).
In internet-speaking language i'm f1016.n333.z2.fidonet.org, and i've
to route to some other domain like this, so i've setup:

# FTN routing to downlink, we are authoritative about this, so we cannot
# fail routing for these domains.
#
ftn_hosts_down:
debug_print = "R: ftn_hosts_down for $local_part@$domain"
driver = manualroute
domains = partial-lsearch;/etc/exim4/ftn_hosts_down
require_files = /etc/exim4/ftn_hosts_down : +/usr/lib/ifmail/ifmail
route_data = ${lookup{$domain}partial-lsearch{/etc/exim4/ftn_hosts_down}}
no_more
transport = ifmail_h

with /etc/exim4/ftn_hosts_down as:

 *.f1018.n333.z2.fidonet.org:    f1018.n333.z2.fidonet.org



Also, i've some ``defaultroute'' for fidonet, again like:

# FTN routing to uplink, less strict routing but we use no_more to prevent
# ftn-style mail to escape from here...
#
ftn_hosts_up:
debug_print = "R: ftn_hosts_up for $local_part@$domain"
driver = manualroute
domains = !+local_domains : partial-lsearch;/etc/exim4/ftn_hosts_up
no_more
require_files = /etc/exim4/ftn_hosts_up : +/usr/lib/ifmail/ifmail
route_data = ${lookup{$domain}partial-lsearch{/etc/exim4/ftn_hosts_up}}
transport = ifmail_h

with /etc/exim4/ftn_hosts_up as:

 # Routing per le 6 zone fido, vanno al GianCheese...
 #
 *.z1.fidonet.org                f805.n333.z2.fidonet.org
 *.z2.fidonet.org                f805.n333.z2.fidonet.org
 *.z3.fidonet.org                f805.n333.z2.fidonet.org
 *.z4.fidonet.org                f805.n333.z2.fidonet.org
 *.z5.fidonet.org                f805.n333.z2.fidonet.org
 *.z6.fidonet.org                f805.n333.z2.fidonet.org


But how i can handle my points, eg, domains like
p2.f1016.n333.z2.fidonet.org?
I've to setup a router that:
a) match all addess like p\d+.f1016.n333.z2.fidonet.org
b) if an address is defined, route it
c) if not, bounce

I've tried with:

# FTN routing for points, rather same as above but we do exact search and
# we use as domains an regexp to match...
#
ftn_points:
debug_print = "R: ftn_points for $local_part@$domain"
driver = manualroute
#domains = partial5()-lsearch;/etc/exim4/local_domains
domains = PointAKAs
require_files = /etc/exim4/ftn_points : +/usr/lib/ifmail/ifmail
route_data = ${lookup{$domain}lsearch{/etc/exim4/ftn_points}}
no_more
transport = ifmail_h

and with /etc/exim4/ftn_points:

 # FidoNet
 #
 p2.f1016.n333.z2.fidonet.org:           p2.f1016.n333.z2.fidonet.org
 p13.f1016.n333.z2.fidonet.org:          p13.f1016.n333.z2.fidonet.org
 p14.f1016.n333.z2.fidonet.org:          p14.f1016.n333.z2.fidonet.org
 p17.f1016.n333.z2.fidonet.org:          p17.f1016.n333.z2.fidonet.org
 p8088.f1016.n333.z2.fidonet.org:        p8088.f1016.n333.z2.fidonet.org


but i've had to put a domains statements with an explicit domain match
to prevent the router to be skipped and defoult routing to my uplink
applied. For me:

PointAKAs = \N^p\d+\.f1016\.n333\.z2\.fidonet\.org\N

Clearly in this way works, but there's some more better way to do so?
eg, without explicitly define domains?


Thanks.

-- 
dott. Marco Gaiarin                    GNUPG Key ID: 240A3D66
  Associazione ``La Nostra Famiglia''                http://www.sv.lnf.it/
  Polo FVG  -  Via della Bont?, 7 - 33078  -  San Vito al Tagliamento (PN)
  marco.gaiarin(at)sv.lnf.it      tel +39-0434-842711  fax +39-0434-842797