Date: Fri, 23 Feb 96 11:05 PST From: pete@pelican.com (Pete Carah) To: questions@freebsd.org Subject: Re: Sendmail -> uucp Message-ID: <m0tq2oG-0000SpC@pelican.com> In-Reply-To: <96Feb19.085540est.20483-2@janus.border.com>
next in thread | previous in thread | raw e-mail | index | archive | help
In article <96Feb19.085540est.20483-2@janus.border.com> you write: >I have my system at home setup to do a similar type of arrangement. >The only catch is, I do uucp across my PPP link. If the link is up, >the connection to the the uucp site is done. If the PPP link is done, >it does a standard UUCP/modem call to do its work... >I don't know if this will work for you. My primary mail transport is >across UUCP. This means your UUCP system has to be configured for TCP. >Then you have to configure your UUCP 'sys' file to try TCP first >then if that fails, try UUCP/modem/dialup.... >If you need examples, let me know.... I've done exactly this at a friend's house (I dial in but am normally up all the time), with the dual sys file entry; since 'alternate' will accept another port type all works fine; it doesn't even wait much to time out when the ppp link is down. If you do a uucp login through a terminal server make sure the ISP has configured the term server (and modems) to NOT use xon/xoff; one of mine had forgotten to do that (he remembered the modems but not the server) and uucp broke rather badly... If the server is a livingston, either have him add a user-id for the uucp session with a login type of TCP-Clear and a destination port of 540 on the right machine (I don't know how to do this on a Cisco, and if the server is another fbsd system then config'ing this is harder), or do a more complicated double dial-out at your place (if you use iijppp in demand-dial mode this is actually pretty easy; I tend to use pppd for the lower cpu overhead, and it won't work as easily.). -- Pete
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m0tq2oG-0000SpC>