• Re: Email allegedly from FamilySearch

    From knuttle@21:1/5 to Ian Goddard on Sat May 13 10:56:00 2023
    XPost: soc.genealogy.britain

    On 5/13/2023 10:10 AM, Ian Goddard wrote:
    Has anyone else received an email allegedly from Familysearch
    congratulating them on being promoted to Level1?

    NOT IN OVER ELEVEN YEARS OF USING FAMILY SEARCH

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ian Goddard@21:1/5 to Denis Beauregard on Mon May 15 10:53:17 2023
    XPost: soc.genealogy.britain

    Denis Beauregard wrote:
    On Sun, 14 May 2023 10:06:25 +0100, Ian Goddard
    <ian_ng@austonley.org.uk> wrote in soc.genealogy.computing:

    Searching for the text online indicates that others have received them
    as well bu no explanation on a look.

    Perhaps this ?


    https://community.familysearch.org/en/discussion/145181/what-does-notification-promoted-to-level-1-mean

    This sounds like a mistake when testing some new feature !


    Yes but it doesn't say much apart from the fact that there are a lot of
    people out there who will click on links in an unsolicited email and
    even try to log in when those links offer a login page.

    FWIW I took a look via a dumb text-only browser but certainly didn't try
    to log in. The IP address in the links isn't the same as the normal familysearch.org but it's Cloudflare's so that leads nowhere.

    What's missing so far is an explanation/apology from familysearch. Not
    even a response to my support message nor anything on the main sit's
    front page.

    As you say, it looks like a mistake. About the only thing that tells us
    is that the familysearch is about as clueless at sending emails as some
    of the recipients are about responding to them.

    Ian

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ian Goddard@21:1/5 to Ian Goddard on Mon May 15 13:00:22 2023
    XPost: soc.genealogy.britain

    Ian Goddard wrote:

    Oops, sent early instead of minimised.

    knuttle wrote:
    If every company responded when someone sent an email under their name
    they would be have to have a permanent staff to handle the volume

    If a company sends me an email expecting me to read it they should be prepared to receive andy reply I might send.  That's just good manners.
    If that would place too great a strain on them it tells them one thing:
    their email isn't really that important so they shouldn't send it.

    I suspect that all too often the reason they won't look at replies is
    that the feedback they'd get about their spam would be too upsetting for
    the precious little marketroids who'd have to read it.

    In any case, it was a support email I queried it with, not the noreply
    that sent it.  I expect support desks to respond - it's their job.

    I don't know how many times have received email and phone calls that
    were masquerade as someone or something else.

    Exactly. So anyone - even familysearch.org users should be extremely
    careful of such and not respond to them. In my case any unsolicited
    email like that gets either dumped or handled with metaphorical tongs
    and asbestos gloves. Some of those responding to the thread were
    clearly oblivious to the dangers.

    No responsible organisation should send out such emails. When they do
    it tells me one thing about the individual or team responsible: they see nothing wrong with the possibility that their recipients could respond
    and that they are, therefore, would see nothing wrong in responding to
    similar unsolicited messages asking then to click on a link. Such
    people are a danger to the businesses or organisations for which they
    work. Th ransomware thieves depend on them.


    While Ideally we should eliminate it, it is like chuck holes in the
    street you drive on, something to watch out for and avoid.

    Any organisation needs to train its staff in use of email and treat
    errors as disciplinary matters.

    There have been a number of cases where bulk emails have been sent out
    CC rather than BCC in situations (e.g. STI clinics) where even the
    identities of other recipients should have been regarded as
    confidential. There have been cases where confidential information has
    been sent to the wrong person or even a mailing list. It's not a cse of ideally we should eliminate it. Such mistakes can represent a serious
    threat to the organisation that makes them and sometimes to their customers.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ian Goddard@21:1/5 to knuttle on Mon May 15 12:46:05 2023
    XPost: soc.genealogy.britain

    knuttle wrote:
    If every company responded when someone sent an email under their name
    they would be have to have a permanent staff to handle the volume

    If a company sends me an email expecting me to read it they should be
    prepared to receive andy reply I might send. That's just good manners.
    If that would place too great a strain on them it tells them one thing:
    their email isn't really that important so they shouldn't send it.

    I suspect that all too often the reason they won't look at replies is
    that the feedback they'd get about their spam would be too upsetting for
    the precious little marketroids who'd have to read it.

    In any case, it was a support email I queried it with, not the noreply
    that sent it. I expect support desks to respond - it's their job.

    I don't know how many times have received email and phone calls that
    were masquerade as someone or something else.

    While Ideally we should eliminate it, it is like chuck holes in the
    street you drive on, something to watch out for and avoid.

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Ian Goddard@21:1/5 to Enno Borgsteede on Tue May 16 12:16:28 2023
    XPost: soc.genealogy.britain

    Enno Borgsteede wrote:
    Op 15-05-2023 om 03:53 schreef Denis Beauregard:
    On Sun, 14 May 2023 10:06:25 +0100, Ian Goddard
    <ian_ng@austonley.org.uk> wrote in soc.genealogy.computing:

    Searching for the text online indicates that others have received them
    as well bu no explanation on a look.

    Perhaps this ?


    https://community.familysearch.org/en/discussion/145181/what-does-notification-promoted-to-level-1-mean


    This sounds like a mistake when testing some new feature !

    I don't think so.

    It was. familysearch.org have confirmed that to me:

    "Last week we changed one of the settings in the Beta Community, which
    is a testing site that we use before anything gets launched here in this Community. That change triggered a mass email that we did not know was
    going to be sent. We are still exploring why the email was sent and who
    got it. We are so sorry for the confusion.

    Please disregard these emails or any others that direct you to the Beta Community."


    I followed the link to the beta community, and signed
    in with my existing FamilySearch account. I did that, because I felt
    safe enough to do so, because it looked like a legitimate page in the FamilySearch domain,

    Thousands of people have done similar things because they felt safe
    because it looked like a legitimate page in a legitimate domain.

    You were lucky this time. It was a legitimate domain, only the email
    was an error.

    What has happened is that familysearch.org have now trained you to be
    accepting of emails which look as if they've come from a trusted source
    and to click on and log into what looks like a trusted site. And next
    time you do that it might be a scammer. You might get your bank account emptied. If you do that on a work computer your company might get taken
    down with ransomware.

    This time you were lucky. Next time you might not be. I repeat, this
    time you were lucky. Please don't push your luck.

    Ian

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