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

"Eric Burger" <eburger@bea.com> Tue, 28 August 2007 18:00 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 1IQ5MQ-0006Eh-OR; Tue, 28 Aug 2007 14:00:18 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IQ5MQ-0006B4-5k for notifications-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 14:00:18 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQ5MP-00068h-Ox for notifications@ietf.org; Tue, 28 Aug 2007 14:00:17 -0400
Received: from repmmg02.bea.com ([66.248.192.39]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQ5MP-0000c1-4E for notifications@ietf.org; Tue, 28 Aug 2007 14:00:17 -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 l7SHxxBH004767; Tue, 28 Aug 2007 10:59:59 -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 l7SHxvDZ007387; Tue, 28 Aug 2007 10:59:58 -0700
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Subject: RE: [Notifications] Use case--reply mail notification
Date: Tue, 28 Aug 2007 10:59:50 -0700
Message-ID: <A5E9CBACB726CB4BAA3DAFF0925C188F016223CD@repbex01.amer.bea.com>
In-Reply-To: <000901c7e8a0$f0ffb610$7c6c460a@china.huawei.com>
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
Thread-Topic: [Notifications] Use case--reply mail notification
Thread-Index: AcflNrQ9WeOsDg6DSXKPwEtHqJeJuQBfQG8OAHqk6pAAP7JPoA==
References: <C2F4F811.9CB7%eburger@bea.com> <000901c7e8a0$f0ffb610$7c6c460a@china.huawei.com>
From: Eric Burger <eburger@bea.com>
To: Qian Sun <sunqian@huawei.com>
x-BEA-PMX-Instructions: AV
x-BEA-MM: Internal-To-External
X-Spam-Score: 0.0 (/)
X-Scan-Signature: 10ba05e7e8a9aa6adb025f426bef3a30
Cc: notifications@ietf.org
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

In the "do it today", the execution step runs an external shell script,
but yes, this is the basic flow.

Remember, that to protect the privacy interests of the recipient, just
as they can prohibit MDN, they can prohibit "automatic SMS
notification." 

-----Original Message-----
From: Qian Sun [mailto:sunqian@huawei.com] 
Sent: Monday, August 27, 2007 7:54 AM
To: Eric Burger
Cc: notifications@ietf.org
Subject: RE: [Notifications] Use case--reply mail notification

Hello, Eric

Any document defines a "reply" disposition type? And some people might
prohibit MDN.

Do you want to set a sieve script like this?

    if header :contains "In-Reply-To" "143243@example.com" {
        notify :message "You got reply mail" "sms: +10231223";

If not, could you explain your solution in more details?

Cheers,
Qian

-----Original Message-----
From: Eric Burger [mailto:eburger@bea.com]
Sent: Saturday, August 25, 2007 9:03 AM
To: Qian Sun; notifications@ietf.org
Subject: Re: [Notifications] Use case--reply mail notification

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.



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