bmw@isgtec.UUCP (Bruce Walker) (07/07/89)
I have two "universes" that I am trying to connect mail between, SunOS 4 and CTIX 5.25 (Convergent Technologies SysVR3). The universes are connected via ether, with the minimal ftp-style suite: ftp, rcp, rsh, etc. But how do I get mail between them? o SunOS has sendmail (with SMTP over TCP), CTIX does not. o CTIX has uucpd (uucp over TCP), SunOS does not. As I see it, I can either get sendmail source and munge it to run under SysV (gack!) or, write an SMTP daemon for SysV, or else get (somehow) a uucpd daemon for SunOS. Before I go off the deep-end, any suggestions? sources? sympathy? Thanks! -- Bruce Walker ...uunet!mnetor!lsuc!isgtec!mutant!bmw ...utzoo!lsuc!isgtec!mutant!bmw ISG Technologies Inc. 3030 Orlando Dr. Mississauga. Ont. Can. L4V 1S8
cyliax@inf.ethz.ch (Ingo Cyliax) (07/13/89)
You could create a special process for the SysV box, that would open a pseudo tty for uucp to connect to and establish an rlogin or telnet connect on the sun. In this fashion, the uucp stuff should still work normally, but actually run over the net. SysV.3 Sun uucico | ttp? uucico | | ttm? (login) | | telnetprocess --------------> telnetd We thought about doing this and almost had it working, but ended up getting V8 uucp on the Sun's V8 uucp can talk over the ethernet with uucpd. -ingo -- /* Ingo Cyliax Stabstelle Software * * cyliax@inf.ethz.ch Department fuer Informatik * * cyliax@ethz.uucp ETH-Zentrum * * Tel: +41 1 256 35 31 CH-8092 Zuerich, Switzerland */
grr@cbmvax.UUCP (George Robbins) (07/16/89)
In article <329@ethz-inf.UUCP> cyliax@inf.ethz.ch.UUCP (Ingo Cyliax) writes: > > You could create a special process for the SysV box, that would open > a pseudo tty for uucp to connect to and establish an rlogin or telnet > connect on the sun. In this fashion, the uucp stuff should still work > normally, but actually run over the net. Actually, if you patch uucico in two places you can do pretty much the same thing. Make a copy of uucico 8-), patch ioctl to simply return 0 and patch diropn to return 1. You now a version of uucp than can be run from uucpd (no-oping ioctl prevents errors from doing tty ioctls on a socket) and that initiates a conversation when spawned with stdin/stdout open on a socket to a uucp daemon (making diropn return a 1 causes uucico to use the file desriptor open on stdout when you request any "direct" line). Yes it's disgusting, yes it works, yes there are better ways. This is based on BSD 4.2 derived uucp, your version is always different, uucpd is redistributable 4.3 Tahoe soure, you have to kludge up your own spawner... -- George Robbins - now working for, uucp: {uunet|pyramid|rutgers}!cbmvax!grr but no way officially representing arpa: cbmvax!grr@uunet.uu.net Commodore, Engineering Department fone: 215-431-9255 (only by moonlite)