Date: Thu, 22 Aug 1996 11:15:46 -0700 (PDT) From: Ken Marsh <durang@u.washington.edu> To: Annelise Anderson <andrsn@andrsn.stanford.edu> Cc: questions@FreeBSD.org Subject: Re: me again. mail question Message-ID: <Pine.A32.3.92a.960822110656.160699D-100000@homer11.u.washington.edu> In-Reply-To: <Pine.BSI.3.94.960822104521.10066B-100000@andrsn.stanford.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
[Huge Omission] > > I've tried using sendmail on my own machine with about 60% success. Some > > messages just never make it to the mailhosts, and they back up the > > mailqueue. Using Pine locally to transport mail to the mailhost is also > > only partially successful. Now I'm telneting an ISP server and using pine > > remotely. This is the only guarantee I can actually send this message. > > > > Ken > > It just seems that something is not set up properly. If pine is > queuing your mail, you must have the mail server in the pine configuration > file set to localhost. Yes. > This means you're using sendmail on your own > machine as the mail transport agent, not the smtp at the isp. Yes. Here's a question for ya: does sendmail see the mail through to the addressee, or does it merely pass it to the SMTP mailhost? > When > you use sendmail -q to send the queued mail, it will (I think) send it > to the default router that's set up when you log in to the isp. That's > why it's important to know what ip address the isp is using for itself, > which should be the default route. This may be dynamically assigned. Yes. I think it is dynamically assigned. It is different every time I dial in to the ISP. A setup I would like to use is one where PINE sends mail to the SMTP mailhost at the ISP. I know how to set that up, but on occasion pine will reach the "sending mail | 100%" point and then lock up. After a long period of time Pine reports that the SMTP connection is lost. I can still ping the SMTP server at this point, so I don't know why the connection is being lost. Perhaps something is timing out? At any rate, I couldn't resolve this problem so I moved on to using sendmail. After that was problematic, I tried POP. I haven't put alot of effort into POP yet, and in the mean time I'm telneting. It's slow, but at least it works. Ken
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.A32.3.92a.960822110656.160699D-100000>