prt7u@holmes.acc.Virginia.EDU (Peter R. Thorsen Jr) (03/20/91)
Howdy, I'm sure this question has been raised before so please be patient with me for asking again. I have recently started using mush here at work. On other systems I have used the mailer usually sends you a little message on the screen when your message has been sent to the recipient's computer. Is there a way to do this using mush? I haven't had any problems with mail not getting to where it is supposed to. But I would like the assurance of knowing that it made it to it's destination safely. Please reply via e-mail. Thanks, Pete -- +--------------------+-----------------------------------------+------------+ | Pete Thorsen | Gualtieri's Law of Inertia: | Send me a | | pete@virginia.edu | "Where there's a will, there's a won't" | $1.00 | +--------------------+-----------------------------------------+------------+
schaefer@ogicse.ogi.edu (Barton E. Schaefer) (03/27/91)
In article <1991Mar20.043627.29699@murdoch.acc.Virginia.EDU> prt7u@holmes.acc.Virginia.EDU (Peter R. Thorsen Jr) writes: } Howdy, } } I'm sure this question has been raised before so please be patient } with me for asking again. I have recently started using mush here } at work. On other systems I have used the mailer usually sends you } a little message on the screen when your message has been sent to } the recipient's computer. Is there a way to do this using mush? You can "set verbose" in your .mushrc file, but that will slow mush down a lot (and won't necessarily tell you the truth). Mush creates a new process to send the mail so that you don't have to wait for it to be sent before you go on to do other things. If you tell mush to be verbose about it, then it'll wait while the mail is sent and tell you everything you want to know. However, there are several caveats. If your computer really does connect "directly" to the recipient's computer when sending mail, you could be in for waits of many minutes for the transaction to complete, depending on network traffic and other details. If you are only mailing to other computers within your own company, this may not be a problem, but if you ever mail to somewhere far across the net you could end up twiddling your thumbs for quite a while (at least until your machine gives up and queues the mail for another try later). If your computer uses UUCP to transfer mail, then you may very quickly get a message saying that the mail was "sent", but it's probably fibbing -- in all likelyhood, the mail has only been placed in a spool directory somewhere to wait for the next time UUCP decides to run. } I haven't had any problems with mail not getting to where it is } supposed to. But I would like the assurance of knowing that it made } it to it's destination safely. In most cases, your mailer can't tell you this. The only thing you can do is request a return receipt, by using (in .mushrc): my_hdr Return-Receipt-To: pete@virginia.edu In this case, *if* the receiving mailer recognizes Return-Receipt-To at all, you will be mailed a confirmation that the message arrived. } Please reply via e-mail. I did, but since mush-users doesn't seem to be gatewaying to/from the net anymore (anyone know why?) I'm posting this as well. -- Bart Schaefer schaefer@zipcode.com Z-Code Software Corporation schaefer@cse.ogi.edu