1Date: Tue, 30 Aug 1994 22:59:15 +0000 2From: Martin Seine <martin@erde.gun.de> 3Subject: FGATE-Point-FAQ 4 5Tja, 6 7da habe ich mir doch letzte Nacht glatt mein Mailsystem zerschossen :-( 8Alle alten Mails und Archive weg. Zum Glueck ist die Adressdatei noch da. 9 10Also: Startet niemals 'pine', wenn su noch in der Session aktiv ist. 11 12Zurueck zum Thema: 13Die smail-Konfiguration gefaellt mir gar nicht. Speziell wenn man davon 14ausgeht, dass das ja fuer neue User sein soll (ach ja: HOWTO waere wohl 15besser als FAQ, oder?). Es sollte schon herauskommen, wenn man nur den 16Rechnernamen oder rechnername.uucp verwendet, dieser in der Worldmap 17registriert sein sollte. 18 19Die hostname-Zeile enthaelt sehr viele Redundanzen. 20Und sie sollte auch nur sinnvolle Moeglichkeiten beinhalten und den 21reinen Rechnernamen ohne Domain nur in Ausnahmefaellen oder bei 22Worldmap-Eintrag. 23 24Meine usr/lib/smail/config: 25hostnames=erde.GUN.de:p100.f413.n2448.z2.fidonet.org 26-visible_name 27-visible_domain 28-smart_path 29 30Ist jetzt schon etwas laenger her, dass ich das konfiguriert habe, daher 31erscheint es mir etwas spanisch, aber es laeuft :-) 32 33Ok, nun zu den Sachen, wo ich immer noch dran feile: 34 35Zum routers-File: 36Der smarthost-Eintrag sollte am Ende kommen, da die Router sukzessive von 37oben nach unten ausgewertet werden. 38 39Meine Eintraege sehen jetzt etwas wild aus, und entsprechen auch nicht der 40Point-Vorstellung, deswegen poste ich sie mal nicht vollstaendig. 41Aber es sollte besser schon ein uuname-Router angegeben sein, denn der ist 42ja flexibel und solange keine UUCP-Hosts definiert sind auch wirkungslos. 43Aber es erspart Fragen, falls UUCP installiert wird. 44 45Dann waere der Einsatz eines queryprogram-drivers sehr ueberlegenswert, weil 46er speziell in Kombination mit mehreren Gate-Netzen gut einzusetzen ist. 47 48Nehmen wir mal als router-Eintrag 49fido: driver=queryprogram; 50 cmd="/usr/local/lib/fidonet/checknode ${lc:host}", 51 read_path, read_transport 52 53dann koennte ein entsprechendes Script (das ja auch im idealen Pfad steht 54:-) ) so aussehen: 55#!/bin/sh 56 57case $1 in 58 *fidonet.org) echo "p0.f1.n2.z3.fidonet.org fido"; exit 0;; 59 *gernet) echo "p4.f5.n6.z7.fidonet.org gernet"; exit 0;; 60esac 61 62exit 1 63 64Hier wird der Name des naechsten Hops (read_path) und das zu verwendende 65Transport-Verfahren (read_transport) durch Leerzeichen getrennt 66zurueckgegeben. 67 68Zu den tranports aber spaeter. 69 70Als naechster router-Eintrag der obligatorische uuname: 71uuname: transport=uux, driver=uuname; 72 cmd="/usr/bin/uuname", 73 domain=erde.GUN.de, required=erde.GUN.de 74 75Ok, domain und required muessen angepasst werden. Durch required wird 76sichergestellt, dass z.B. 'ne Mail an 'test' nicht durch die UUCP-Node 77'test' gematcht wird. An die UUCP-Node 'test' geht's nur mit 78'test.erde.GUN.de'. 79 80Einen pathalias habe ich auch drin, aber der ist mit Vorsicht zu geniessen 81und da bin ich noch in der experimentellen Phase. 82 83Als letzter kommt der smarthost und der uebernimmt alle Mails, die bislang 84noch nicht gematcht wurden. Bei mir ist's ein smtp-Pfad, aber fuer einen 85Point sollte es in etwa so aussehen: 86smart_host: transport=fido, driver=smarthost; 87 path=p0.f1.n2.z3.fidonet.org 88 89 90Dadurch braucht's diese Path-Files nicht mehr. Alles, was nicht durch die 91vorhergehenden Router abgewickelt wird, geht per fido zu 3:2/1.0@fidonet.org 92 93 94Nun gut. Ab zu den Transports. Ich habe hier ein Standard-Transports, dass 95eigentlich die meisten Wuensche abdeckt und nur minimal ediert werden muss. 96Aber fuer einen Point duerfte das zu maechtig sein, daher nur das 97wichtigste (hmm, naeheres hinsehen sagt mir, dass vieles darin sehr 98lehrreich ist und daher vollstaendig. Der Fido-Teil ist am Ende :-) )... 99 100# @(#)samples/generic/transports 2.00 8/29/94 22:55 101 102# This file defines the configuration of the transport subsystem as 103# compiled into the smail binary. By modifying the source files 104# conf/EDITME, src/config.h or src/default.c the actual internal 105# configuration can be changed. Thus, this should be matched up 106# against thes files before assuming this is completely correct. 107# 108# If a run-time transports file is created, then its entries will 109# complement or replace the compiled-in transport entries. Thus, 110# contrary to use of the routers and directors files, you do not need 111# to copy and localize this file in order to add new transports. 112# 113# 114# IMPORTANT FOR INTERNET USERS 115# 116# The smtp, uucp_zone_smtp, inet_zone_smtp, and local_smtp transports 117# should be configured to use the DNS for finding MX and A records, 118# if the host was not resolved by the bind version of the inet_hosts 119# router. To configure this, uncomment the use_bind attributes on 120# the various tcpsmtp-based transport definitions. 121# 122# 123# IMPORTANT FOR SCO UNIX SYSTEMS 124# 125# Recent SCO UNIX systems use the MMDF file format. If you wish to 126# have smail generate this format, then comment out the unix_from_hack 127# and the first suffix lines, in the "local" and "file" transports, 128# and uncomment all lines that are commented with "MMDF mailbox format". 129# 130# 131# IMPORTANT FOR SYSTEM V RELEASE 4 USERS 132# 133# The SVR4 mailx expects to find Content-Length header fields on 134# messages. If such a header is not found (or if a remote site 135# supplies an incorrect Content-Length header), then mailx may split 136# your mailbox file into messages at inappropriate boundaries. To 137# add a Content-Length field to messages appended to your mailbox 138# files, and sent to shell-command or file addresses, uncomment all 139# attributes that are indicated with "SVR4 mailbox format". This 140# will also ensure that you have a "Content-Type" field, defaulting 141# the content type to "text". 142# 143# You will likely also wish to uncomment unix_from_hack from the 144# local, pipe, and file transports, since prepending > to lines 145# starting with From is not necessary with this the SVR4 mailbox 146# format. You can also comment out the suffix="\n" lines in the 147# local, and file transports, since a blank line is not required 148# between messages for the SVR4 mailbox format. 149# 150# 151# IMPORTANT FOR USE WITH HoneyDanBer UUCP 152# 153# Systems with HoneyDanBer UUCP (for example, System V Release 4) 154# can invoke uux with -a$sender -g$grade to cause UUCP errors to 155# be mailed to the message sender, and to alter UUCP queue priorities 156# based on Precedence header fields. For SVR4, you should add the 157# following to your /etc/uucp/Grades file: 158# 159# 9 9 Any User Any 160# A A Any User Any 161# C C Any User Any 162# a a Any User Any 163# n n Any User Any 164# 165# This is because the SVR4 HDB UUCP uses long message grade names 166# on the uux command line, which are not supported by Smail. 167# 168# 169# HANDLING TRANSIENT UUCP FAILURES 170# 171# Many systems seem to get failures from uux from time to time. I 172# guess this is load related. Smail normally returns bounce messages 173# in such situations. However, generating a bounce message can be 174# annoying if the failures are truly transient. 175# 176# The only way to handle this, if you encounter this often, is to 177# make sure that your UUCP configuration doesn't have any conflicts 178# with your smail configuration (which implies that uux should never 179# fail for configuration-related errors). Then, uncomment the 180# defer_child_errors attribute in the various uux-based transports 181# defined in this file. This will cause smail to retry (at a later 182# time) any failures encountered by executing uux. 183 184 185# local - deliver mail to local users 186# 187# By default, smail will append directly to user mailbox files. 188# 189# IMPORTANT FOR SYSTEM V AND SCO USERS 190# 191# comment out the mode=0600 line below, and uncomment the mode=0660 192# line, to get the correct mailbox file permissions for your system. 193local: driver=appendfile, # append message to a file 194 return_path, # include a Return-Path: field 195 from, # supply a From_ envelope line 196 unix_from_hack, # insert > before From in body 197 # comment out the above line for 198 # MMDF mailbox format and for 199 # use with the Content-Length 200 # header fields. 201# SVR4 mailbox format: uncomment the below 3 lines 202# remove_header="Content-Length", 203# append_header="${if !header:Content-Type :Content-Type: text}", 204# append_header="Content-Length: $body_size", 205 local; # use local forms for delivery 206 207 file=/var/spool/mail/${lc:user}, # location of mailbox files 208# file=/usr/mail/${lc:user}, # use this location for System V 209 group=mail, # group to own file for System V 210 mode=0600, # For BSD: only the user can 211 # read and write file 212# mode=0660, # under System V, group mail can access 213 # use this for SCO UNIX, as well 214 suffix="\n", # append an extra newline 215 # comment out the above line for 216 # MMDF mailbox format and for 217 # use with the Content-Length 218 # header fields. 219# notify_comsat, # notify comsat daemon of delivery 220# suffix="\1\1\1\1\n", # MMDF mailbox format 221# prefix="\1\1\1\1\n", # MMDF mailbox format 222 223# local - an alternate local transport that calls on /bin/lmail 224# 225# Some systems have special local conventions for mail delivery that 226# smail does not understand. Such conventions may include adding 227# special headers, or may include particular locking conventions. For 228# such systems, smail can use a system-provided program for delivery 229# to user mailbox files. On most systems, the /bin/mail program will 230# perform mail delivery according to local conventions. However, 231# smail will often require that /bin/mail be replaced with a program 232# that calls out to smail to perform delivery. By convention, the 233# original /bin/mail program should be saved to /bin/lmail. 234# 235# It may be necessary to modify this entry to operate within your 236# local conventions. 237# 238# NOTE: If you wish to use this alternate local entry, you must 239# comment out the regular local transport entry, and uncomment the 240# entry below. 241#local: driver=pipe, # call out to a program 242# return_path, # include a Return-Path: field 243# local, # use local forms for delivery 244# from, # supply a From_ envelope line 245# -max_addrs; # give multiple addresses to command 246# 247# cmd="/bin/lmail $($user$)" 248 249# pipe - deliver mail to shell commands 250# 251# This is used implicitly when smail encounters addresses which begin with 252# a vertical bar character, such as "|/usr/lib/news/recnews talk.bizarre". 253# The vertical bar is removed from the address before being given to the 254# transport. 255pipe: driver=pipe, # pipe message to another program 256 return_path, # include a Return-Path: field 257 from, # supply a From_ envelope line 258 unix_from_hack, # insert > before From in body 259 # comment out the above line for 260 # use with the Content-Length 261 # header fields. 262# SVR4 mailbox format: uncomment the below 3 lines 263# remove_header="Content-Length", 264# append_header="${if !header:Content-Type :Content-Type: text}", 265# append_header="Content-Length: $body_size", 266 local; # use local forms for delivery 267 268 cmd="/bin/sh -c $user", # send address to the Bourne Shell 269 parent_env, # environment info from parent addr 270 pipe_as_user, # use user-id associated with address 271 ignore_status, # ignore a non-zero exit status 272 ignore_write_errors, # ignore write errors, i.e., broken pipe 273 umask=0022, # umask for child process 274 -log_output, # do not log stdout/stderr 275 276# file - deliver mail to files 277# 278# This is used implicitly when smail encounters addresses which begin with 279# a slash or squiggle character, such as "/usr/info/list_messages" or 280# perhaps "~/Mail/inbox". 281file: driver=appendfile, 282 return_path, # include a Return-Path: field 283 from, # supply a From_ envelope line 284 unix_from_hack, # insert > before From in body 285 # comment out the above line for 286 # MMDF mailbox format and for 287 # use with the Content-Length 288 # header fields. 289# SVR4 mailbox format: uncomment the below 3 lines 290# remove_header="Content-Length", 291# append_header="${if !header:Content-Type :Content-Type: text}", 292# append_header="Content-Length: $body_size", 293 local; # use local forms for delivery 294 295 file=$user, # file is taken from address 296 append_as_user, # use user-id associated with address 297 expand_user, # expand ~ and $ within address 298 suffix="\n", # append an extra newline 299 # comment out the above line for 300 # MMDF mailbox format and for 301 # use with the Content-Length 302 # header fields. 303 mode=0644, # you may wish to change this 304 # mode, depending upon local 305 # conventions and preferences 306# suffix="\1\1\1\1\n", # MMDF mailbox format 307# prefix="\1\1\1\1\n", # MMDF mailbox format 308 309# uux - deliver to the rmail program on a remote UUCP site 310# 311# HDB UUCP users should comment out the first cmd= line below, and 312# uncomment the second. 313uux: driver=pipe, 314 uucp, # use UUCP-style addressing forms 315 from, # supply a From_ envelope line 316 max_addrs=5, # at most 5 addresses per invocation 317# max_addrs=1, # use this if some of your neighbors 318# # can't handle multiple addresses 319# # given to their rmail. You might, 320# # alternately, want to configure 321# # a uux_one_addr transport that 322# # does this. 323 max_chars=200; # at most 200 chars of addresses 324 325 # the -r flag prevents immediate delivery, parentheses around the 326 # $user variable prevent special interpretation by uux. 327 cmd="/usr/bin/uux - -r $host!rmail $(($user)$)", 328 #cmd="/usr/bin/uux - -r -a$sender -g$grade $host!rmail $(($user)$)", 329 pipe_as_sender, # have uucp logs contain caller 330 log_output, # save error output for bounce messages 331# defer_child_errors, # retry if uux returns an error 332 333# demand - deliver to a remote rmail program, polling immediately 334# 335# HDB UUCP users should comment out the first cmd= line below, and 336# uncomment the second. 337demand: driver=pipe, 338 uucp, # use UUCP-style addressing forms 339 from, # supply a From_ envelope line 340 max_addrs=5, # at most 5 addresses per invocation 341# max_addrs=1, # use this if some of your neighbors 342# # can't handle multiple addresses 343# # given to their rmail. You might, 344# # alternately, want to configure 345# # a demand_one_addr transport that 346# # does this. 347 max_chars=200; # at most 200 chars of addresses 348 349 # with no -r flag, try to contact remote site immediately 350 cmd="/usr/bin/uux - $host!rmail $(($user)$)", 351 #cmd="/usr/bin/uux - -a$sender -g$grade $host!rmail $(($user)$)", 352 pipe_as_sender, # have uucp logs contain caller 353 log_output, # save error output for bounce messages 354# defer_child_errors, # retry if uux returns an error 355 356# uusmtp - deliver to the rsmtp program on a remote UUCP site 357# 358# The rsmtp program is assumed to to take batched SMTP requests. 359# 360# HDB UUCP users should comment out the first cmd= line below, and 361# uncomment the second. 362uusmtp: driver=pipe, 363 uucp, # use !-style addresses for routing 364 bsmtp, # send batched SMTP commands 365 -max_addrs, -max_chars; # no limit on number of addresses 366 367 # supply -r to prevent immedate delivery, the recipient addresses 368 # are stored in the data sent to the standard input of rsmtp. 369 cmd="/usr/bin/uux - -r $host!rsmtp", 370 #cmd="/usr/bin/uux - -r -a$sender -g$grade $host!rsmtp", 371 pipe_as_sender, # have uucp logs contain caller 372 log_output, # save error output for bounce messages 373# defer_child_errors, # retry if uux returns an error 374 375# demand_uusmtp - deliver to a remote rsmtp program, polling immediately 376# 377# HDB UUCP users should comment out the first cmd= line below, and 378# uncomment the second. 379demand_uusmtp: 380 driver=pipe, 381 uucp, # use !-style addresses for routing 382 bsmtp, # send batched SMTP commands 383 -max_addrs, -max_chars; # no limit on number of addresses 384 385 # with no -r flag, try to contact remote site immediately 386 cmd="/usr/bin/uux - $host!rsmtp", 387 #cmd="/usr/bin/uux - -a$sender -g$grade $host!rsmtp", 388 pipe_as_sender, # have uucp logs contain caller 389 log_output, # save error output for bounce messages 390# defer_child_errors, # retry if uux returns an error 391 392# inet_uusmtp, inet_demand_uusmtp - batched SMTP conforming to specification 393# 394# These transports specify that transmitted addresses will conform to 395# the SMTP specification. If a route is needed to deliver to a 396# specified host, then route-addr addresses (@host1,@host2:user@destination) 397# will be used. This violates recommendations of RFC1123, but routes 398# are not generally required in networks where RFC1123 recommendations 399# fully apply. 400# 401# HDB UUCP users should comment out the first cmd= line below, and 402# uncomment the second. 403inet_uusmtp: 404 driver=pipe, 405 inet, # use route-addr addresses for routing 406 bsmtp, # send batched SMTP commands 407 -max_addrs, -max_chars; # no limit on number of addresses 408 409 # supply -r to prevent immedate delivery, the recipient addresses 410 # are stored in the data sent to the standard input of rsmtp. 411 cmd="/usr/bin/uux - -r $host!rsmtp", 412 #cmd="/usr/bin/uux - -r -a$sender -g$grade $host!rsmtp", 413 pipe_as_sender, # have uucp logs contain caller 414 log_output, # save error output for bounce messages 415# defer_child_errors, # retry if uux returns an error 416 417# HDB UUCP users should comment out the first cmd= line below, and 418# uncomment the second. 419inet_demand_uusmtp: 420 driver=pipe, 421 inet, # use route-addr addresses for routing 422 bsmtp, # send batched SMTP commands 423 -max_addrs, -max_chars; # no limit on number of addresses 424 425 # with no -r flag, try to contact remote site immediately 426 cmd="/usr/bin/uux - $host!rsmtp", 427 #cmd="/usr/bin/uux - -a$sender -g$grade $host!rsmtp", 428 pipe_as_sender, # have uucp logs contain caller 429 log_output, # save error output for bounce messages 430# defer_child_errors, # retry if uux returns an error 431 432# smtp - deliver using SMTP over TCP/IP 433# 434# The below four drivers are configured in only if your system supports 435# BSD socket networking. 436# 437# Connect to a remote host using TCP/IP and initiate an SMTP conversation 438# to deliver the message. The smtp transport is included only if BSD 439# networking exists. 440# 441# The uucp attribute can be specified for transfers within the UUCP 442# zone. The inet attribute must be specified for transfers within the 443# Internet. 444# 445# NOTE: This is hardly optimal, a backend should exist which can handle 446# multiple messages per connection. 447# 448# ALSO: It may be necessary to restrict max_addrs to 100, as this is the 449# lower limit SMTP requires an implementation to handle for one 450# message. 451smtp: driver=tcpsmtp, 452 inet, # if UUCP_ZONE is not defined 453 #uucp, # if UUCP_ZONE is defined 454 -max_addrs, -max_chars; # no limit on number of addresses 455 456 short_timeout=5m, # timeout for short operations 457 long_timeout=2h, # timeout for longer SMTP operations 458 service=smtp, # connect to this service port 459# For internet use: uncomment the below 4 lines 460# use_bind, # resolve MX and multiple A records 461# defnames, # use standard domain searching 462# defer_no_connect, # try again if the nameserver is down 463# -local_mx_okay, # fail an MX to the local host 464 465uucp_zone_smtp: 466 driver=tcpsmtp, 467 uucp, # use !-style addresses for routing 468 -max_addrs, -max_chars; # no limit on number of addresses 469 470 short_timeout=5m, # timeout for short operations 471 long_timeout=2h, # timeout for longer SMTP operations 472 service=smtp, # connect to this service port 473# For internet use: uncomment the below 4 lines 474# use_bind, # resolve MX and multiple A records 475# defnames, # use standard domain searching 476# defer_no_connect, # try again if the nameserver is down 477# -local_mx_okay, # fail an MX to the local host 478 479inet_zone_smtp: 480 driver=tcpsmtp, 481 inet, # use route-addr addresses for routing 482 -max_addrs, -max_chars; # no limit on number of addresses 483 484 short_timeout=5m, # timeout for short operations 485 long_timeout=2h, # timeout for longer SMTP operations 486 service=smtp, # connect to this service port 487# For internet use: uncomment the below 4 lines 488# use_bind, # resolve MX and multiple A records 489# defnames, # use standard domain searching 490# defer_no_connect, # try again if the nameserver is down 491# -local_mx_okay, # fail an MX to the local host 492 493local_smtp: 494 driver=tcpsmtp, 495 local_xform, # transfer using local formats 496 -max_addrs, -max_chars; # no limit on number of addresses 497 498 short_timeout=5m, # timeout for short operations 499 long_timeout=2h, # timeout for longer SMTP operations 500 service=smtp, # connect to this service port 501# For internet use: uncomment the below 4 lines 502# use_bind, # resolve MX and multiple A records 503# defnames, # use standard domain searching 504# defer_no_connect, # try again if the nameserver is down 505# -local_mx_okay, # fail an MX to the local host 506 507# local_* - local forms for all of the remote transport entries 508# 509# Local format transports are useful when transferring mail messsages 510# within coordinated networks that all run Smail3.1. When the local 511# attribute is enabled for a transport that delivers messages to a 512# remote machine, any local addresses in the header or envelope of the 513# message are left as local-format addresses, and the sender is left 514# as a local login name. 515# 516# This convention for message tranfers allows local networks to be 517# hidden by the common mail users and by users external to the 518# network. Messages transferred to remote nodes in the network will 519# appear as though they originated on the receiving node. Messages 520# that eventually leave the network (and are thus delivered by a 521# transport that does not have the local attribute set) will be 522# transformed into remote-format messages, with qualified domain names 523# for all local-format addresses. 524# 525# This can be very convenient for networks that have a central mail 526# processor that handles all mailing lists and forwarding for the 527# network, and where user names are kept coordinated throughout the 528# network. 529# 530# HDB UUCP users should comment out the first cmd= line below, and 531# uncomment the second. 532local_uux: 533 driver=pipe, 534 local_xform, # transfer using local message format 535 uucp, # use uucp-conformant addresses 536 from, # supply a From_ envelope line 537 max_addrs=5, # at most 5 addresses per invocation 538 max_chars=200; # at most 200 chars of addresses 539 540 # the -r flag prevents immediate delivery, parentheses around the 541 # $user variable prevent special interpretation by uux. 542 cmd="/usr/bin/uux - -r $host!rmail $(($user)$)", 543 #cmd="/usr/bin/uux - -r -a$sender -g$grade $host!rmail $(($user)$)", 544 pipe_as_sender, # have uucp logs contain caller 545 log_output, # save error output for bounce messages 546# defer_child_errors, # retry if uux returns an error 547 548# HDB UUCP users should comment out the first cmd= line below, and 549# uncomment the second. 550local_demand: 551 driver=pipe, 552 local_xform, # transfer using local formats 553 uucp, # use uucp-conformant addresses 554 from, # supply a From_ envelope line 555 max_addrs=5, # at most 5 addresses per invocation 556 max_chars=200; # at most 200 chars of addresses 557 558 # with no -r flag, try to contact remote site immediately 559 cmd="/usr/bin/uux - $host!rmail $(($user)$)", 560 #cmd="/usr/bin/uux - -a$sender -g$grade $host!rmail $(($user)$)", 561 pipe_as_sender, # have uucp logs contain caller 562 log_output, # save error output for bounce messages 563# defer_child_errors, # retry if uux returns an error 564 565# HDB UUCP users should comment out the first cmd= line below, and 566# uncomment the second. 567local_uusmtp: 568 driver=pipe, 569 local_xform, # transfer using local formats 570 bsmtp, # send batched SMTP commands 571 -max_addrs, -max_chars; # no limit on number of addresses 572 573 # supply -r to prevent immedate delivery, the recipient addresses 574 # are stored in the data sent to the standard input of rsmtp. 575 cmd="/usr/bin/uux - -r $host!rsmtp", 576 #cmd="/usr/bin/uux - -r -a$sender -g$grade $host!rsmtp", 577 pipe_as_sender, # have uucp logs contain caller 578 log_output, # save error output for bounce messages 579# defer_child_errors, # retry if uux returns an error 580 581# HDB UUCP users should comment out the first cmd= line below, and 582# uncomment the second. 583local_demand_uusmtp: 584 driver=pipe, 585 local_xform, # transfer using local formats 586 bsmtp, # send batched SMTP commands 587 -max_addrs, -max_chars; # no limit on number of addresses 588 589 # with no -r flag, try to contact remote site immediately 590 cmd="/usr/bin/uux - $host!rsmtp", 591 #cmd="/usr/bin/uux - -a$sender -g$grade $host!rsmtp", 592 pipe_as_sender, # have uucp logs contain caller 593 log_output, # save error output for bounce messages 594# defer_child_errors, # retry if uux returns an error 595 596# FIDO-Transports via Gateway 597fido: from, return_path, 598 driver=pipe; 599 cmd="/var/local/lib/fidonet/rfc2ftn -w $ADDR", 600 pipe_as_sender 601 602fidogate: from, return_path, 603 driver=pipe; 604 cmd="/var/local/lib/fidonet/rfc2ftn -w $user", 605 pipe_as_sender 606 607oldfido: from, received, return_path, 608 driver=pipe; 609 cmd="/usr/bin/uux - -r -g$grade flyer!rmail 610 $((${strip:user})$)", 611 pipe_as_sender 612 613 614 615-------------- 616 617So. Das faellt mir erstmal zum smail-Teil ein. (ach ja: der 618oldfido-Transport dient zum Transitrouting via Internet, um von Classic die 619Lites zu erreichen .-) ). 620 621Wenn noch Fragen sind: Bitte sehr, ich warte immer auf Mails ;->>> 622 623 624ciao 625Martin 626 627--------------------------------------------------------------------- 628Martin Seine martin@erde.gun.de 629 Martin.Seine@FernUni-Hagen.de 630 631 632