Support » Plugin: Post Notif » required email address

  • Resolved Heimhenge

    (@heimhenge)


    Hiya Devon,

    Still using your plug-in, despite the fact that I need to manually activate the post notification instead of having a cron job send it. Hoping you include that functionality in a future update.

    My question: Your plugin documentation says that in order to send post notifications I must have an email address associated with my domain. Understood. That’s the way it’s been working for some time now.

    But here’s what happened … my Sky Lights WP blog had been a sub-domain of my business website heimhenge.com. Specifically, it was http://heimhenge.com/skylights/

    I recently migrated that blog to its own domain: sky-lights.org (not yet active). GoDaddy wants to charge me $50/year to set up email for that domain.

    Will my previous email address (skylights@heimhenge.com) which is still active be valid as an email address for Post Notif?

Viewing 9 replies - 1 through 9 (of 9 total)
  • Plugin Author Devon Ostendorf

    (@devonostendorf)

    Hi Dan,

    First of all, let me say that I do appreciate your considerable patience as it relates to the long-anticipated next version, where post notification scheduling will actually behave logically. Speaking of which, I will be working, in earnest, on it this weekend and will send you an email with more details and a request.

    As to your question about whether your heimhenge.com email address will work with Post Notif when sending from sky-lights.org, I suspect it will not or, if it does, your successful delivery rate will be low. I say this, as an admitted email ignoramus, because I believe that 1) email servers generally prefer to send emails from accounts already configured to send email from the current domain and 2) email servers generally prefer to receive email from addresses with domain suffixes matching the domain of the sending server. Now, I know that people have had success using Post Notif with Gmail and other webmail addresses as their sending address (and they are obviously not hosting their blogs at gmail.com) so I’m not sure precisely what would happen if you try to use your heimhenge.com email address from sky-lights.org; I’d suggest you do try just to see what happens! You can certainly use me as a test recipient if that would be helpful.

    Having said all of that, though, I can’t believe GoDaddy actually wants to charge you $50/year for the privilege of sending and receiving email; I have had some truly low-budget hosting over the years and they have never charged me anything for email, so I wonder what you get for that?

    Thanks,
    Devon

    Hiya Devon,

    Appreciate your continued work toward getting a cron job integrated with Post Notif. Looking forward to not needing that manual send every Monday morning.

    GoDaddy (like all hosts) has their pro’s and cons’ … the biggest thing for me is their excellent tech support, all stateside, easy escalation when you need it. And their wait time is low by industry standards. But it looks like I won’t be needing their email service for my new site.

    I suspected my original email might work since my new site used to be a subdomain of my business site. I tried sending myself a test email and received it no problem, so tonite I’ll be doing a mass-send and see what happens. I’ll poll some of my subscribers and let you know in a few days.

    Dan

    Plugin Author Devon Ostendorf

    (@devonostendorf)

    Hi Dan,

    Glad to hear that it sounds like your (potential) email “issue” was not a problem after all!

    Thanks,
    Devon

    OK, the email experiment has been run. I used an email address from my heimhenge.com domain as the “email sender email address” on the Post Notif Settings page in my new sky-lights.org domain. Did a mass Post Notif to my subscribers on Monday. Half of my beta group failed to receive the notification. And they did check their spam folders.

    So then I changed the email address to the one I got with sky-lights.org and sent a second mass test notification. They all received it just fine.

    So it looks like I’ll have to pay for that second email address to get my notifications to work. No complaints about Post Notif … just about the way email servers work. You’d think this would be easier.

    Thanks for the feedback Devon. -Dan

    Plugin Author Devon Ostendorf

    (@devonostendorf)

    Hi Dan,

    It looks like I spoke too soon. Sorry to hear your experiment turned out similarly to how I (originally) feared it might. As I’ve said many times prior, email delivery overall is a black hole of misery and I am foolish for even getting involved tangentially via this plugin. But such is life, right?!

    At least we’ll get your scheduled delivery stuff worked out here before too long..

    Thanks,
    Devon

    Plugin Author Devon Ostendorf

    (@devonostendorf)

    Hi Dan,

    I released Post Notif 1.1.3 this morning, which should get you off the beta version of the plugin once you have a chance to apply the update.

    Thank you for all the time you devoted to testing the various iterations of the new functionality; your feedback was exceptionally helpful and I sincerely appreciate it!

    Thanks,
    Devon

    Awesome plugin dude. Thanks for your hard work. Will update after tonite’s post and let you know how it goes. Expecting no issues.

    Happy to report that v1.1.3 is running smoothly. Auto/manual send options are intuitive and prevent the mass emailing that got me blacklisted. Tried both previously published and drafts for future posts … it’s all clear and rock solid. Thanks. Another cup of coffee has been sent your way.

    Plugin Author Devon Ostendorf

    (@devonostendorf)

    Thanks, Dan; glad to hear all is well (and the coffee was delicious!).

Viewing 9 replies - 1 through 9 (of 9 total)
  • The topic ‘required email address’ is closed to new replies.