public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: chalenge response software
Date: Sun, 31 Oct 2004 11:54:49 -0700	[thread overview]
Message-ID: <002f01c4bf7b$1dfdee40$0d00a8c0@merlin> (raw)
In-Reply-To: <200410311116.i9VBFwHI029894@ms-smtp-04-eri0.ohiordc.rr.com>

Whether or not you can run something like what I have discussed depends on 
exactly how you pick up your mail. The short answer is, I don't recommend it 
unless you run your own server. Here is the reason. When you pick up your 
mail via fetchmail or what ever mechanism you are using, the 
chalenge/response software will examine the messages and send out 
confirmations. However, this does not happen until you pick up the mail, 
which is probably quite a while after the person sends it. Then, when the 
person replies, the chalenge/response system doesn't receive the 
confirmation until the next time you pick up your mail. I think you can see 
what will happen. Messages can end up taking a long time to be delivered to 
you. It may not be so bad with people who have an always on connection and 
poll their mail stores every few minutes, but I'd still say the ideal 
situation for a system like this is if you have your own domain and your own 
server running it. There are a few client-side chalenge/response solutions 
out there, but I don't recommend them for the same reason.
--
Joseph C. Lininger
jbahm@pcdesk.net
Verification: 5eab38a77ac40416e075be8f50607ff7 



      reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Joseph C. Lininger
 ` Chuck Hallenbeck
   ` Adam Myrow
     ` Joseph C. Lininger [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002f01c4bf7b$1dfdee40$0d00a8c0@merlin' \
    --to=jbahm@pcdesk.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).