Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Subscriptions: Add import option for subscribe by email #535

Closed
manovotny opened this issue May 13, 2014 · 32 comments

Comments

@manovotny
Copy link

commented May 13, 2014

It's no secret that Google is ending support for some of its services. Some more publicly than others. One of the more recent, silent casualties seems to be FeedBurner's subscribe by email feature.

Some of my clients (and others around the internet) have reported that FeedBurner has stopped sending out emails to readers who have signed up to receive posts by email.

While MailChimp is a viable alternative, I would love to stick with the WordPress ecosystem, as it's the least likely to change on itself, and use Jetpack's subscribe by email option.

Sadly, from everything I read, it appears that the ability to import subscribers was intentionally left out of Jetpack.

Would you kindly reconsider adding this feature as I am sure many a trying to flee from FeedBurner and / or Google ending some critical services.

Thanks for the consideration.

And if I am overlooking an import option, please let me know. I'd be happy to be mistaken. :)

@jeherve

This comment has been minimized.

Copy link
Member

commented May 13, 2014

if I am overlooking an import option, please let me know.

You're correct. Jetpack doesn't allow you to import subscribers from a third-party service at the moment. That's something we need to look into, but before we add this option we'll need to make sure that spammers can't abuse the system.

Nobody wants to see spammers start using Jetpack Subscriptions to send spam; it would be bad for the people being spammed, obviously, but it would also have an impact on the overall efficiency of Jetpack Subscriptions, as some email providers might choose to filter out all WordPress.com notification emails if spammers started to use it.

That doesn't mean we're not considering it, though. We'll keep you posted here once we make progress with this!

@manovotny

This comment has been minimized.

Copy link
Author

commented May 13, 2014

@jeherve : :

Totally not asking for a hasty rush job here.

I saw the same concerns you listed above on the Jetpack blog post on viewing current subscribers.

I am all for doing things the right way, even if that means it takes a bit longer, so there is no argument there.

I am more than happy that you're at least giving it consideration. Thanks for the reply.

@jeherve jeherve added this to the vFuture milestone Aug 11, 2014

@bradonpurpose

This comment has been minimized.

Copy link

commented Jan 31, 2015

Just want to put my vote in for a way to import emails from older services. I'd like to use only Jetpack for my blogs and get away from the cumbersome Subscribe2 plugin. In the meantime, I appreciate the workaround to create a Subscribe page and have subscribers resubscribe.
BRAD

@samhotchkiss

This comment has been minimized.

Copy link
Contributor

commented Feb 2, 2015

I would love to hear some ideas from folks on how to import lists without opening JP up as a platform for spammers to spam for free.

@bradonpurpose

This comment has been minimized.

Copy link

commented Feb 15, 2015

I'm hardly a web guru on such subjects but seems like you could use the same kind of Captcha options to prevent most spammers. Truthfully, I don't understand how JP works enough to know how spammers would take advantage of it. If someone with JP could start by explaining that, maybe we could collectively come up with some ideas.

@samhotchkiss

This comment has been minimized.

Copy link
Contributor

commented Feb 25, 2015

Hey @bradonpurpose,

The issue would be that someone could take a list of, say, 100,000 email addresses that they obtained in a non-kosher way (say, they bought a list of stolen email addresses, or they collected them in some way not approved by CAN-SPAM), then send spam/marketing emails to them using the WordPress.com servers. This would both put us in a questionable position legally and make the WordPress.com mail servers more likely to have emails sent out by our legitimate users land in spam boxes.

Does that help clarify the issue?

@jeherve

This comment has been minimized.

Copy link
Member

commented May 8, 2015

@chaselivingston

This comment has been minimized.

Copy link
Contributor

commented Jul 14, 2015

Suggested in 2260855-t

@samhotchkiss samhotchkiss modified the milestones: vFuture, Needs Triage Aug 29, 2015

@dereksmart

This comment has been minimized.

Copy link
Member

commented Aug 29, 2015

@samhotchkiss's has a good point. not something that we will be supporting at this time.

@dereksmart dereksmart closed this Aug 29, 2015

@mackaaij

This comment has been minimized.

Copy link

commented Aug 29, 2015

Hmm maybe you could think about this again. I expect Google to switch of Feedburner as well and then people come looking for a solution. Maybe you could offer an automatic link between Feedburner and WordPress for addresses that went through double opt-in? Or limit the number of addresses one can import like Aweber does? Or offer to send all subscribers a link to reconfirm?

@kraftbj

This comment has been minimized.

Copy link
Contributor

commented Sep 2, 2015

If Google kills Feedburner completely and offers an API to export subscribers, that's something on the table. Generic e-mail importing, though, is something we're not going to support at this time.

@mackaaij

This comment has been minimized.

Copy link

commented Sep 2, 2015

Early switchers at disadvantage :) Let's see how long it will take Google to switch off Feedburner indeed.

@jeherve

This comment has been minimized.

@RCowles

This comment has been minimized.

Copy link
Member

commented Nov 4, 2015

Requested in 2405993-t

@jeherve

This comment has been minimized.

@jeherve

This comment has been minimized.

@jeherve jeherve modified the milestone: Needs Triage Feb 15, 2016

@jeherve

This comment has been minimized.

@jeherve

This comment has been minimized.

@jeherve

This comment has been minimized.

@jeherve

This comment has been minimized.

Copy link
Member

commented Sep 2, 2016

@jeherve

This comment has been minimized.

Copy link
Member

commented Nov 23, 2016

@jeherve

This comment has been minimized.

Copy link
Member

commented Jan 27, 2017

@jeherve

This comment has been minimized.

Copy link
Member

commented Mar 28, 2017

@jeherve

This comment has been minimized.

@seejacobscott

This comment has been minimized.

Copy link

commented Jun 14, 2017

requested here: 3265145

@csonnek

This comment has been minimized.

Copy link
Member

commented Jul 13, 2017

requested in 3321124-t

@Automattic Automattic deleted a comment from yustinnovita Sep 22, 2017

@gracie

This comment has been minimized.

Copy link

commented Oct 25, 2017

Requested in 754301-zd

@jeherve

This comment has been minimized.

Copy link
Member

commented Nov 6, 2017

Also in 775475-zen

@StefMattana

This comment has been minimized.

Copy link

commented Jan 10, 2018

Also suggested in 886106-zen

@jeherve

This comment has been minimized.

Copy link
Member

commented Feb 9, 2018

Also in 948160-zen

@StefMattana

This comment has been minimized.

Copy link

commented Jun 5, 2018

Related and suggested something very similar in https://wordpress.org/support/topic/jetpack-blog-subscription-2/

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.