Re: [Notifications] Use case--reply mail notification

Eric Burger <eburger@bea.com> Sat, 25 August 2007 11:03 UTC

Return-path: <notifications-bounces@ietf.org>
Received: from [127.0.0.1] (helo=stiedprmman1.va.neustar.com) by megatron.ietf.org with esmtp (Exim 4.43) id 1IOtQK-0003Cn-IQ; Sat, 25 Aug 2007 07:03:24 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IOtQJ-00037h-3R for notifications-confirm+ok@megatron.ietf.org; Sat, 25 Aug 2007 07:03:23 -0400
Received: from [10.91.34.44] (helo=ietf-mx.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IOtQI-00037Y-QC for notifications@ietf.org; Sat, 25 Aug 2007 07:03:22 -0400
Received: from repmmg02.bea.com ([66.248.192.39]) by ietf-mx.ietf.org with esmtp (Exim 4.43) id 1IOtQG-0000Y1-78 for notifications@ietf.org; Sat, 25 Aug 2007 07:03:22 -0400
Received: from repmmr01.bea.com (repmmr01.bea.com [10.160.29.71]) by repmmg02.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l7PB3A3C022523; Sat, 25 Aug 2007 04:03:10 -0700
Received: from repbex01.amer.bea.com (repbex01.bea.com [10.160.26.98]) by repmmr01.bea.com (Switch-3.2.7/Switch-3.2.7) with ESMTP id l7PB37H6007042; Sat, 25 Aug 2007 04:03:09 -0700
Received: from 10.43.242.9 ([10.43.242.9]) by repbex01.amer.bea.com ([10.160.26.98]) with Microsoft Exchange Server HTTP-DAV ; Sat, 25 Aug 2007 11:03:08 +0000
User-Agent: Microsoft-Entourage/11.3.6.070618
Date: Fri, 24 Aug 2007 21:03:13 -0400
Subject: Re: [Notifications] Use case--reply mail notification
From: Eric Burger <eburger@bea.com>
To: Qian Sun <sunqian@huawei.com>, notifications@ietf.org
Message-ID: <C2F4F811.9CB7%eburger@bea.com>
Thread-Topic: [Notifications] Use case--reply mail notification
Thread-Index: AcflNrQ9WeOsDg6DSXKPwEtHqJeJuQBfQG8O
In-Reply-To: <004f01c7e536$b4931040$7c6c460a@china.huawei.com>
Mime-version: 1.0
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 1.9 (+)
X-Scan-Signature: e1e48a527f609d1be2bc8d8a70eb76cb
Cc:
X-BeenThere: notifications@ietf.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Message Notifications interest group discussion list <notifications.ietf.org>
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www1.ietf.org/pipermail/notifications>
List-Post: <mailto:notifications@ietf.org>
List-Help: <mailto:notifications-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/notifications>, <mailto:notifications-request@ietf.org?subject=subscribe>
Errors-To: notifications-bounces@ietf.org

Why not use MDN and a sieve filter?  Sounds like major surgery to do what
people do every day with today's tools.


On 8/22/07 11:35 PM, "Qian Sun" <sunqian@huawei.com> wrote:

> Hi, all
> 
> Scenario: Bob is sending a email to Alice. Bob wants to get a instant
> notification via SMS something if Alice replies, since he is eager to know the
> reply of Alice. He is not interested in other emails. When Bob's mailbox in
> the email server recieves a new email, and find out it is a reply from Alice
> for that mail, a notification of SMS,like "You have got a reply mail from
> Alice", will be sent to Bob's cellphone.
> 
> Problem: For the email sending part, I prefer to realize this requirement by
> using a SMTP extension, e.g. define a new parameter for MAIL command, which
> includes the SMS URI or IM URI. (To Webmail, we need not to do any standard.)
> For the notification part, pager mode message may be better; SUB/NOT event
> mechanism is not necessary. For example, SIP MESSAGE could be a good choice,
> if the users only want to get few notifications.
> 
> Market: It might be an attractive feature to enhance the existing email
> service.
> 
> Opinion?
> 
> Cheers,
> Qian
> 
> 
> 
> 
> 
> _______________________________________________
> Notifications mailing list
> Notifications@ietf.org
> https://www1.ietf.org/mailman/listinfo/notifications


Notice:  This email message, together with any attachments, may contain information  of  BEA Systems,  Inc.,  its subsidiaries  and  affiliated entities,  that may be confidential,  proprietary,  copyrighted  and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.


_______________________________________________
Notifications mailing list
Notifications@ietf.org
https://www1.ietf.org/mailman/listinfo/notifications