Xref: utzoo comp.mail.sendmail:3091 comp.mail.headers:688 comp.mail.misc:5253 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!mp.cs.niu.edu!rickert From: rickert@mp.cs.niu.edu (Neil Rickert) Newsgroups: comp.mail.sendmail,comp.mail.headers,comp.mail.misc Subject: Re: How does one send mail to a CompuServe user? Message-ID: <1991Apr21.021624.2151@mp.cs.niu.edu> Date: 21 Apr 91 02:16:24 GMT References: <12541.27f0ee07@amherst.bitnet> Organization: Northern Illinois University Lines: 34 In article beh@wookumz.bu.edu (Bruce E. Howells) writes: > >That compuserve.com address will cause problems for mailers which can not >resolve MX records - spent a bit of time fighting with such a relic over at >BU. > >If your mailer does not recognize compuserve.com, try routing via >saqqara.cis.ohio-state.edu. Ask someone local about how to do this - if >your mailer can't cope with MXs, it's messed enough to be strange. (A good >first guess would be nnnnn.nnnn%compuserve.com@saqqara.cis.ohio-state.edu) That sounds like bad advice. If your mailer does not recognize MX records, junk it and get a decent one. The software you will need is probably as close as your nearest ftp archive site. (It might even be on your machine already under the name '/usr/lib/sendmail.mx'). If, for some reason you are really stuck with a bad mailer, configure it to send all outgoing SMTP mail to a friendly relay host which does have a decent mailer. Obviously you should coordinate this with the admin of the relay host. If you don't administer the machine, and can't change it, explain the problem to your administrator and encourage him to change it. If you can't use MX records, getting to 'compuserve.com' is only one of your problems. There are many sites you will not be able to send mail to. -- =*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*= Neil W. Rickert, Computer Science Northern Illinois Univ. DeKalb, IL 60115 +1-815-753-6940