George, Wes | 23 May 20:27 2016

IETF IMAP suggestions

Hi - 

I've been trying to transition over to using IMAP for access to the IETF mailing lists that I'm subscribed to, and I have a couple of thoughts I wanted to share as a complete newbie when it comes to shared IMAP folders.

First, it may be worth breaking up the folders so that the current folder named after the mailing list only contains the last {12, 18, 24, whatever} months of list mail, and then an archive folder that is named [mailing-list]-archive or similar, where all messages older than the above age are moved, or a default that only provides the last 12 months of messages for IMAP sync or something. I find that even if one selects only a certain subset of the available folders to subscribe to, the act of asking your mail client to download even headers-only for some of the older mailing lists (some have existed for 20+ years) is bound to make it very unhappy for several days.
Case in point: I had to download 100K+ message headers for IETF <at> IETF, which took a good portion of the weekend. I then had to mass-select everything irrelevant from past years, delete them (and then mark them read so that the unread counter would be useful), and after several days, it's still less than 10% complete in updating the server on the status of all of those messages for my account, which is making it slow to download the message content for anything I actually want to read. Some of this may be a function of my mail client (Outlook 2011 mac, FWIW) being unable to bound the date scope for synchronizing messages i.e. a setting that tells it "Only sync last X months", and probably other limitations, but it's still a consideration in terms of the load on the server and ease of use for the end user.

Second, while a junk email box exists for those clients that expect one, it's doesn't appear to be writable or tied to my account, and thus I'm getting repeated and persistent Permission Denied errors when my client tries to move messages into the junk box. I'm not sure if there's a better solution to this (I have no option in my mail client to store junk locally, I tried) but thought I'd bring it up for your awareness. 

Thanks,

 

Wes George

 

Anything below this line has been added by my company’s mail server, I have no control over it.

-----------



This E-mail and any of its attachments may contain Time Warner Cable proprietary information, which is privileged, confidential, or subject to copyright belonging to Time Warner Cable. This E-mail is intended solely for the use of the individual or entity to which it is addressed. If you are not the intended recipient of this E-mail, you are hereby notified that any dissemination, distribution, copying, or action taken in relation to the contents of and attachments to this E-mail is strictly prohibited and may be unlawful. If you have received this E-mail in error, please notify the sender immediately and permanently delete the original and any copy of this E-mail and any printout.
--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Stephen Farrell | 19 May 03:00 2016
Picon
Picon

comment from someone using the I-D submission tool for the 1st time


Hiya,

A previously inactive (with the tools) co-author on one of
my documents had to take over submission of a final version.
I asked him for any comments as a first time user of that.
He said:

