locked
Loose Catch-Up Test (1) RRS feed

  • Question

  • Loose Catch-Up test. This is the thread to mark Watched. It is being
    composed and sent on the TcpTrace account. Loose Catch-Up Test (2) will be
    composed and sent on another account or simply done using the web forum.
    Before leaving those other accounts, check (e.g. using telnet or another
    account) to see that the bridge can see all of those messages, then send one
    final comment to the Loose Catch-Up Test (1) thread. Then check to see
    that the bridge can see that last message too. Finally, do one of the
    Synchronize commands on the TcpTrace account to see what you get. In
    particular check to see if Synchronize All is doing an XHDR References
    (because of the first thread being marked Watched) and then if that
    redefines what a "New message" is. If it does the "Loose Catch-Up
    feechur/bug" is still present in WLMail but without the Synchronize All
    workaround. In OE Synchronize All does not do the XHDR References check
    for Watched threads. I'm not exactly sure if the bug was ever completely
    fixed in OE. I think it was working better than I had seen it working in
    WLMail but out of habit I never really tried to use anything but
    Synchronize All on OE. My impression is that both the functionality and
    the usability of NNTP synchronization changed in WLMail in ways that up to
    now I have never bothered taking the time to fully analyse.
     
     
    Saturday, June 12, 2010 4:08 PM

All replies

  • Second message in watched thread.   Expected to be seen at the expense of any preceding messages.  E.g. all of Loose Catch-Up Test (2).
     
    Make sure that the bridge has this message before you try your Synchronize command on the first account.
    Saturday, June 12, 2010 4:35 PM
  •  
    Second message in watched thread.   Expected to be seen at the expense of any preceding messages.  E.g. all of Loose Catch-Up Test (2).
     
    Make sure that the bridge has this message before you try your Synchronize command on the first account.
    Sent from other account.   Unwatched message for other thread is still in the Outbox, since I sent it with Work Offline set (unintentionally).   So this, if sent while Working Online, should cause both to be Posted.  It certainly doesn't help that WLMail has gratuitously removed Work Offline from its composition windows...
    Saturday, June 12, 2010 5:16 PM
  • Another message for the watched thread (sent from the other account--while Working Online is in the main Window's Status bar.  
     
    BTW No useful indicators in the WLMail composition window.   More meddling in functionality that the developers were clearly clueless about.
    Saturday, June 12, 2010 5:38 PM
  • Another reply to a watched thread, intended to make all posts in Loose Catch-Up (4) get ignored.
    Sunday, June 13, 2010 12:14 AM