Welcome to the NavList Message Boards.

NavList:

A Community Devoted to the Preservation and Practice of Celestial Navigation and Other Methods of Traditional Wayfinding

Compose Your Message

Message:αβγ
Message:abc
Add Images & Files
    or...
       
    Reply
    Re: Google groups server issues
    From: George Huxtable
    Date: 2007 Apr 25, 08:45 +0100

    
    
    |
    | Today, I noticed a number of weird distribution problems with the
    | list, and I had to bring the archive up to date with a bunch of manual
    | transfers and edits. Last week, I was surprised to see that two
    | messages were sent out by the servers with the same message number,
    | 2636 (!). The first one should have been 2635 so I re-numbered it for
    | the archive. Ten days ago, message 2570 seems not to have distributed
    | to most of the list (I added it by hand to the archive).
    |
    | First of all, please do not worry: we have a backup list service
    | already in place if it becomes necessary. But I would like to hear of
    | any issues list members may have had in the past few weeks.
    | Specifically, could you please go the archive here
    |   www.fer3.com/arc
    | and look at messages for the past ten days. It's about a hundred
    | messages. Compare against the messages you have received by email (if
    | you follow the group by email), and let me know how many you have
    | missed. Thanks.
    |
    | I have zipped up the messages for that period:
    |  http://www.fer3.com/arc/200704/200704.zip
    | The files are ordinary full-header email files. Most email programs
    | should be able to import them but you may need to change the file
    | extension from .emx (my extension) to .txt or .dat. Don't download
    | this file if the previous two sentences don't make sense to you!
    |
    | -FER
    
    ===============
    
    Response from George.
    
    I haven't done what Frank requests, but I have scanned incoming message
    numbers from Navlist, from 2500 up.
    
    The results are as follows-
    
    2570. No such message, just as Frank said
    
    2569. I had said, in navlist 2598, that that too was missing, but I have
    since discovered it. Sorry about that.
    
    2535. No such message
    
    2536. Two different messages, sent at about the same time from Alex, have
    this number. So that looks more like a misnumbered message rather than a
    missing message.
    
    2679. No such message.
    
    2580. No such message.
    
    2581. Two different messages, both sent by Alex but at different times, have
    this number. So that looks like a combination of misnumbered message and
    missed message.
    
    Otherwise, everything seems to be in sequence, up to 2685.
    
    Where there's any suspicion that some messages have not been fully
    circulated, then surely the best solution is for Frank to repost copies of
    them, prominently marked as backup copies, as new postings with a new
    number. That way, everyone gets to see them without having to make a special
    visit. As I suggested in 2598.
    
    George.
    
    contact George Huxtable at george---.u-net.com
    or at +44 1865 820222 (from UK, 01865 820222)
    or at 1 Sandy Lane, Southmoor, Abingdon, Oxon OX13 5HX, UK.
    
    
    
    --~--~---------~--~----~------------~-------~--~----~
    To post to this group, send email to NavList@fer3.com
    To unsubscribe, send email to NavList-unsubscribe@fer3.com
    -~----------~----~----~----~------~----~------~--~---
    
    

       
    Reply
    Browse Files

    Drop Files

    NavList

    What is NavList?

    Join NavList

    Name:
    (please, no nicknames or handles)
    Email:
    Do you want to receive all group messages by email?
    Yes No

    You can also join by posting. Your first on-topic post automatically makes you a member.

    Posting Code

    Enter the email address associated with your NavList messages. Your posting code will be emailed to you immediately.
    Email:

    Email Settings

    Posting Code:

    Custom Index

    Subject:
    Author:
    Start date: (yyyymm dd)
    End date: (yyyymm dd)

    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site
    Visit this site