"
While I'm writing about tools: The draft submission tool has a field
"replaces", which tripped me up because I assumed that what I was
uploading was replacing the earlier version.  Apparently a draft does
not replace itself, or even an earlier version of itself... a few
words on the form ("earlier versions of the draft will be automatically
replaced and should not be listed here") or some logic in the form
handler to silently remove "replaces itself" indications would avoid
some confused "it says there's an error, but everything looks fine to
me" moments.
"

So I'm just passing that on to you. I can see what he means
though, our semantics for replaced-by is a bit special and
assumes some insider knowledge.

Cheers,
S.

Attachment (smime.p7s): application/pkcs7-signature, 5191 bytes
--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Michael Richardson | 13 May 20:24 2016
X-Face
Picon

document history


Considering:
        https://datatracker.ietf.org/doc/draft-ietf-6man-rfc2460bis/history/

can the tools be told that draft-ietf-6man-rfc2460bis replaces rfc2460 (via
draft-hinden-6man...) , such that a diff against the original is trivial to ask for?

--
Michael Richardson <mcr+IETF <at> sandelman.ca>, Sandelman Software Works
 -= IPv6 IoT consulting =-

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Martin Vigoureux | 10 May 11:07 2016
Picon

Datatracker rights for the Shepherd Role ?

Hello,

in BESS we are starting to systematically ask for volunteers to shepherd 
documents we last call.
But for them to be autonomous, and to also experiment the 
tools/datatracker, I was wondering if rights could be given to them (in 
the same way as for Secretaries, Delegates, ... in 
datatracker.ietf.org/wg/wg-name/edit/) but which would only apply to the 
document(s) that they shepherd.

Thoughts?

Thanks
-m

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Cullen Jennings | 9 May 21:41 2016
Picon
Gravatar

Idnits-2.14.01 feedback


For *years* idnits has been giving me warning like 

 -- The document date (May 9, 2016) is 152 days in the past.  Is this
     intentional?

Am I doing something wrong? Any plans to fix?

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Eric Rescorla | 1 May 23:00 2016

Tools is down

Not sure where to send this:

"It's not just you! http://tools.ietf.org looks down from here."

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
=JeffH | 23 Apr 00:48 2016

integrating working group mailing lists with github.com?


fyi/fwiw, the W3C has pretty well worked out how to incorp github.com
repos into their processes, including mailing lists.

Here's some info that we IETF oughta at least look at and perhaps
borrow/leverage -- it would be great if we could at least stand up a 
github-notify-mla instance..

  mailing list integration w/github issues & pull requests & pushes, etc
  https://github.com/dontcallmedom/github-notify-ml/

  note that https://github.com/dontcallmedom/github-notify-ml/index.py
  needs to be installed and configured on a internet-accessible web server,
  and registered with github.com as a webhook endpoint. how the W3C's
  instance is config'd is noted here:

    https://github.com/dontcallmedom/github-notify-ml#w3c-instance

see also...

Using GitHub for W3C specifications
https://www.w3.org/2015/Talks/1217-github-w3c/#/1

hth,

=JeffH
s

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Lou Berger | 21 Apr 21:15 2016
Picon

unable to record on webex

Hi,
    I just tried to record a WG- related meeting and am getting an error saying there is no available storage.  Can you help?

Thanks,
Lou


--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Robert Sparks | 14 Apr 23:53 2016

Fwd: Configuration change complete (was Re: Changes in using the global whitelist on IETF lists)

fyi


-------- Forwarded Message -------- Subject: Date: From: To:
Configuration change complete (was Re: Changes in using the global whitelist on IETF lists)
Thu, 14 Apr 2016 16:52:46 -0500
Robert Sparks <rjsparks <at> nostrum.com>
wgchairs <at> ietf.org


The change to add <at> global-whitelist to each list's configuration is now complete.
(As mentioned on other threads, we held off making this change during the server upgrades and during IETF 95).

If you need to revert the change for any reason, use the mailman configuration interface to remove <at> global-whitelist from your list's accept_these_nonmembers setting.

Please let me know if you see any unexpected behavior from your list.

RjS

On 2/18/16 9:40 AM, Robert Sparks wrote:


On 2/17/16 12:55 PM, Jonathan Lennox wrote:

On Feb 3, 2016, at 12:45 AM, IETF Chair <chair <at> ietf.org> wrote:

For the last few months, several working group lists have been utilizing a global-whitelist containing the full set of addresses that are subscribed to or have been whitelisted for any mailman list at ietf.org. This is working well, and we will be configuring all new mailing lists to use this global-whitelist by default. We also plan to adjust the configuration of existing lists to use the global-whitelist later this month.

If you are an administrator of a mailman list at ietf.org and you do not wish your list's configuration to be altered to use the global-whitelist, please send a note to ietf-action <at> ietf.org before February 19, 2015 asking that your list configuration remain unchanged.

Has this not yet been implemented (since it’s not yet February 19th),
No, it hasn't been implemented yet.
or is ietf-secretariat-reply <at> ietf.org not included in the global whitelist?
That address is in the global whitelist.
I just had to manually approve a “milestones changed” e-mail from the datatracker.
You (and any list maintainer) can set up use of the global whitelist immediately if you want to.
Just go put <at> global-whitelist in your lists' accept_these_nonmembers configuration field on the Privacy options page.

I expect it will be several days after the 19th before the remaining lists are touched. I'll send a note when that happens.




--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org
Clifford Denney | 13 Apr 01:49 2016
Picon

Rfcindex-1.05 feedback

clifford.denney <at> gmail.com

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org

Glen | 12 Apr 18:11 2016

Re: recent spam subscriptions to ietf.org lists

> From: "HANSEN, TONY L" <tony <at> att.com>
> Subject: [Tools-discuss] recent spam subscriptions to ietf.org lists
> Date: April 11, 2016 at 10:34:44 AM GMT-3
> To: Tools-discuss <tools-discuss <at> ietf.org>, WGChairs <wgchairs <at> ietf.org>
>
> I'm seeing spam subscriptions ramping up again, using random subaddresses
> off of a handful of gmail addresses. So far they all match these patterns:
>
> ^leafylagann\+.+ <at> gmail.com
> ^kemo.mart\+.+ <at> gmail.com
> ^kezukaya\+.+ <at> gmail.com
> ^dramaalertbiz\+.+ <at> gmail.com
> ^killerkeemstar\+.+ <at> gmail.com
> ^newdramaalert\+.+ <at> gmail.com
>
> - Tony

This was forwarded to me for response.

The way to combat this is to add a per-list configuration addition to
the "banned addresses" section of the list config...

When we saw this previously, it was all +numeric suffixes.

Doing something like,

^[a-zA-Z0-9_.-]+\+[0-9]+ <at> gmail.com

would probably stop all of them.

Or, the list owner could limit it to the known prefixes, and do a
separate entry for each one, like this:

^kemo.mart\+[0-9]+ <at> gmail.com

Of course, Tony's rules suggest that the address space has spread to
alpha characters, so his rules might work better.

AMS has applied these to the lists we manage; but it is up to each
list owner to choose to use one (or more) of the above methods on your
particular lists (or not.)

Glen
Glen Barney
IT Director
AMS (IETF Secretariat)

--

-- 
Tools-discuss mailing list
Tools-discuss <at> ietf.org
https://www.ietf.org/mailman/listinfo/tools-discuss

Please report datatracker.ietf.org bugs at http://tools.ietf.org/tools/ietfdb
Please report tools.ietf.org bugs at http://tools.ietf.org/tools/issues or
send email to webmaster <at> tools.ietf.org


Gmane