One of the things that you should watch for is any indication that the party that actually sent the message is not the party that the message is supposedly from. In the case of this message, it is supposed to be from Shaw, who provide my Internet service. Obviously I want to continue my Internet service, but, in this case, the message doesn't come from Shaw (a Canadian company), but from BTConnect, a British company. Obviously a Canadian Internet provider would have no need to route their email via a different provider in Britain.
But there is another factor here, and that is a problem with Shaw. Shaw, in providing an interface for email, should be providing its users with the information about who sent the message. Shaw does not. The creator of this message has crafted the message such that the "personal name field" shows "Shaw." But Shaw, in presenting the message, does not provide the actual email address, only the personal name field. The only reason that I was able to quickly figure out that "Shaw" wasn't the actual sender was that the images in the message were stored on an external server, and the email system balked at displaying them.
There are a bunch of fairly obvious red flags in this message. Supposedly it is in regard to a Google Workspace. Right off the top, we should suspect that nobody who works for Google would need, or even be allowed, to use an obviously external email server such as defence-s.org. Then there is the fact that VCN (and particularly my account on it) isn't run by Google. In addition, the link to contract.lisojea.contractors is extremely suspect.
However, note that the user interface for this system does at least give you this information rather than hiding it.
No comments:
Post a Comment