Re: sms notification
Tony Hansen <tony@att.com> Sat, 25 December 2004 18:48 UTC
Received: from above.proper.com (localhost.vpnc.org [127.0.0.1]) by above.proper.com (8.12.11/8.12.9) with ESMTP id iBPImVCX017150; Sat, 25 Dec 2004 10:48:31 -0800 (PST) (envelope-from owner-ietf-mta-filters@mail.imc.org)
Received: (from majordom@localhost) by above.proper.com (8.12.11/8.12.9/Submit) id iBPImG3C016370; Sat, 25 Dec 2004 10:48:16 -0800 (PST)
X-Authentication-Warning: above.proper.com: majordom set sender to owner-ietf-mta-filters@mail.imc.org using -f
Received: from kcmso2.proxy.att.com (kcmso2.att.com [192.128.134.71]) by above.proper.com (8.12.11/8.12.9) with ESMTP id iBPImCXg016037 for <ietf-mta-filters@imc.org>; Sat, 25 Dec 2004 10:48:13 -0800 (PST) (envelope-from tony@att.com)
Received: from maillennium.att.com ([135.25.114.99]) by kcmso2.proxy.att.com (AT&T IPNS/MSO-5.5) with ESMTP id iBPImBuo007111 for <ietf-mta-filters@imc.org>; Sat, 25 Dec 2004 12:48:11 -0600
Received: from [135.70.59.127] (unknown[135.70.59.127](misconfigured sender)) by maillennium.att.com (mailgw1) with ESMTP id <20041225184801gw1000mt38e> (Authid: tony); Sat, 25 Dec 2004 18:48:01 +0000
Message-ID: <41CDB5E5.2020307@att.com>
Date: Sat, 25 Dec 2004 13:48:05 -0500
From: Tony Hansen <tony@att.com>
User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: serj <serjshaklein@mail.ru>
CC: ietf-mta-filters@imc.org
Subject: Re: sms notification
References: <41CC4891.5060909@mail.ru> <41CD678D.3070902@isode.com> <41CD67ED.9000901@mail.ru>
In-Reply-To: <41CD67ED.9000901@mail.ru>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Sender: owner-ietf-mta-filters@mail.imc.org
Precedence: bulk
List-Archive: <http://www.imc.org/ietf-mta-filters/mail-archive/>
List-ID: <ietf-mta-filters.imc.org>
List-Unsubscribe: <mailto:ietf-mta-filters-request@imc.org?body=unsubscribe>
Whose sieve sources? Remember, this mailing list is about the sieve protocol and its extensions. Individual implementations may or may not implement any or all of the extensions. Given that this particular draft was never published as an RFC, it's not surprising you didn't find an implementation of it in the sources you happened to look at. Tony serj wrote: > > yes, i saw it. > but i didnt find sms notification methods even in sieve sources > > Alexey Melnikov wrote: > >> serj wrote: >> >>> does somebody use sms notification in sieve? >> >> I think some implementations of the Notify Sieve extension >> (http://www.oceana.com/ftp/drafts/draft-martin-sieve-notify-01.txt) >> use SMS.
- sms notification serj
- Re: sms notification serj
- Re: sms notification Alexey Melnikov
- Re: sms notification Tony Hansen
- Re: sms notification Matthew Elvey