[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Non Delivery Report




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: <owner-ietf-fax@xxxxxxx>
Received: (from root@localhost)
 by popmail.dircon.co.uk (8.8.5/8.8.7) id AAA10561
 for equisys; Thu, 21 May 1998 00:04:58 +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 <IETF-FAX@xxxxxxx>;
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: <199805202245.SAA29464@xxxxxxxxxxxxxxx>
X-URI: http://www.cs.utk.edu/~moore/
From: Keith Moore <moore@xxxxxxxxxx>
To: George.Pajari@xxxxxxxxxxx (George Pajari)
cc: moore@xxxxxxxxxx (Keith Moore), GK@xxxxxxx, IETF-FAX@xxxxxxx,
        moore@xxxxxxxxxx
Subject: Re: Mail collection
reply-to: ietf-pop3ext@xxxxxxx
In-reply-to: Your message of "Wed, 20 May 1998 15:34:24 PDT."
             <199805202234.PAA14190@xxxxxxxxxxxxxxxxxxx>
Date: Wed, 20 May 1998 18:45:29 -0400
Sender: owner-ietf-fax@xxxxxxx
Precedence: bulk
X-Envelope-To: <pcrawley@xxxxxxxxxxx>
X-UIDL: 0d29d9ca1ce1314426497086bc722de9

> 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 ietf-pop3ext@xxxxxxx


Received: (from Administrator@localhost) by Blue_Server.equisys.com
(8.6.9/8.6.9) id AAA00613 for postmaster; Thu, 21 May 1998 00:10:30 GMT
Date: Thu, 21 May 1998 00:10:30 GMT
From: ietf-pop3ext@xxxxxxx
Message-Id: <199805210010.AAA00613@xxxxxxxxxxxxxxxxxxxxxxx>
Apparently-To: postmaster