If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below. |
|
|
|
Thread Tools | Rate Thread | Display Modes |
Ads |
#2
|
|||
|
|||
Skype current version
micky wrote:
There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 Is this an old phishing email and they forgot to change 7 to 12? But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. What's going on? Do I have version 12 now or version 7? Authentication-Results: mx01.rcn.cmh.synacor.com ; spf=fail; sender-id=fail Authentication-Results: mx01.rcn.cmh.synacor.com ; dkim=permfail (body hash did not verify) Authentication-Results: mx01.rcn.cmh.synacor.com ; sender-id=fail Received-SPF: fail (mx01.rcn.cmh.synacor.com: domain bounce.email.skype.com does not designate 38.102.228.57 as permitted sender) So, does this look real? How suspicious is it that they tried so hard to hide the headers? The Skype page about phishing says that email.skype.com is one of their 7 genuine domains, but can't a phisher use any from address he wants? It looks fake, and the content of it sounds fake. I would ignore it. -- Joel Crump |
#3
|
|||
|
|||
Skype current version
micky wrote:
There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 My Skype does *not* say "About this Version:", but just "Skype TM Version ...", so you should probably re-check what you did. Is this an old phishing email and they forgot to change 7 to 12? I don't think so. The first (from bottom to top) 'Received:' header looks legit, i.e. directly from skype.com to microsoft.com: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. Correct. What's going on? Do I have version 12 now or version 7? I'm sure you have 7. Just go to (Windows) Control Panel - Programs and Features (or whatever is the Window 10 equivalent) and check there. Mine says 7.40 iunder Name and and 7.40.103 under Version. [...] So, does this look real? How suspicious is it that they tried so hard to hide the headers? The Skype page about phishing says that email.skype.com is one of their 7 genuine domains, but can't a phisher use any from address he wants? I don't think anybody hid anything. It's probably you not knowing how to get Eudora to show you what you want/need. And yes, it's trivial to fake From:/To:/Cc:/Bcc: etc.. [..] P.S. On the phone, the updates happen automatically I assume and I don't know where to find the version number of any app I have. What's a guy to do? Settings - Manage apps - tap on desired app, i.e. Skype - Bingo! |
#4
|
|||
|
|||
Skype current version
micky wrote:
I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 Is this an old phishing email and they forgot to change 7 to 12? But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. What's going on? Do I have version 12 now or version 7? https://en.wikipedia.org/wiki/Skype That lists: Windows - 8.31 Windows UWP - 12.1815 UWP = Universal Windows Platform https://docs.microsoft.com/en-us/win...platform-guide UWPs are those apps (versus programs) that run on Win8+. So, it depends on whether you are running a local full program or a UWP app. list of headers in scam mail The last Received header (the one at the top) is for your end. They get prepended to the header section as the message passes through each mail server. When tracing them download to the sender's server, some spammers will insert bogus headers hoping you think their spam originated from elsewhere. In tracing through them (and changing the 'by' and 'from' clause order to more easily see that the following Received header's 'from' clause is the same as the prior Received header's 'by' clause, and getting rid of what is after 'with' since that doesn't help with tracking), they look like: Received: by md03.rcn.cmh.synacor.com with ... from mx01.rcn.cmh.synacor.com (LHLO mx.rcn.com) (10.33.3.179) Received: from [38.102.228.57] ([38.102.228.57:4487] (from = Bigfoot - perhaps Synacor added this header) Received: by LITEMAIL57.bigfoot.com (LiteMail v3.03(LITEMAIL57)) with ... (internal processing by Bigfoot, so no 'from' clause) Received: by litemail17.bigfoot.net with ... from mta21.email2.microsoft.com ([136.147.186.21]) --. Received: |-- these match by mta21.email2.microsoft.com id hmef9q163hss --' for ...(envelope-from ) I don't see an obvious bogus header but the scammer hides behind Bigfoot. Looks like someone using Skype (Microsoft) sent the e-mail to a Bigfoot account that is configured to redirect e-mails sent to it so they go to you. I haven't used Bigfoot in many years. When I used it, it was just a redirection service used to hide your true e-mail address but when receiving e-mail; i.e., you gave out your Bigfoot e-mail address and Bigfoot redirected the e-mail to your true e-mail account; however, any replies to such redirected e-mails originated from your true account, so Bigfoot wasn't a very good forwarding service (only incoming mails hide your true account but replies exposed your true account). I don't use Skype but the first Received header indicates it was a bounce, so the spammer deliberately bounced a message, like they sent to Bigfoot which sent to Skype (which you won't see in this message's headers) which bounced back to Bigfoot which then redirected to you. Maybe Bigfoot now allows mailing lists, so bouncing back to Bigfoot would send the bounce to the mailing list. I doubt a spammer would dedicate a Bigfoot account just to you. Synacor/RCN must be associated with your e-mail provider (perhaps e-mail service from your ISP) as that is the last Received header. For proper Received header tracking, Syncacor should've added a Received header with a 'from' clause showing Bigfoot and a 'by' clause showing their own server that received the message from Bigfoot. Looks like the scammer used Bigfoot to send to Skype with a deliberately invalid target knowing it would bounce back to Bigfoot which would return the bounced message to a multiple accounts. From: https://ef.bigfoot.com/ef/en/infopag...arding.default the free account would be too limited for a scammer or spammer: just 50 messages per day. The premium account allows power forwarding (https://ef.bigfoot.com/ef/en/infopag...ding.default#4) which might be how the scammer gets Bigfoot to send bounces back to multiple targets. That means you could complain to Bigfoot about the spam/scam message using to get them to kill that account (if they keep logs or the To header in Skype's bounce is valid). So, does this look real? No. How suspicious is it that they tried so hard to hide the headers? The Skype page about phishing says that email.skype.com is one of their 7 genuine domains, but can't a phisher use any from address he wants? Looks like a deliberate bounce by the spammer. Send to an invalid target at Skype, Skype sends a bounce, the sending server returns the bounce where configured (which lists multiple "owning" accounts and how the spammer targets a mailing list). It's been a long time since I inhabited the alt.spam newsgroups but, as I recall, there are folks there that may be more expert at parsing the headers in an e-mail. You'll have to filter out all the Google Groupers (since those are spammers dumping their turds in that newsgroup). I tried to submit the headers to Spamcop.net's parser but your copy here was too mangled. Note: If your newsreader can NOT wrap lines for some lines then do that for the headers you copy into your message here. I gave up trying to edit the headers so the parser could understand them. You could open a free account at Spamcop.net and submit a report. When you enter the suspect e-mail's headers and body, they will parse it to show how they traced through the headers. BTW, who named phishing phishing? Surely not the phishermen? https://en.wikipedia.org/wiki/Phishing "fishing" mispelled but phonetically the same as "phishing", as in "phishing for suckers" (yep, there are fish called suckers). |
#5
|
|||
|
|||
Skype current version
VanguardLH wrote:
[...] Received: by md03.rcn.cmh.synacor.com with ... from mx01.rcn.cmh.synacor.com (LHLO mx.rcn.com) (10.33.3.179) Received: from [38.102.228.57] ([38.102.228.57:4487] (from = Bigfoot - perhaps Synacor added this header) Received: by LITEMAIL57.bigfoot.com (LiteMail v3.03(LITEMAIL57)) with ... (internal processing by Bigfoot, so no 'from' clause) Received: by litemail17.bigfoot.net with ... from mta21.email2.microsoft.com ([136.147.186.21]) --. Received: |-- these match by mta21.email2.microsoft.com id hmef9q163hss --' for ...(envelope-from ) I don't see an obvious bogus header but the scammer hides behind Bigfoot. No, Bigfoot very likely is micky's MSP, because his From: line (of his post) says '. [...] I don't use Skype but the first Received header indicates it was a bounce, so the spammer deliberately bounced a message, like they sent to Bigfoot which sent to Skype (which you won't see in this message's headers) which bounced back to Bigfoot which then redirected to you. I just checked my mail archive and in August 2017, I got a similar (legit) email message from Skype with a similar Received: header: Received: by mta9.email2.microsoft.com id hksgus163hs2 for [email protected]; Wed, 30 Aug 2017 20:37:01 +0000 (envelope-from ) My message went directly from mta9.email2.microsoft.com to my MSP, so the header was *not* forged. [...] So, does this look real? No. I think it does (look real) and you got off on the wrong (Big)foot! :-) BTW, in my response to micky I said that the first/bottom 'Received:' header was hard to forge. I of course meant the last/top one. [...] |
#6
|
|||
|
|||
Skype current version
Frank Slootweg wrote:
VanguardLH wrote: [...] Received: by md03.rcn.cmh.synacor.com with ... from mx01.rcn.cmh.synacor.com (LHLO mx.rcn.com) (10.33.3.179) Received: from [38.102.228.57] ([38.102.228.57:4487] (from = Bigfoot - perhaps Synacor added this header) Received: by LITEMAIL57.bigfoot.com (LiteMail v3.03(LITEMAIL57)) with ... (internal processing by Bigfoot, so no 'from' clause) Received: by litemail17.bigfoot.net with ... from mta21.email2.microsoft.com ([136.147.186.21]) --. Received: |-- these match by mta21.email2.microsoft.com id hmef9q163hss --' for ...(envelope-from ) I don't see an obvious bogus header but the scammer hides behind Bigfoot. No, Bigfoot very likely is micky's MSP, because his From: line (of his post) says '. [...] I don't use Skype but the first Received header indicates it was a bounce, so the spammer deliberately bounced a message, like they sent to Bigfoot which sent to Skype (which you won't see in this message's headers) which bounced back to Bigfoot which then redirected to you. I just checked my mail archive and in August 2017, I got a similar (legit) email message from Skype with a similar Received: header: Received: by mta9.email2.microsoft.com id hksgus163hs2 for [email protected]; Wed, 30 Aug 2017 20:37:01 +0000 (envelope-from ) My message went directly from mta9.email2.microsoft.com to my MSP, so the header was *not* forged. [...] So, does this look real? No. I think it does (look real) and you got off on the wrong (Big)foot! :-) BTW, in my response to micky I said that the first/bottom 'Received:' header was hard to forge. I of course meant the last/top one. [...] You could be correct if micky is using Bigfoot. If so, Bigfoot is forwarding the e-mail to micky's real e-mail provider (Synacor/RCN) and the first Received header is from an MS server to micky's Bigfoot account. Odd that MS would use a server with a hostname of bounce (in the envelope data showing the sender). From micky's copy of the headers and his post here, looks like he has more than one Bigfoot account (misc07 and mm2005). If they were his own accounts, I'd have thought micky would've munged those out to prevent his own Bigfoot accounts from getting harvested. Nothing to munge out in Synacor/RCN's Received header to identify his account there. Seeing the message body would also indicate if the e-mail were a scam or authentic by looking at to where the hyperlinks point. Other than the e-mail issue, according to the wikipedia article there are different versions of Skype depending on whether you get the client program or the UWP app. On another issue, micky showed the following header: Authentication-Results: mx01.rcn.cmh.synacor.com ; dkim=permfail (body hash did not verify) The message got modified in transit. Makes me wonder if micky's Bigfoot account is adding a signature or otherwise modifying the original message so its hash got changed. |
#7
|
|||
|
|||
Skype current version
Frank Slootweg wrote:
micky wrote: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. If you know which is the first Received header added by a mail server and not inserted by a spammer. An old trick is for the spammer's client to add a fake Received header to the body of their message. Normally the header section is delimited from the body by a blank line (presence of /n/n after the last header); however, I've seen the fake Received header in the header section (no blank delimiter line). Maybe this is the spammer using their own SMTP server to connect to a real e-mail provider's SMTP server, and the spammer has their server (using the same SMTP commands as any e-mail client) prepending the fake Received header before passing it onto the real SMTP server. Normally you look for the 'from' clause in a Received header to match on the 'by' clause in the just-prior Received header. That fails when a server has internal routing that only show a 'from' clause or only shows a 'by' clause but those often have IP addresses at the e-mail provider or using internal IP addresses. Sometimes the Received headers are rather mangled, so it can be tough to be sure no bogus ones were added by the spammer before passing it through the following SMTP servers. The first Received header is an example of an incomplete header: no 'from' clause. That's because it was an internal handoff. |
#8
|
|||
|
|||
Skype current version
In comp.mail.eudora.ms-windows, on Tue, 2 Oct 2018 20:38:40 -0500,
VanguardLH wrote: You could be correct if micky is using Bigfoot. If so, Bigfoot is forwarding the e-mail to micky's real e-mail provider (Synacor/RCN) and the first Received header is from an MS server to micky's Bigfoot account. Odd that MS would use a server with a hostname of bounce (in the envelope data showing the sender). From micky's copy of the headers and his post here, looks like he has more than one Bigfoot account (misc07 and mm2005). Yes, I have several. (Sorry it took all day to get back to you about this.) I was going to use different ones for different purposes, but it didnt' really work out well. And I shouldn't badmouth bigfoot, which has not charged me for 15 or 20 years, but they've had outages, for 2 to 4 days, 2 or 3 times, and I think once for 6 weeks. I don't know if they affected paying customers or not, but I suspect they did, because the outages didn't come with a request to start paying. I was going to delete one address if it got too much spam, but then I'd use one address for two or more purposes so if I deleted it, I wouldn't get the emails I wanted. So I never deleted any of them. If they were his own accounts, I'd have thought micky would've munged those out to prevent his own Bigfoot accounts from getting harvested. Good point there. I did with one instance, but I see now that I missed the other one. Just didn't see it. Nothing to munge out in Synacor/RCN's Received header to identify his account there. Seeing the message body would also indicate if the e-mail were a scam or authentic by looking at to where the hyperlinks point. Other than the e-mail issue, according to the wikipedia article there are different versions of Skype depending on whether you get the client program or the UWP app. Yes, that must be where the conflict in version numbers comes from. Years ago I searched for Skype in my windows and then created a shortcut for it that I pinned to the taskbar, plus I think I updated it before as if it were not a windows=embedded program, and so gradually I forgot that it was part of windows. On another issue, micky showed the following header: Authentication-Results: mx01.rcn.cmh.synacor.com ; dkim=permfail (body hash did not verify) The message got modified in transit. Makes me wonder if micky's Bigfoot account is adding a signature or otherwise modifying the original message so its hash got changed. Aha. For years it didn't do anything, but for the last 2 years or so it sometimes** adds a banner at the top, and it did that in this case. I didn't know until you just said it that that couuld make hashes not match. **I don't know why sometimes it does and sometimes it doesn't. Maybe it depends on how many emails I've gotten in a month with each one. Bigfoot is very generous and I'd recommend it if it werent' for outages. But I have to read the thread again much more slowly to really understand it. I'll post back in a day or two. |
#9
|
|||
|
|||
Skype current version
micky wrote:
VanguardLH wrote: On another issue, micky showed the following header: Authentication-Results: mx01.rcn.cmh.synacor.com ; dkim=permfail (body hash did not verify) The message got modified in transit. Makes me wonder if micky's Bigfoot account is adding a signature or otherwise modifying the original message so its hash got changed. Aha. For years it didn't do anything, but for the last 2 years or so it sometimes** adds a banner at the top, and it did that in this case. I didn't know until you just said it that that couuld make hashes not match. **I don't know why sometimes it does and sometimes it doesn't. Maybe it depends on how many emails I've gotten in a month with each one. Bigfoot is very generous and I'd recommend it if it werent' for outages. But I have to read the thread again much more slowly to really understand it. I'll post back in a day or two. I remember looking at another forwarding service (forget its name but think they disappeared since then - maybe it was SpamMotel) where they added a statistics banner to the top of the forwarded e-mail. The problem is that it would corrupt digitally signed e-mails. Not necessarily encrypted e-mails but those where the sender hashed their e-mail using an e-mail certificate to create a digital signature. Any modification of the e-mail would invalidate the digital signature. The same can happen using anti-virus software that appends a fake signature onto outgoing e-mails, like Avast and others. The signature is fake because it is not a valid signature delimiter line, like 3 dashes and a newline instead of 2 dashes, a space, and then a newline. When the client composes the e-mail and digitally signs it (by computing a hash to record in the header) using the certificate added to that client, it then passes through the AV's proxy to get modified to add the fake signature. The client's hash is no longer valid after the modification to later add the fake signature which is spam promoting the AV program hence spamifying the sender's outbound e-mails. Anything that watermarks an e-mail outside the client that digitally signed it will invalidate the digital signature. In the aforementioned forwarding service, there was an option of whether or not to add the statistics banner to e-mails that they forwarded to my real account. Maybe Bigfoot has a similar user-configurable switch. A long time back I played with Bigfoot. As a forwarding service, they were okay. However, as an anonymizing forwarding service, they sucked. E-mails forwarded through them were as-is to your real account. If you replied to those e-mails, the replies originated from whatever accounts you configured in your e-mail client, so it highly likely your real account got exposed in the headers because the origination for your reply was through your own real account. While the Received headers would show your reply came from your real account instead of from Bigfoot, your client may be adding headers showing through which account your reply was sent. Your real account might also add headers at the server to identify the sender. In contrast, Spamgourmet (free and paid) and SpamEx (paid only - they dropped their free accounts a long time ago). Spamgourmet lets me create aliases on the fly. SpamEx required me to log into my account there to create the alias. When SpamEx had free accounts although crippled (but with quotas well above my typical e-mail volume), I used them. When they discarded the free accounts, I moved to Spamgourmet who, by the way, is used by several companies to provide aliased forwarding services, like at Craigslist. Another problem with Bigfoot is that a lot of sites refuse to allow you to use those forwarding services. Sometimes I hit one that refuses to let me use a Spamgourmet forwarding alias. They want a real account. For example, when registering an account at many web-based forums, they won't let me use a forwarding service. Those are blacklisted by the forum sites. Some won't even let you use Gmail or Hotmail because those are free accounts, and the forum wants you using something like your ISP e-mail service. I learned a long time ago to protect my real e-mail address, so the first e-mail address that I give any site regardless of how well they are known is an aliased forwarding e-mail address, like with Spamgourmet. I've had stores starting spewing spam at me because, for example, I wanted them to notify me when a ship-to-store purchase was ready for pickup. Only after they've proven non-spammy after about 6 months do I update my account with them to reflect my real e-mail, or sometimes all they ever get is the alias. Another problem with Bigfoot is they seem to batch up the forwards to your real account. That is, they will receive several e-mails before they get around to forwarding them to your real account. As I recall, their batch interval was 1 hour. That was for the free account that I had with them back then. While not true of Bigfoot, Spamgourmet, SpamEx or true aliased forwarding e-mail providers, some services (e.g., MailDrop) dump your e-mails into a pool that other users can see if they know or guess your e-mail address used at that service, so your e-mails aren't private. I've seen this mostly with several disposable e-mail services. I remember Gmail trying to allow disposable e-mail addresses by simply appending something like +alias to the username. Yeah, like folks told to use can't figure out your true account. All e-mail services have outages. Sometimes their fault, like their equipment going down or they do maintenance, and sometimes not their fault, like a webhosting service going down or the server at a contracted service going down. Bigfoot may have gone down occasionally but I've also had temporarily outages at SpamGourment, SpamEx, my ISP, and even Hotmail (although it's been a few years since that last happened). |
#10
|
|||
|
|||
Skype current version
Yesterday, I wrote:
[...] I just checked my mail archive and in August 2017, I got a similar (legit) email message from Skype with a similar Received: header: Received: by mta9.email2.microsoft.com id hksgus163hs2 for [email protected]; Wed, 30 Aug 2017 20:37:01 +0000 (envelope-from ) My message went directly from mta9.email2.microsoft.com to my MSP, so the header was *not* forged. I just got another 'A Skype update may be required' e-mail notification. It's similar to the above mentioned August 2017 one and similar to micky's. Also this one went directly from mta40.email2.microsoft.com to my MSP. I checked the links in this e-mail and they all point to skype.com, i.e. legit. Note to micky: The 'From:' line is my correct e-mail address, i.e. the e-mail address in my Skype Account and the body of the message contains my correct 'Account Name:' (i.e. my Skype Name). Conclusion: The e-mails are legit. |
#11
|
|||
|
|||
Skype current version
In alt.comp.os.windows-10, on 2 Oct 2018 18:51:14 GMT, Frank Slootweg
wrote: micky wrote: There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 My Skype does *not* say "About this Version:", but just "Skype TM Version ...", so you should probably re-check what you did. Is this an old phishing email and they forgot to change 7 to 12? I don't think so. The first (from bottom to top) 'Received:' header looks legit, i.e. directly from skype.com to microsoft.com: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. Correct. What's going on? Do I have version 12 now or version 7? I'm sure you have 7. Just go to (Windows) Control Panel - Programs and Features (or whatever is the Window 10 equivalent) and check there. Mine says 7.40 iunder Name and and 7.40.103 under Version. Good idea. I'd forgotten that versions are listed there. But it's not even there! That's when I remembered that Skype came included in some version of Win10. And I guess that is the reason for the different version number. I found it a nuisance to Search for Skype before opening it so I managed to create a shortcut and pin it to the task bar, and I thought I once updated it by going to the skype download webpage. [...] So, does this look real? How suspicious is it that they tried so hard to hide the headers? The Skype page about phishing says that email.skype.com is one of their 7 genuine domains, but can't a phisher use any from address he wants? I don't think anybody hid anything. It's probably you not knowing how to get Eudora to show you what you want/need. And yes, it's trivial to fake From:/To:/Cc:/Bcc: etc.. Then it's strange that the Skype anti-phishing page bothers to say what their valid domains are and without giving a warning that seeing one means nothing. [..] P.S. On the phone, the updates happen automatically I assume and I don't know where to find the version number of any app I have. What's a guy to do? Settings - Manage apps - tap on desired app, i.e. Skype - Bingo! |
#12
|
|||
|
|||
Skype current version
micky wrote:
In alt.comp.os.windows-10, on 2 Oct 2018 18:51:14 GMT, Frank Slootweg wrote: micky wrote: There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 My Skype does *not* say "About this Version:", but just "Skype TM Version ...", so you should probably re-check what you did. Is this an old phishing email and they forgot to change 7 to 12? I don't think so. The first (from bottom to top) 'Received:' header looks legit, i.e. directly from skype.com to microsoft.com: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. Correct. What's going on? Do I have version 12 now or version 7? I'm sure you have 7. Just go to (Windows) Control Panel - Programs and Features (or whatever is the Window 10 equivalent) and check there. Mine says 7.40 iunder Name and and 7.40.103 under Version. Good idea. I'd forgotten that versions are listed there. But it's not even there! That's when I remembered that Skype came included in some version of Win10. And I guess that is the reason for the different version number. As VanguardLH mentioned, the version 12 thingy is an UWP (Universal Windows Platform) / Metro / Modern / whatever *app* which uses Windows 10's Fisher-Price interface (Thanks, Stan)! You should be ashamed of yourself! Not just for having the poor taste of using such a disgusting POS, but having the audacity to publicly and openly confess such a disgraceful act! Shame on you! |
#13
|
|||
|
|||
Skype current version
micky wrote:
There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 Is this an old phishing email and they forgot to change 7 to 12? Skype Classic(the years long UI, last version 7x) is being deprecated. In the foreseeable future only the Universal Windows App[UWA] version(V12 Windows 10 and V8 Skype Desktop based on the UWA) will be available *and* required, thus standardizing the desktop version feature set across Win7, 8x, 10 and more closely aligning the product with the MSFT Store UWA feature set. The latest information can be found on the Skype blog web site qp Editor’s note, September 27, 2018: We’re continuing to work on your most requested features. Recently we launched call recording and have started to roll out the ability to search within a conversation. You’ll soon be able to add phone numbers to existing contacts, have more control over your availability status, and more. As we continue to focus on and improve Skype version 8, support for Skype versions 7, and below will end on November 1, 2018 on desktop devices and November 15, 2018 on mobile and tablet devices. == Although you may be able to use older versions for a little while, we encourage you to update today to avoid any interruption. Editor’s note, August 31, 2018: We’ve been listening to your feedback and are working to bring some of the most-requested features from Skype version 7 to version 8. To ensure customers have an uninterrupted Skype experience as we do this, Skype version 7 will continue to work for a limited time. Stay tuned for updates on the final date for version 7. In the meantime, we encourage everyone to update now to avoid any future inconvenience. /qp cf. https://blogs.skype.com/news/2018/07...e-for-desktop/ -- ...w¡ñ§±¤ñ msft mvp windows experience 2007-2016, insider mvp 2016-2018 |
#14
|
|||
|
|||
Skype current version
In comp.mail.eudora.ms-windows, on 4 Oct 2018 17:52:55 GMT, Frank
Slootweg wrote: micky wrote: In alt.comp.os.windows-10, on 2 Oct 2018 18:51:14 GMT, Frank Slootweg wrote: micky wrote: There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 My Skype does *not* say "About this Version:", but just "Skype TM Version ...", so you should probably re-check what you did. Is this an old phishing email and they forgot to change 7 to 12? I don't think so. The first (from bottom to top) 'Received:' header looks legit, i.e. directly from skype.com to microsoft.com: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. Correct. What's going on? Do I have version 12 now or version 7? I'm sure you have 7. Just go to (Windows) Control Panel - Programs and Features (or whatever is the Window 10 equivalent) and check there. Mine says 7.40 iunder Name and and 7.40.103 under Version. Good idea. I'd forgotten that versions are listed there. But it's not even there! That's when I remembered that Skype came included in some version of Win10. And I guess that is the reason for the different version number. As VanguardLH mentioned, the version 12 thingy is an UWP (Universal So it doesn't stand for UnWanted Program? Windows Platform) / Metro / Modern / whatever *app* which uses Windows 10's Fisher-Price interface (Thanks, Stan)! You should be ashamed of yourself! Not just for having the poor taste of using such a disgusting POS, but having the audacity to publicly and openly confess such a disgraceful act! Shame on you! I'm ashamed of myself for many reasons, but not sure why I should be here. That I use Skype, or that I use the Skype that came with windows? As to the first, what is better? As to the second, I thought maybe I could install a totally separate copy, but then I'd have two copies, wasted space, and I didn't want that. |
#15
|
|||
|
|||
Skype current version
micky wrote:
In comp.mail.eudora.ms-windows, on 4 Oct 2018 17:52:55 GMT, Frank Slootweg wrote: micky wrote: In alt.comp.os.windows-10, on 2 Oct 2018 18:51:14 GMT, Frank Slootweg wrote: micky wrote: There is a bigger email component to this post further down. I got an email today saying that they could tell I had recently used Skype ver. 7 and that support for that was ending in November. Update Now. I almost did that until I checked my Skype and it said it was version 12! About this Version: Skype 12.1815.210.0 My Skype does *not* say "About this Version:", but just "Skype TM Version ...", so you should probably re-check what you did. Is this an old phishing email and they forgot to change 7 to 12? I don't think so. The first (from bottom to top) 'Received:' header looks legit, i.e. directly from skype.com to microsoft.com: Received: by mta21.email2.microsoft.com id hmef9q163hss for ; Tue, 2 Oct 2018 16:32:13 +0000 (envelope-from ) The first header is hard to fake/forge, so if it's legit, that's a good indication of the message to be legit. But I went to Skype Download and by golly, it wants to install version 8. Not 12 or 13. Correct. What's going on? Do I have version 12 now or version 7? I'm sure you have 7. Just go to (Windows) Control Panel - Programs and Features (or whatever is the Window 10 equivalent) and check there. Mine says 7.40 iunder Name and and 7.40.103 under Version. Good idea. I'd forgotten that versions are listed there. But it's not even there! That's when I remembered that Skype came included in some version of Win10. And I guess that is the reason for the different version number. As VanguardLH mentioned, the version 12 thingy is an UWP (Universal So it doesn't stand for UnWanted Program? Windows Platform) / Metro / Modern / whatever *app* which uses Windows 10's Fisher-Price interface (Thanks, Stan)! Of course it *is* an UnWanted Program, but as I said, it *stands for* 'Universal Windows Platform'. And because we're talking about Microsoft here, 'Universal' means that it's anything but. So don't expect your Windows 8.1. thingy to run on Windows 10 or vice versa. 'Compatibility'? You silly, silly boy! You should be ashamed of yourself! Not just for having the poor taste of using such a disgusting POS, but having the audacity to publicly and openly confess such a disgraceful act! Shame on you! I'm ashamed of myself for many reasons, but not sure why I should be here. That I use Skype, or that I use the Skype that came with windows? As to the first, what is better? No, that you use Skype is fine. Skype is great. It's the best since sliced bread. I Skype all the time. Sadly enough there's never anyone at the other end. I wonder why *that* is? As to the second, I thought maybe I could install a totally separate copy, but then I'd have two copies, wasted space, and I didn't want that. A bit of consisency in your arguments wouldn't come astray! You imply that you don't want to waste space, but at the same time you admit that you're running Windows 10! What's up with *that*!? Not to mention that you can't run 10. Limp yes, run no! So be a man - or at least act like one - and upgrade to at least Windows 8.1, but preferably to Windows 7! |
|
Thread Tools | |
Display Modes | Rate This Thread |
|
|