Non Delivery Report

postmaster@Blue_Server.equisys.com
Newsgroups gmane.ietf.pop3ext
Message-ID <199805210731.HAA00575@Blue_Server.equisys.com>

Your Message

    To:  Huw Charles
       postmaster
    Subject:  Re: Mail collection

Was not delivered for the following reasons:

    Delivery failed to MS:postmaster.
    Reason: 1 (transfer impossible)
    diagnostic:  0 (OR name (Email address) unrecognized).
    MSEXCH:MSExchangeMTA:MSX1:EMERALD.


Original message body follows...



POP received a message that does not appear to be for this site:

Return-Path: <[email protected]>
Received: (from root@localhost)
 by popmail.dircon.co.uk (8.8.5/8.8.7) id AAA10571
 for equisys; Thu, 21 May 1998 00:04:59 +0100 (BST)
Received: from mail.proper.com (mail.proper.com [206.86.127.224])
 by popmail.dircon.co.uk (8.8.5/8.8.7) with ESMTP id AAA10533;
 Thu, 21 May 1998 00:04:56 +0100 (BST)
Received: (from majordomo@localhost) by mail.proper.com (8.8.8/8.7.3) id
PAA01746 for ietf-fax-bks; Wed, 20 May 1998 15:41:57 -0700 (PDT)
Received: from spot.cs.utk.edu (SPOT.CS.UTK.EDU [128.169.92.189]) by
mail.proper.com (8.8.8/8.7.3) with ESMTP id PAA01742 for <[email protected]>;
Wed, 20 May 1998 15:41:56 -0700 (PDT)
Received: from spot.cs.utk.edu by spot.cs.utk.edu with ESMTP (cf v2.11c-UTK)
          id SAA29464; Wed, 20 May 1998 18:45:30 -0400 (EDT)
Message-Id: <[email protected]>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <[email protected]>
To: [email protected] (George Pajari)
cc: [email protected] (Keith Moore), [email protected], [email protected],
        [email protected]
Subject: Re: Mail collection
reply-to: [email protected]
In-reply-to: Your message of "Wed, 20 May 1998 15:34:24 PDT."
             <[email protected]>
Date: Wed, 20 May 1998 18:45:29 -0400
Sender: [email protected]
Precedence: bulk
X-Envelope-To: <[email protected]>
X-UIDL: a65aa2b0c4b4a89ee79fe33ddf1de3cc
Status: U

> According to Keith Moore:
> > If on the other hand, we can do some careful tweaking to POP to let
> > it support confirmation of transfer and relaying of envelope information, 

> > and if ISPs offer the tweaked version of POP rather than what we have
> > now, (which are admittedly big IFs) then we can keep mail reliability 
from
> > degrading.
>
> Obviously I'm missing something here but it would seem to me that the
> effort of persuading ISPs to offer tweaked POP (and to get MUA software
> developers to support tweaked POP, etc. down the food chain) would seem
> isomorphic to the problem of getting them all to use
> "SMTP+TURN+authentication"

maybe, maybe not.  It depends on whether "supporting tweaked POP"
is seen as adding significant overhead.  It also depends on whether
the ISP thinks it can make more money by refusing to support tweaked
POP, and offering an SMTP+TURN service.

> And if the two problems are equally difficult, isn't pushing
> "SMTP+TURN+authentication" better for all?

The question is whether the two are equally difficult.

> Of course, we might have to rename "SMTP+TURN+authentication" POP4
> (POPng anyone?) in order to fool the masses into adopting it. It seems the
> only difference between selling POP+tweaks vs. SMTP+TURN+etc. is the name,
> n'est-ce-pas?

it's probably easier to tweak POP to transfer mail reliably,
than to tweak SMTP to allow it to read messages.

Keith

p.s. since discussion of POP extensions probably doesn't belong on
this list, I suggest that further discussion of these issues be
held on [email protected]


Received: (from Administrator@localhost) by Blue_Server.equisys.com
(8.6.9/8.6.9) id AAA00584 for postmaster; Thu, 21 May 1998 00:10:43 GMT
Date: Thu, 21 May 1998 00:10:43 GMT
From: [email protected]
Message-Id: <199805210010.AAA00584@Blue_Server.equisys.com>
Apparently-To: postmaster
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.