Hallo Jonathan,

On Sun, 30 Jun 2002 17:39:59 -0500GMT (1-7-02, 0:39 +0200GMT, where I
live), you wrote:

>> Only bad configured mailservers respond to delivery confirmation
>> requests and clients should not respond to them without a user
>> confirmation.

> Why would you say a badly configured server? Surely a delivery
> confirmation should come from the server to say it has been
> delivered? Otherwise it'd not be called that.

But what server should send it? Messages pass several servers. How
does a server know that it's the last one in the line? If it sent the
message further by smtp, it's not likely the last server, but it
happens that messages pass multiple pop3-boxes before arriving at the
the client of the addressee. (It's not common, but it'd be a severe
breach of privacy if all pop3 servers in such a chain responded to a
delivery confirmation request.)

When should a server respond? When it stores the message in a pop3 box
or when the message gets collected? A confirmation is rather useless
when you receive it before the recipient got his copy. You might think
that your message reached me (you got your confirmation), but I'm on
holiday and receive your message three weeks later. Maybe respond when
it gets collected? That's the problem messages get scanned when
they're received, not when they're downloaded from the server.

Apart from the obvious privacy matters it's clear that a server should
never respond to a receipt confirmation request. So it should be done
by the client and that should never be done without permission of the
user.

If I might catch any ISP of mine responding to a delivery conf req,
he's lost a customer.

JA> As for the reading confirmation, that is a user option, and in
JA> most mail clients, asks if the end user wants to send one.

Yep, most.
-- 
Groetjes, Roelof


________________________________________________________
Current Ver: 1.60q
FAQ        : http://faq.thebat.dutaint.com 
Unsubscribe: mailto:[EMAIL PROTECTED]
Archives   : http://tbudl.thebat.dutaint.com
Moderators : mailto:[EMAIL PROTECTED]
TBTech List: mailto:[EMAIL PROTECTED]
Bug Reports: https://www.ritlabs.com/bt/

Reply via email to