RE: [Notifications] Use case--reply mail notification
Qian Sun <sunqian@huawei.com> Wed, 29 August 2007 03:40 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 1IQEQJ-0003IN-GJ; Tue, 28 Aug 2007 23:40:55 -0400
Received: from notifications by megatron.ietf.org with local (Exim 4.43) id 1IQEQI-0003II-VH for notifications-confirm+ok@megatron.ietf.org; Tue, 28 Aug 2007 23:40:54 -0400
Received: from [10.90.34.44] (helo=chiedprmail1.ietf.org) by megatron.ietf.org with esmtp (Exim 4.43) id 1IQEQI-0003I9-Jj for notifications@ietf.org; Tue, 28 Aug 2007 23:40:54 -0400
Received: from szxga02-in.huawei.com ([61.144.161.54]) by chiedprmail1.ietf.org with esmtp (Exim 4.43) id 1IQEQH-0002El-Ev for notifications@ietf.org; Tue, 28 Aug 2007 23:40:54 -0400
Received: from huawei.com (szxga02-in [172.24.2.6]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JNI005F2NIVDI@szxga02-in.huawei.com> for notifications@ietf.org; Wed, 29 Aug 2007 11:40:07 +0800 (CST)
Received: from huawei.com ([172.24.1.24]) by szxga02-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTP id <0JNI00GUINIUUQ@szxga02-in.huawei.com> for notifications@ietf.org; Wed, 29 Aug 2007 11:40:07 +0800 (CST)
Received: from s32328b ([10.70.108.124]) by szxml04-in.huawei.com (iPlanet Messaging Server 5.2 HotFix 2.14 (built Aug 8 2006)) with ESMTPA id <0JNI0040FNIPS3@szxml04-in.huawei.com> for notifications@ietf.org; Wed, 29 Aug 2007 11:40:06 +0800 (CST)
Date: Wed, 29 Aug 2007 11:40:01 +0800
From: Qian Sun <sunqian@huawei.com>
Subject: RE: [Notifications] Use case--reply mail notification
In-reply-to: <A5E9CBACB726CB4BAA3DAFF0925C188F016223CD@repbex01.amer.bea.com>
To: 'Eric Burger' <eburger@bea.com>
Message-id: <000001c7e9ee$47d5a320$7c6c460a@china.huawei.com>
MIME-version: 1.0
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1409
X-Mailer: Microsoft Office Outlook 11
Content-type: text/plain; charset="utf-8"
Content-transfer-encoding: 7bit
Thread-index: AcflNrQ9WeOsDg6DSXKPwEtHqJeJuQBfQG8OAHqk6pAAP7JPoAATXg6Q
X-Spam-Score: 0.5 (/)
X-Scan-Signature: 944ecb6e61f753561f559a497458fb4f
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
Hello Eric I don't think so. A recipient can not prohibit things in sender's mail server. And the sender's mail server has no reason to prohibit the sender to know what stuff is in the sender's mailbox. In detail: When a reply email arrives at sender's mail server, the server may check if the in-reply-to or references header field of this reply email contains the recorded message-id value of original email. If YES, then the sender's server can send an automatic SMS notification to the sender. The recipient can prohibit MDN in his email client, but how can the recipient prohibit this "automatic SMS notification"? Cheers, Qian -----Original Message----- From: Eric Burger [mailto:eburger@bea.com] Sent: Wednesday, August 29, 2007 2:00 AM To: Qian Sun Cc: notifications@ietf.org Subject: RE: [Notifications] Use case--reply mail notification 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
- [Notifications] Use case--reply mail notification Qian Sun
- Re: [Notifications] Use case--reply mail notifica… Eric Burger
- RE: [Notifications] Use case--reply mail notifica… Qian Sun
- RE: [Notifications] Use case--reply mail notifica… Eric Burger
- RE: [Notifications] Use case--reply mail notifica… Qian Sun
- Re: [Notifications] Use case--reply mail notifica… Eric Burger