Forum Replies Created

Viewing 5 replies - 1 through 5 (of 5 total)
  • Bleh, I thought I responded to this.

    I think I got it to stop by filling in the notification field.
    I had previously had it unchecked and not filled in.

    Up until that point it was still throwing errors about 2 weeks ago, yea.

    We’re running PHP 5.4. Is there a setting optimization that’d help?

    I’m assuming that’s in your error log?

    We have a release going out this week that I think should fix it, but if not we can gather some more info and trace it down.

    Yessir.
    I took a quick look over at GitHub to see if you had pushed any changes, but it looked like the previous fix was the newest; and I didn’t see a beta branch or the like to comb through.

    So I figured I’d post.
    Thanks for the update. 🙂

    Thread Starter codeGlaze

    (@codeglaze)

    Resolved! (Only took 13 hours >.>)

    Okay so! For people looking to properly authenticate their website generated emails … here is some help.

    1. Use mail-tester.com !

    * You are given a randomly generated email address to send your test emails to. You can use that same address repeatedly. There’s a refresh option at the top of the ‘results’ page. Use it each time you send a new test email to that address.

    2. Enable/setup SPF for your emails.

    * mail-tester.com has a ton of guides customized to many hosts.

    3. Sign your email with DKIM

    • Install Amazon SES DKIM Mailer
      (Thank you Roger MacRae, you are a godsend)
    • Generate a DKIM key set (socketlabs)
    • -> ‘Domain’ is the domain for your emails… what ever comes after the @ in your email.

      So me@example.com would be example.com
      BUT me@my.example.com would be my.example.com.
      No need for www. or http://

      -> ‘Selector’ can seriously be anything. Just keep it short.
      [ Instructions from the WP Plugin ]

    • Copy your Private Key
      ( Including —–BEGIN RSA PRIVATE KEY—– and —–END RSA PRIVATE KEY—– )
    • Paste your Private Key into a file named .htkeyprivate
    • Upload .htkeyprivate to the ROOT level of your server. (The very top level, outside of the ‘www’ folder.)
    • Set permissions to 400 or 440
    • Add your public domainkey to your DNS Records (MX Entry / DNS Zone Editor / etc)
      [Here’s a guide]
    • -> Select the domain you will be adding the DNS entries to.
      -> You will be adding (or editing) two new TXT records.
      -> First record:

    • HOST = _domainkey
    • TTL = 14400
    • Type = TXT
    • Points to = t=y;o=~;

    -> Save
    -> Second record:
    (this is where your need your ‘selector’ from about and your PUBLIC key)

    • HOST = <your selector here>_domainkey
    • TTL = 14400
    • Type = TXT
    • Points to = <your PUBLIC KEY here>

    -> Save

    The value t=y advises that the domain is still in testing mode. Once all is set up and working, you’ll want to remove that.

    o=~ specifies that some of the mail from your domain is signed, but not all. You should specify o=- if all of the mail coming from your domain will be signed.

    4. If you are on any blacklists, start the process of trying to remove yourself from them.

    [05-Jan-2014 19:50:21 UTC] PHP Warning:  Missing argument 2 for SendPress_Notifications_Manager::send_notification(), called in /wp-content/plugins/sendpress/classes/class-sendpress-notifications-manager.php on line 43 and defined in /wp-content/plugins/sendpress/classes/class-sendpress-notifications-manager.php on line 172
    
    [05-Jan-2014 19:50:21 UTC] PHP Warning:  Invalid argument supplied for foreach() in /wp-content/plugins/sendpress/classes/class-sendpress-notifications-manager.php on line 188

    This is being thrown about once a day for us. Any insight as to why (Or what I can do)?

    Running 0.9.7.1

Viewing 5 replies - 1 through 5 (of 5 total)