• Terrible time with email corruption

    From Norm Why@21:1/5 to All on Fri Jun 4 16:41:54 2021
    Hi All,

    I've had a lot trouble with email. On closer inspection one test email
    showed a character error in address: E.g.

    <Ahmed.Hoque@viu?.ca> should be viu.ca

    Where do I start? Server?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Norm Why@21:1/5 to All on Fri Jun 4 17:26:31 2021
    Hi All,

    I've had a lot trouble with email. On closer inspection one test email
    showed a character error in address: E.g.

    <Ahmed.Hoque@viu?.ca> should be @viu.ca

    Where do I start? Server?

    I found the source of the corruption. It came during cut and paste from a webpage. Maybe that implicates mouse drivers locally?

    Comments?

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Paul@21:1/5 to Norm Why on Fri Jun 4 22:56:27 2021
    Norm Why wrote:
    Hi All,

    I've had a lot trouble with email. On closer inspection one test email
    showed a character error in address: E.g.

    <Ahmed.Hoque@viu?.ca> should be @viu.ca

    Where do I start? Server?

    I found the source of the corruption. It came during cut and paste from a webpage. Maybe that implicates mouse drivers locally?

    Comments?

    I would start by doing (in Web browser)

    Save As (Web Page Complete)

    This places an HTM file and a folder, in the downloads
    folder (assuming the download finishes). Some web sites
    are designed on purpose, to thwart attempts to "save as"
    like this.

    Now, look at the HTM file with whatever text editor
    works best for you, and see if you can spot an issue
    there.

    If necessary, you can switch over to HxD on the HTM file,
    as a double check of what kind of garbage is in the file.

    https://mh-nexus.de/en/hxd/

    You may be asking the mouse to copy something which is
    completely inappropriate for the situation. And the address
    may need to be cleaned up manually, to suit. You won't know
    why this happened, until you've examined the file for silly
    stuff.

    There was one NIC, which had a corrupted word every N bytes,
    caused by a hardware bug. As far as I know, anyone using that
    NVidia crap NIC, would have switched to a separate card, long
    ago. I never did hear whether NVidia figured out a way to
    patch that problem. Most NICs are pretty good with your data,
    and they use CRC32 to request retransmission, which improves
    the error floor a bit.

    HTH,
    Paul

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)