• Email Oddity

    From Jeff Gaines@jgnewsid@outlook.com to alt.comp.os.windows-10 on Thu Nov 12 21:41:09 2026
    From Newsgroup: alt.comp.os.windows-10


    I reported to Microsoft in mid October 2026 a bug in Visual Studio 2026 relating to links to files, I kept track of it via their website.

    Today I received 3 x emails from "Visual Studio" (visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21 October updating me on progress as this is investigated, the headers show these dates.

    Any thoughts on how 3 old emails turn up all together nearly a month after
    the dates shown on them?

    I use eM Client and all my other emails (usually confirming I have spent
    more money) have come through OK.

    I may follow up with a legal group as I don't know what would happen if
    these were needed as evidence, but I'd appreciate any thoughts first.
    --
    Jeff Gaines Dorset UK
    The fact that there's a highway to hell and only a stairway to heaven says
    a lot about anticipated traffic numbers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Carlos E.R.@robin_listas@es.invalid to alt.comp.os.windows-10 on Thu Nov 12 23:07:31 2026
    From Newsgroup: alt.comp.os.windows-10

    On 2026-11-12 22:41, Jeff Gaines wrote:

    I reported to Microsoft in mid October 2026 a bug in Visual Studio 2026 relating to links to files, I kept track of it via their website.

    Today I received-a 3 x emails from "Visual Studio" (visualstudio- noreply@microsoft.com) dated 15 October, 16 October and 21 October
    updating me on progress as this is investigated, the headers show these dates.

    Any thoughts on how 3 old emails turn up all together nearly a month
    after the dates shown on them?

    Simple: follow the internal headers named "Received: ". First one is at
    the bottom, last one is at the top. Each time a post passes a server,
    first the machine writes a Received: paragraph, then copies the email it
    has just received for transfer on to the next hop just below that paragraph.

    All those paragraphs are time stamped, so you can find out where any
    email got stuck for a minute or a year.
    --
    Cheers, Carlos.
    ESEfc-Efc+, EUEfc-Efc|;
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Simon@invalid@invalid.invalid to alt.comp.os.windows-10 on Fri Nov 13 00:01:13 2026
    From Newsgroup: alt.comp.os.windows-10

    On 12/11/2026 21:41, Jeff Gaines wrote:
    Today I received-a 3 x emails from "Visual Studio" (visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21 October updating me on progress as this is investigated, the headers
    show these dates.


    I don't know if this issue is related to the problems with Microsoft
    servers that were mentioned in the news today. I'm still having trouble logging into my Outlook account in Thunderbird, so it seems the issue
    hasn't been fully resolved yet.

    <https://www.bbc.co.uk/news/articles/c5gm3g9ldz8xo>







    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bob West@bobwest@invalid.com to alt.comp.os.windows-10 on Fri Nov 13 00:52:24 2026
    From Newsgroup: alt.comp.os.windows-10

    On Nov 12, 2026 at 6:01:13rC>PM CST, "Simon" <invalid@invalid.invalid> wrote:

    On 12/11/2026 21:41, Jeff Gaines wrote:
    Today I received 3 x emails from "Visual Studio"
    (visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21
    October updating me on progress as this is investigated, the headers
    show these dates.


    I don't know if this issue is related to the problems with Microsoft
    servers that were mentioned in the news today. I'm still having trouble logging into my Outlook account in Thunderbird, so it seems the issue
    hasn't been fully resolved yet.

    <https://www.bbc.co.uk/news/articles/c5gm3g9ldz8xo>

    It hasn't. There is a worldwide outage. Been pulling my hair out all day. Should have googled it earlier.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeff Gaines@jgnewsid@outlook.com to alt.comp.os.windows-10 on Fri Nov 13 08:58:20 2026
    From Newsgroup: alt.comp.os.windows-10

    On 13/11/2026 in message <qtsJS.28173$aI4.15717@fx15.iad> Simon wrote:

    On 12/11/2026 21:41, Jeff Gaines wrote:
    Today I received-a 3 x emails from "Visual Studio" >>(visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21 >>October updating me on progress as this is investigated, the headers
    show these dates.


    I don't know if this issue is related to the problems with Microsoft
    servers that were mentioned in the news today. I'm still having trouble >logging into my Outlook account in Thunderbird, so it seems the issue
    hasn't been fully resolved yet.

    <https://www.bbc.co.uk/news/articles/c5gm3g9ldz8xo>

    Could well be Simon, thank you :-)

    I'm getting a string of error messages trying to collect mail from my outlook.com accounts this morning.
    --
    Jeff Gaines Dorset UK
    We chose to do this not because it is easy but because we thought it would
    be easy.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul@nospam@needed.invalid to alt.comp.os.windows-10 on Fri Nov 13 07:55:01 2026
    From Newsgroup: alt.comp.os.windows-10

    On Fri, 11/13/2026 3:58 AM, Jeff Gaines wrote:
    On 13/11/2026 in message <qtsJS.28173$aI4.15717@fx15.iad> Simon wrote:

    On 12/11/2026 21:41, Jeff Gaines wrote:
    Today I received|e-a 3 x emails from "Visual Studio"
    (visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21 >>> October updating me on progress as this is investigated, the headers
    show these dates.


    I don't know if this issue is related to the problems with Microsoft
    servers that were mentioned in the news today. I'm still having trouble
    logging into my Outlook account in Thunderbird, so it seems the issue
    hasn't been fully resolved yet.

    <https://www.bbc.co.uk/news/articles/c5gm3g9ldz8xo>

    Could well be Simon, thank you :-)

    I'm getting a string of error messages trying to collect mail from my outlook.com accounts this morning.


    https://www.bbc.com/news/live/cq5y10ge3dp3t

    "No signs it was malicious: Microsoft executive Charles Lamanna said
    this is not a cyber-security incident. An expert told the BBC earlier
    that the outage looked like "incredible incompetence".
    "

    That's why we have Experts. They can pick the right words at a time like this :-)

    Paul

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From VanguardLH@V@nguard.LH to alt.comp.os.windows-10 on Sat Nov 14 00:37:54 2026
    From Newsgroup: alt.comp.os.windows-10

    Jeff Gaines <jgnewsid@outlook.com> wrote:

    I reported to Microsoft in mid October 2026 a bug in Visual Studio 2026 relating to links to files, I kept track of it via their website.

    Today I received 3 x emails from "Visual Studio" (visualstudio-noreply@microsoft.com) dated 15 October, 16 October and 21 October updating me on progress as this is investigated, the headers show these dates.

    Any thoughts on how 3 old emails turn up all together nearly a month after the dates shown on them?

    I use eM Client and all my other emails (usually confirming I have spent more money) have come through OK.

    I may follow up with a legal group as I don't know what would happen if these were needed as evidence, but I'd appreciate any thoughts first.

    As Carlos mentions, look at the datestamps in the Received headers. The
    Date header is created by the client when it is composing/editing a
    message. That means you could start composing an e-mail, send it out 10
    days later, but the Date header shows the 10-day datestamp when the
    sender's client last modified the message. A message could sit in the
    sender's Draft folder for a long time before the sender actually tells
    their client to do a send.

    Don't rely on the Date header since the sender's client creates that
    header. Look at datestamps for headers the *servers* add as the message bounces between them. I've seen, for example, e-mails from Walmart that
    took 27 hours to get out of Walmart's network about a delivery that was completed over a day ago. A message could be stalled by the sender, so
    the Date header is way out of whack, or at any server in the hops
    between sender to you.
    --- Synchronet 3.22a-Linux NewsLink 1.2