Xref: utzoo comp.mail.misc:1085 comp.mail.uucp:1440 comp.sources.d:2458 Path: utzoo!utgpu!water!watmath!clyde!bellcore!faline!thumper!ulysses!andante!mit-eddie!bbn!uwmcsd1!leah!bingvaxu!sunybcs!bowen From: bowen@sunybcs.UUCP Newsgroups: comp.mail.misc,comp.mail.uucp,comp.mail.sendmail,comp.sources.d Subject: Re: routing problem with sendmail/smail Keywords: mail,smail,sendmail,route Message-ID: <12545@sunybcs.UUCP> Date: 12 Jul 88 16:32:03 GMT References: <589@ndcheg.cheg.nd.edu> <426@ncar.ucar.edu> Reply-To: bowen@sunybcs.UUCP (Devon E Bowen) Organization: SUNY/Buffalo Computer Science Lines: 24 In article <426@ncar.ucar.edu> woods@handies.UCAR.EDU (Greg Woods) writes: >In article <589@ndcheg.cheg.nd.edu> evan@ndcheg.cheg.nd.edu (Evan Bauman) writes: >> >>Since this is coming in via uucp, and not sendmail, rmail (which >>is really smail in disguise!) assumes that this is mail bound for >>another uucp link and bypasses sendmail completely. > > I ran into this one too, when first installing smail long before I ever >heard of BIND. The only fix I was able to come up with is the following >hack to main.c, which causes sendmail to be called EVERY TIME the program >is called as "rmail". I think this is (now, at least) a compile time option to smail. I've got ours set up to bounce everything up to sendmail and I didn't put any hacks in it at all. I had to do this because smail didn't update the path as it went through us and it made us invisible to mail passing through us. Not good when replying. Now I bounce it to sendmail and sendmail takes care of updating the headers, etc. Devon Bowen Packet: KA2NRC@WA0PTV University at Buffalo BITNET: bowen@sunybcs.BITNET Internet: bowen@cs.Buffalo.EDU UUCP: ...!{ames,boulder,decvax,rutgers}!sunybcs!bowen