Greg Skinner (firstname.lastname@example.org)
Fri, 03 Apr 87 10:25:46 -0800
There is still a hole with current TCP mailers in that often mail
really travels an extra hop. That is, mail for email@example.com
gets sent to the machine at "somewhere.edu", which after accepting the
mail, turns around and forwards it the machine the user reads mail on.
I would prefer an acknowledgement that mail has actually been placed
in the users mailbox, rather than just handing the mail to a
"reliable" delivering agent at the site.
Like the gentleman from rice said, you don't always know when mail is
placed in the user's mailbox. It may be a post-office type system,
where mail is read from a mail server, but composed from the mail
client. Everything is done without forwarding. When do you decide that
the mail is in the mailbox?
Domain names were designed to handle lots more than just machine name
to IP address mappings. At some point, it will (hopefully) be possible
to register mailboxes in the system. That way, mail sent to
firstname.lastname@example.org will not necessarily mean sending the mail to
"somewhere.edu". Rather, sendmail will find the real agent via
nameserver queries about "email@example.com". Now mail gets sent
directly to the machine where the user's mailbox resides, and now when
the mail is no longer in the sender's local queue, it really is in the
correct mailbox, and not still in transit somewhere.
It still might be in transit somewhere -- the mailbox entries may point
to non-Internet sites which will require at least an extra hop at a mail
Does this "ack" scheme imply retransmission of a mail message until a
retransmission timeout? I would hate to see those old "Message queued
for 3 days -- will try again for another 12 days" messages from mailers
coming to my mailbox again.
This archive was generated by hypermail 2.0b3 on Thu Mar 09 2000 - 14:37:47 GMT