Skip to main content

What is the record for spamming new users?

News broke today on tech outlets like The Verge and TechCrunch about a new calendar service called Sunrise.  Login options for the web application version include Google and Facebook.  A quick look around after logging in via each of these methods yielded an appealing interface, but nothing really enough to sway users away from whatever they're currently using.

What is impressive though is how quickly the spam machine was fired up.  The following message was received only hours after the brief tour from earlier in the day.  Here is the message veiled under the "From" address of "support@sunrise.am."

Dear user,

Today is an exciting day for Sunrise. We're launching on both Desktop and Android.

 [image]

 You can start using Sunrise everywhere for free.

On desktop, Sunrise will help you stay organized by combining all the information you need in one place. The desktop app is fast, beautiful and brings everything you love about Sunrise to your desktop. It takes 5 seconds to get started.

Sunrise for Android brings the best calendar to the most popular mobile platform. We've worked really hard to make an amazing user-experience for Android and leverage all the great features of Android, like widget and rich notifications. We've made this video to show you the app:

 [embedded video]

 Download Sunrise for Android and try Sunrise on Desktop now.

We're proud of your support. Today, we are making Sunrise available everywhere and we are just getting started.
 
Thank you for making Sunrise better, everyday.
 
"Sunrise is the first great calendar app for Android and web" – The Verge.
 
– Team @sunrise

Wow!  If this was a welcome message or a collection of usage tips, that would be one thing, but it's an announcement.  The email address this was sent to was collected from logging in to the service.  An announcement is redundant.  As such, this amounts to nothing more than junk mail and a nomination for the quickest exploitation of a user's email address.

Comments

Post a Comment

Popular posts from this blog

Remove control of Chrome being managed by organization on personal devices

Chrome may indicate that it's being managed by a user's organization. This warning is provided by the Chrome Policies feature of the browser. To know if an instance of Chrome is managed by an organization, there will be an entry at the bottom of the browser’s hamburger menu (three dot menu), on the right side of the browser window that reads, "Managed by your organization." This is likely due to an entry in the Chrome Policies listing, which can be found by loading this page in the browser: chrome://policy The policies listed in this section are stored in the computer's file system in one of the following locations as JSON files. /usr/share/chromium/policies/managed /usr/share/chromium/policies/recommended Remove the offending JSON files, and click the Reload policies button. The Managed by your organization entry in the browser menu should be gone. A notice like this on instances of Chrome for work, school, library, or other devices that belong to an organizati...
Post a Comment
Read more

Allow Windows authentication using SQL Server driver with DBeaver

DBeaver will allow Microsoft Windows single sign on access when connecting to Microsoft SQL Server using the SQL Server driver (rather than jTDS ).  From the driver properties settings, set the integratedSecurity flag to true . Open the Connection configuration panel and choose the Driver properties section. Set the integratedSecurity flag to true . A subtle, but important step is to not provide username and password credentials to the connection.
7 comments
Read more

Connecting to SQL Server with jTDS using Windows Authentication

UPDATE:   At one point the tip in this article to set the USENTLV2 flag to true was accurate, but it appears it is no longer necessary, at least as far as DBeaver 's use of the driver is concerned.  If it solves an authentication problem, then great.  The expectation is that, an update in one of the packages that make this sort of connection possible has resolved the issue that at one time made this flag necessary. Connecting to Microsoft SQL Server using jTDS with a username and password that's managed by the database manager is pretty straightforward.  It may become a little more problematic however, when trying to use Windows authentication when connecting from a Windows machine. Do not supply a username and password. Set the USENTLMV2 property to true. NOTE:   Step 1 assumes a connection being made from a Windows machine.  If the connection is being made from something else, user credentials may actually be necessary. If the connect...
7 comments
Read more