Re: [Extra] Fwd: Personnel change for extra WG

Michael Peddemors <michael@linuxmagic.com> Wed, 03 April 2019 23:40 UTC

Return-Path: <michael@linuxmagic.com>
X-Original-To: extra@ietfa.amsl.com
Delivered-To: extra@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD041200FB for <extra@ietfa.amsl.com>; Wed, 3 Apr 2019 16:40:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level:
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RbLghwvd1bOF for <extra@ietfa.amsl.com>; Wed, 3 Apr 2019 16:40:42 -0700 (PDT)
Received: from fe1.cityemail.com (mail-ob1.cityemail.com [104.128.152.18]) by ietfa.amsl.com (Postfix) with ESMTP id 78A431202E1 for <extra@ietf.org>; Wed, 3 Apr 2019 16:40:42 -0700 (PDT)
Received: (qmail 5305 invoked from network); 3 Apr 2019 23:40:41 -0000
Received: from riddle.wizard.ca (HELO [192.168.1.55]) (michael@wizard.ca@104.128.144.8) by fe1.cityemail.com with (AES128-SHA encrypted) SMTP (e444d1aa-5669-11e9-a01f-9bc39f70b3b8); Wed, 03 Apr 2019 16:40:41 -0700
To: extra@ietf.org
References: <49b87029-7cc2-4324-9d97-f7fa2b8762ce@www.fastmail.com> <25ed8a44-6fce-4778-d9cd-d732b7cb91f6@linuxmagic.com> <533a9f07-80c6-4cbc-b7af-fe10ce62580c@www.fastmail.com> <1003410466.3899.1554328149896@appsuite.open-xchange.com>
From: Michael Peddemors <michael@linuxmagic.com>
Organization: LinuxMagic Inc.
Message-ID: <a2c72491-03f9-b08d-0db0-edea22ec7e4f@linuxmagic.com>
Date: Wed, 3 Apr 2019 16:40:41 -0700
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.5.1
MIME-Version: 1.0
In-Reply-To: <1003410466.3899.1554328149896@appsuite.open-xchange.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-GB
Content-Transfer-Encoding: 8bit
X-MagicMail-OS: Linux 3.11 and newer
X-MagicMail-UUID: e444d1aa-5669-11e9-a01f-9bc39f70b3b8
X-MagicMail-Authenticated: michael@wizard.ca
X-MagicMail-SourceIP: 104.128.144.8
X-MagicMail-RegexMatch: 0
X-MagicMail-EnvelopeFrom: <michael@linuxmagic.com>
X-Archive: Yes
Archived-At: <https://mailarchive.ietf.org/arch/msg/extra/dS_HtKwINm_iKNTX5MeU1lZBI9U>
Subject: Re: [Extra] Fwd: Personnel change for extra WG
X-BeenThere: extra@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Email mailstore and eXtensions To Revise or Amend <extra.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/extra>, <mailto:extra-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/extra/>
List-Post: <mailto:extra@ietf.org>
List-Help: <mailto:extra-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/extra>, <mailto:extra-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 03 Apr 2019 23:40:49 -0000

On 2019-04-03 2:49 p.m., Michael Slusarz wrote:
>> On March 28, 2019 at 10:11 AM Bron Gondwana <brong@fastmailteam.com> 
>> wrote:
>>
>> Regarding the IMAP flags, it sounds like you are asking for the 
>> $JunkRecorded flag to be standardised, as a keyword which is only set 
>> on user action?
> Similar keywords were part of the IMAP keyword registry draft 
> (eventually RFC 5788), before it was taken out:
> 
> https://tools.ietf.org/rfcdiff?url2=draft-melnikov-imap-keywords-04.txt
> 
> Maybe Alexey can comment on the reasoning.
> 
> (I'll note that $AutoJunk, along with $NoJunk, made it into some RFC 
> 4551/5162/7162 examples...)
> 
> For our customers, the much more interesting question is a method to 
> inform mail clients *how* to report messages as Junk (or Not Junk).  RFC 
> 6154 is as close as there is to a standard, with its "\Junk" label, but 
> it doesn't explicitly provide details on whether messages moved to the 
> \Junk mailbox, (or moved out of it) are definitively reported to an 
> AV/AS provider.
> 
> A SPECIAL-USE label of something like "\JunkReporting", with an explicit 
> definition that messages moved into this mailbox by user action are 
> reported as Junk and messages moved out of this mailbox by user action 
> are reported as Not Junk, would be tremendously useful.
> 
> michael


We would support this idea, but want to of course mention, that we have 
to work with email client providers who still want their own use of a 
flag, eg for training etc.. that the client would be responsible for 
setting both flags, instead of just mucking with the \JunkReporting 
flag.. or using it for purposes other than what it is intended.

Of course, it would be nice to define from an IMAP side, a 'hook' 
mechanism, so that on detection of the change in that flag, a server 
defined action could be called.

And should marking a message with that flag, mean that IMAP should move 
it to the special use junk folder?  Or if it is in the junk folder, 
should IMAP move the message to inbox?

We would of course like to see a 'hook' mechanism, that can be used so 
we can also use that information for adding to the users 
blacklist/whitelist natively via IMAP, instead of only through our 
webmail implementations, no matter what email client the end user is using.




-- 
"Catch the Magic of Linux..."
------------------------------------------------------------------------
Michael Peddemors, President/CEO LinuxMagic Inc.
Visit us at http://www.linuxmagic.com @linuxmagic
A Wizard IT Company - For More Info http://www.wizard.ca
"LinuxMagic" a Registered TradeMark of Wizard Tower TechnoServices Ltd.
------------------------------------------------------------------------
604-682-0300 Beautiful British Columbia, Canada

This email and any electronic data contained are confidential and intended
solely for the use of the individual or entity to which they are addressed.
Please note that any views or opinions presented in this email are solely
those of the author and are not intended to represent those of the company.